Teamcenter Dimensional Planning and Validation Administration Guide. Publication Number PLM00151 H

Transcription

1 Teamcenter 10.1 Dimensional Planning and Validation Administration Guide Publication Number PLM00151 H

2 Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc Siemens Product Lifecycle Management Software Inc. All Rights Reserved. Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks, or service marks belong to their respective holders. 2 Dimensional Planning and Validation Administration Guide PLM00151 H

3 Contents Proprietary and restricted rights notice About the Dimensional Planning and Validation solution What is the Dimensional Planning and Validation solution? Components Flow of data Tasks that you perform Defining quality inspection process About defining an inspection quality process Basic elements of defining quality data Understanding a bill of resource Understanding a process structure (bill of process) Relationship between a bill of resource and a plant process structure Understanding plant process structures Example of a process structure with an associated product Overview of what is attached to an inspection device and measurement routine Managing the inspection definition Defining measurement data collection Defining engineering data Exporting to the DPV Device Client Administering measurement database Administering the measurement database Set the selection criteria Archive the data Purge the data Restore data Using DPV measurements Getting started Configure DPV Measurements View measurement data events Change the activation state of measurement data events Glossary A-1 Index Index-1 PLM00151 H Dimensional Planning and Validation Administration Guide 3

4

5 Chapter 1 About the Dimensional Planning and Validation solution What is the Dimensional Planning and Validation solution? Understanding the analysis of measurement data Components Flow of data Tasks that you perform PLM00151 H Dimensional Planning and Validation Administration Guide

6

7 Chapter 1 About the Dimensional Planning and Validation solution What is the Dimensional Planning and Validation solution? Siemens PLM Software provides Tecnomatix Dimensional Planning and Validation (DPV), a quality management solution you can easily integrate into your Teamcenter environment. DPV enables the extended enterprise to collect, manage, dimensionally analyze, and report on quality measurement information. It provides rapid access to design and manufacturing information that directly influences your enterprise s quality targets. DPV provides you with: Enterprise-wide visibility to quality information. An integrated definition of your measurement process coordinated with product design, manufacturing planning, and plant layout. In-depth analysis of captured measurement information. Associative reporting, with initial and updated reports. Historical and summary measurement reporting. DPV is a scalable solution with three configurations: Core Provides the foundation of DPV, which is the storage and analysis of measurement data. Site Provides DPV Core capabilities, plus provides the viewing and monitoring of measurement data through Web-based reports called ETL Health reports using the DPV ETL Web site. Enterprise Provides DPV Site capabilities, plus provides additional summarized historical reports, and enables the entire enterprise to identify, analyze, and share measurement data using Teamcenter community collaboration. Components PLM00151 H Dimensional Planning and Validation Administration Guide 1-1

8 Chapter 1 About the Dimensional Planning and Validation solution Understanding the analysis of measurement data Once inspection devices (such as, vision, coordinate measurement machine (CMM), and handheld) measure the manufacturing process, they place the data in pre-defined folders (). DPV Device Client moves the data from these locations to the Teamcenter database for storage, management, and global access. This is a triggered event that takes place when new data files are available. DPV Device Client loads data into the database in real time. The tasks include: Validating data and sending alarms if errors are found. Checking for duplicate data. Here is an illustration of the flow of data through DPV Device Client: Components The Dimensional Planning and Validation solution is comprised of the following key components: 1-2 Dimensional Planning and Validation Administration Guide PLM00151 H

9 About the Dimensional Planning and Validation solution Core At the shop floor level, physical inspection devices capture and store real-time metrics. Typically, these inspection devices include laser gap analysis, coordinate measuring machines (CMM), optical and digital measurement devices, hand-held devices, and any number of physical inspection systems. Tecnomatix DPV Device Client for real-time data loading, storing, and monitoring of quality data obtained from the inspection devices. Teamcenter for database definition and management. The Visualization Illustration and Reporting & Analysis in the Teamcenter lifecycle visualization suite for root-cause analysis and reporting. Site The Site configuration provides the added dimensions of: Microsoft SQL Server reporting services (SSRS). Siemens PLM Software Visualization Automation Server for graphical reporting. Enterprise The Enterprise configuration provides the added dimensions of: DPV Microsoft SQL Analysis Server (DPV-SSAS) for historical reporting. PLM00151 H Dimensional Planning and Validation Administration Guide 1-3

10 Chapter 1 About the Dimensional Planning and Validation solution Teamcenter community collaboration for report publishing and collaboration across your enterprise. Flow of data The component, DPV Device Client, collects measurement data from inspection devices (such as, vision systems, coordinate measurement machines (CMM), and handheld devices) on the shop floor. The data can be in ASCII or Document Markup Language (DML). DPV Device Client translates the data into a standard data loading format and stores the data in its database for analysis and backup. It then sends the collected data to the Teamcenter database for storage. Teamcenter makes the measurement data available to you through Teamcenter community collaboration so you can create and view reports of the data to get an overall perspective of the data. You can schedule reports and set triggers for their creation. You then use DPV Reporting & Analysis to visualize and analyze the data to help identify and resolve issues. DPV Reporting & Analysis provides you with a wide range of reports and features to analyze the data, including charts, advanced filtering of data, and mathematical data transformations. In addition, you can export the data for analysis in Variation Analysis. Tasks that you perform Administrators and general end-users perform tasks in the Dimensional Planning and Validation solution: Administrators manage the collection of data. 1-4 Dimensional Planning and Validation Administration Guide PLM00151 H

11 About the Dimensional Planning and Validation solution End-users use the data collected. Each task may be performed in a different product or interface. This documentation shows how to perform the administrative tasks performed in Teamcenter. For information about performing tasks in other products, see the DPV documentation collection installed with DPV. Administrative tasks To perform this task Define the measurement data to be collected Configure how data is collected from plant inspection devices and stored in the DPV Device Client history database Monitor the flow of measurement data Administer the system, including: Archiving, purging, and restoring measurement data Managing historical reporting Managing the reporting services of Visualization Automation Server Use this product Teamcenter rich client DPV Device Client Configuration Editor DPV ETL Dashboard Web Part Teamcenter community collaboration or DPV ETL Web site DPV Error Viewer DPV Measurements Manufacturing Process Planner thin client DPV-SSAS Cube Manager Vis Automation Server Manager Learn about the product here Defining an inspection quality process and the Defining an inspection quality process tutorial Configuring the collection of measurement data in the DPV documentation collection Monitoring measurement data Viewing Dimensional Planning and Validation status Using DPV Measurements Administering the measurement database Managing DPV-SSAS historical reporting Administering the Visualization Automation Server PLM00151 H Dimensional Planning and Validation Administration Guide 1-5

12 Chapter 1 About the Dimensional Planning and Validation solution To perform this task Define and manage reports: Define the navigation structure for viewing reports Define the historical summary reports to be generated Monitor and manage the generation of reports Use this product Microsoft SQL Server Reporting Services (SSRS) and Visualization Automation Server Microsoft Report Manager Microsoft Visual Studio (or other compatible report authoring application) DPV Hierarchy Editor Report Management Web Part in Teamcenter community collaboration Learn about the product here Administering reports for DPV Viewer Web Part End-user tasks To perform this task Create and view reports of the data Analyze the measurement data Use this product DPV Reporting & Analysis Visualization Illustration DPV Viewer Web Part in Teamcenter community collaboration DPV Reporting & Analysis Create report templates DPV Reporting & Analysis Learn about the product here Viewing reports using the DPV Viewer Web Part Authoring graphical reports Authoring graphical reports tutorial Using DPV Reporting & Analysis Authoring graphical reports Visualization Illustration DPV Viewer Web Part in Teamcenter community collaboration 1-6 Dimensional Planning and Validation Administration Guide PLM00151 H

13 Chapter 2 Defining quality inspection process About defining an inspection quality process Basic elements of defining quality data Understanding a bill of resource Understanding a process structure (bill of process) Relationship between a bill of resource and a plant process structure Understanding plant process structures Example of a process structure with an associated product Overview of what is attached to an inspection device and measurement routine Managing the inspection definition About managing the inspection definition Define an organizational structure Create a collaboration context object Creating templates About templates Creating an inspection device template About creating an inspection device template Create an inspection device Create forms associated with the inspection device Creating a measurement routine template About creating a measurement routine template Create a measurement routine Create forms associated with the measurement routine DPVExportToRegions Tips for managing forms Create a form View your forms in the Attachments view Edit your form View and work with all your forms List of forms used Defining measurement data collection PLM00151 H Dimensional Planning and Validation Administration Guide

14 About defining measurement data collection Defining bill of resource About defining a bill of resource Create a plant structure Define an inspection device from a template Defining parsing scripts About defining parsing scripts Working with common code scripts About common code scripts Routines in the common code script Adding error messages to a common code script Extending the common script Debugging parsing scripts Export a common parsing script to DPV Device Clients Working with script parameters About script parameters Examples of using parsing script parameters Define script parameters Attach custom scripts to inspection devices Standard parsing scripts Duplicate data Specifying the transfer of information About specifying the transfer of information Set the transfer of information Set the end-of-routine flag Working with DML data About working with measurement data in DML format Example of measurement data in DML format Feature types supported in DML Use script parameters to extract data from the DML file Using forms to define item and phase name Custom feature attributes in DML format Defining engineering data About defining engineering data Defining a plant process structure About defining a plant process structure Create a process structure (bill of process) Specify the location of the plant Alternative abbreviations Define the shift times Define error notification during data loading Add plants to the Teamcenter measurement database Defining a measurement routine About defining a measurement routine Create a measurement routine from a template Define error notification during data loading Define export to regions Adding feature data About adding feature data Feature validation Defining feature data in an Excel Engineering workbook Defining feature data in an.xml file Managing feature data files Dimensional Planning and Validation Administration Guide PLM00151 H

15 Feature item types Defining if a feature or feature attribute is needed Defining split events Standard attribute codes Generating engineering data from measurement data Defining custom feature attributes Defining custom feature attributes About adding custom feature attributes and rules Add the custom feature attribute to the routine definition (Optional) Add the feature attributes to the list of values in Business Modeler IDE (Optional) Creating rules to extract feature attribute names Set the default attribute (DFLT) handling Defining cluster groups About working with clusters and cluster groups Revisions and cluster groups Create a cluster group View cluster groups associated with a routine Compare cluster group revisions Define datum transformations Revisions and datum transformations Example of a DPVDatumXForm.xml file Table of XML elements for datum transformations Define triggers Define feature mapping Associate a product, plant, and bill of process Approving measurement routines Releasing and revising measurement routines Create a new revision of a routine Exporting to the DPV Device Client About exporting to the DPV Device Client Export the measurement routine to the DPV Device Client Export the inspection device to the DPV Device Client Export the plant to the DPV Device Client Managing AI objects created during export Setting access to remove AI objects Check for exported objects and ignore the date-time filter PLM00151 H Dimensional Planning and Validation Administration Guide

16

17 Chapter 2 Defining quality inspection process About defining an inspection quality process Managing what should be measured on a product, referred to as engineering data, and managing the collected measurement data consists of: Basic elements of defining quality data. Managing the inspection definition. Defining measurement data collection. Defining engineering data. Exporting the DPV Device Client. Basic elements of defining quality data Two basic Teamcenter elements define the quality data. They are designed in Manufacturing Process Planner. A bill of resource to store information about the inspection devices, remote transfer agents, and scripts that measure and manage the measurement data. A bill of process that defines the engineering data. A bill of process is a hierarchical structure that represents the measurement or inspection process within a given plant. The structure defines the locations where the measurement routines are executed throughout the plant. The MEPrPlantProcess process is its root. A measurement routine defines the actual elements that are measured. These elements are grouped together as a single operation (the routine) within the process. PLM00151 H Dimensional Planning and Validation Administration Guide 2-1

18 Chapter 2 Defining quality inspection process Understanding a bill of resource You store information about the inspection devices, remote transfer agents, and parsing scripts in a bill of resource in Teamcenter. The bill of resource lets you see the actual resources that are used to measure a routine. Each device in the bill of resource refers to an actual inspection device. In the figure, they are labeled CMM1, CMM2, and Vision 1. Each device has a translator and a path to the directory where the device stores the measurement results. 2-2 Dimensional Planning and Validation Administration Guide PLM00151 H

19 Defining quality inspection process The top level of the bill of resource is a plant of the type of MEPrPlant. You can then have stations below it of the type MEPrStation. Inspection devices are modeled using items of the type InspectionDevice. Relationship between a bill of resource and a product structure Understanding a process structure (bill of process) When defining engineering data, you create a process structure (bill of process) using Manufacturing Process Planner. The bill of process contains the measurement routines and products. The measurement routines are operations within the plant. Each routine has a set of features to be measured and associated data, such as nominal coordinates, vectors, and tolerances. The following example shows a bill of process with a measurement routine, Meas Rout 100, which has the products P1 and P2 assigned to it. Before you can begin, you must have defined the product and plant process. PLM00151 H Dimensional Planning and Validation Administration Guide 2-3

20 Chapter 2 Defining quality inspection process This help does not cover creating a product. You should follow the instructions in the Manufacturing Process Planner Guide to create them. Relationship between a bill of resource and a plant process structure The bill of resource defines the items on the plant floor, while the plant process structure (bill of process) defines what is happening on the plant floor. You associate the bill of resource to the plant process structure using the Manufacturing Process Planner allocation methodology. You assign measurement resources from the plant to the process. The same resource occurrence can be assigned to multiple processes. The MEPrPlantProcess in the bill of process must have the same name as the MEPrPlant in the bill of resource. The inspection device must have a parent item (MEWorkareas). The following shows two related bill of resource and bill of process. 2-4 Dimensional Planning and Validation Administration Guide PLM00151 H

21 Defining quality inspection process Understanding plant process structures Create a complete process structure (bill of process) before you can define a measurement routine. The top level of the process structure is a plant with a type of MEPrPlantProcess. Optionally, it can have a structure underneath it of: Assembly line o Zone within the assembly line Station within the zone Here is an example with plants and zones: PLM00151 H Dimensional Planning and Validation Administration Guide 2-5

22 Chapter 2 Defining quality inspection process Users use the plant information you define here to query for the appropriate measurement data in Teamcenter lifecycle visualization. After creating the plant process, attach forms to specify its location, shift start times, and how frequently you are notified of errors. For detailed instructions on creating a process structure and form, see the Manufacturing Process Planner Guide. Example of a process structure with an associated product The following is an example of a process structure with a measurement routine, Meas Rout 100, which has the products P1 and P2 assigned to it. 2-6 Dimensional Planning and Validation Administration Guide PLM00151 H

23 Defining quality inspection process Overview of what is attached to an inspection device and measurement routine Inspection device The following elements are attached to an inspection device to define it: Parsing scripts that translate the measurement data from the device. Forms, such as those specifying parsing script parameters and the location of the remote transfer agents. Standard View folder and revision master forms. The following is an example of data attached to an inspection device. Measurement routine The following elements are attached to a measurement routine to define it: Forms, such as those defining the error notification. Feature data. The following is an example of data attached to an inspection device. Managing the inspection definition About managing the inspection definition Many objects make up the definition of the inspection process, including: Bill of resource. PLM00151 H Dimensional Planning and Validation Administration Guide 2-7

24 Chapter 2 Defining quality inspection process Inspection devices. Process structure (bill of process). To help you manage these objects: Define an organizational structure in My Teamcenter in which to store the objects. Create a collaboration context object to store the inspection objects and then use it to load all objects into Manufacturing Process Planner at the same time. Create templates from which users can quickly create new routines and inspection devices. Templates are generic placeholders. Users create the actual occurrences of these objects from the templates. See tips for managing forms. Define an organizational structure Before creating the bill of resource and process structure (bill of process), create folders in which to store the devices, remote transfer agents, and scripts you create. This is for organizational purposes only and, is, therefore, optional. 1. In My Teamcenter, create a new folder (File New Folder) and name it for your project. 2. Create subfolders within the new folder for storing objects. For example, create BOR, BOP, Devices, and Context. Create a collaboration context object After you have created and associated all the inspection definition objects, create a collaboration context object to hold the collection. You can then send the entire collaboration context object to the Manufacturing Process Planner. 1. In Manufacturing Process Planner, select the product associated with the inspection definition, and choose File Save As New Collaboration Context. 2. Enter a name and optional description for the object. 3. Click Save. You receive a message that the collaboration context object has been saved to your Newstuff folder in My Teamcenter. 4. Click OK. The collaboration context object appears in your Newstuff folder in My Teamcenter. 5. Copy the collaboration context object to the Context subfolder you created in your project folder. To send the collaboration context object to Manufacturing Process Planner, right-click it and choose Send to Manufacturing Process Planner. 2-8 Dimensional Planning and Validation Administration Guide PLM00151 H

25 Defining quality inspection process Creating templates About templates Administrators create templates from which users can quickly create new routines and inspection devices. Templates are generic placeholders. Users create the actual occurrences of these objects from the templates. Tip To check the templates, associate them with a routine and send the device or routine to DPV Device Client. Templates are helpful for users creating multiple routines. You do not need to create them, however, if you are only creating a single routine. You can simple follow the instructions to create an inspection device or measurement routine and not create a template from it. Creating templates involves: Creating an inspection device template. Creating a measurement routine template. Creating an inspection device template About creating an inspection device template An inspection device represents an actual inspection device on the factory floor monitoring the manufacturing process. Creating a template for an inspection device consists of: Creating an inspection device. Creating the forms that define the inspection device, such as specifying parsing script parameters and the location of the remote transfer agents. Create an inspection device 1. In My Teamcenter, choose File New Item. 2. From the list, select InspectionDevice. 3. Click Next. 4. Click Assign to fill in the Item ID and Revision ID boxes. 5. Type in a name for the template, such as Inspection device template. 6. (Optional) Enter a description to help a user identify the template. 7. Click Finish. 8. Click Close. PLM00151 H Dimensional Planning and Validation Administration Guide 2-9

26 Chapter 2 Defining quality inspection process Create forms associated with the inspection device 1. In My Teamcenter, select the inspection device revision. Click the plus sign (+) next to the inspection device to view the revision. 2. Create the following forms selecting Apply between each creation so you can continue making them: DPVDeviceLocation DPVMeasmtDeviceDef DPVMeasmtParseParam 3. Click OK. 4. Check out and edit each form to enter any default information in the fields to assist the user in defining an inspection device. Click a form name listed in step 2 to learn about its fields. Creating a measurement routine template About creating a measurement routine template Create a measurement routine template for each type of inspection device. Creating a template consists of: Create a measurement routine. Create the forms that define the measurement routine, such as specify error notification. Create a measurement routine 1. In Manufacturing Process Planner, click Create New Operation. You can also choose File New Operation. 2. In the New Operation dialog box, from the Operation Type list, select one of the following: If the inspection device being used is a Vision station Coordinate measuring machine (CMM) Handheld measurement device Any type of device Select this operation type MEVisInspection MECMMInspection MEHHInspection MEInspection There can be other user-defined types of MEInspection for other types of inspection devices Dimensional Planning and Validation Administration Guide PLM00151 H

27 Defining quality inspection process 3. Click Next. 4. Click Assign to fill in the Operation ID and Revision ID boxes. 5. Type in a name for the template, such as Measurement routine template. 6. (Optional) Enter a description to help a user identify the template. Create forms associated with the measurement routine 1. In Manufacturing Process Planner, right-click the measurement routine template and choose Open with Attachments as shown. The Attachment view appears beside the measurement routine, as shown. 2. In the Attachments view, select the measurement routine (the top line). You must select the root process (top line) in the data pane to create a form. 3. Create the following forms, as necessary, selecting Apply between each creation so you can continue making them: DPVErrorNotification DPVExportToRegions DPVMeasmtContext DPVRoutineInfo DPVTriggerConfig 4. Click OK. PLM00151 H Dimensional Planning and Validation Administration Guide 2-11

28 Chapter 2 Defining quality inspection process 5. Check out and edit each form to enter any default information in the fields to assist the user in defining a measurement routine. Click a form name listed in step 3 to learn about its fields. DPVExportToRegions Type the region number and any customer-defined values. Tip Type 1 for Region 1, 2 for Region 2, and so on. The number must be unique. Tips for managing forms Create a form For detailed instructions, see the Manufacturing Process Planner Guide. 1. Choose File New Form. 2. In the New Form dialog box, click the form type you want to attach. 3. Assign a name and description to the object. 4. Select the Open on Create check box to edit the form options. 5. Click OK. View your forms in the Attachments view The Attachments view allows you to see the forms attached to an item revision, view and edit the forms, add new forms, and remove forms from an item revision. This view is available from nearly every Teamcenter rich client application, including My Teamcenter, Manufacturing Process Planner, and Part Planner. 1. In a rich client application, such as Manufacturing Process Planner, right-click the revision of the item, for example a routine, and choose Open with Attachments as shown. The Attachments view appears beside the measurement routine Dimensional Planning and Validation Administration Guide PLM00151 H

29 Defining quality inspection process 2. (Optional) Drag the Attachments view to the left to display it in the entire width of the Teamcenter interface. Edit your form 1. View your forms in the Attachments view. 2. In the Attachments view, double-click a form. The form appears, as shown for the DPVErrorNotification form. 3. Click Check-Out and Edit. 4. In the Check-out dialog box, click Yes. The buttons along the bottom of the form change. PLM00151 H Dimensional Planning and Validation Administration Guide 2-13

30 Chapter 2 Defining quality inspection process 5. Edit the form and when you are finished, click Save and Check-In. 6. In the Check-In dialog box, click Yes. View and work with all your forms You can open all your forms in separate Viewers to compare them or to work with them at the same time. 1. View your forms in the Attachments view. 2. In the Attachments view, right-click a form, and choose Open with Viewer, as shown. A Viewer appears on the right containing the form Dimensional Planning and Validation Administration Guide PLM00151 H

31 Defining quality inspection process 3. Freeze the Viewer so it only shows the content for this form even if you select another by clicking the Disable response to selections tool. 4. Continue creating Viewers for each form and freezing the content. The result is a collection of Viewer tabs in the right pane, similar to shown. 5. Click between Viewers to edit each form or drag the Viewers so they are stacked horizontally and you can view all the forms at once, as shown. PLM00151 H Dimensional Planning and Validation Administration Guide 2-15

32 Chapter 2 Defining quality inspection process List of forms used The following tables list all the forms used to define components. Use them to make sure that you have created or edited all the necessary forms. Forms for bill of process The form The default form of the object DPVLocation DPVShiftTime DPVErrorNotification DPVExportToRegions DPVMeasmtContext DPVRoutineInfo DPVTriggerConfig Is attached to Plant Routine Forms for bill of resource 2-16 Dimensional Planning and Validation Administration Guide PLM00151 H

33 Defining quality inspection process The form DPVDeviceLocation Is attached to Inspection device (copy in context) DPVMeasmtDeviceDef DPVMeasmtContext DPVMeasmtParseParam Defining measurement data collection About defining measurement data collection Defining how measurement data is collected consists of the following: Defining a bill of resource. Specifying the transfer of information. Defining scripts. Working with measurement data in DML format. Defining bill of resource About defining a bill of resource Working with a bill of resource involves: Creating a plant structure. Defining an inspection device from a template. For an introduction to defining a bill of resource, see the Dimensional Planning and Validation tutorial. Create a plant structure 1. In Manufacturing Process Planner, choose File New Workarea. 2. Choose MEPrPlant. 3. Click Next. 4. Click Assign to automatically fill in the ID and Revision boxes. 5. Type in a name for the new plant. PLM00151 H Dimensional Planning and Validation Administration Guide 2-17

34 Chapter 2 Defining quality inspection process To facilitate measurement data loading, the plant name specified in the bill of resource must match the plant name in the measurement files. 6. Click Finish. The plant name cannot exceed 30 characters or the Application Interface (AI) objects exported for that plant will not be downloaded to DPV Device Client. The Plant tab appears, as shown. 7. Select the top level in the structure (MEPrPlant) and repeat the workarea creation process to create the line (MEPrLine) and the station (MEPrStation). 8. (Optional) In My Teamcenter, verify that the bill of resource has been created, and copy and paste the bill of resource from the Newstuff folder into a designated project folder. Copy and paste the plant level item into the project folder; the structure beneath it comes along. Define an inspection device from a template Each device instance corresponds to an actual inspection device in a plant. When you create the inspection device from a template, Teamcenter creates all the necessary forms you need to define the device. You will edit the forms. If you do not have a template, create the inspection device as instructed in Create inspection device and do not call it a template. Then, create all the necessary forms listed in Create forms associated with the inspection device. 1. In Manufacturing Process Planner, choose File New From Template Item from Template. 2. Click the Choose Template tab, type the name of the template in the Template ID box, and select Use Template. Alternatively, you can search or browse for the template you require Dimensional Planning and Validation Administration Guide PLM00151 H

35 Defining quality inspection process Tip Click Add to Favorites to save the template to a favorites palette so it can be quickly accessed and used. To search for a template: a. Click the Choose Template tab. b. Next to the Template ID box, click Find the Template by Name. c. In the Find Template by Name dialog box, type the search criteria including wildcards, such as *template*. d. Click Find. The templates that match the criteria appear in the dialog box. e. Select the desired template. 3. Click the Configuration tab and choose the cloning rule Cloning. If required, you can also change the revision rule on this tab. 4. Change the name of the device (for example, Perceptron, PCDMIS, or Zeiss). All other values (ID, revision, type, description) are automatically set for you. 5. Click OK. A new tab appears listing the inspection device. 6. Copy the inspection device to your bill of resource: a. Select the inspection device, and choose Edit Copy. PLM00151 H Dimensional Planning and Validation Administration Guide 2-19

36 Chapter 2 Defining quality inspection process b. Select the bill of resource tab and select the location for the inspection device. c. Choose Edit Paste. 7. Right-click the inspection device and choose Open with Attachments. 8. In the Attachments view, view the forms created for the inspection device, similar to the figure shown. 9. Check out and edit the forms following the instructions in Specifying the transfer of information. 10. Click Save and Check-In. Defining parsing scripts About defining parsing scripts Parsing scripts translate data from many types of inspection devices. The data can be in either ASCII or Document Markup Language (DML) format. All code that is common to the scripts is stored in common scripts that are called from the parsing scripts. DPV provides standard scripts. You can create custom device-specific scripts (for example, to accommodate local configuration differences, such as language). These device-specific scripts should allow for the processing of input data files from multiple routines. You can also use script parameters to define custom information. Defining parsing scripts involves: Working with the common code scripts. Working with script parameters. Attaching custom scripts to the inspection device. Listing of standard scripts. Working with common code scripts About common code scripts All code that is common to all parsing scripts is stored in a common script, which is much like a sub-routine. Any change to the common code propagates to all scripts that call the common code script. You can manage a common script in Teamcenter and export it to multiple DPV Device Client installations. The common code script is a Visual Basic class and contains methods or actions that can be performed that apply to all the plants in your DPV installation. The standard scripts use the methods for basic functions, such as extracting the script parameters, writing the error log file, and so on. Using the Script Debug Utility 2-20 Dimensional Planning and Validation Administration Guide PLM00151 H

37 Defining quality inspection process provided, you can customize these methods, as well as add your own, such as defining a method for trace code mapping and adding specific common code. You can also modify the corresponding parsing scripts to call this common code. You can then pass parameters to the customized script and extend the common script to create individual error log files for each failed measurement data file. You debug the common script using the Script Debug Utility workspace, without needing to access DPV. Customizing the common script requires Visual Basic.NET and Visual Studio (IDE) knowledge. In the DPV Device Client configuration, the common script is stored in the CommonScript folder under the xmlcfg folder. During the DPV Device Client installation process, the default common script is automatically copied to the Commonscript folder only if it does not exist. If the common script already exists, it is not overwritten. You can view information about the common script being used by a DPV Device Client installation (item ID, revision, and date/time of the common device script) through the DPV ETL Error Viewer. For more information, see Viewing DPV Device Client Status in the DPV help collection. Routines in the common code script The following routines, which are used in the standard parsing scripts, can be customized in the common script. You can also add your own routines. The routine Public Sub CollectScriptParams() Public Sub SetDefault() Public Function skipdataline(byval strkeyarray() As String, ByVal intstartindex As Integer, ByVal strflowtype As String, Optional ByVal intsearchtype As Integer = 0) As Integer Does the following Collects script parameter values and stores them in corresponding variables within the common script. Sets default values for parameters specific to the common script. The script sets the default values defined in this function. If any value is present as script parameters in the configuration file, the value in the configuration file overwrites the default value that this function sets. Accepts an array of strings and skips any data file line that starts with or contains any of the strings in the array. It can skip forward or backward, and look for lines that StartWith or Contains any of the strings in the array. By default, it checks using StartsWith. PLM00151 H Dimensional Planning and Validation Administration Guide 2-21

38 Chapter 2 Defining quality inspection process The routine Public Sub logerror(byval errorcode As Integer) Public Sub RecordErrors() Does the following Accepts an error code from the user and adds the errorcode and relevant error message to the arraylist, which contains the list of errors encountered in this data file. The error codes and respective error messages are already stored in a hashmap, which this method uses to retrieve the required error message based on the code sent by the user. This routine can be called any number of times within the script wherever the user wants to log a message. For more information, see About adding error messages to a common code script. Creates an error text file in the errorfiles folder under the device. It writes all the error messages in the arraylist used in the Public Sub logerror(byval errorcode As Integer) method to this text file. This routine should be called only once and only if the measurement data file fails just before exiting the parsing script. Adding error messages to a common code script About adding error messages to a common code script You can add error messages to a common code parsing script by adding new entries to the hterrorlog hash table in the common script using the initerrorlogger() method. You can then raise the errors using pre-defined error codes (in the hashtable) or have the system construct the error messages based on arguments that are passed in. Define custom error messaging The following steps describe how to add and test new error messages through the common script. 1. Add new error messages to the following method in the common script: This method initializes the error logger and adds the error codes with corresponding error messages to the error log hashtable hterrorlog. The following are two examples of how to add new error messages to this method. Example 1 is a simple error message of string type, while Example 2 uses place holders for variables. The variables receive values from the device parsing script Dimensional Planning and Validation Administration Guide PLM00151 H

39 Defining quality inspection process Example 1 Example 2 2. Call this code from the correct place in the device parsing script. The message is then written to the error text file through the logerror method of the common script. Modify the device parsing script as follows to log the new error: Because the error messages are about not finding the routine name, log them through the getroutinename() method. 3. After modifying both the common script and the device parsing script, export them to DPV Device Client. Check for successful compilation of the scripts. 4. After successful compilation, process a measurement data file and check whether or not the new error message is logged to the error text file. Generating error messages from arguments To generate error messages using arguments that are passed in, use the logerror method within the common script. It can receive any number of arguments to facilitate custom error messages. In this example, Args () is a parameter array, and is a way to pass multiple (variable) numbers of parameters to the same function. This method reads all the parameters passed and creates an error message string by formatting them. Example Add the error message to the hashtable: hterrorlog.add(123456, Attribute {0] is invalid for Feature {1} ) Then, in the logerror () function, format the string with the arguments passed in: strerrormessage = String.Format(strErrorMessage, strattrname, strftrname) PLM00151 H Dimensional Planning and Validation Administration Guide 2-23

40 Chapter 2 Defining quality inspection process Example of error logging in the common code script The following code snippet shows an example of the error logging routine described in the last two entries in Routines in the common code script. that file extensions are added to the file name as appropriate. Public Sub logerror(byval errorcode As Integer) Dim strerrormessage as String If hterrorlog.contains(errorcode) Then strerrormessage = hterrorlog(errorcode).tostring() Format your message using arguments as below strerrormessage = String.Format(strErrorMessage, strattrname, strftrname) alsterrorlist.add(errorcode + ":" + strerrormessage) Else alsterrorlist.add("error Message not there for error code:" + errorcode) else format your own message End If End Sub Public Sub RecordErrors() Dim swlogwriter As StreamWriter = Nothing Dim i As Integer If (Directory.Exists(filePath + "\erorfiles") = False) Then Directory.CreateDirectory(filePath + "\erorfiles") End If strfilepath = filepath + "\erorfiles\" + filename + "_err.txt" swlogwriter = File.AppendText(strFilePath) For i = 0 To alsterrorlist.count - 1 swlogwriter.writeline(alsterrorlist(i)) Next i swlogwriter.close() 2-24 Dimensional Planning and Validation Administration Guide PLM00151 H

41 Defining quality inspection process End Sub Error messages for parser errors The following describes the error messages that appear in the Issues list in the DPV ETL Dashboard when you view issues with a measurement data file. For more information, see Monitoring measurement data in the DPV help collection. For more information about the DPVShiftTime form, see Define the shift times. For more information about the location of the attributes rules XML file, see Specify the location of the attribute rules XML file. For more information about attribute rules XML file, see Define the rules. Parser Error Message Routine configuration data for Routine: (Routine_Name) under plant: (Plant_Name) is using for Data file processing Device configuration data for Device: (Device_Name) under plant: (Plant_Name) is using for Data file processing Incomplete Device Configuration file - (File_Name) Could not find script file (Script_Path) for the Device (Device_Name) under the Plant (Plant_Name) Compiled script for the Device : (Device_Name) under plant: (Plant_Name) is using for Data file processing Meaning and Cause The routine configuration data is being used for the measurement data file processing and the updated routine configuration file arrives in the %FLAPP%\XMLCFG\DPVRoutine\ folder. The device configuration data is being used for measurement data file processing and the updated device configuration file arrives in the %FLAPP%\XMLCFG\DPVDevice\ folder. The alive_test_interval_min, location_name, or data_directory value is not present in the DPVDeviceLocation form of the inspection device configuration XML. For more information about the DPVDeviceLocation form, see Set the transfer of information. The inspection device configuration XML file is copied into the %FLAPP%\XMLCFG\DPVDevice\ folder but the corresponding script is not present in that folder. The compiled script for any device under a plant is being used for data file processing and the updated inspection device configuration and script files arrive (in the %FLAPP%\XMLCFG\DPVDevice\ folder). PLM00151 H Dimensional Planning and Validation Administration Guide 2-25

42 Chapter 2 Defining quality inspection process Parser Error Message Compile failed with (Number_of_Error) errors "Error endtime < starttime - dow=(day_of_week), shift=(shift_number)" Error starttime of this shift < endtime of last shift dow=(day_of_week), shift=(shift_number) Error endtime of current day > starttime of next day dow=(day_of_week) Required Device configuration not present for the device (Device_Name) Either there is no data in the Data file or Parser unable to access datafile (File_Path) Compiled script not present for the Device (Device_Name) Under the plant (Plant_Name) Routine Name neither present in data file name nor in Contents of the data file (File_Path) Length of the Routine Name is more that 32 characters Unable to start Thread for the Plant - " + strplant Unable to start Thread for Purge old data files File path for At File path for Attribute Rules XML is empty. Exiting the DPVParser application... Unable to read Attribute Rules XML from the path specified. Exiting the DPVParser application... Meaning and Cause Script compilation errors occur. The end time of any shift is less than the start time of that shift in the shift definition form (DPVShiftTime). The start time of any shift is less than the end time of the previous shift in the shift definition form (DPVShiftTime). The shift end time of any day is greater than the shift start time of the next day in the shift definition form (DPVShiftTime). The inspection device configuration data is not present when the measurement data file (for any device) is processed. The shift end time of any day is greater than the shift start time of the next day in the shift definition form (DPVShiftTime). The compiled script is not present for a particular inspection device under a plant when the measurement data file is processed. The routine name value is not present either in the measurement data file name or in the contents of the data files when the measurement data file is processed. The length of the routine name or the spec doc name value is more than 32 characters at the time of data file processing. The thread creation fails for a particular plant. Each plant has a separate thread running for it to process measurement data files under that plant. The start new thread fails for measurement data file purging. The path for the attributes rules XML is blank in the Configuration Explorer. There is no attributes rules XML file present at the path specified in Configuration Explorer Dimensional Planning and Validation Administration Guide PLM00151 H

43 Defining quality inspection process Parser Error Message Unable to Read Parser Configuration data from FactoryLink. Exiting the DPVParser application... Invalid Routine configuration XML file - + f.fullname Invalid Plant configuration XML file - + f.fullname Invalid Device configuration XML file - + f.fullname Device ID not present in the Device configuration XML file Device Name not present in the Device XML configuration file Ill-formed Attribute Rules XML file. Exiting the DPVParser application... Incorrect Attribute XML file specified. Exiting the DPVParser application... Length of the Attribute code -" + attributecode + " in the rule node - " + node.outerxml + " is more that 5 characters. Unsupported Condition specified in the rule node - + node.outerxml Position is mandatory for Condition Chars in the rule node - + node.outerxml Condition attribute missing for rule node - + node.outerxml Either Condition or conditionkey or attributecode is missing for rule node - + node.outerxml The data file (" + filepath + ") copied into wrong folder hierarchy Error in Compiled script for the Device - " + strdevicename + " Under the plant - " + strplantname Meaning and Cause The startuptask fails to read configuration information from DPV Device Client. The read routine configuration file and collection of routine node details fail. The read plant configuration file and the collection of plant node details fail. The read device configuration file and the collection of device node details fail. The device ID is not present in the inspection device configuration file. The device is invalid in this case. The device name is not present in the inspection device configuration file. The device is invalid in this case. The loading of the attribute rules XML file to a XML document fails. If there are no nodes starting with Rule (that is, there are no valid rules in the loaded XML file). If the attribute code is more than five characters, the rule object is not added to the array list and log error message. If the Condition attribute in the rule node is something other than EndsWith, StartsWith, Contains, or Chars. The Condition is Chars in a rule node but there is no Position attribute. The Condition attribute is missing for a rule node. Either the Condition, conditionkey, or attributecode is missing for a rule node. The measurement data file is copied to the incorrect folder location in the hierarchy. The compiled script is present for a device, but is equal to null. PLM00151 H Dimensional Planning and Validation Administration Guide 2-27

44 Chapter 2 Defining quality inspection process Parser Error Message The data file (" + filepath + ") contains Features with no valid attribute code(dflt). Invalid data in Position in rule with conditionkey- + rule1.conditionkey Chars in conditionkey not equal to the position specified in rule with conditionkey- + rule1.conditionkey Script file - + strscriptpath + does not exists for the Device - + strdevice + under the Device parent - + strdeviceparent + under the Plant - + strplant Meaning and Cause The blnfaildfltattribute command line argument is set to FAIL and the file contains the DFLT feature attribute type, so the measurement data file fails. For more information about the DFLT feature attribute type, see Set the default attribute (DFLT) handling. The Position attribute in any rule node contains non-integer data. The length of conditionkey is not equal to the difference of startposition and endposition of the Position value. Determines whether or not the inspection device script file exists. If it does not exist, then writes the message to the error log file. Error messages for raw validation errors The following describes the error messages that appear in the Issues list in the DPV ETL Dashboard when you view issues with a measurement data file. For more information, see Monitoring measurement data in the DPV help collection. For more information about parsing scripts, see Defining parsing scripts. Validation Error Message Invalid Field Value (F=V) Field (F) multiply defined Field (F) not present Cannot find measurement data file F Meaning and Cause Field value (V) did not pass the validation checks for this field (F). If this field value came from a raw measurement data file, correct the raw data file. If the field value came from a Teamcenter form, correct the form value. Field (F) was defined multiple times. There is most likely an error in the parsing script. Field (F) is required, but it was not output by the DPV Parser. This could be an error in the raw measurement data file or the Teamcenter configuration. If the field is intended to be in this type of raw measurement data file, correct the file. If the field does not come from this type of raw data file, correct the Teamcenter configuration. The measurement data file cannot be read Dimensional Planning and Validation Administration Guide PLM00151 H

45 Defining quality inspection process Validation Error Message Routine ID was not present in measurement data file F Routine ChgLvl was not present in measurement data file F Plant Name specified in FacilityName (P) is not valid. Plant name cannot be determined from measurement data file P Unknown Routine Name (SpecDocName) R in Plant P No Build Information Found in DML Error Retrieving Build Information from DML BuildLbl does not have a value Meaning and Cause The output of DPV Parser did not specify the routine name in the SpecDocName field. This is most likely an error in the parsing script. The output of DPV Parser did not specify the routine change level in the SpecChgLvl field. This is most likely an error in the parsing script. The plant name (P) is not known by the validation process. This is usually caused because a routine XML definition had fatal errors in it. The plant names are defined when a routine definition is downloaded. If the routine definition is not valid, then the plant name is not known. Check the DPV Validation log file for errors. The output of DPV Parser did not specify the plant name (P) specified in the FacilityName field. This is typically an error in the parsing script. The routine name (R) output by DPV Parser is not defined within the plant (P) of the Teamcenter bill of process. Correct the Teamcenter configuration and submit the routine to the Export_Routine_to_AI workflow. For more information about creating bill of processes, see Defining a plant process structure. For more information on submitting a routine to workflow, see Export the measurement routine to the DPV Device Client. DPV Parser did not pass any build data. This is most likely a bad raw measurement data file or an error in the parsing script. Output of DPV Parser was ill-formed. This is most likely an error in the parsing script. The BuildLbl (job number) was not specified. Either correct the raw measurement data file or correct the Teamcenter configuration. PLM00151 H Dimensional Planning and Validation Administration Guide 2-29

46 Chapter 2 Defining quality inspection process Validation Error Message Duplicate Feature Attribute F / A Planned feature (F) not present Required feature (F) not present Planned feature attribute (F/A) not present Required feature attribute (F/A) not present Build contains no feature data Ill-formed Feature/Attribute Invalid Limit: Feature=F, Tolerance=T, usl=u, lsl=l Ill-formed Spec/Reject Validation Successful for DML File (F) Meaning and Cause The feature (F) or attribute (A) is defined multiple times in the raw measurement data file. Correct the raw measurement data file. The feature (F) is not present in the raw measurement data file. This is only a warning. The required feature (F) is not present in the raw measurement data file. This is an error. The feature (F) or attribute (A) is not present in the raw measurement data file. This is only a warning. The required feature (F) or attribute (A) is not present in the raw measurement data file. This is an error. There is no feature data in the raw measurement data file. There must be at least some data. The output of the parser is not formatted correctly. This is a bug in the DPV Parser. The USL or LSL specified was not a valid floating point number. This is most likely a bad specification/reject file. Correct the specification/reject file. For more information, see Defining specifications in a DPV Excel Engineering workbook. The output of DPV Parser is not formatted correctly. This is an error in DPV Parser. Validation was successful. Extending the common script Examples of extending the common script The common script that Siemens PLM Software provides is only a place holder for all the common code. By default, it only contains the basic functions, such as extracting the script parameters, writing the error log file, and so on. You need to add any specific common code and modify the corresponding parsing scripts to call the common code. The following are examples for modifying the common script: Extracting a new script parameter Adding a new method for extracting trace codes 2-30 Dimensional Planning and Validation Administration Guide PLM00151 H

47 Defining quality inspection process Setting default values for script parameters Extracting parameter-based routine names from the measurement data file For information about defining error messages see Define custom error messaging. Example of extracting a new script parameter The common script that Siemens PLM Software provides contains the following method for collecting script parameter values and storing them into corresponding variables within the script: This method reads the values of script parameters, such as ROUTINENAMEKEY, EVENTYPEKEY, ITEMTYPEKEY, PROJECTNAMEKEY, and so on. To add a new script parameter, for example NEWSCRIPTPARAM, add the following code to this method to read the value: You also must declare the new variable strnewscriptparameter at the start of the class: Example of adding a new method for extracting trace codes To retrieve a trace code value from the TraceCode section of a measurement data file, add a new method for extracting the trace codes through script parameters using the following method signature. The method returns the trace value in string format. All the parsing scripts must be modified to use the common script object for methods that are implemented in the common script. An object of CommonScript type is already created in the default parsing scripts, through which the new methods can be called. Example of setting default values for script parameters To set the default values of script parameters for all parsing scripts using the common script, use the following method: PLM00151 H Dimensional Planning and Validation Administration Guide 2-31

48 Chapter 2 Defining quality inspection process The script first sets the default value throughout the function. If any value is present for a script parameter, then that value overwrites the value set in this function. For example, if you want to specify a default value for the NEWSCRIPTPARAM that was shown extracted in the Example of extracting a new script parameter, add the following line of code: strnewscriptparameter = DefaultStringValue Example of extracting parameter-based routine names from the measurement data file To extract the routine name from the data file based on script parameters, implement the logic to use the script parameter in the parsing script. Script parameters defined in the device configuration XML are passed to the getroutinename() method so you can extract the routine name from a desired location within the measurement data file. The common code parsing script only provides an interface method that passes the script parameters to the compiled script object. Because this parameter is required for extraction of the routine name, it should be specified on the device. The following is an example of how to read the routine name based on the script parameter and not the default location from a CDI measurement data file. By default, in a CDI measurement data file, the routine name is read from the SpecDocName field as shown. You may also want to read it from another field, for example, RoutineName. 1. Modify the following to add logic to the CDI device parsing script to read the routine name based on the script parameter and not the default location: 2-32 Dimensional Planning and Validation Administration Guide PLM00151 H

49 Defining quality inspection process 2. After modifying the device parsing script, export it to the DPV Device Client. Check for successful compilation. 3. After successful compilation, process a measurement data file and check whether or not the routine name is read using the RoutineNameKey script parameter. Debugging parsing scripts See your DPV support personnel for information about the debug workspace. Use the Script Debug Utility to debug a parsing script, including debugging the use of any common code scripts. Tip To debug the common code script, paste the common code into the CommonScript.vb file as shown in the figure. PLM00151 H Dimensional Planning and Validation Administration Guide 2-33

50 Chapter 2 Defining quality inspection process Export a common parsing script to DPV Device Clients You can export a common parsing script to multiple DPV Device Client installations. When you send the common script to the DPV Device Client, the DPV Device Client finishes processing any previously started parsing scripts and uses the new common script for any new parsing tasks. You do not need to restart the DPV Device Client. The common parsing script does not need to be under a station since it is common to all stations. You can store it in the Newstuff folder or any folder. 1. Create a device item revision: a. In My Teamcenter, click Home or the folder where you want to create the common device. b. Choose File Item. c. From the list, select CommonDevice. d. Click Next. e. Click Assign to fill in the Item ID and Revision ID boxes. f. Type in a name and description for the common script item. g. Click Finish. 2. Attach the common script to the device item revision /A:1-CommonScriptDevice View /A CommonScript 3. Send the common script to the DPV Device Clients: a. Right-click the common device item revision and choose Create Workflow Process. b. In the New Process dialog box, from the Process Template list, select Export Common Device to AI. The file names automatically fill in. c. Verify that the targets specified in the New Process dialog box are correct. d. Click OK. e. In the Information dialog box, click OK. The common script is automatically sent to the DPV Device Clients for processing. When the processing is complete, the following message is logged in the DPVParser log file: 2-34 Dimensional Planning and Validation Administration Guide PLM00151 H

51 Defining quality inspection process Update Common Script has loaded successfully... An application Interface (AI) object is created. The AI object contains a.plmxml file with the information you exported. For more information about AI objects, see Managing AI objects created during export. Error messages during the exporting Error messages during common parsing script loading If the common parsing script compilation fails when the DPV Device Client starts, the DPV Parser is not started. The following error message is logged in the DPVParser log file: [ERROR] Compilation errors in the Common Script. application... Exiting the DPVParser If the common script is updated and fails to compile, when the DPV Device Client is running, the DPV Device Client reverts to the earlier working script. The following message is logged in the DPVParser log file: [ERROR]: Compilation errors in the updated Common Script. earlier script... Reverting to the Working with script parameters About script parameters Parameters can be passed to parsing scripts using the DPVMeasmtParseParam form that can be attached to the inspection device and/or the routine. By defining parameters in scripts, you can use the same parsing script for different inspection devices. This is particularly helpful when you have localization issues, such as how the date is displayed or the language used. Instead of creating two scripts, you can create one script using parameters. In addition, you can pass parameters from a device to a parsing script that uses the common script. The following is the overall workflow used to process parameters. Examples of using parsing script parameters PLM00151 H Dimensional Planning and Validation Administration Guide 2-35

52 Chapter 2 Defining quality inspection process Define script parameters Examples of using parsing script parameters The following provide examples of using parameters with parsing scripts. Using parameters to specify the inspection device type Using parameters for localization issues Using parameters with a.csv script Using parameters to specify the inspection device type If the inspection device type is not contained within the measurement data file, then the default is Inspection Device. You can overwrite this by defining the following parameter value in the parsing parameter form (DPVMeasmtParseParam) attached to the inspection device: Adding this parameter results in the device_type being set to Vision, as shown in DPV Measurements Dimensional Planning and Validation Administration Guide PLM00151 H

53 Defining quality inspection process Using parameters for localization issues Using parameters, you can use a single script to parse different comma-separated value (CSV) files with different languages. If time and data is in column 1 in one language, such as English, and in column 2 in another language, such as Spanish, then set parameters for each of these conditions. Use parameters in a single script to change the label for time from English to Spanish. Using parameters with a.csv script Measurement data is commonly received in a CSV file, as shown below. The parsing script for this measurement data would have the following defined within it for the column headers: 1 Date and time Indicates the column header for the data and time. that multiple methods for defining the date and time are supported, based on the structure of the data. 2 Serial number Indicates the column header for the serial number. 3 Non-feature data (multiple) Indicates the column header for non-feature data (for example, Date, Collector ID, and so on). PLM00151 H Dimensional Planning and Validation Administration Guide 2-37

54 Chapter 2 Defining quality inspection process 4 Trace codes Indicates the column header for trace codes. Trace codes are information added to a measurement data file to define specific conditions that apply to a particular serial number (for example, product variants, such as having a sunroof or no sunroof). You could replace this script with a generic script that defines the column headers using parameter forms attached to the inspection device. There would be five forms. Two forms for non-features because the param_value length is restricted to 64 characters, which does not allow all the non-feature values to be defined in one field. The values for the first form for non-features are: Set this option param_label param_value To the following NonFeatures Date, Collector ID, Operator, Shift, LMI Serial#, Body Style The values for the second form for non-features are: Set this option To the following param_label NonFeatures1 param_value Part Serial # Form to define the trace code columns: Set this option param_label param_value To the following TraceCodeColumns Operator, Body Style Form to define the part serial number header (PVIHeader): Set this option To the following param_label PVIHeader param_value Part Serial # Form to define the date header (DateHeader): Set this option param_label param_value To the following DateHeader Date 2-38 Dimensional Planning and Validation Administration Guide PLM00151 H

55 Defining quality inspection process Define script parameters 1. In Manufacturing Process Planner, in the Attachments view, select the inspection device. You must select the inspection device in the Attachments view to create a form. The script parameter form for the routine name must be added to the inspection device and not the routine in Teamcenter. 2. Create a form of the type DPVMeasmtParseParam. 3. Enter the following: Use this option param_type To do this Identify the type of parameter: Trace Pass the param_label and param_value values (see the two rows in this table) to the parsing script. Feature Rename Rename a feature during parsing. Example Use this when a feature has one name when it is in the raw measurement data file and another name when it is in Teamcenter. param_label Script Parameter Parameters to be passed to the parsing script. Specify the label for the parameter. Example When you are renaming a feature, this specifies the original name of the feature. param_value Script parameters for measurement data in DML format Specify the value of the parameter. Example When you are renaming a feature, this specifies the original value of the feature. List of forms used PLM00151 H Dimensional Planning and Validation Administration Guide 2-39

56 Chapter 2 Defining quality inspection process Tips for managing forms Attach custom scripts to inspection devices 1. In Manufacturing Process Planner, select the inspection device, and choose File New Dataset. 2. Choose Text. 3. Click OK. 4. Verify that the parsing script appears as an attachment on the inspection device. 5. In the Import box, click... and navigate to the inspection device parsing script. 6. Click OK. 7. Copy the inspection device to the BOR folder: a. Right-click the inspection device, and choose Copy. b. In My Teamcenter, select the BOR folder and choose Edit Paste. Standard parsing scripts Dimensional Planning and Validation provides standard parsing scripts. The following table identifies the inspection device types and their corresponding scripts provided with Dimensional Planning and Validation. All the scripts are located in: FLINK\Installs\DPV\Parsing Scripts The device Has the script PC/PC-DMIS PCDMIS_1.txt PCDMIS_2.txt PCDMIS_3.txt PCDMIS_3.1.txt PCDMIS_3.1.txt PCDMIS_3.2.txt Zeiss/UMESS UMESS_1.txt Zeiss SMC/UMESS Zeiss SMC/UMESS Format 2 5. UMESS_2.txt UMESS_3.txt UMESS_4.txt Wentzel/Metrosoft Metrosoft_1.txt Metrosoft_2.txt 2-40 Dimensional Planning and Validation Administration Guide PLM00151 H

57 Defining quality inspection process The device Zeiss/Metroligic/DMIS LKDMIS Perceptron IPNET Perceptron P1000 Perceptron Spec/Reject Datamyte 501/Transcend Laser Gauge Has the script DMIS.txt LKDMIS.txt PERCEPT_1.txt Perceptron_CDI.txt SPEC_REJECT.txt CSV.txt GTalker.txt Duplicate data Duplicate data occurs when there are communication failures and the inspection devices do not know that the data was already collected. Duplicated data will have the same routine ID and job serial number. DPV Device Client marks the data as being a duplicate and then adds the latest data as the final data. The data appears in the log file as: Measurement Event Type = D Example For example, vision stations can lose the connection to the machine that provides them with their job serial numbers so they process the data as the same number again and again. Specifying the transfer of information About specifying the transfer of information Remote transfer agents send the data files that the inspection devices produce to the regional computers running DPV Device Client, which then send the data to the parsing scripts to be translated. The parsing scripts translate the data into a common XML format (DML) and send it to the DPV Device Client databases for storage in the passed or failed directories. Remote transfer agents track statistics on the transfer of data and store errors in a file. PLM00151 H Dimensional Planning and Validation Administration Guide 2-41

58 Chapter 2 Defining quality inspection process A remote transfer agent runs on each inspection device computer. A plant can have multiple inspection device computers. Each inspection device computer can collect data for one or more inspection devices. For information on installing the remote transfer agents, see Installing the Dimensional Planning and Validation solution in the DPV help collection. Set the transfer of information Set the end-of-routine flag Set the transfer of information Define where the remote transfer agent and the directory where the data files are located. 1. In the Attachments view, select the inspection device. You must select the inspection device in the Attachments view to create a form. 2. Check out and edit the form of the type DPVDeviceLocation. 3. Enter the following: 2-42 Dimensional Planning and Validation Administration Guide PLM00151 H

59 Defining quality inspection process Use this option location_name data_directory alive_test_interval_min To do this Identify the inspection device computer where the remote transfer agent runs. Provide a unique name for each computer. This could be the computer name or IP address if they are unique across the entire network. If not unique, use another unique naming convention. Identify the full path to the data files on the inspection device. Specify the interval at which you expect the inspection device to report. Enter an integer. 4. Click Check-In. List of forms used Tips for managing forms Set the end-of-routine flag The end-of-routine flag defines the character (letter or symbol) that indicates that a routine is complete. The end-of-routine flag cannot be set to a character that is present in the routine name. 1. In the Attachments view, select the inspection device. You must select the inspection device in the Attachments view to create a form. 2. Check out and edit the form of the type DPVMeasmtDeviceDef. 3. Enter the following: Use this option end-of-routine To do this Identify the character that represents the end of the routine. Example If the data file name is UBVIS_380ES_ cdi and the end-of-routine flag is _, the routine name is computed from the data file as UBVIS (that is, until the first occurrence of _ ). Specify this same name in the shopfloor_name box in the DPVRoutineInfo form. 4. Click Check-In. List of forms used PLM00151 H Dimensional Planning and Validation Administration Guide 2-43

60 Chapter 2 Defining quality inspection process Tips for managing forms Working with DML data About working with measurement data in DML format You can collect measurement data in ASCII or Dimensional Markup Language (DML) 2.0 format. Dimensional Planning and Validation parses the data using the same parsing scripts. DML is an XML-based language for representing measurement results so it can be transmitted between applications that generate and use dimensional information. The DML format has three basic components: Header information to identify the data (qis_def) Tolerance specification Feature specification Example of measurement data in DML format This sample DML file contains an example of measurement data. It is annotated to explain the different aspects of measurement data in DML format. If this file downloads as a zip file, change its extension to docx. Feature types supported in DML The following feature types are supported in the DML schema: Point Line Plane Circle Cylinder Sphere Cone Open slot Closed slot Point Curve Torus Features of the type ellipse, pattern, and constant Xsect are not supported Dimensional Planning and Validation Administration Guide PLM00151 H

61 Defining quality inspection process The Engineering XML file generated from the XML Generation Utility contains feature types that are not present in the Teamcenter feature list of values (LOVs). Therefore, when you import the Engineering XML, these features are ignored and are not imported in the Excel Engineering workbook. To have the feature types included in the workbook, add them to the Teamcenter features LOV using Business Modeler IDE, before importing the engineering XML into Teamcenter (using Tools Import Feature Data). Use script parameters to extract data from the DML file Information about the measurement data is read from the header data by default. The information includes routine name, build label, and data and time. The following shows the information expected in the header for routine: If this data is to be read from the qis_def section of a DML file and not the header, as shown for the routine name, add script parameters to the parsing scripts to extract the data from the qis_def section: You use forms to define the script parameters. 1. If the routine name is to be read from the qis_def section of a DML file, add a script parameter form (DPVMeasmtParseParam) to the inspection device with the param_name of RoutineNameKey and a value of Routine. For more information, see Define script parameters. The param value can change depending on the type attribute of the qis_def node: <qis_def label="dcx_19" type="routine" value="dmlroutine" /> 2. In the same way, add script parameter forms for the following to be read from the qis_def section of the DML file, as shown in the figure: PLM00151 H Dimensional Planning and Validation Administration Guide 2-45

62 Chapter 2 Defining quality inspection process Trace Codes: The value can be a comma-separated list of all trace codes to be read Param_name = TraceCodeKeys Param_values = Category,Serial Number <qis_def label="dcx_20" type="category" value="ps" /> <qis_def label="dcx_21" type="serial Number" value="050110" /> Other parameters you can define are: DateKey TimeKey EvenTypeKey ItemTypeKey FacilityNameKey ProjectNameKey PhaseNameKey SiteLocationKey DeviceTypeKey Using forms to define item and phase name By default, Item_name and Phase_name are read from the qis_def section: <qis_def label="dcx_22" type="item_name" value="itemname123" /> If they are not in the qis_def section, add the corresponding forms (DPVRoutineInfo for Item_name and DPVMeasmtContext for Phase_name) to the routine. These values are required for the file to pass validation Dimensional Planning and Validation Administration Guide PLM00151 H

63 Defining quality inspection process For more information on creating a routine and the forms needed, see Create a measurement routine from a template and Create forms associated with the measurement routine. Custom feature attributes in DML format If measurement data in DML format contains custom feature attributes that are not in the Teamcenter list of values (LOV), the generated Engineering XML file contains the new attributes. However, when you attach the engineering data using Tools Import Feature Data in Teamcenter, Teamcenter checks whether the attribute codes are in the attribute LOV and if they are not, it ignores them. Therefore, before exporting the routine to the workflow, you must add the attributes to the Engineering workbook that defines the feature in both worksheets (FeatureInfo and ENGG tabs) and fill the corresponding columns (under the feature). This is a temporary solution, however, and only applies to that instance of the Engineering XML. If the custom attributes appear in more files, then for a permanent solution, add the custom attributes to the attribute LOV using Business Modeler IDE. For more information on defining feature data and adding the feature attributes to the LOV in Business Modeler IDE, see Adding feature data and Defining custom feature attributes. Example If a feature contains two custom attributes, DMIN and DMAX, that are not defined in the Teamcenter list of values (LOV), they are not imported to the Engg Excel worksheet. Therefore, after importing the engineering XML, manually add DMIN and DMAX to the Excel worksheet (both the FeatureInfo and ENGG tabs) and fill in the corresponding columns (under the feature) before exporting the routine to workflow. For the FeatureInfo tab in the Engineering workbook: 1. Add DMIN and DMAX to the attribute information as Attributes 8 and 9: PLM00151 H Dimensional Planning and Validation Administration Guide 2-47

64 Chapter 2 Defining quality inspection process 2. Add the attribute values to the corresponding columns under the feature: For the ENGG tab in the Engineering workbook: 1. Add DMIN and DMAX to the attribute information as Attributes 8 and 9: Add the attribute values to the corresponding columns under the feature: 2-48 Dimensional Planning and Validation Administration Guide PLM00151 H

65 Defining quality inspection process Defining engineering data About defining engineering data You store the engineering data that defines your measurement process in a bill of process. Learn how to: Define plant process structure. Define measurement routines. Associate a product, plant, and bill of process. Approve measurement routines. For an introduction to defining engineering data, see the Dimensional Planning and Validation tutorial. Defining a plant process structure About defining a plant process structure Working with a plant process structure involves: Creating a plant process structure. Specifying its location. Defining its shift start times. Defining error notification. Adding the plant process structure to the Teamcenter measurement database. Understand plant process structures. Create a process structure (bill of process) Create a process structure (bill of process) that mirrors the structure of the bill of resource. 1. Create the plant process: a. In Manufacturing Process Planner, click Create New Process. You can also choose File New Process. b. In the New Process dialog box, from the Process Type list, select MEPrPlantProcess. c. Click Next. d. Click Assign to automatically populate the Process ID and Revision boxes. PLM00151 H Dimensional Planning and Validation Administration Guide 2-49

66 Chapter 2 Defining quality inspection process e. In the Name box, enter the plant name. The plant name cannot exceed 30 characters or the Application Interface (AI) objects exported for that plant will not be downloaded to DPV Device Client. f. Click Finish. A new tab appears for the process. g. (Optional) Select the process you just created, and create another process that defines an assembly line using the steps outlined in step 2. Use a Process Type of MEPrLineProcess. h. (Optional) Select the assembly line you just created, and create another process that defines a zone using the steps outlined in step 2. Use a Process Type of MEPrZoneProcess. Tip To view its contents, you may have to expand the process (click the +). i. (Optional) Select the zone you just created, and create another process that defines a station using the steps outlined in step 2. Use a Process Type of MEPrStatnProcess. Specify the location of the plant 1. In Manufacturing Process Planner, click the tab for the process structure. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, select the plant process. You must select the root process (MEPrPlantProcess) in the data pane to create a form. 4. Create a form of the type DPVLocation. 5. Specify the following: Use this option region country To do this Enter the region in which the plant is located (Region 1, Region 2, and so on). Enter the country in which the plant is located Dimensional Planning and Validation Administration Guide PLM00151 H

67 Defining quality inspection process Use this option time_zone To do this Enter the time zone of the plant. The time_zone box accepts any of the standard Windows time zones. View them in the Windows Date and Time Properties dialog box: In the task bar, double-click Time. From the Start menu, choose Settings Control Panel Date and Time. The time_zone box accepts only 32 characters. There are four time zone definitions that are not unique in the first 32 characters: (GMT-07:00) Chihuahua, La Paz, Mazatlan - Old (GMT-07:00) Chihuahua, La Paz, Mazatlan - New (GMT-06:00) Guadalajara, Mexico City, Monterrey Old (GMT-06:00) Guadalajara, Mexico City, Monterrey - New New is the default choice. If you want the old definition, use one of the following: (GMT-07:00) Old - Chihuahua, La Paz, Mazatlan (GMT-06:00) Old - Guadalajara, Mexico City, Monterrey Alternative abbreviations 6. Click OK. List of forms used Tips for managing forms Alternative abbreviations In addition to the standard Windows time zones listed in the Date and Time Properties dialog box, the time_zone box accepts the following common abbreviations. PLM00151 H Dimensional Planning and Validation Administration Guide 2-51

68 Chapter 2 Defining quality inspection process Abbreviation MIT HST AST PST MST MST7 CST EST5 EST GMT WET CET EET IST CHST JST KST Meaning Midway Island Time Hawaii Standard Time Alaska Standard Time Pacific Standard Time Mountain Standard Time Arizona Central Standard Time Indiana (East) Eastern Standard Time Greenwich Mean Time Western European Time Central European Time Eastern European Time India Standard Time Chinese Standard Time Japan Standard Time Korean Standard Time Define the shift times Use the DPVShiftTime form to specify shift times for a plant. There should only be one form per plant. Only production days need to be defined. Any day with no shift defined is assumed to not be a production day. 1. In Manufacturing Process Planner, click the tab associated with the plant process. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, select the plant process. You must select the plant process in the Attachments view to create a form. 4. Create a form of the type DPVShiftTime. 5. Type the start times for the shifts in the boxes, for each day of the week. It is in 24-hour format: hh:mm. Example If the start time is 8:00 a.m., type 08: Dimensional Planning and Validation Administration Guide PLM00151 H

69 Defining quality inspection process Tip You can specify a shift that continues until the next day. For example, the following specifies a late Monday shift that runs until 5:59 the next day: 6. Click OK. List of forms used Monday 3 Start: 22:00 End: 5:59 You can include hours from a previous day in a shift. For example, the following specifies that the Tuesday shift starts at 10:00 on Monday, because 2 hours are subtracted from the start of Tuesday. Tuesday 3 Tips for managing forms Start: 2:00 End: 5:59 Define error notification during data loading Error notification can also be defined for a particular measurement routine. If you define it for a routine, it overrides the value defined for the plant. 1. In Manufacturing Process Planner, click the tab associated with the plant process. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, select the plant process. You must select the plant process in the Attachments view to create a form. 4. Create a form of the type DPVErrorNotification. 5. Select when you want to be notified of errors. Use this option None All First To do this Report no errors. Report each time there is an error. Report the first time there is an error in a series of errors. PLM00151 H Dimensional Planning and Validation Administration Guide 2-53

70 Chapter 2 Defining quality inspection process Example If the first three data files have errors, and the fourth and fifth do not, while the sixth does, then you receive the following messages, depending on how you set the option: Set it to All, receive messages for first, second, third, and sixth files. Set it to First, receive messages for the first and sixth files. 6. Click OK. List of forms used Tips for managing forms Add plants to the Teamcenter measurement database If the measurement data is stored in a remote measurement database, add a reference to the new plant process structure in that measurement database. After adding the reference, Teamcenter stores all data that is processed for that plant in the measurement database. In addition, if a link to a remote measurement database is not available, you can create a link to it if both the Teamcenter and measurement databases are Oracle databases. This step does not need to be performed if the measurement data resides within the Teamcenter database instance. The group to which you belong must be part of the DPV Admin group for you to have permission to add the plant to a measurement database. For more information, see the Preferences and Environment Variables Reference. You must know which database link is associated with which measurement database. For information about creating links to measurement databases, see Creating links in Teamcenter to the measurement databases in the Installing the Dimensional Planning and Validation solution guide in the DPV help collection. 1. In Manufacturing Process Planner, right-click the top of the plant process structure (the MEPrPlantProcess item) and choose Send Plant ID. The Send Plant ID dialog box appears Dimensional Planning and Validation Administration Guide PLM00151 H

71 Defining quality inspection process 2. Enter the following: For the field PlantID DB Type Do the following The text box is automatically filled with the item ID of the selected plant. You cannot change it. Select: ORACLE The measurement database is an Oracle database. SQLSERVER The measurement database is a remote SQL server. Link Name SQLSERVERLOCAL The measurement and Teamcenter databases reside on the same physical server. Select the link to the measurement database. See your system administrator for information about the link names and the associated measurement databases. For Oracle Teamcenter databases, you can select New to create a new link to an Oracle measurement database. For information about creating links, see Creating links in Teamcenter to the measurement databases in the Installing the Dimensional Planning and Validation solution guide in the DPV help collection. 3. Click OK. Either of the following messages appear: PLM00151 H Dimensional Planning and Validation Administration Guide 2-55

72 Chapter 2 Defining quality inspection process The <plant name> will be added to the measurement database. The plant <plant name> already exists in the measurement database. 4. Click OK. Clicking OK updates the plant to the new database link. Defining a measurement routine About defining a measurement routine After creating the process structure, define the measurement routine as an operation within the plant. The type of operation you create depends on the type of inspection device. After defining the routine, add feature data. Measurement routines cannot be shared between plants. They belong to only one plant. When data for a routine is not collected in a single file, you can merge the files into one event stored in the Teamcenter measurement database. You specify the merging when you define the feature data, using the option loading split ID. See Defining split events. The tasks to create a measurement routine include: Create a measurement routine from a template Define error notification Define export to regions Add feature data Define custom feature attributes Work with clusters and cluster groups Define datum transformations Define triggers Define feature mapping Create a measurement routine from a template When you create the measurement routine from a template, Teamcenter creates all the necessary forms you need to define the routine. You will edit the forms. If you do not have a template, create the measurement routine as instructed in Create a measurement routine and do not call it a template. Then, create all the necessary forms listed in Create forms associated with the measurement routine Dimensional Planning and Validation Administration Guide PLM00151 H

73 Defining quality inspection process 1. In Manufacturing Process Planner, select the tab associated with the process structure. 2. Select the plant or a location in the plant (assembly, zone, or station) for which you want to define a measurement routine. 3. Choose File New From Template Operation from Template. 4. Click the Choose Template tab, type the name of the template in the Template ID box, and select Use Template. Alternatively, you can search or browse for the template you require. Tip Click Add to Favorites to save the template to a favorites palette so it can be quickly accessed and used. To search for a template: a. Click the Choose Template tab. b. Next to the Template ID box, click Find the Template by Name. c. In the Find Template by Name dialog box, type the search criteria including wildcards, such as *template*. d. Click Find. The templates that match the criteria appear in the dialog box. e. Double-click the desired template. 5. Click the Configuration tab and choose the cloning rule Mapping_Consumes. If required, you can also change the revision rule on this tab. 6. Change the name of the routine. All other values (ID, revision, type, description) are automatically set for you. 7. Click OK. 8. In the Attachments view, view the forms created for the measurement routine. 9. Check out and edit the forms following the instructions in: Define error notification during data loading Export the measurement routine to DPV Device Client PLM00151 H Dimensional Planning and Validation Administration Guide 2-57

74 Chapter 2 Defining quality inspection process Define error notification during data loading Error notification is always defined for the plant. If you define it for a routine, it overrides the value you defined for the plant. 1. In Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, select the routine. You must select the routine in the Attachments view to create a form. 4. Check out and edit the form of the type DPVErrorNotification. 5. Select when you want to be notified of errors. Use this option None All First To do this Report no errors. Report each time there is an error. Report the first time there is an error in a series of errors. Example If the first three data files have errors, and the fourth and fifth do not, but the sixth does, then you receive the following message, depending on how you set the option: Set to All, receive messages for first, second, third, and sixth files. 6. Click Check-In. List of forms used Tips for managing forms Define export to regions Set it to First, receive messages for the first and sixth files. Configure the measurement routine so its data can be sent to another region (for example, Region 2 Teamcenter) and measurement data from the two different regions can be compared. This is an optional feature. It must also be defined in the. 1. In Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears Dimensional Planning and Validation Administration Guide PLM00151 H

75 Defining quality inspection process 3. In the Attachments view, select the routine. You must select the routine in the Attachments view to create a form. 4. Check out and edit the form of the type DPVExportToRegions. 5. Type the region number and any customer-defined values. Type 1 for Region 1, 2 for Region 2, and so on. The number must be unique. 6. Click Check-In. List of forms used Tips for managing forms Adding feature data About adding feature data Feature data is attached to the measurement routine as an Excel dataset. You can create the data in XML or Excel. All edits are done in Excel. The following sections describe how to define feature data: Feature data validation. Define feature data in a DPV Excel Engineering workbook. Define specifications in a DPV Excel Engineering workbook Define feature data in an.xml file. PLM00151 H Dimensional Planning and Validation Administration Guide 2-59

76 Chapter 2 Defining quality inspection process You can also define split events, define custom feature attributes and generate feature data from measurement data. Feature validation About DPV feature data validation When you edit a DPV Excel Engineering workbook through Teamcenter, it is associated with a rule set that validates the feature data you enter. The rule set is a collection of macros stored in a Microsoft Excel binary workbook (.xlsb). Siemens PLM Software provides a default rule set. We also recommend that you create your own custom rule set to validate the feature data against your company s standards. In particular, use it to define the specification set worksheets names. You associate a DPV Engineering Excel workbook with a custom rule set when you import it. You can also change the association using the Apply Rule Set command. The workbook is always associated with the default rule set that Siemens PLM Software provides. When you edit the workbook, you can activate and run validations using both the default and the selected custom rule set. You can run static validations of the entire workbook or runtime validation of the current cell. The rule sets create discrepancy worksheets in which to display any validation errors, for example, you entered a name that contains characters that are not allowed. They highlight cells with errors in red and cells with warnings in yellow. When you correct the errors, the corresponding entries are deleted from the discrepancy worksheets. In addition to rule set validation, the Teamcenter server validates the feature data when you import and save the Excel Engineering workbook. If the server validation fails, the routine data cannot be sent to client applications, such as DPV Device Client, DPV Reporting & Analysis, and DPV-SSAS Dimensional Planning and Validation Administration Guide PLM00151 H

77 Defining quality inspection process Teamcenter server validation In addition to the DPV rules validation that occurs while you are editing a DPV Excel Engineering worksheet, the Teamcenter server validates the feature data when you import it into a DPV Excel Engineering dataset (Tools Import Feature data) and when the dataset is saved. Server validation reports the outcome of the validation as Success or Fail. Any warnings in the DPV Excel Engineering worksheet (highlighted in yellow) pass the Teamcenter server validation. In addition, the master form of the routine revision with which the DPV Excel Engineering dataset is associated is updated with information about the validation. For more information, see View Teamcenter server validation status. the following: If the server validation fails, the routine data cannot be sent to client applications, such as DPV ETL, DPV Reporting & Analysis, and DPV-SSAS. Teamcenter server validation is always performed during a workflow process. The date and time validation of routine revisions created before 9.0 is blank. Therefore, they are sent to client applications even if they have errors. To change this, associate the routine revisions created before 9.0 with a rule set using the Apply Rule Set command. Then, open or save the dataset. The server validation automatically runs and the master form of the routine revision is updated. DPV rule set validation The default DPV rule set provided ensures the following about the feature data in a DPV Excel Engineering workbook: Feature name The feature name is unique. The feature name is a maximum length of 32 characters. The feature name is an alphanumeric string. All characters are allowed except:, < > \ / # ( ) { } [ ] : ; * ^ % Feature ID Feature IDs are automatically generated, and the Feature ID column is read only (cannot be edited). Feature IDs are unique within a given routine. Numeric fields The following fields must be in numeric or empty elements (required fields cannot be blank). o In the Feature Info worksheet: x, y, z, i, j, k, i2, j2, k2, Significance, and Nominal. PLM00151 H Dimensional Planning and Validation Administration Guide 2-61

78 Chapter 2 Defining quality inspection process i, j, k, i2, j2, k2 - No warning is issued when any of these fields are blank. x, y, z A warning is issued if any of these fields are blank. o In the specification set code worksheets: LSL, TAR, and USL. If all the fields (LSL, TAR, USL) are blank, then no warning is issued, o Otherwise, if any one or two of the fields are blank, there is a warning. String-based numbers (for example, 1.000) used in releases before the DPV 9.0 release are supported but are converted to a number when data is sent to client applications, such as DPV Reporting & Analysis, DPV Device Client, and DPV-SSAS. Consistency of data between worksheets The following error and warnings occur for inconsistent data between the Feature Info, specification, and feature mapping worksheets: Errors o There are feature labels in the specification or feature mapping worksheets that are not in the Feature Info worksheet. In the feature mapping worksheets, only features of the dataset s routine revision are verified. o There are attribute codes in the specification worksheets that are not in the Feature Info worksheet. Warnings o There are feature labels in the Feature Info worksheet that are not in one or more of the specification set code worksheets. o There are attribute codes in the Feature Info worksheet that are not in one or more of the specification set code sheets. Required fields Error messages appear if any of the following are not entered or are incorrect. o All header information in the Feature Info, specification set code, and feature mapping worksheets. o Feature information worksheet: Attribute code values in header rows Feature ID Feature label o Specification set code worksheet: Attribute code values in header rows. If there is an attribute code header column, it must have all values. However, not all attribute codes in the feature info sheet need to be in specification set code sheets. However, it is recommended that the same codes be in both worksheets Dimensional Planning and Validation Administration Guide PLM00151 H

79 Defining quality inspection process Feature label o Feature mapping worksheet: All columns and their headers are validated but only the Feature Label (the first column) is validated for whether it exists in the Feature Info worksheet. Feature label header Routine ID of referenced routine o Adding and deleting features When you delete or rename a feature in the Feature Info worksheet, the DPV rule set does not add, remove, or rearrange the content of any existing valid specification set code sheets. Any corresponding errors or warnings are marked only on the existing cells. Adding worksheets and comments o Adding a specification sheet When you add a new specification sheet, the header rows, including the attribute code names, and all the feature labels from the Feature Info sheet are automatically added. The LSL, TAR, and USL files are left blank and no default values are entered. The list of available names for specification worksheets in the Discrepancy worksheet cannot be edited. Users with access to creating rule sets can modify the macro that defines the specification set code names in the rule set and change the list of specification names. When a user adds a sheet and its name is in the list, the sheet is treated as a specification worksheet. Otherwise, it is treated as a comment worksheet unless it is a Feature Info or feature mapping worksheet. A specification set code name can be up to 26 characters. It cannot contain the following characters:, < > \ / # ( ) { } [ ] : ; * ^ % For more information about modifying the default DPV rules set, see Create a custom DPV validation rule set. o o Comment columns You can add columns to the feature information sheet after the last feature attribute columns. These are treated as comments. No system action is taken on these comment columns (for example, they are not visible in any application except Excel). If you attempt to add a comment column before the last feature attribute column, it is flagged as an error. Comment worksheets You add additional worksheets to the DPV Excel Engineering workbook for storing comments. Deleting columns PLM00151 H Dimensional Planning and Validation Administration Guide 2-63

80 Chapter 2 Defining quality inspection process Users cannot remove required columns. Required columns for the Feature Info worksheet o o o o o o o o o o Feature ID Feature Label Feature Type Alt Ftr Label Feature Description Active Status Need Loading Split Id x, y, z, i, j, k, i2, j2, k2 Under attribute code in the Feature Info worksheet: Significance Measurement Need Nominal Required columns for a specification worksheet o o Feature Label Under attribute code in the specification sheet: LSL TAR USL Required columns for a feature mapping worksheet o o Feature Label column for routine Feature Label column for referenced routine. Working with DPV validation errors As you edit a DPV Excel Engineering workbook with rules validation activated, any errors are displayed in the cells Dimensional Planning and Validation Administration Guide PLM00151 H

81 Defining quality inspection process Errors shown in cells Any problems with the feature data are highlighted in the cells of the workbook. Errors are highlighted in red and warnings in yellow. In addition, comments may appear next to the cell explaining the error. Any warnings in the workbook pass the Teamcenter server validation. Errors shown in discrepancy worksheets In addition to displaying errors in cells, the validation rule sets create discrepancy worksheets to display validation errors: The default rule set that Siemens PLM Software provides creates a worksheet called Discrepancy to display any default validation errors, such as you entered a name that contains characters that are not allowed. A custom rule set creates a worksheet (usually named User Discrepancy) to display custom validation errors, such as you entered a name that is inconsistent with your company s standards. The following is an example of possible errors shown in the Discrepancy worksheet. Clicking a cell in a discrepancy worksheet places the cursor in the cell with the error so you can correct it. When you correct the error, its corresponding entry is deleted from the discrepancy worksheet. Configure Excel for DPV rules validation 1. Depending on your version of Microsoft Office, access the Excel Options dialog box. PLM00151 H Dimensional Planning and Validation Administration Guide 2-65

82 Chapter 2 Defining quality inspection process Example In Excel 2003, click the Microsoft Office button ( Excel Options. ) and click 2. On the left, click Customize Ribbon and make sure Add-Ins is in your list of displayed tabs. If it is not, add it and click OK. 3. On the left, click Trust Center and then click Trust Center Settings. 4. In the Trust Center dialog box, click Macro Settings. 5. Select Enable all macros. 6. Under Developer Macro Settings, select Trust access to the VBA project object model. 7. Click OK and then click OK again. Run DPV rule set static and runtime validations After opening a DPV Engineering Excel workbook for feature definition, you must run static validations of the entire workbook. After running static validations, you can toggle on and off runtime validation, which validates the current cell you are editing. Turning off runtime validation speeds up the entry of multiple cells because you do not have to wait for validation after each entry. that if you turn on runtime validation, you can still quickly copy and paste cells across worksheets because runtime validation only validates the current cell and not the entire workbook. You must first run static validations to turn on runtime validation. The options for running static and runtime validations are available from the Add-Ins menu, which is automatically displayed when you open a DPV Engineering Excel workbook Dimensional Planning and Validation Administration Guide PLM00151 H

83 Defining quality inspection process 1. In Teamcenter, open a DPV Engineering Excel workbook for editing in Excel. The discrepancy worksheets appear. In addition, the associated XLSB rulesets are downloaded to the your XLSTART folder (for example, C:\Users\userid\AppData\Roaming\Microsoft\Excel\XLSTART). 2. From the Add-in menu in Excel, click APPLY XLSB(RULESET). If there are XLSB files associated with the DPV Engineering Excel worksheet, the Static Validations button is enabled. 3. Click Static Validations. After the first run, the Static Validations and Runtime On/Off buttons in the Discrepancy worksheet are disabled. Navigating to another worksheets enables the buttons, as shown when you navigate from the Discrepancy worksheet to the Feature Info worksheet. PLM00151 H Dimensional Planning and Validation Administration Guide 2-67

84 Chapter 2 Defining quality inspection process 4. (Optional) Navigate to another worksheet and toggle Runtime On/Off as you edit the workbook. View Teamcenter server validation status View the status of the validation that the Teamcenter server (not the DPV validation rule set) performed on a DPV Excel Engineering dataset. 1. In My Teamcenter, select the master item revision form for the routine revision with which the DPV Excel Engineering dataset is associated. 2. Click the Viewer tab. The date and time of the last validation and the status of that validation appear. If the date is blank, the Excel Engineering dataset has not been validated. Values for validation status include: Success, Failure, and Not Done. The date and time are the local date and time of the Teamcenter server. The date and time validation of routine revisions created before 9.0 are blank. For more information, see Teamcenter server validation. Associate a routine with a custom DPV validation rule set When you import feature data, it is associated with the default DPV validation rule set and you are prompted to associate the dataset with a custom DPV validation rule set. You can change the custom rule set with which it is associated at any time. You apply the custom rule set to the routine revision with which the workbook is associated Dimensional Planning and Validation Administration Guide PLM00151 H

85 Defining quality inspection process You can only apply a custom rule set to a routine revision to which you have write permission. You often do not have permission to a routine revision that has been released. If the routine revision is released, revise it before using the Apply Rule Set command. 1. In Manufacturing Process Planner, right-click the routine revision with which you want to associate the custom DPV validation rule set, and choose Apply Rule Set. The Apply Rule Set dialog box appears, listing all the custom rule sets available. 2. Select the custom rule set to use for validation of the feature data, and click OK. Learn more about DPV rule set validation. Create a custom DPV validation rule set It is recommended that you create a custom DPV validation rule set. In particular, create a custom rule set to specify the specification set code worksheet names. Then, when a user adds a worksheet and its name is in the list of specification set code worksheets, the sheet is treated as a specification set code worksheet. Otherwise, it is treated as a comment sheet unless it is a Feature Info or feature mapping sheet. A specification set code name can be up to 26 characters. It cannot contain the following characters:, < > \ / # ( ) { } [ ] : ; * ^ % 1. Use the standard Teamcenter functionality (Access Manager and Organization) to set the users who can create custom DPV validation rule sets. 2. Set the Teamcenter DatsetTypesPref preference to include the Dpv0RuleSetDataset value. DatsetTypesPref sets the dataset types that are listed when users choose the System New Dataset command. 3. Create a Microsoft Excel binary workbook (.xlsb) containing the validation macros. 4. In Teamcenter, create an item revision of the type DPV0RuleSet. Learn about types of rule sets. 5. Create a dataset of the type DPV0RuleSetDataset containing the Microsoft Excel binary workbook (.xlsb) associated with the DPV0RuleSet item revision. PLM00151 H Dimensional Planning and Validation Administration Guide 2-69

86 Chapter 2 Defining quality inspection process 6. Release the DPVRuleSet item revision. Once the DPVRuleSet item revision is released, it can be associated with a measurement routine or operation. When you release the custom rule set, it is listed under Specifications. Use the copy action Copy as Object. For more information about releasing routines, see Releasing and revising measurement routines. Teamcenter item types for DPV validation rule sets To differentiate between the default DPV validation rule set that Siemens PLM Software provides and those that you create, they are each defined as different item types in Teamcenter: Default rule set The rule set that Siemens PLM Software provides is of the type Dpv0RuleSiemens. Only one instance of this item type is allowed in a Teamcenter database. This item instance is created by default when creating or upgrading the Teamcenter database to version 9.0 or later. Therefore, no user can create or delete the instance of this item type. The rules in the default rule set are password-protected so they cannot be modified. Custom rule set A rule set that you create is of the item type DPV0RuleSet and the dataset attached to it is an item revision of the type DPV0RuleSetDataset. For more information about modifying or creating a custom DPV rule set, see Create a custom DPV validation rule set Dimensional Planning and Validation Administration Guide PLM00151 H

87 Defining quality inspection process Defining feature data in an Excel Engineering workbook About the sample DPV Excel Engineering workbook The sample Excel Engineering workbook dpvexcel.xlsx that is provided in the dpv_install.zip file of the install kit defines the feature data. Use Excel 2003 or later to edit it. The Excel Engineering workbook sample contains worksheets for defining the features and tolerances and displaying errors and comments: FeatureInfo Worksheet where you enter all the feature-level information and nominal data of the feature attributes. Each row represents a different feature. Each feature can have many feature attributes. ENGG and DML Default set of tolerances (specification set) against which the measurement data will be compared for data collected in ASCII format (ENGG) or Document Markup Language format (DML). It represents engineering tolerances. You can add additional worksheets containing other sets of specifications. The name of the sheet is the same as the specification set. Discrepancy worksheets The default rule set creates a worksheet called Discrepancy to display any validation errors, such as if you entered a name that contains characters that are not allowed. A custom rule set also creates a tab (usually named User Discrepancy) to display custom validation errors, such as if you entered a name that is inconsistent with your company s standards. When you correct errors in the feature data, the corresponding entries are deleted from the Discrepancy and User Discrepancy worksheets. Working with validation errors Comment worksheets You can add comment worksheets or comment columns to the DPV Excel Engineering workbook to assist you in understanding the entered data. Comment columns must be added after all other required columns. PLM00151 H Dimensional Planning and Validation Administration Guide 2-71

88 Chapter 2 Defining quality inspection process Tip Use Excel functionality, such as sorting and filtering, to help you enter and manage the data. Add feature data to a DPV Excel Engineering workbook The sample DPV Excel Engineering workbook dpvexcel.xltx provided in the dpv_install.zip file of the install kit defines feature data. About the sample Excel file. Names of features must be unique within the routine. Tip Use Excel functionality, such as sorting and filtering, to help you enter and manage the data. In addition, to keep the headers visible when scrolling in the worksheet, freeze the pane. Hide rows and columns in the workbook as you need to assist in entering data. All validation rules still work regardless of whether or not the rows and columns are visible. Do not delete required columns. Add comment worksheets or comment columns to the DPV Excel Engineering workbook to assist you in understanding the entered data. Comment columns must be added after all other required columns. 1. Do one of the following: Create a DPV Excel Engineering workbook, create a dataset, and import it into Teamcenter. Use the dpvexcel.xltx sample file located in the dpv_install.zip to get started. Edit an existing DPV Excel Engineering workbook. For the Dimensional Planning and Validation rule set validation to be triggered, you must work with the DPV Excel Engineering workbook inside of Teamcenter. 2. Activate the DPV rule set validation, Learn more about DPV feature data validation. 3. In the FeatureInfo worksheet, fill in the following information to define features and feature attributes. In the Excel column Labeled Do the following Feature-level information 2-72 Dimensional Planning and Validation Administration Guide PLM00151 H

89 Defining quality inspection process In the Excel column Labeled Do the following A Feature ID Leave blank. DPV validation automatically creates it. Used internally by DPV. B Feature Label Enter a name for the feature. Enter only alphanumeric characters. Do not use special characters. The feature name is used for reporting. C Feature Type Specify the feature type used in datum transformation: Point Hole Pin Slot Tab D Alt Feature Label Set an alternative name for the feature for systems that may have length requirements so you can enter another name by which to reference the feature. The alternate feature label is used in the Analysis window in DPV Reporting & Analysis and in DPV Device Client if a feature cannot PLM00151 H Dimensional Planning and Validation Administration Guide 2-73

90 Chapter 2 Defining quality inspection process In the Excel column Labeled Do the following be identified by the feature label. E Feature Description Enter a description for the feature. F Active status Enter whether or not DPV Device Client and DPV Reporting & Analysis should process data for this feature. Enter either: Y Process the data. N Do not process the data. G Need Set what DPV Device Client should do if the feature is not present. H Loading Split ID Enter the Loading Split ID to which this feature should be assigned. Loading Split ID indicates that the data from different loading split IDs should be merged into one event. Learn more about splitting feature data, including an example. If the features are collected in a single event, leave Loading Split ID blank (or empty). There is no limit to the number of files to be merged. Assign each split a different name. For example, Left, Right, Top, Bottom, Middle, and so on Dimensional Planning and Validation Administration Guide PLM00151 H

91 Defining quality inspection process In the Excel column Labeled Do the following I, J, K, L, M, N, O, P, and Q X, Y, Z, I, J, K, I2, J2, and K2 Enter the nominals X, Y, Z, I, J, K, i2, j2, and k2. X, Y, and Z are the anchor point coordinates used in interactive reporting. i, j, and k are the vector normal direction. I2, J2, and K2 are the second vector normal direction for slots. Nominals cannot be the same as the specification limits USL, LSL, and Target. Add specifications. Attribute-level information For each attribute, enter its name under the Attributen header. All child elements of feature nominals are required. If there are no i2, j2, and k2 values, enter the feature nominals with empty elements. PLM00151 H Dimensional Planning and Validation Administration Guide 2-75

92 Chapter 2 Defining quality inspection process In the Excel column Labeled Do the following R (for attribute 1) Significance Enter the significance of the feature attribute: 0 Insignificant 1 Significant If this value is blank, data is not loaded through the extract, translate, and load (ETL) process. S (for attribute 1) Measurement Select how the coordinate measuring machine (CMM) probe measures a point for: Surface - Takes into account the actual vector of the measured geometry. Vector - Takes the nominal vector. DPV Reporting & Analysis uses the information for datum transformation calculations. T (for attribute 1) Need Set what DPV Device Client should do if the attribute is not present. U (for attribute 1) Nominal The ideal nominal value of each attribute. Typically, 0 for deviations. 4. (Optional) Add specifications. 5. Choose File Save. A message appears asking you if you want to save the workbook as a macro-free workbook. 6. Click Yes Dimensional Planning and Validation Administration Guide PLM00151 H

93 Defining quality inspection process Define derived features A derived feature calculates its value from two or more existing features or feature attributes based on a mathematical expression (for example, a derived feature midpoint between two feature attributes could be used to examine variability between the two). The classification accuracy of tolerances based on derived features is typically higher than that of the original features. A derived feature can only have derived feature attributes in it. It cannot have any normal attributes (X_DEV, Y_DEV, and so on). There can be only one derived feature attribute per derived feature. Derived features are not supported when importing feature data through an.xml file. You can only define the derived feature while editing in Excel. Rules for handling mid and reference points. 1. Edit an existing DPV Excel Engineering workbook. 2. To add a derived feature, enter the derived feature name and set its type to Derived in the Feature Type column (column C). This derived feature would not have any normal attributes. It has only derived attributes, as shown in the example: 3. To add a derived attribute, add four columns as if creating a new attribute (a set of four columns: Significance, Measurement Approach, Need, and Nominal.) The columns must be in the order specified. 4. Add a fifth column after Nominal called Expression, as shown in the example. This column would be under the same heading (attribute code merged cell) as the other four columns. 5. Set the attribute code. PLM00151 H Dimensional Planning and Validation Administration Guide 2-77

94 Chapter 2 Defining quality inspection process 6. Type the expression using the feature label and attribute codes, enclosing the attributes in square brackets [], as shown in the example. Example For example, [ftr_1.attr_1]*[ftr_1.attr_2] Separate the feature label and attribute code using a dot. Every feature attribute should be enclosed with square brackets []: [Rout2PlTest1.X_DEV]*[Rout2PlTest2.X_DEV] The mathematical expressions can include the following functions: Adding specification set codes to derived attributes is the same as setting them for a normal attribute. Make sure that the Derived:<att_code> is placed in the header and define the specifications in the appropriate sheet. The function With the symbol add + subtract - divide / multiply * sine sin() cosine cos() tangent tan() inverse sin asin() inverse cosine acos() inverse tangent atan() raise to power n ^n square root sqrt() 2-78 Dimensional Planning and Validation Administration Guide PLM00151 H

95 Defining quality inspection process The function absolute value With the symbol abs() 7. Save the workbook. Rules for derived features of mid and reference points Midpoint expression The syntax to define a midpoint expression is: MID_POINT([FEATURE_NAME],[FEATURE_NAME], I=x.xx,J=x.xx,K=x.xx) Required [FEATURE_NAME],[FEATURE_NAME] Specify the two features for the midpoint. Optional I=x.xx,J=x.xx,K=x.xx Reference point expression REF_POINT([FEATURE_NAME],X=x.xx,Y=x.xx,Z=x.xx, I=x.xx,J=x.xx,K=x.xx) Required Either [FEATURE_NAME] or X=x.xx,Y=x.xx,Z=x.xx X=x.xx,Y=x.xx,Z=x.xx takes precedence over the feature name. Optional Either [FEATURE_NAME] or X=x.xx,Y=x.xx,Z=x.xx I=x.xx,J=x.xx,K=x.xx For a reference point, either the feature name or the X, Y, and Z components must be specified. If X, Y, and Z are specified, they define the reference location; otherwise, a feature name must be specified. If both a feature name and X, Y, and Z are specified, X, Y, and Z take precedence and define the feature location. If either X, Y, or Z are not specified and feature label is specified, the feature label takes precedence. Defining specifications in an Excel spreadsheet About defining specifications in a DPV Excel Engineering workbook Add specification types and limits to feature attributes. Specification types and limits set the deviations that are allowed from the nominal values. You set the specifications within the context of a particular routine. DPV provides the default specifications in the ENGG and DML worksheets in the dpvexcel.xltx sample workbook. You can add additional worksheets containing other sets of specifications. The name of the sheet is the same as the specification set. You can also specify one-sided tolerances so DPV Reporting & Analysis ignores one side when performing PLM00151 H Dimensional Planning and Validation Administration Guide 2-79

96 Chapter 2 Defining quality inspection process Statistical Process Control (SPC) calculations. For more information, see Setting one-sided tolerances. You set user-defined specification codes to define the specification types. DPV Reporting & Analysis and historical reporting (DPV-SSAS) use the codes to determine which specification limits to use when performing SPC calculations. You can change between specification sets in DPV Reporting & Analysis by setting the properties of a result set. If you do not define the specifications, summary calculations on the measurement data on which the specifications are based are not performed. Define specifications in a DPV Excel Engineering workbook Define specifications in a DPV Excel Engineering workbook 1. Do one of the following: Create a DPV Excel Engineering workbook using the dpvexcel.xltx sample file, create a dataset, and upload it to Teamcenter. Edit an existing DPV Excel Engineering workbook. For the DPV rules validation to be triggered, you must work with the workbook though Teamcenter. If you have already created feature and attributes in the DPV Excel Engineering workbook and DPV rule set validation is configured, the worksheet is already populated with the feature and its attributes. All you will need to do is to add the tolerance information. 2. Activate the DPV rule set validation, Learn more about DPV feature data validation. 3. Create or rename a worksheet to define one or more of the following specification limit values. Name the worksheet the name of the type of specification being defined. If you enter a name for the specification worksheet that is not defined in the custom validation rule, the sheet is created as a comment sheet. For more information, see Create a custom DPV validation rule set. Target, LSL, and USL are mandatory fields. LSL and USL can be zero but they cannot be null Dimensional Planning and Validation Administration Guide PLM00151 H

97 Defining quality inspection process Use this column Feature Label To do this Enter the name of the feature to be associated with the specification. If you have already created feature and attributes in the workbook and DPV rule set validation is activated, the worksheet is already populated with the feature name. Attributen LSL Target The label must match the list on the FeatureInfo tab. In the row under this header, enter the name of the attribute. If you have already created feature and attributes in the workbook and DPV rule set validation is activated, the worksheet is already populated with the attributes. Set the lower value for the specification limit. This is a real number. Set the target value. This is a real number. For build-to-normal scenarios, the target value is equal to the nominal. For functional-build scenarios, the target value allows a manufacturing target to be set that differs from the design nominal. The functional build philosophy states that the relationship between parts is important, not the individual parts. Therefore, it is not always necessary to build each part to nominal. Rather, the target value for one part can be matched to the mean value of another. PLM00151 H Dimensional Planning and Validation Administration Guide 2-81

98 Chapter 2 Defining quality inspection process Use this column USL To do this Set the upper value for the specification limit. This is a real number. 4. Choose File Save. A message appears asking you if you want to save the workbook as a macro-free workbook. 5. Click Yes. Setting one-sided tolerances If your result set has one-sided tolerances, you can specify that either the upper (USL) or lower (LSL) specification limits be ignored by entering -1E+08 in the appropriate field in the DPV Excel Engineering worksheet. When you enter -1E+08 as a specification limit, DPV Reporting & Analysis ignores that side of the tolerance when calculating its three outputs: Cpk, Ppk, and the estimated percent out of spec. For example, this would be helpful if you wanted to ignore processes in which lower and upper specifications are unacceptable or are not applicable, such as the one-sided diameter of a hole. The following shows an example of setting USL to -1E+08 for the CN0026 feature and the results that appear in the DPV Reporting & Analysis Analysis window. Defining frozen control limits To better support situations in which your process is tightly controlled and you do not want calculated control limits to appear in in DPV Reporting & Analysis, you can freeze specification limits for individual feature attributes. This option ensures that the DPV Reporting & Analysis uses only those frozen limits and does not recalculate limits for every new query or data source update Dimensional Planning and Validation Administration Guide PLM00151 H

99 Defining quality inspection process In the DPV Excel Engineering workbook, add the following workbook worksheets to contain the control limits for specific feature attributes. Workbook sheet label Type of chart for which this sheet freezes limits R_CL X-Bar and R XBar X_CL X-Bar and R Range IMR_L I-MR IBar Area of the chart to which frozen limits apply IMR_R I-MR Moving Range The frozen worksheet labels appear as specification limit types in the Spec Limit list in the Analysis window: The following is an example of a workbook with the worksheets and a limit set for a feature attribute of CN26. Defining feature data in an.xml file About defining feature data in an.xml file The tasks to define feature data in an.xml file include: Adding feature data to an.xml file. Importing feature data from an.xml file. PLM00151 H Dimensional Planning and Validation Administration Guide 2-83

100 Chapter 2 Defining quality inspection process Tip You can also define custom feature attributes. Add feature data to an.xml file Using the table of XML elements for reference, add the elements and attributes to an.xml file to define feature data. A template is available in the dpv_install.zip file in the DPV install kit. This sample.xml file contains three features. The first two features already exist in Teamcenter (they have a non-blank IDs) and are being modified, while the third feature is being added (its ID is blank). The second feature defines attributes for Z_DEV, X_ACT, and Y_DEV. The hierarchy of the.xml file is: Routine <routine> tag. Feature <feature> tag. A routine can have zero or more features. Feature nominals <feature_nominals> tag. Only one per feature. Attributes <attribute> tag. A feature has zero or more attributes. Spec limits <tolerance> tag. An attribute has zero or more spec limits. Tip Before starting you may want to define custom feature attributes. 1. Create an.xml file in an XML or text editor. Enter the following, which acts as a container for the feature data and is common for any.xml file. <?xml version= 1.0 encoding=utf-8?> <engineering_data version= 1.0 > </engineering_data> 2. Within engineering_data, add the routine element. <?xml version= 1.0 encoding=utf-8?> <engineering_data version= 1.0 > <! -Add routine element here- > </engineering_data> A routine is identified by its item ID (id), name (name), and revision (version). For a detailed explanation, see the table of XML elements. The routine element helps you manage the.xml file. It tells you which routine the feature data belongs to. It does not perform any real function. Example <routine id="000036" name="routineg1_1" version="a"> </routine> 3. Within the routine element, add the feature data. <?xml version= 1.0 encoding=utf-8?> <engineering_data version= 1.0 > <routine id="000036" name="routineg1_1" version="a"> 2-84 Dimensional Planning and Validation Administration Guide PLM00151 H

101 Defining quality inspection process <! -Add feature data here- > </routine> </engineering_data> Feature data consists of feature elements one element for every feature to be added to the routine. Each feature has properties (name, alternate name, type, status, need, description, and loading split ID) that are attributes of the feature element. For a detailed explanation, see the table of XML elements. Example <feature name="featg2" alternate_name="g2" type="slot" status="active" need="optional" description="another feat" loading_split_id="value"> 4. Within the feature element, add feature content. <?xml version= 1.0 encoding=utf-8?> <engineering_data version= 1.0 > <routine id="000036" name="routineg1_1" version="a"> <feature name="featg2" alternate_name="g2" type="slot" status="active" need="optional" description="another feat" loading_split_id="value"> <! -Add feature content here- > </feature> </routine> </engineering_data> Feature content consists of feature nominals and attributes, which have tolerances. Feature nominals Feature nominals consist of X, Y, Z, I, J, K, I2, J2, and K2. For a detailed explanation, see the table of XML elements. Example <feature_nominals> <x>0</x> <y>0</y> <z>0</z> <i>0</i> <j>0</j> <k>0</k> <i2>0</i2> <j2>0</j2> <k2>0</k2> </feature_nominals> PLM00151 H Dimensional Planning and Validation Administration Guide 2-85

102 Chapter 2 Defining quality inspection process All child elements of feature nominals are required. If there are no i2, j2 and k2 values, enter the feature nominals with empty elements as follows: <feature_nominals> <x>0</x> <y>0</y> <z>0</z> <i>0</i> <j>0</j> <k>0</k> <i2></i2> <j2></j2> <k2></k2> </feature_nominals> Feature attributes Each feature has a set of attributes. Each attribute is captured as an attribute element. The attribute properties include type, significance, need, measurement approach, and nominal, which appear as attributes of the element. For a detailed explanation, see the table of XML elements. Tip Example You can define custom feature attributes. <attribute type="x_act" significance="value" need="optional" measurement_approach="value" nominal="9.0"> </attribute> Tolerance Each attribute has a set of specifications defined. Each specification is defined using a tolerance element. For a detailed explanation, see the table of XML elements. The tolerance element has spec_set_code as an attribute, indicating the name of the specification set. The USL, LSL, and target are captured as child elements. Example <tolerance spec_set_code="engg"> <usl>1.2</usl> <lsl>2.1</lsl> <target>0</target> </tolerance> 5. Repeat this process to add as many tolerances to the attribute, as many attributes to the feature, and as many features to the routine as required Dimensional Planning and Validation Administration Guide PLM00151 H

103 Defining quality inspection process Table of XML elements Although some of the values in the elements are optional (for example, i2, j2, k2), you should keep the values in the.xml file. Leave them blank if you do not want to use them. Use this element With these attributes To do this engineering_data version Identify the version of the engineering format data schema. Do not change the value. routine feature The routine information helps you track the routine to which the.xml file belongs. It performs no real function. The actual routine information is obtained from the Manufacturing Process Planner when you import the.xml file. id name version name alternate_name Provide an identifier to define the routine. Identify the routine. Provide the application version persistent identifier used to find the routine in the Teamcenter database. Identify the feature. Enter only alphanumeric characters. Do not use special characters. The feature name is used for reporting. Provide an alternative name for systems that have length requirements so you can enter another name by which to reference the feature. PLM00151 H Dimensional Planning and Validation Administration Guide 2-87

104 Chapter 2 Defining quality inspection process Use this element With these attributes To do this type The alternate feature label is used in the Analysis window in DPV Reporting & Analysis and in DPV Device Client if a feature cannot be identified by the feature label. Specify the type of feature: Point Hole Pin Slot status description need Tab Indicate whether or not the feature is active or inactive. An inactive feature does not show up in queries even if there is data for the feature. It is also excluded from summary calculations. Values are: Y - Process the data. N - Do not process the data. Provide a description of the feature. Set what DPV Device Client should do if the feature is not present Dimensional Planning and Validation Administration Guide PLM00151 H

105 Defining quality inspection process Use this element With these attributes To do this feature (continued) loading_split_id Enter the loading split ID to which this feature should be assigned. loading_split_id is used when data for a routine is not collected in a single file but in several. You can merge the files into one event stored in the Teamcenter measurement database. Learn more about defining split events, including an example. If the features are collected in a single event, leave loading_split_id blank (or empty). attribute type significance measurement_ approach There is no limit to the number of files to be merged. Assign each split a different name. For example, Left, Right, Top, Bottom, Middle, and so on. Enter the attribute code. Enter the significance of the feature attribute: 0 Insignificant 1 Significant Select how the coordinate measuring machine (CMM) probe measures a point for: Surface Takes into account the actual vector of the measured geometry. Vector Takes the nominal vector. DPV Reporting & Analysis uses the information for PLM00151 H Dimensional Planning and Validation Administration Guide 2-89

106 Chapter 2 Defining quality inspection process Use this element With these attributes To do this tolerance need nominal spec_set_code datum transformation calculations. Set what DPV Device Client should do if the feature is not present. Specify the nominal value for the attribute. This is a real number. Enter a character string to define the type of specification. Enter any string for the specification. that if you make a typographical error, it defines a new specification code. feature_nominals All values are real numbers. All feature nominal attributes are case sensitive. You must enter them as lowercase. Although some of the usl lsl target x y z I j k About defining specifications in a DPV Excel Engineering workbook. Specify the upper value for the spec limit. A real number. Specify the lower value for the spec limit. A real number. Specify the target value. A real number. Specify the nominal value for the feature. Specify the nominal value for the feature. Specify the nominal value for the feature. Specify the nominal value for the feature. Specify the nominal value for the feature. Specify the nominal value for the feature Dimensional Planning and Validation Administration Guide PLM00151 H

107 Defining quality inspection process Use this element With these attributes To do this values in the elements are optional (for example, i2, j2, k2), you should keep the values in the.xml file. Leave them blank if you do not want to use them. <feature_ nominals> <x>0</x> <y>0</y> <z>0</z> <i>0</i> <j>0</j> <k>0</k> <i2></i2> <j2></j2> <k2></k2> </feature_ nominals> i2 j2 k2 Specify the nominal value for the feature. Specify the nominal value for the feature. Specify the nominal value for the feature. Example.xml file The sample.xml file contains three features. The first two features already exist in Teamcenter (they have a non-blank IDs) and are being modified, while the third feature is being added (its ID is blank). The second feature defines attributes for Z_DEV, X_ACT, and Y_DEV. Managing feature data files Create a dataset and import feature data Create a DPVExcel dataset to store the feature data. As you create the dataset, you can optionally import a DPV Excel Engineering workbook containing the data. There is only one dataset for a routine. 1. In the Manufacturing Process Planner, click the tab associated with the process structure. 2. Select the routine for which you want to create the dataset. 3. Choose File New Dataset. 4. From the Type list, select DPVExcel. PLM00151 H Dimensional Planning and Validation Administration Guide 2-91

108 Chapter 2 Defining quality inspection process 5. Assign a name and description to the dataset. 6. Import a DPV Excel Engineering workbook containing feature data by doing the following: a. Next to the Import box, click Browse. b. Browse for the file and click OK. c. Click OK. d. (Optional) Associate the dataset with a custom rule set. Upload feature data into an existing DPVExcel dataset Places the uploaded feature data into an existing DPVExcel dataset. You must save the DPV Excel Engineering workbook as an.xslx file before you can upload it. 1. In Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, right-click the existing data set associated with the routine, and choose Named References. 4. In the Named References dialog box, choose Upload. 5. Browse for the DPV Excel Engineering workbook and click Upload. Import feature data from XML You can import an.xml file containing feature data. Teamcenter creates a DPVExcel dataset to store the data in the DPV Excel Engineering format. It associates the dataset it creates with a DPV validation rule set. If no DPV validation rule set is available, the DPV Excel Engineering dataset is not added to the routine revision and an error message appears. 1. In Manufacturing Process Planner, select the routine revision with which you want to associate the feature data. Do not select the routine revision on the Attachments page. 2. Choose Tools Import Feature Data. The Import Feature Data dialog box appears Dimensional Planning and Validation Administration Guide PLM00151 H

109 Defining quality inspection process 3. Assign a name and description to the dataset. 4. Enter the location and name of the file (.xml). Click to browse for the file. 5. Select a rule set to associate with the dataset. 6. Click OK. Add feature data to an.xml file Defining feature data in an Excel Engineering workbook About DPV feature data validation Edit an existing Excel Engineering dataset Tip Use Excel functionality, such as sorting and filtering, to help you enter and manage the data. In addition, set freeze pane to keep the headers visible when scrolling in the worksheet. 1. In Manufacturing Process Planner, click the tab associated with the process structure (bill of process). 2. Right-click the process, and choose Open with Attachments. The Attachment view appears. 3. In the Attachments view, double-click the DPV Excel Engineering dataset. 4. Activate the DPV rule set validation, Learn more about DPV feature data validation. 5. Edit the dataset. 6. Choose File Save. A message appears asking you if you want to save the workbook as a macro-free workbook. PLM00151 H Dimensional Planning and Validation Administration Guide 2-93

110 Chapter 2 Defining quality inspection process 7. Click Yes. Feature item types The following types are available for features: Point Feature Hole Pin Slot Tab Defining if a feature or feature attribute is needed The following table explains the options you can set for need in the DPV feature data definition. If set to Required Planned Optional DPV Device Client does the following Creates a load error when the feature or feature attribute is not present. Creates a warning when the feature or feature attribute is not present, but marks the loading of the data as successful. Does not generate a warning if the feature or feature attribute is not present, and marks the loading of the data as successful. You can change how DPV Device Client handles the planned data. Defining split events Often feature data for a routine is not collected in a single file but in several. You can merge the files into one event that is stored in the Teamcenter measurement database. In the DPV Excel Engineering workbook and the XML feature data, a loading split ID represents the events (loading splits) that should be merged into one event. Data about the split event is not available in reports or DPV-SSAS until all the required split event data is in the Teamcenter measurement database. You can, however, use DPV Reporting & Analysis to query and view event data before it is all collected by setting the Event Type parameter to H in the Query list Dimensional Planning and Validation Administration Guide PLM00151 H

111 Defining quality inspection process Example If the left side of a car is stored in one file and the right side in a separate file, enter the following for split level ID: LeftSide for all features that are part of the left side. RightSide for those belonging to the right side. Because these are the only two groups of measurements to be merged, each feature belongs to either LeftSide or RightSide (there should be no features without a loading split ID). When the extract, translate, and load (ETL) processing encounters a split event, it stores the data for the side received first into the Teamcenter measurement database. When the other side is measured, its data is merged into the data for the first side. There is no limit to the number of files to be merged. Assign each split a different name. For example, Left, Right, Top, Bottom, Middle, and so on. There is no limit to the number of files to be merged. Assign each split a different name. For example, Left, Right, Top, Bottom, Middle, and so on. The ETL process is not sensitive to the actual characters used. A threshold set in the DPV Configuration Explorer to define how extra feature attributes are handled applies to split events. If a measurement data job arrives with extra feature attributes, the number of feature attributes used to determine the percentage of the threshold is based on the split in the DPV Engineering Excel workbook. For example, if the job is a LH job, the number of feature attributes used to determine percentage calculation for the threshold is defined by the LH feature attributes in the workbook. Standard attribute codes Attribute code AB AN ANGLE AV Co COA DEV DFLT DIA DS D_DEV Description Angle between Angularity Angle Parallelism Concentricity Coaxiality Deviation Default attribute Diameter Distance Dia deviation PLM00151 H Dimensional Planning and Validation Administration Guide 2-95

112 Chapter 2 Defining quality inspection process Attribute code Description FLDIF Flush difference FLS Flush FLT Flatness FPS Feet per second GAP Gap HEI Height IRLCL IMR R Low Cont Lim IRUCL IMR R Up Cont Lim IXLCL IMR X Low Cont Lim IXUCL IMR X Up Cont Lim LCL Lower Control Limit LEN Length LO Location LSL Lower spec Limit MS1 Miscellaneous 1 MS2 Miscellaneous 2 MS3 Miscellaneous 3 MS4 Miscellaneous 4 PA Polar angle PD Dia prep to pin PER Perpendicularity POR Polar radius PR Profile RAD Radius RN Roundness RO Runout RS Dev surface report RT Dev approach vector S2S Side-to-side diff SM Seal margin STR Straightness SV Dev surface vector TPS True position spec T_NOM Target value UCL Upper control limit USL Upper spec limit 2-96 Dimensional Planning and Validation Administration Guide PLM00151 H

113 Defining quality inspection process Attribute code VIS WID XRLCL XRUCL XXLCL XXUCL X_ACT X_DEV Y_ACT Y_DEV Z_ACT Z_DEV NX NY NZ I J K Description Visual check Width Xbar R low cont lim Xbar R up cont lim Xbar X low cont lim Xbar X up cont lim X actual location X direction deviation Y actual location Y direction deviation Z actual location Z direction deviation NX NY NZ I J K Generating engineering data from measurement data Generating engineering data from measurement data DPV users and administrators can use the XML Generation stand-alone utility to generate engineering data from a measurement data file. The result is an Excel Engineering workbook with all the engineering data from the data file. The XML Generation utility is installed when you install DPV Device Client. To generate an Engineering Excel workbook, you must enter the following files: Measurement data file Parsing script (Optional) Common code script You can also enter the following, if required: Plant, device, and routine configuration files Encoding Attribute rules XML file PLM00151 H Dimensional Planning and Validation Administration Guide 2-97

114 Chapter 2 Defining quality inspection process Generate engineering data 1. From the Start menu, choose All Programs Factory Link XML Generation Utility. 2. In the Select Measurement Data File box, enter the path to the data file from which the Engineering Excel workbook will be created. 3. In the Select Parsing Script box, enter the path to the parsing script for the selected data file. The parsing script is compiled internally and the data is parsed using the methods in this parsing script. 4. (Optional) In the Select Common Script box, enter the path to the common code script for the selected data file. 5. (Optional) In the Optional inputs section of the XML Generation Utility dialog box, enter the following: Routine, Device, or Plant Configuration files These are input script parameters for the parsing script. These configurations files are extracted from Teamcenter and are in the folder on the ETL server: DPVRoutine/ DPVDevice folders in the %flapp%/dpv folder. Encoding This input is required only for data files of type PCDMIS 3.1. This file has special characters, such as NOME DA PEÇA, SÉRIE, NÚMERO, and so on. To correctly read and parse this file, encoding should be set to UTF7 either in the device configuration file or through this input. If the encoding is not set, these special characters cannot be read and are interpreted incorrectly Dimensional Planning and Validation Administration Guide PLM00151 H

115 Defining quality inspection process Attribute Rules XML This is required only if the feature attributes are not listed separately in the data file and are instead embedded in the feature name. To extract the feature attribute code from the feature name these rules will be applied. For more information on attribute rules XML file, see Working with the attribute rules XML file. 6. Click Generate Engineering XML. Defining custom feature attributes Defining custom feature attributes Dimensional Planning and Validation provides a standard set of feature attributes. You can also add feature attributes to match your company s measurement data or modify existing ones: About adding feature attributes and rules Add the custom feature attribute to the routine definition (Optional) Add the feature attributes to the list of values in Business Modeler IDE (Optional) Work with the attribute rules XML file Set the default attribute (DFLT) handling About adding custom feature attributes and rules To add custom feature attributes and rules, do the following as shown in the figure: 1. Add the new feature attribute to the routine definition in Teamcenter. The routine contains a list of all the valid attribute codes for that particular routine. DPV Device Client uses this list during the validation task (DPV Validate) to verify the measurement data that it gets from the parser task (DPV Parser). 2. (Optional) Add the new attribute to the DPV List of Values (LOV) through the Business Modeler IDE (Integrated Development Environment), a tool for configuring and extending Teamcenter. This is required only if you want the attribute code to be transformed to its abbreviation when a user queries for it in DPV Reporting & Analysis. 3. (Optional) Define a rule to extract the feature attribute data from the measurement file. If your custom attribute name is not explicitly specified in the raw data measurement file, you need to create a rule in the attribute rules XML file to specify how to extract it. For example, if its name is contained within the feature label, you need to define a rule that specifies how to extract it. You can easily read and modify the attribute rules XML file using the Attribute Rules XML Editor. PLM00151 H Dimensional Planning and Validation Administration Guide 2-99

116 Chapter 2 Defining quality inspection process 4. (Optional) Place the updated attribute rules XML file on a server that can be accessed by various DPV Device Client servers in the deployment. The location of the attribute rules XML file was specified during the installation of DPV Device Client. You can change it using the DPV Device Client Configuration Editor. DPV Parser reads the raw measurement data file using the device-specific parsing script. This data is then passed in a common XML format (DML) to DPV Validate for validation of data. The correct data, including the new attribute, is inserted into the SQL database. From there, DPV Reporting & Analysis and Teamcenter community collaboration access the data for viewing and analysis. You may need to modify the associated parsing script to correctly parse the new attribute type. For filtering in the DPV-SQL Server Analysis Services (DPV-SSAS) and SQL Server Reporting Services (SSRS), clusters must be created in DPV-SSAS and SSRS. 5. Restart DPV Device Client Dimensional Planning and Validation Administration Guide PLM00151 H

117 Defining quality inspection process Add the custom feature attribute to the routine definition As described in Adding features, add the new feature attribute to the definition of the routine in Teamcenter. The process is the same as for adding a standard attribute code: 1. Open the Excel Engineering workbook associated with the routine, and add the custom feature attribute definition to it as you would any standard attribute. 2. Export the measurement routine definition to DPV Device Client. (Optional) Add the feature attributes to the list of values in Business Modeler IDE If you want the attribute code to be transformed to its abbreviation in DPV Reporting & Analysis, add the new feature attributes to the DPV list of values (LOV). If you do not require this transformation, you do not need to add the attribute code to the LOV. Example To transform the attribute code X_DEV to its abbreviation X in DPV Reporting & Analysis, create a value in the LOV made up of its code and abbreviation separated by a ~ character (X_DEV~X). When the data in the data file comes in as X_DEV, it is transformed to X when sent to DPV Reporting & Analysis in a query. For more information about using the Business Modeler IDE, see the Business Modeler IDE Guide. Start the Business Modeler IDE and create a new project 1. Click Start and choose Programs Teamcenterxxx Business Modeler IDE. 2. Choose File New Project. 3. In the New Project wizard, expand Business Modeler IDE and select New Business Modeler IDE Template. 4. Click Next. 5. Type a Project Name, for example, AddNewFtrAttrtoLOV. 6. Click Next. 7. In the Prefix box, type a prefix to use for the project. This prefix is placed on every data model item you create to identify it as belonging to this project. 8. Next to the Dependent templates directory box, click Browse and browse for the following location containing the Dimensional Planning and Validation templates, where xxx is the version of Teamcenter: install_dir/program Files/Siemens/Teamcenter/Tcxxx/bmide/templates 9. Click OK. 10. In the Dependent Templates pane, select the following templates: Foundation PLM00151 H Dimensional Planning and Validation Administration Guide 2-101

118 Chapter 2 Defining quality inspection process Customization for em-server Integration Database Configuration for DPV 11. Click Finish. The templates load. This may take a while. Add a value to the LOV 1. Access the Business Modeler IDE perspective by choosing Window Open Perspective Other Business Modeler IDE. 2. In the Extensions view, expand the project you just created until you see the LOV folders displayed. 3. Double-click DPVFtrAttCode. The LOV appears. All its values appear in the Details view. 4. To the right of the value table, click Add. 5. In the Add LOV Value dialog box, in the Value box, type a value and its abbreviation separated by a ~ character. Example To define New Width, with the value NWID and the abbreviation NW, enter NWID~NW. 6. Click Finish. Save the project and deploy it to Teamcenter 1. Choose File Save Data Model and click OK. 2. Set the following, if necessary: Ensure that the Teamcenter server is running and that the BMIDE_ALLOW_DEPLOYMENT_FROM_CLIENT preference on the server is set to TRUE, which is the default. To access preferences in the My Teamcenter application within the Teamcenter rich client, choose Edit Options and at the bottom of the Options dialog box, click Index. Define a server connection profile, which specifies the Teamcenter servers to connect to: a. Choose Window Preferences. b. In the Preferences dialog box, choose Teamcenter Server Connection Profiles. c. Click Add. The Teamcenter Repository Connection wizard runs. d. Enter the required values and select OK Dimensional Planning and Validation Administration Guide PLM00151 H

119 Defining quality inspection process 3. Select the project in a view and on the main toolbar, click the Deploy Template button. The Deploy wizard runs. 4. From the Server Connection Profiles box, choose the server to which to deploy the extensions to. 5. Change any information and enter the password to access the server. 6. Click Finish. (Optional) Creating rules to extract feature attribute names (Optional) About creating attribute rules The attribute rules XML file contains a list of rules that specify how to determine attribute codes if they are not explicitly specified in the raw data measurement file. For example, if the measurement file does not contain an entry for the feature attribute name (FeatureAttributeType) but instead incorporates the name into its alternative feature label (AltFeatureLbl), you must create a rule that specifies how to extract the name from the feature label. Define the rules Specify the location of the attribute rules XML file Rule conditions Syntax of the attribute rules XML file Define the rules Use the Attribute Rule XML Editor to define the rules for the attribute rules XML file. The default attribute rules XML file is included with the Dimensional Planning and Validation installation. The sequence of the rules is important. They are in top to bottom priority, with the first rules taking precedence. For example, if you have the following two rules in this order: <Rule condition="chars" Position="2" conditionkey="d" atribute_code="dim" /> <Rule condition="chars" Position="1" conditionkey="d" atribute_code="dos" /> Then if a feature label contains a D in both its second and first positions, it will be interpreted as having the attribute code DIM and not DOS. If you reversed the order, then it would be interpreted as DOS. 1. Choose Start All Programs FactoryLink Launch Attribute Rules XML Editor. PLM00151 H Dimensional Planning and Validation Administration Guide 2-103

120 Chapter 2 Defining quality inspection process 2. Type the path and name of the attribute rules XML file, or click Browse to search for a file. Tip A scroll bar on the right lets you scroll through the file. The arrows on the right change the sequence of the rules. 3. Set the values for the new rule using the Condition, Condition Key, and Attribute Code options. For more information about syntax, see Rule conditions. 4. Click Insert Above, Insert Below, or Insert Last to insert the rule into the attribute rules XML file. Tip To Delete a rule Change the sequence of rules Modify existing rule Do the following Select the rule to be deleted and click Delete Selected. Select the rule to be moved and click an arrow on the right. Select the rule to be modified, change the desired value, and click Modify Existing. 5. Click Save to save the attribute rules XML file. The Attribute Rule XML Editor checks to verify that the conditions for the rule are correct. If they are not, a warning message appears listing the errors Dimensional Planning and Validation Administration Guide PLM00151 H

121 Defining quality inspection process and the invalid rules are highlighted in yellow. You cannot save the file until the errors are corrected. For more information on syntax, see Syntax of the attribute rules XML file. 6. Restart the DPV Device Client. You must restart DPV Device Client because DPV Parser reads the XML in to memory only at startup. Any changes made to the XML will be applied only after a restart. Specify the location of the attribute rules XML file The location of the attribute rules XML file was specified during the installation of DPV Device Client. You can change it using the DPV Device Client Configuration Editor. DPV Parser accesses and reads the XML from this path at startup. If the access to the XML fails, DPV Parser does not start and logs an error message in its log file, located at flapp\log\dpvparser.log, where flapp is the location of DPV Device Client. Tip You can: Have a different set of rules for each server by placing a different attribute rules XML file on each server where DPV Device Client is deployed. Use the same set of rules across various DPV Device Client servers by placing the attribute rules XML file on a shared location accessible to all the servers. Have the system administrator at the user site do this by creating mapped drives or network shared paths to Windows or UNIX machines. 1. To start Configuration Explorer, on your desktop, click the DPV Device Client Configuration Explorer icon. 2. In the tree structure on the left, under your server branch, expand Dimensional Planning & Validation Device Data Parsing Device Data Parser Configuration. 3. Double-click C:\FLDPV\RawData to open the form. 4. In the Attribute Rules XML File Path box, type the path for the attribute rules XML. PLM00151 H Dimensional Planning and Validation Administration Guide 2-105

122 Chapter 2 Defining quality inspection process Rule conditions The rule conditions used in the attribute rules XML file are: EndsWith Use the EndsWith condition to specify that if the ending (right-most portion) of the feature name in the raw measurement data file matches the string specified in conditionkey, the attribute_code specifies the attribute type for that feature label. Example <Rule condition="endswith" conditionkey="(f/a)" attribute_code="x_dev" /> If the feature name ends in F/A, the feature attribute code is X_DEV. StartsWith Use the StartsWith condition to specify that if the beginning (left-most portion) of the feature name in the raw measurement data file matches the string specified in conditionkey, the attribute_code specifies the attribute type for that feature label. Example <Rule condition="startswith" conditionkey="gap " atribute_code="gap" /> Contains If the feature name starts with GAP, the feature attribute code is GAP. Use the Contains condition to specify that if the feature name in the raw measurement data file matches the string specified in conditionkey, the attribute_code specifies the attribute type for that feature label. Example <Rule condition="contains" conditionkey="(i/o)" atribute_code="y_dev" /> If the feature name contains I/O, the feature attribute code is Y_DEV. Chars Use the Chars condition to specify that if the feature name in the raw measurement data file contains the characters specified in conditionkey in the positions specified in Position, the attribute_code specifies the attribute type for that feature label. <Rule condition="chars" Position="3-5" conditionkey="xxg" atribute_code="s2s" /> If the third through fifth characters in the feature name are XXG, then the feature attribute code is s2s. Syntax of the attribute rules XML file The contents of the attribute rules XML file must conform to the following. If they do not, when you save the file, a warning message appears listing the errors and Dimensional Planning and Validation Administration Guide PLM00151 H

123 Defining quality inspection process yellow highlighting appears on the invalid rules in the Attribute Rule XML Editor. You cannot save the file until the errors are corrected. The value of attribute_code must be no longer than five characters or it is ignored. All rules with the following are ignored: o o o Invalid conditionkeys tags Invalid values under each attribute of the rule No required attributes under the rule. During processing, DPV Parser writes an error message to its log file, located at flapp\log\dpvparser.log, where flapp is the location of DPV Device Client. If a rule condition of Chars is used, the rule must contain a Position tag. The XML must be valid. Set the default attribute (DFLT) handling If an attribute code is not specified in the raw data measurement file for a feature name, DPV Parser determines the attribute code by applying the rules in the attribute rules XML file. If none of the rules apply (no valid attribute code is found even after applying all the rules), the attribute code for that feature name is set to DFLT. You can set an argument in the DPV Device Client Configuration Explorer to fail or pass a file when a DFLT attribute is encountered. The default is to pass the file. 1. To start Configuration Explorer, on your desktop, click the DPV Device Client Configuration Explorer icon. 2. In the tree structure on the left, under your server branch, expand DPV System System Configuration System Configuration Information. 3. Double-click DISMDL Loader FR. 4. In the Program Arguments box, type: FAILDFLT to fail the file if the DFLT attribute is encountered. Entering FAILDFLT means that if the attribute code is not found after applying all the rules in the attribute rules XML file, DPV Device Client fails the data file containing any features with the DFLT attribute. Therefore, if the FAILDFLT argument is set, DPV Parser no longer supports the DFLT attribute. No argument, the default, to process and store the DFLT attribute in the measurement database. This requires no changes. PLM00151 H Dimensional Planning and Validation Administration Guide 2-107

124 Chapter 2 Defining quality inspection process Entering no argument means that the DFLT attribute is processed and stored in the measurement database, as long as the definition of that attribute is present in the routine s definition in Teamcenter (stored in the engineering Excel sheet). Also, as in normal processing, only one occurrence of the attribute is stored in the measurement database. Therefore, if a feature has two DFLT attributes, only one of them is stored in the measurement database. Defining cluster groups About working with clusters and cluster groups You can create cluster groups to combine multiple clusters from different sources and routines. The clusters you create are available to others when they load the data source in DPV Reporting & Analysis. You can also view, compare, and copy cluster groups. For information about creating clusters, see Working with clusters in the DPV Reporting & Analysis online help. When you create a cluster in DPV Reporting & Analysis and save it to Teamcenter, it is saved as an item of type DPVCluster, attached to the inspection device. To remove a cluster from a routine, in Manufacturing Process Planner, select the cluster and select Edit Remove. Revisions and cluster groups When creating revisions of cluster groups, note the following. When creating a new revision of a routine, use the Revise and Relate to Latest option in the Define attached Objects pane for each cluster revision attached to the routine that you want to revise. For clusters that you do not want to revise, leave the copy action as Copy as Reference Dimensional Planning and Validation Administration Guide PLM00151 H

125 Defining quality inspection process For a routine revision, the default copy action for cluster revision attachments is Copy as reference. For more information about revising routines, see Releasing and revising measurement routines. When creating a new revision of a cluster group, use the Relate to Latest option to relate each cluster revision within that cluster group revision to the latest cluster revision or to keep at the current revision level. PLM00151 H Dimensional Planning and Validation Administration Guide 2-109

126 Chapter 2 Defining quality inspection process Use the List Cluster Groups command to copy the clusters and cluster groups to a folder for easy selection for revision and release. For more information, see View cluster groups associated with a routine and Compare cluster group revisions. Create a cluster group The most common and recommended way to create a cluster group is to use DPV Reporting & Analysis and save it to Teamcenter. For information about creating clusters, see Working with clusters in the DPV Reporting & Analysis online help. 1. In My Teamcenter, click Home or the folder where you want to create the cluster group. 2. Choose File Item. 3. Assign a name and description to the item. 4. From Item Type, select DPVCluster Group. 5. Click OK. 6. Collect the clusters of interest by performing a general saved query. 7. Copy and paste the clusters into the cluster group. Use Paste... and the DPVClusterGroupContent relationship type. View cluster groups associated with a routine You can view the cluster groups that a routine s clusters belong to and every revision of those cluster groups. You can also copy the cluster groups to the clipboard so you can place them in a folder where you can release or revise them or add them to another routine. For more information about revising cluster groups, see Revisions and cluster groups. 1. In the Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the routine for which you want to view cluster groups, and choose List Cluster Groups One Revision. The routine must be of the type MEVisInspection, MEHHInspection, MECMMInspection, or MEInspection to use the List Cluster Group command. A list of cluster groups associated with the routine appears, sorted by cluster group revision name. You can view the cluster s name, item and revision IDs, and the release status Dimensional Planning and Validation Administration Guide PLM00151 H

127 Defining quality inspection process Tip To change how the list is sorted, click the header, such as Item ID. To expand the width of a column, double-click its header. 3. (Optional) To copy the cluster group revisions to the clipboard, do one of the following: Click Copy All to copy all revisions to the clipboard. Hold down the Ctrl key (to select non-contiguous groups) or Shift key (to select contiguous groups) and select the desired cluster group revisions in the dialog box and click Copy Selected. Compare cluster group revisions You can compare the cluster groups associated with two different revisions of a routine. You can also copy the cluster groups to the clipboard so you can place them in a folder where you can release or revise them or add them to another routine. For more information about releasing cluster groups, see Revisions and cluster groups. 1. In the Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the revision of a routine against which you want to compare another revision, and choose List Cluster Groups Two Revisions. The routine must be of the type MEVisInspection, MEHHInspection, MECMMInspection, or MEInspection to use the List Cluster Group command. A list of revisions of the routine appear. By default, the revision on which the initially selected revision is based is selected and highlighted in italics bold. PLM00151 H Dimensional Planning and Validation Administration Guide 2-111

128 Chapter 2 Defining quality inspection process Example It you are comparing routine revision E against routine revision C, and revision E was created based on revision C, the following list of revisions appear for you to select, with routine revision C in italics bold. 3. Select the routine revision against which you want to compare the initially selected routine revision, and click OK. The Routine s Cluster Group Revision Report dialog box appears. A blank row in one list indicates that the cluster group in the same row in the second list is not present in that revision of the routine. Highlighting indicates that a cluster group revision contains cluster revisions that are newer than those in the cluster group revision. For example, cluster group revision grp1 contains cluster revision c2, revision A. However, there is a newer revision of c2 (revision B). An asterisk in the report indicates that the cluster group revisions do not match. The E-Report Group revision differs. Tip To change how the list is sorted, click the header, such as Item ID. To expand the width of a column, double-click its header Dimensional Planning and Validation Administration Guide PLM00151 H

129 Defining quality inspection process 4. (Optional) To copy the cluster group revisions to the clipboard, do one of the following: Click Copy All to copy all revisions to the clipboard. Select a cluster group revision in the dialog box and click Copy Selected. Define datum transformations A datum transformation is a subset of features used to reference and identify the deviation of other features relative to itself where fixture setup is difficult, expensive, or impossible. In addition to providing more exact measurement data, datum transformations often reduce the number of required measurement device setups. When you define a datum transformation in Teamcenter, you define it is a dataset on the associated cluster. The dataset is an XML file of the type DPVDatumXForm. Example of a DPVDatumXForm.xml file The hierarchy of the.xml file is: <datumtransform> <primaryfeatures> Primary features <secondaryfeatures> Secondary features <tertiaryfeatures> Tertiary features 1. Create an.xml file in an XML or text editor. Enter the following, which acts as a container for the data transformation. For version, enter the version of Teamcenter currently used. This example shows 8.2. <?xml version="1.0" encoding="utf-8"?> <datumxforms version="tc 8.2"> </datumxforms> 2. Within datumxforms, add the datatransform element. <?xml version="1.0" encoding="utf-8"?> <datumxforms version="tc 8.2"> <! Add datatransform element here > </datumxforms> A datumtransform element has attributes that specify whether or not to use feature vectors and the axes for the primary, secondary, and tertiary datums. For a detailed explanation, see the table of XML elements. Example <datumtransform usefeaturevectors="yes" primaryaxis="x" secondaryaxis="x" tertiaryaxis="x"> 3. Within datumtransform, define the primary, secondary, and tertiary datums and their features. <?xml version="1.0" encoding="utf-8"?> <datumxforms version="tc 8.2"> <datumtransform usefeaturevectors="yes" primaryaxis="x" secondaryaxis="x" tertiaryaxis="x"> <! Add primary, secondary, and tertiary feature elements here > PLM00151 H Dimensional Planning and Validation Administration Guide 2-113

130 Chapter 2 Defining quality inspection process </datumxforms> The primary, secondary, and tertiary consists of the features. For a detailed explanation, see the table of XML elements. Example <Primary Features> <feature id="" x="" y="" z="" i="" j="" k="" i2="" j2="" k2="" offset=""/> For tips and cautions, see the procedure for creating datum transformations in DPV Reporting & Analysis. 4. After creating the.xml file, click the cluster, and choose File New Dataset. 5. Assign a name and description to the dataset. 6. From the Type list, select DPVDatumXForm. Revisions and datum transformations Revisions and datum transformations Because it is a dataset, a datum transformation does not have its own revision control. A revision of the cluster, however, results in the new revision having its own copy of the transformation definition. This new copy can be modified independent of the definition on the previous cluster revision. Example Cluster 1/Revision A > Transformation Definition 1 Transformation Definition 1 does not have any revision control with respect to Cluster 1/Revision A. If Cluster 1/Revision A is revised, Cluster 1/Revision B has a copy of Transformation Definition 1. This can be modified without affecting the definition on the earlier version of the transformation on the cluster s revision A. Cluster 1/Revision B > Transformation Definition 1 This is a copy of Revision A s definition. Modifications here do not affect the Cluster 1/ Revision A s datum transformation definition. Example of a DPVDatumXForm.xml file <?xml version="1.0" encoding="utf-8"?> <datumxforms version="tc 8.2"> <datumtransform usefeaturevectors="yes" primaryaxis="x" secondaryaxis="y" tertiaryaxis=""> <primaryfeatures> <feature id="101" x="1" y="1" z="1" i="1" j="1" k="1" i2="" j2="" k2="" offset="1.2"/> <feature id="102" x="2" y="2" z="2" i="2" j="2" k="2" i2="" j2="" k2="" offset="3.6"/> <feature id="103" x="3" y="3" z="3" i="3" j="3" k="3" i2="" j2="" k2="" offset=""/> </primaryfeatures> <secondaryfeatures> <feature id="202" x="2" y="2" z="2" i="2" j="2" k="2" i2="" j2="" k2="" offset=""/> Dimensional Planning and Validation Administration Guide PLM00151 H

131 Defining quality inspection process <feature id="203" x="3" y="3" z="3" i="3" j="3" k="3" i2="" j2="" k2="" offset=""/> </secondaryfeatures> <tertiaryfeatures> <feature id="301" x="2" y="2" z="2" i="2" j="2" k="2" i2="" j2="" k2="" offset="4.8"/> </tertiaryfeatures> </datumtransform> </datumxforms> Table of XML elements for datum transformations Although some of the values in the elements are optional, you should keep the values in the.xml file. Leave them blank if you do not want to use them. Use this element With these attributes To do this dataxforms version Identify the version of the datum transformation format data schema. Do not change the value. datumtransform usefeaturevectors Specify whether or not to use feature vectors: YES NO primaryaxis Must be uppercase. Specify the primary axis: X Y secondaryaxis Z Specify the secondary axis: X Y tertiaryaxis Z Specify the tertiary axis: X Y Z PLM00151 H Dimensional Planning and Validation Administration Guide 2-115

132 Chapter 2 Defining quality inspection process Use this element With these attributes To do this primaryfeatures secondaryfeatures tertiaryfeatures feature Holder for the primary features Holder for the secondary features Holder for the tertiary features id x y z I j k Identify the feature. Define triggers Attach a trigger form to each routine that needs a graphical report created (called a triggered report) whenever it is processed. For more information, see Administering reports in the DPV help collection. 1. In Manufacturing Process Planner, click the tab associated with the process structure. 2. Right-click the process, and choose Open with Attachments. The Attachments view appears. 3. In the Attachments view, select the routine. 4. Check out and edit the form of the type DPVTriggerConfig. 5. In trigger_reports enter the Boolean flag that specifies whether or not to trigger a report for this routine when a measurement event is received. 6. Set the preference DPV_ccuaservice_url. The value is the URL at which the SSRS Custom Cache Updating Application (CCUA) is hosted. 7. Click OK. Define feature mapping Teamcenter can store the mapping between features across measurement routines so you can compare measurements from different inspection devices (referred to as device compare). The mapping can then be retrieved when queried for in DPV Reporting & Analysis. 1. Review the Excel Engineering datasets belonging to the routines to determine the common features to be mapped Dimensional Planning and Validation Administration Guide PLM00151 H

133 Defining quality inspection process 2. Open the dataset of the first routine. 3. Add a new worksheet with the name FeatureMap and copy the Feature label column from the FeatureInfo worksheet and paste it in the FeatureMap sheet. Example The following shows an example of adding the Feature Label column with three features. 4. In the FeatureMap worksheet, enter the mapping for the different routines in the columns: one column per routine with mapped features: Enter the routine ID and revision in the same row as the Feature Label heading. Enter the feature to which the initial feature is to be mapped in the same row as the initial feature. Separate the routine ID and revision using a ~ character, as shown in the example. Only the feature names are used during the mapping. The attributes are not entered in the mapping worksheet. It is assumed that all the attributes of the respective features are mapped. Example In the following example of an Excel workbook with feature mapping defined, Column A lists the features that belong to the routine associated with this Excel workbook (ExampleRoutine). It has three features: ftr1, ftr2, and ftr3. The Columns B and C list the IDs and revisions of the routines to which these features will be mapped. In the example: ftr1 of ExampleRoutine is mapped to feature5 of the routine with the ID GMO003 and revision 1. ftr2 of ExampleRoutine is mapped to FTRA of the routine with the ID GMO045 and revision 2. PLM00151 H Dimensional Planning and Validation Administration Guide 2-117

134 Chapter 2 Defining quality inspection process There is no mapping for ftr3 in either of these routines. To delete the feature mapping, delete the worksheet or the row of mapping. Associate a product, plant, and bill of process As with any process you create in Manufacturing Process Planner, you must associate a plant to a process structure (bill of process) and a product to a process structure to set up relationships between them. The following is a basic procedure for associating product parts to the process structure with a specific occurrence type. For the latest instructions and more details on how to associate plants, products, and processes, see the Manufacturing Process Planner Guide. 1. Right-click a product revision in the Product tab and choose Copy. 2. Select the Process tab containing the process. 3. Right-click the routine and choose Paste As, as shown in the figure. 4. From the list that appears, choose either relation: Choose MeConsumed MeWorkArea To set up the relation Consumed items for the process. Assigned work area in the operation. The commands available to you are determined by your administrator Dimensional Planning and Validation Administration Guide PLM00151 H

135 Defining quality inspection process Approving measurement routines Releasing and revising measurement routines When you are done editing a measurement routine revision, it is recommended that you release it before using the routine in the inspection process. Releasing a routine and its clusters locks the routine so no changes can be made. Perform the approval process using the Teamcenter workflow engine. For information on how to model and apply a workflow that is suitable for your needs, see the Workflow Designer Guide. Releasing a routine and all its attachments freezes them so no more changes can be made to the features or forms. Until a measurement routine revision is sent through a workflow to DPV Device Client, DPV Device Client continues to use previously sent revision. When a measurement routine revision is sent to DPV Device Client, Teamcenter creates a.plmxml representation of it and manages that file in its vault. DPV Device Client reads the data and processes it. Each measurement routine revision has a unique identifier based on standard Teamcenter functionality. In Teamcenter, the routines themselves are revised, but the features and the features attributes are not under revision control. DPV Device Client may run on a different computer from Teamcenter. The Teamcenter.xml files for released routines are stored in the Teamcenter vault. If there is a communication failure between the DPV Device Client computer and the Teamcenter computer, the updated.plmxml files are not visible until communication is restored. Learn more about revising: Routines Clusters and cluster groups Datum transformations Create a new revision of a routine For basic information about creating a revision of an item in Teamcenter, see the My Teamcenter Guide. You can choose to revise each cluster revision attached to the routine and relate it to the latest item revision. It is recommended that you release and/or revise routines before releasing or revising cluster groups and clusters. 1. In My Teamcenter, select the routine that you want to create a new revision of and choose File Revise. The Revise dialog box appears. 2. (Optional) In the Define the basic information for the new item revision pane, type the name of the new revision. PLM00151 H Dimensional Planning and Validation Administration Guide 2-119

136 Chapter 2 Defining quality inspection process 3. (Optional) Type a description of the revision and choose a unit of measure for the revision. 4. Click Next. The Define additional item revision information pane appears. 5. (Optional) Enter values for the routine revision attributes. 6. Click Next. The Define attached objects pane displays the clusters, cluster groups, forms, and Excel Engineering datasets attached to the routine. Copy as Reference is the default (all changes to the reference copy affect the original object). Clusters are listed under Manifestations. 7. Choose copy options for the objects related to the source revision by clicking the icon to the right of the object in the tree. For clusters, select Revise and Relate to Latest or Copy as Reference. For forms or Excel Engineering datasets, select Copy as Object. The copy options are: Use this option Don t Copy To do this Selectively copy objects from one revision to another. Objects that are designated as Don t Copy appear with a line through them in the Destination tree Dimensional Planning and Validation Administration Guide PLM00151 H

137 Defining quality inspection process Use this option Copy as Object Copy as Reference Relate to Latest Revise and Relate to Latest To do this Create a new object of the same type and relation to the parent object. Objects created by this method are totally independent of the parent object. Therefore, any changes to the copied object are not reflected in the original object. Copied objects appear in bold in the Destination tree and can be renamed. Copy the object as a reference to the original object. All changes to the reference copy affect the original object. The names of attachments that are copied as references cannot be modified. Allow you to relate the selected object to the latest item revision with an Is Represented By relation. Allows you to revise the selected object and relate the new object revision to the latest item revision with an Is Represented By relation. 8. Click Next. The Select open option and alternate id display option pane appears. 9. (Optional) Set the open, display, or checkout option for the new revision. 10. Click Finish. The new revision is created as a copy of the previous revision object. 11. (Optional) Create revisions of cluster and cluster groups. Tip Use the Compare Cluster command to copy the clusters and cluster groups to a folder for easy selection for revision and release. For more information, see View cluster groups associated with a routine and Compare cluster group revisions. Exporting to the DPV Device Client About exporting to the DPV Device Client After you define the inspection process, you export the objects to the DPV Device Client for processing: Export the measurement routine to the DPV Device Client PLM00151 H Dimensional Planning and Validation Administration Guide 2-121

138 Chapter 2 Defining quality inspection process Export the inspection device to the DPV Device Client Export the plant to the DPV Device Client Check for exported objects. Export the measurement routine to the DPV Device Client After you define the measurement routine and configured the DPV Device Client, you export the routine to the DPV Device Client for processing. 1. In Teamcenter, send the bill of process to Manufacturing Process Planner. 2. Select the routine to export (for example, MEInspection or MEVISInspection). 3. Check out and edit the following three forms: For the form Define DPVRoutineInfo shopfloor_name Enter the name of the routine as it is known on the shop floor. Example Enter underbody222left if the routine is known by that name on the shop floor even if it is UB_222LH in Teamcenter. The shop floor name must match the name in the raw data file when working with certain data types. measured_item Part number. DPVMeasmtContext Required only when the raw data file does not define the properties. It is optional on both the routine and the inspection device. If the raw data file contains the value, then that value is used. Otherwise, the value defined in the form on the routine is used and lastly the value on the form of the inspection device is used. item_measured Select Part, Tool, or Fixture Dimensional Planning and Validation Administration Guide PLM00151 H

139 Defining quality inspection process For the form Define site Enter the location of the inspection device. project Specify the name of the program associated with the routine. phase Enter the phase. For example, PRD or TEST. build_label_type Enter the build label (for example, JSN, PVI, and DCN). DPVTriggerConfig Required only when the routine needs to be defined for triggers. This replaces the need for creating a triggers folder in Teamcenter. 4. Choose File New Workflow Process. For more information, see Define triggers. 5. In the New Process dialog box, from the Process Template list, select ExportRoutine_To_AI. The file names automatically fill in. 6. Verify that the targets specified in the New Process dialog box are correct. 7. Click OK. The Information dialog box appears. 8. Click OK. The routine is automatically sent to the DPV Device Client for processing. List of forms used Tips for managing forms Export the inspection device to the DPV Device Client After you define the inspection device and configured the DPV Device Client, you export the inspection device to the DPV Device Client for processing. Once the Application Interface (AI) objects are downloaded, the following directory structure is created: DPVBASEPATH\<PlantName>\<DeviceParentName><DeviceName> PLM00151 H Dimensional Planning and Validation Administration Guide 2-123

140 Chapter 2 Defining quality inspection process Example D:\FLDPV\RawData\FFX_ASM\000057_Perceptron\000001_X0_Perceptron 1. In Teamcenter, send the bill of resource to Manufacturing Process Planner. 2. Display the Attachments view. 3. From the main structure view, and not the Attachments view, select the device and its immediate parent. 4. Choose File New Workflow Process. 5. From the Process Template list, select ExportDevice_To_AI. The file names automatically fill in. 6. Verify that the targets specified in the New Process Dialog for Plant Name and Routine are correct. 7. Click OK. The device is automatically sent to the DPV Device Client for processing. Check for all exported objects Export the plant to the DPV Device Client This workflow exports only the plant (of type MEPRPlantProcess) information (including forms) to the DPV Device Client. This is particularly useful when there are changes to a forms associated with a plant after you have exported the routines to the DPV Device Client. Example If you change the shift timings in the DPVShiftStartTime form attached to the plant, you can use this workflow to export the plant information to the DPV Device Client. 1. In Teamcenter, send the bill of process to Manufacturing Process Planner. 2. Select the plant of type MEPRPlantProcess to export. 3. Choose File New Workflow Process. 4. In the New Process dialog box, from the Process Template list, select ExportPlant_To_AI. The file names automatically fill in. 5. Verify that the targets specified in the New Process dialog box are correct. 6. Click OK. 7. In the Information dialog box, click OK. The plant is automatically sent to the DPV Device Client for processing. If a plant name exceeds 30 characters, the application interface (AI) objects exported for that plant will not be downloaded to DPV Device Client Dimensional Planning and Validation Administration Guide PLM00151 H

141 Defining quality inspection process Managing AI objects created during export Application Interface (AI) objects are created in a user s Newstuff folder when inspection devices, common scripts, or routines are exported to the DPV Device Client through a Teamcenter workflow. The AI object contains a PLM XML file with the information you exported. Tip You can view the status of an AI object by expanding the object. DPV Device Client periodically scans Teamcenter for AI objects (or modified AI objects), identified as belonging to the plants to be downloaded, and downloads the PLM XML into the DPVDevice and DPVRoutine folders under the FLINK/xmlcfg folder in the DPV Device Client configuration: It translates the PLM XML into a common XML format for uploading. PLM XML files that fail to translate are placed into DevicePLMXMLFailed or RoutinePLMXMLFailed folders. Tip You can monitor this process using the using the DPV Error Viewer. For more information, see Viewing DPV Device Client status in the DPV help collection. When the DPV Device Client consumes the contents of an AI object, it sends a message back to Teamcenter confirming it. On a daily basis, it removes any consumed AI objects that are more than 24 hours old. It removes them at a hard-coded time of 0:00:00 (the time is the local time on the DPV Device Client installation) or when the DPV Device Client is restarted. The DPV Device Client user account must have been set up with access to remove AI objects. PLM00151 H Dimensional Planning and Validation Administration Guide 2-125

142 Chapter 2 Defining quality inspection process The DPV Device Client does not delete the AI objects. It just removes them from the Newstuff folders. The AI objects are still in the Teamcenter database. Only automatically created DPV AI objects are removed from Newstuff folders. If an AI object appears in more than one user s Newstuff folder, the AI object is removed from all users Newstuff folders. The automatic removal of DPV AI objects only occurs fromnewstuff folders. Setting access to remove AI objects To provide the DPV Device Client account with access rights to remove Application Interface (AI) objects from Newstuff folders, add the following ACL to the Teamcenter installation: Has Type (Newstuff Folder) It sets the rules that grant AI object removal privileges. Add the ACL to your Teamcenter installation using the CreateAIRuleInACL executable. If the Teamcenter installation s rule tree is different than the default rule tree or it has write restrictions, you need to set up the rule manually. For more information about adding the rule, see Creating the application interface (AI) rule in the access control list (ACL) in the Installing the Dimensional Planning and Validation Solution guide in the DPV help. For more information about setting up rule trees manually, see the Upgrade Guide. Check for exported objects and ignore the date-time filter The first time you start the DPV Device Client, it downloads all pending exported objects: measurement routines, inspection devices, and plants. The exported objects are application interface (AI) objects and were created using the export to AI workflows. The objects are downloaded and translated as routine/device configuration files in the %FLAPP%\DPVRoutine and %FLAPP%\DPVDevice folders. After exporting any pending objects, DPV Device Client sets a date-time filter of either: The last successfully downloaded object Dimensional Planning and Validation Administration Guide PLM00151 H

143 Defining quality inspection process The current date-time if there are no objects to be downloaded. It applies the date filter to all queries so it only downloads objects exported after the last successfully downloaded object. (Optional) To have the DPV Device Client check for all objects and ignore the date-time filter, do the following to remove the CreatedAfterFilter from the registry key. The CreatedAfterFilter value only needs to be deleted if you have AI objects pending to be downloaded prior to the last successfully downloaded AI object. 1. Stop the DPV Device Client. 2. Using the registry editor (regedit), delete the CreatedAfterFilter value from the registry key. The registry key location depends on whether DPV Device Client is installed on a 32- or 64-bit machine: For 32-bit machine, it is located here: HKEY_LOCAL_MACHINE\SOFTWARE\Tecnomatix\FactoryLink For 64-bit machine, it is located here: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tecnomatix\FactoryLink 3. Start the DPV Device Client. PLM00151 H Dimensional Planning and Validation Administration Guide 2-127

144

145 Chapter 3 Administering measurement database Administering the measurement database Set the selection criteria Archive the data Purge the data Restore data PLM00151 H Dimensional Planning and Validation Administration Guide

146

147 Chapter 3 Administering measurement database Administering the measurement database The Dimensional Planning and Validation solution provides a set of utilities for archiving and purging measurement data that you no longer need and to help you limit the requirements for database size. dpv_archive Removes unneeded records from the database based on a set of selection criteria and creates a data file for restoring the data. dpv_restore Loads deleted data back into the database using the data file that dpv_archive created. dpv_purge Deletes records permanently based on the set of selection criteria. It does not create a data file for restoring the data. The selection criteria are stored in the database and read whenever the utilities are run. You use the Teamcenter thin client to enter the criteria and the Teamcenter command window to run the utilities. You should also perform all the basic administrator tasks for the database you are using for dimensional planning and validation as you do for any database, such as adding users and backing up the data. For information on activating/deactivating measurement data, see Using DPV Measurements. Set the selection criteria Set the criteria for archiving or purging data. 1. In the Teamcenter thin client, in My Teamcenter, choose Edit Options. 2. Click the Advanced tab, and select Dimensional Planning and Validation Purge Criteria. PLM00151 H Dimensional Planning and Validation Administration Guide 3-1

148 Chapter 3 Administering measurement database 3. Select the selection criteria by which to automatically archive or purge the database. You can specify one set of criteria per plant and inspection device type. For the option Plant ID Device Type Unit of Time No of Days/Months No of Records Do the following Enter the ID of the plant (not its name). Enter the type of inspection device, such as CMM or vision (not the individual device). Set to the unit of time either months or days. Enter the number of months or days of data, such as 30, to archive or purge, depending on the time setting above. Enter the number of records required for the archive or purge to begin. That number of records must remain in the database after the archiving occurs. 4. Click OK. 5. Click Close. If you use the same plant ID and inspection device type combination in a second set of selection criteria, it overwrites the earlier criteria (that is, the number of months/days and minimum number of records). You can add any number of plant and inspection device pairs to the criteria list, each with its own time and records criteria. All pairs are archived or purged. The number of records criterion, described next, is evaluated, and the decision whether or not to archive or purge is performed independently for each plant and inspection device pair. All data archived from running dpv_archive is written to a single output file. 3-2 Dimensional Planning and Validation Administration Guide PLM00151 H

149 Administering measurement database Time and minimum number of records work together to specify the criteria for archiving or purging, so you need to specify both time and number of records. When dpv_archive or dpv_purge is run, the program first determines if the number of records criterion is satisfied. Example In this example, if in a six-day period only 50 records were created, the records would not be archived because the archiving would result in fewer records remaining in the database than was specified for the given plant ID and inspection device type pair. If Has the following Plant ID 8340 Device Type vision Unit of Time days No of Days/Months 6 No of Records 100 If Has the following Plant ID 4022 Device Type handheld Unit of Time days No of Days/Months 6 No of Records 100 In this example, when either dpv_archive or dpv_purge is run, the program first determines if the number of records criterion is satisfied. If it is, it deletes all the records in the database belonging to the Taipei plant that are from any CMM device and are greater than six months old. If dpv_archive had been run, all records would be written to a data file from which they could later be restored. For the number of records criterion to be met in this scenario, there must be 101 or more records for the Taipei and CMM combination that are six months or younger. If Plant ID 8832 Device Type Unit of Time No of Days/Months 6 Has the following CMM No of Records 100 months PLM00151 H Dimensional Planning and Validation Administration Guide 3-3

150 Chapter 3 Administering measurement database Archive the data The records that dpv_archive utility archives are events, feature actuals, and trace codes. You set the criteria for archiving the data in the Teamcenter thin client. The set of criteria you can specify is the same as that for purging. You archive the data manually through the Teamcenter command window. The archived data is stored in a file with tab-separated values whose name and location to be stored are user-defined. The file may contain data belonging to more than one plant because the utility runs for each selection criteria set. 1. Access a Teamcenter command window. Tip On a Windows system, click the Start button and choose Programs Teamcenter Command Prompt. On UNIX or Linux system: a. Set the TC_DATA environment variable to your TC_DATA directory. b. Set the TC_ROOT environment variable to your TC_ROOT directory. c. Run source tc_profilevars. 2. At the Teamcenter command prompt, run dpv_archive <filename>, where filename is the name of the file to contain the archived data. The file must include an extension, such as.dat. Example dpv_archive measdata_jan dat 3. View and save the file containing the archived data. If you want a regular process, you can use cron or other system tools to set up a regular running program. Purge the data Set the criteria for purging the data to free up database space. You manually purge the data once you set up the criteria using the Teamcenter command window. You set the criteria for purging in the Teamcenter thin client. The set of criteria you can specify is the same as that for archiving. 1. Access a Teamcenter command window. 3-4 Dimensional Planning and Validation Administration Guide PLM00151 H

151 Administering measurement database Tip On a Windows system, click the Start button and choose Programs Teamcenter Command Prompt. On UNIX or Linux system: a. Set the TC_DATA environment variable to your TC_DATA directory. b. Set the TC_ROOT environment variable to your TC_ROOT directory. c. Run source tc_profilevars. 2. At the Teamcenter command prompt, run dpv_purge. Restore data To restore archived data, run the restore utility with the file name containing the archived data. 1. Access a Teamcenter command window. Tip On a Windows system, click the Start button and choose Programs Teamcenter Command Prompt. On UNIX or Linux system: a. Set the TC_DATA environment variable to your TC_DATA directory. b. Set the TC_ROOT environment variable to your TC_ROOT directory. c. Run source tc_profilevars. 2. At the Teamcenter command prompt, run dpv_restore <filename>, where filename is the archive file to be restored. Example dpv_restore measdata_jan dat PLM00151 H Dimensional Planning and Validation Administration Guide 3-5

152

153 Chapter 4 Using DPV measurements Getting started About DPV Measurements Before you begin DPV Measurements interface Configure DPV Measurements View measurement data events Change the activation state of measurement data events PLM00151 H Dimensional Planning and Validation Administration Guide

154

155 Chapter 4 Using DPV measurements Getting started About DPV Measurements Use the Teamcenter application, DPV Measurements, to view measurement data events based on their date, JSN number, or routine name. You can also display the features associated with the events and activate or deactivate selected events. Before you begin Enable DPV Measurements Configure DPV Measurements To enable DPV Measurements you must install the Dimensional Planning and Validation solution during installation: Under Extensions, select: o Manufacturing Process Management and then: Database Configuration for DPV Customization for emserver integration Before using DPV Measurements, be sure to: Set up your quality process inspection process to have measurement data events. For more information, see Defining quality inspection process. Set up who can change the activation state of measurement data events using DPV Measurements. For more information, see Configure DPV Measurements. Start DPV Measurements To view the time and date of measurement events in DPV Measurements, after updating Dimensional Planning and Validation (DPV) and Teamcenter to 10.1, you must update each of your measurement databases. For more information, see the Upgrade Guide. In the navigation pane, click DPV Measurements. PLM00151 H Dimensional Planning and Validation Administration Guide 4-1

156 Chapter 4 Using DPV measurements DPV Measurements interface The DPV Measurements interface is a single perspective in which to search and view measurement data events. 1 Plant ID Use to select the plant whose measurement data events you want to view. 2 Routines Use to select the routine whose data you want to view. 3 Measurement viewing options Use to select how you want to view and display the data. Configure DPV Measurements By default, all users can change the activation state of measurement data events. To protect your data, define the preference DPVAdmin to hold the names of the groups of users who can change the activation state. Groups not in DPVAdmin can read the events but they cannot change their activation state. If no preference is defined, all users have the privilege to change the activation state. For more information on defining DPVAdmin, see the Preferences and Environment Variables Reference. 4-2 Dimensional Planning and Validation Administration Guide PLM00151 H

157 Using DPV measurements To view the time and date of measurement events in DPV Measurements, after updating Dimensional Planning and Validation (DPV) and Teamcenter to 10.1, you must update each of your measurement databases. For more information, see the Upgrade Guide. View measurement data events You can view measurement data events based on their date or JSN number. 1. In the Teamcenter rich client, click DPV Measurements in the navigation pane. If DPV Measurements does not appear in the navigation pane: a. Beneath the navigation pane, select Configure Applications (>>) and choose Navigation Pane Options. b. From the list of available applications, select DPV Measurements and use the + to place it in your list of primary or secondary applications. c. Click OK. 2. From Plant ID, select a plant. 3. From the list of routines IDs that appears, select the routine whose data you want to display. 4. Select one of the following: Use dates from and enter the dates during which the measurement data was collected. Use JSN and enter the JSN (build label) of the data. The exact JSN is required. Wildcards are not supported. 5. Select one of the following to choose to display features along with the events: Display events and their features to display features with the events. Display events only to display only the events. 6. Click Get Data. DPV Measurements displays the data that matches the criteria, as shown below. The first column active indicates whether the data is active or inactive: 1 Active 0 Inactive PLM00151 H Dimensional Planning and Validation Administration Guide 4-3

158 Chapter 4 Using DPV measurements In the event_type column, normal jobs are listed as N and duplicate jobs as D. 7. If you choose to view features, use the scroll bar to scroll to the right to view the features in the last columns. The feature column headers consist of the feature name and feature attribute code. Sort the data on any column by clicking the column header. To clear the data displayed, click Clear Contents. Change the activation state of measurement data events Activate or deactivate measurement data events based on their date or JSN number. When data is deactivated, users cannot query for it and it does not appear in quality reports. It is not deleted and can be restored by activating it. By default, all users can change the activation state of events. To protect your data, define the preference DPVAdmin to hold the names of groups of users who can change the activation state. Groups not in DPVAdmin can read the events but they cannot change the activation state. If no preference is defined, all users will have the privilege to change the activation state. For more information on defining DPVAdmin, see the Preferences and Environment Variables Reference. 1. View the measurement data events to activate or deactivate. 2. Highlight the data you want to activate or deactivate. You can make multiple selections. 3. Click either: 4-4 Dimensional Planning and Validation Administration Guide PLM00151 H