Teamcenter Manager For SolidWorks User Guide
UserGuide
User Manual:
Open the PDF directly: View PDF .
Page Count: 64
Download | |
Open PDF In Browser | View PDF |
Teamcenter Integration for SolidWorks® Users Guide Version 8.3.0 TranscenData A Business of International TechneGroup Incorporated DuPont Circle Milford OH, 45150 ITI PROVIDES THIS PROGRAM AS IS AND WITH ALL FAULTS. ITI SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. ITI DOES NOT WARRANT THAT THE OPERATION OF THE PROGRAM WILL BE UNINTERRUPTED OR ERROR FREE. i-Man® is a registered trademark of UGS Corp. Siemens and the Siemens logo are registered trademarks of Siemens AG. UGS, Teamcenter and UGS Teamcenter are trademarks or registered trademarks of UGS or its subsidiaries. This software and related documentation are proprietary to UGS Corp. ©2009 UGS Corp. All rights reserved. SolidWorks® is a registered trademark of SolidWorks Corporation. Copyright© 2009 International TechneGroup Incorporated, 5303 DuPont Circle, Milford, Ohio 45150, U.S.A. All Rights Reserved. This program contains software licensed from UGS Corp. ©2009 UGS Corp. All Rights Reserved i Contents Introduction ................................................................................................................................... 1 Technical Support ......................................................................................................................... 1 Starting SolidWorks and the Teamcenter Integration for SolidWorks .................................. 1 From the Desktop ........................................................................................................................ 1 From the Teamcenter Rich Client ............................................................................................... 1 The Teamcenter Task Pane.......................................................................................................... 2 Teamcenter Quick Launch Bar ................................................................................................... 3 Teamcenter Status Tree............................................................................................................... 5 SolidWorks Type Icons........................................................................................................... 5 Teamcenter Status Icons ......................................................................................................... 6 Teamcenter Operation Progress .............................................................................................. 7 Integration Dialog Windows ........................................................................................................ 7 Shortcut Menu Functions ............................................................................................................. 8 Checkout ..................................................................................................................................... 9 Checkout History ........................................................................................................................ 9 Cancel Checkout ......................................................................................................................... 9 Delete .......................................................................................................................................... 9 Transfer Ownership .................................................................................................................... 9 Where Referenced ..................................................................................................................... 10 Detecting Newer Model Versions .............................................................................................. 10 Opening a SolidWorks Model Previously Saved to Teamcenter ............................................ 11 The Open Dialog ....................................................................................................................... 12 Find the top level model ....................................................................................................... 12 Browsing Teamcenter Folders and items .......................................................................... 12 Browsing the Rich Client Selection .................................................................................. 12 Searching Teamcenter ....................................................................................................... 12 Select the top level model ..................................................................................................... 13 Choose top level options ....................................................................................................... 14 Where Referenced: Searching for References to a Selected Model .................................... 15 Using seed parts .................................................................................................................... 15 Multi-Site: Working with Models Owned by Remote Sites ................................................ 16 Transfer Ownership .......................................................................................................... 17 Remote Checkout .............................................................................................................. 17 The Open Dependencies Dialog ............................................................................................... 18 Configure the structure ......................................................................................................... 20 Select the actions to be applied ............................................................................................. 20 Lightweight ........................................................................................................................... 21 Revision Configuration ......................................................................................................... 21 Opening the precise configuration of an assembly ........................................................... 21 Filters .................................................................................................................................... 21 ii Opening SolidWorks Configurations .................................................................................... 22 Creating a new Teamcenter item and SolidWorks model ...................................................... 22 Saving SolidWorks models to Teamcenter ............................................................................... 24 The Save Dialog ........................................................................................................................ 24 Updating Model Names while Saving ...................................................................................... 26 Creating a New Item ................................................................................................................. 26 The Replace Item ID Dialog ................................................................................................. 28 Creating a New Item Revision .................................................................................................. 30 Saving Configurations and Design Tables ................................................................................ 30 Exclude from bill of materials Flag .......................................................................................... 31 Saving Auxiliary Files .............................................................................................................. 31 Adding Items to a Teamcenter Folder ...................................................................................... 32 Submitting Items to a Teamcenter Workflow ........................................................................... 32 Managing models in session ....................................................................................................... 33 Detecting updates in Teamcenter .............................................................................................. 33 Updating in-session models from Teamcenter ......................................................................... 34 Inserting models from Teamcenter ........................................................................................... 37 Replacing models from Teamcenter ......................................................................................... 39 Managing Work Directories ...................................................................................................... 44 The Update Dialog .................................................................................................................... 44 Browsing and Updating Files.................................................................................................... 45 Deleting Files ............................................................................................................................ 46 Canceling a Checkout ................................................................................................................. 47 Changing User Settings .............................................................................................................. 48 Changing Group and Role ........................................................................................................ 48 Integration to Teamcenter Rich Client ..................................................................................... 48 Launch to SolidWorks Button .................................................................................................. 49 Revise........................................................................................................................................ 49 Save As ..................................................................................................................................... 49 Baseline ..................................................................................................................................... 49 Appendix ...................................................................................................................................... 50 Configurations........................................................................................................................... 50 Managed and Unmanaged..................................................................................................... 50 Save Dialog Buttons ............................................................................................................. 50 Recommendations for working with configurations............................................................. 50 Toolbox Parts ............................................................................................................................ 51 Usage..................................................................................................................................... 53 Create Configurations ....................................................................................................... 53 Create Parts ....................................................................................................................... 53 Create Parts on Ctrl-Drag.................................................................................................. 53 iii Create Parts as SWPrt ....................................................................................................... 53 Duplicating Items and Structures .............................................................................................. 54 In-Session Duplicate ............................................................................................................. 54 The Advanced Replace Item ID Dialog .................................................................................... 56 Pattern Elements ............................................................................................................... 57 Replacement Elements ...................................................................................................... 58 Templates .......................................................................................................................... 59 iv Introduction The Teamcenter® Integration for SolidWorks® provides access to Teamcenter from within the SolidWorks environment. You can search Teamcenter for models and open them in SolidWorks, save models back to Teamcenter and update bills of material (BOMs), create new items and revisions, reserve models so others cannot modify them while you are working on them, and cancel your reservations. This guide assumes you already know how to use SolidWorks. You should also have a basic familiarity with the Teamcenter concepts of an item, item revision, dataset, and BOM. The Teamcenter Integration for SolidWorks stores each SolidWorks model in its own dataset, and gives the dataset the same name as the model. Each dataset is stored in an item revision, and each item revision belongs to an item. When this guide mentions a SolidWorks model in Teamcenter, it is referring to the combination of the item, revision, and dataset that contain the SolidWorks model file. Technical Support For technical support, please contact the UGS Global Technical Access Center (GTAC). You can reach GTAC via the World Wide Web at http://support.ugs.com/ or by telephone: United States and Canada (800) 955-0000 In other countries please see http://support.industrysoftware.automation.siemens.com/services/global_number.pdf for additional telephone numbers, or call (714) 952-5444. Starting SolidWorks and the Teamcenter Integration for SolidWorks From the Desktop Start the Teamcenter Integration for SolidWorks by selecting it from your Start menu, or doubleclick on the startsw.bat script found in the bin subdirectory of the Teamcenter Integration for SolidWorks installation. From the Teamcenter Rich Client If you are working in the Teamcenter Rich Client, you can double-click on a SolidWorks dataset, or you can select the dataset and use the Open command in the Rich Client’s File menu. In the Rich Client’s Navigator application, you can also select one or more items, item revisions, and datasets, then click the button, located in the toolbar near the top of the window. This starts a new SolidWorks session, displays the Integration’s Open dialog, and shows the selected model in the dialog’s From Rich Client folder. If a SolidWorks session already exists when the button was selected, the select model(s) will be routed directly to the active integration session, and the user will see the integration’s Open dialog, as shown below. 1 Figure 1 The Teamcenter Open dialog See Opening a SolidWorks Model Previously Saved to Teamcenter for more information on the Open dialog. The Teamcenter Task Pane When the Teamcenter Integration for SolidWorks is available in SolidWorks, the Teamcenter task pane appears on the right side of SolidWorks window1. Click on the Teamcenter tab to access the task pane. 1 All Teamcenter operations are initiated from the Teamcenter task pane. The integration does not override any native SolidWorks functionality. 2 Figure 2 the Teamcenter Task Pane The Teamcenter task pane is divided into three sections: Teamcenter Quick Launch Bar, Teamcenter Status Tree, and Teamcenter Operation Progress. The top section, Quick Launch Bar, contains a row of icons to launch Teamcenter operations. The operations are used to save data to Teamcenter, retrieve data from Teamcenter and manage checkouts. The middle section, Status Tree, shows the Teamcenter status of in-session models. The bottom section, Operation Progress, provides an indication of operations in progress. Teamcenter Quick Launch Bar Figure 3 The Teamcenter Quick Launch bar Action icons are used to perform Teamcenter functions. Through these operations, users can retrieve (Open) data from Teamcenter and save data to Teamcenter. Additionally, the icons are used to check out, and cancel the checkouts of data. Below is a description of each of the icons. Each icon has an implied title. Sections of this document are dedicated to describing each operation in detail. 3 Create Creates an Item in Teamcenter and creates the associated model in SolidWorks. You select the SolidWorks template file and specify the Teamcenter Item Type, the Item Id, and the Item Name. The dataset is checked out of Teamcenter but the SolidWorks file is not saved to Teamcenter. The SolidWorks file is saved to disk. Open Finds a model in Teamcenter and opens it in SolidWorks. You may choose to obtain a read-only copy of the model or to check out the model for modification. Checkout means Teamcenter reserves the model for you. Nobody else can check out the model and save a modified version back to Teamcenter while you have it reserved. Save Saves the current model to Teamcenter. Optionally, you may choose to create a new revision of the model or save the model to a different Teamcenter item. Save All Saves to Teamcenter all models in the SolidWorks session. Update Directory Updates, deletes or purges SolidWorks files in a selected directory. Cancel Checkout Cancels your reservation on SolidWorks models currently checked out to you. You do not have to open a model in SolidWorks to cancel your reservation on it. User Settings Changes your Teamcenter group and role. Refresh Refresh the Teamcenter status icons. For all models in session, the status icon will be updated based on the latest information from Teamcenter. The integration does not refresh automatically, not even when expanding the nodes of the status tree. The integration only refreshes after an integration operation or selecting the refresh button. Users should periodically refresh to ensure the icons and attribute information are current. About Version information pertaining to the integration. The first time you use one of these commands in a SolidWorks session, the Integration will prompt you for your Teamcenter user name and password. Once successfully logged in to Teamcenter, you will not have to log in again for the remainder of that SolidWorks session. 4 Teamcenter Status Tree Figure 4 Status in the Teamcenter Task Pane From the status tree, the user can determine the status of all in-session models and use Right Mouse Button (RMB) pop-up menus to perform operations on selected models. By default, the tree is collapsed when the user first expands the task pane, showing just a single node, “Open in SolidWorks”. The user must expand the tree nodes to see the full structure. Each node consists of two icons followed by a text string. The first icon indicates the SolidWorks type and the second icon indicates the Teamcenter status. By default, the text contains the Teamcenter Item Id and revision, the document description, SolidWorks document name and SolidWorks configuration name. Drawings will not have configuration text and if a model has not been saved to Teamcenter, the Teamcenter text will be blank. SolidWorks Type Icons Drawing SolidWorks type is a drawing (.sldprt). Drawings will not contain configuration text. Assembly SolidWorks type is an assembly (.sldasm) Assemblies will always have configuration text. Part SolidWorks type is a part (.sldprt). Parts will always have configuration text. Toolbox Part SolidWorks type is a toolbox part. Toolbox parts will always have configuration text. 5 Teamcenter Status Icons New If no icon is present, then the model has not been checked into Teamcenter or was moved from one directory to another. When the status is blank, the text will not contain Teamcenter information. Ambiguity The grey question mark (ambiguity) status is displayed if the model’s status in Teamcenter is uncertain. In Teamcenter The user has the latest revision of the model. The revision is neither released nor checked out by any user. Checked Out The user has the checked out the latest revision of the model. Checkout Restricted The user has the latest revision of the model. The revision is checked out by another user. Released The user has the latest revision of the model. The revision is released. Yield The user does not have the latest model. A newer revision or newer version exists in Teamcenter. Operations can be performed directly on nodes in the tree via a shortcut menu. Nodes are selected by one of three ways: 1) left mouse click on a single node 2) using shift left mouse click or control left mouse click to select multiple nodes 3) selecting one or more models in the SolidWorks feature tree. Once selected, the shortcut menu is exposed by right mouse button click on one of the selected nodes. Selecting an option from the menu initiates an operation on the selected nodes’ models. Figure 5 The Right Mouse Button shortcut menu Collapse All All selected nodes and their children are collapsed as if the “-“ button had been selected on all of the nodes. Expand All All selected nodes and their child nodes are expanded as if the “+” button had been selected on all of the nodes. 6 Checkout Check out the model. If the checkout cannot be obtained the operation will not succeed and the status will remain as it was. Check-in Check in the model. The save dialog will appear, enabling the user to store the model into Teamcenter. Cancel Checkout Cancel the checkout of the model. Checkout History A dialog is brought up to view the checkout history of the model. Update Attributes Synchronize the attributes from Teamcenter for the selected models. Attributes are synchronized during open, but a user may wish to synchronize again because another user has changed the attributes in Teamcenter or the model was not brought into session during the open operations (was lightweight or suppressed). The site administrator should use the attribute mapping section of Administration Guide to configure attributes for synchronization. Update Model Update the model from Teamcenter by fetching the model again and reloading it in the current SolidWorks session. Insert Model Find and insert a model from Teamcenter into the active assembly. Replace Model Replace the selected component with a substitute from Teamcenter. The success or failure of the actual replacement, within the SolidWorks session, depends upon the degree of similarity between the two components, as well as any mating constraints to the parent assembly. Teamcenter Operation Progress Figure 6 Teamcenter progress bar A progress bar is displayed indicating that an integration operation is in progress. While the bars scroll, the user should not use the SolidWorks session. At times, the integration must manipulate SolidWorks, so the user may observe changes on the screen. . After the integration has completed interaction with SolidWorks, the integration attempts to preserve the session state when possible. Integration Dialog Windows Each of the Teamcenter functions listed above leads to one or more dialog windows. The SolidWorks user interacts with Teamcenter using the buttons, check boxes, selection lists, and other elements of these dialogs. Except for the User Settings and About dialogs, each dialog is designed to display CAD models and allow the user to manage them. The CAD models are consistently displayed in a table format, allowing the user to select a single model, a contiguous range of models or a non-contiguous set of models. Object selection follows the usual paradigm: Use Ctrl-click to select non-contiguous sets, and use Shift-click to select a contiguous set. When at least one model is selected, a right mouse button pop-up menu is enabled. This is called the 7 “Shortcut menu”. It provides a set of convenience functions appropriate to the context of the operation and the status of the selected object(s). In the figure below, a set of models is selected in the Save dialog, and only those functions which can be performed on the selected models are enabled; the remainder are grayed out: Figure 7 the Save Dialog Shortcut Menu Functions 3. Select one of the following commands from the shortcut menu. Checkout Reserves the model. This does not export the model’s file from Teamcenter. Checkout History Shows details about previous check out and check in operations performed on the selected model. Cancel Checkout Cancels your reservation on selected models. Delete Deletes searches in the Open, Insert and Replace dialogs and deletes models from disk in the Teamcenter Update dialog. Transfer Ownership Transfers ownership of the model from a remote site to your site, making it possible to modify and save the model at your site. This transfer affects the model’s entire item, including all revisions of the model. 8 Where Referenced In the Open, Insert, and Replace Dialogs, results in a “where referenced” search being added to the Open Dialog’s search folder. These commands are described in more detail in the following sections. Checkout The Checkout command reserves the selected models. The command skips models that are already reserved and models that are not in Teamcenter. Before any models are checked out, you will be prompted to enter a comment and change ID, similar to the information you are asked to provide when checking out a model with the Open dialog. This command does not export the model’s file from Teamcenter, so you can safely check out a model that is already open in your SolidWorks session or is in a local directory. Changes you have made to the local model will not be lost. Once you have reserved the model, you can save it to Teamcenter, although you should always be careful when saving a model that was not reserved until long after its file was exported. For example, you may fetch a model from Teamcenter without checkout, and later use the shortcut menu to reserve it when you are ready to save your changes back to Teamcenter, but between the time you fetch the model and the time you reserve it, other users can change the model in Teamcenter. A recommended practice when using the Checkout command is to verify first that Teamcenter does not have a newer version of the model. See the section titled Detecting Newer Model Versions for more information on determining whether a model in Teamcenter has changed. Checkout History The Checkout History command can only be initiated for one row of a table. When selected a popup dialog appears with a table of the model’s check-in and checkout history. Cancel Checkout The Cancel Checkout command cancels your reservation on selected models. The command skips models that you have not reserved. Before any of your reservations are canceled, you will be prompted to confirm that you want to cancel your checkouts Delete The Delete command deletes the model from disk in the Manager Dialog and deletes searches on the Open Dialog. Transfer Ownership The Transfer Ownership command transfers ownership of the selected model from a remote site to your site. This command actually transfers the model’s entire item to your site, including all revisions of the model and the other datasets, forms, and Teamcenter objects attached to the 9 item. If several rows are selected, all of the items that are owned by remote sites will be transferred to your site. The command skips models that are already owned by your site. The Integration does not allow you to check out models owned by remote sites, so transferring ownership to your site is a first step if you need to modify and save such a model back to Teamcenter. After transferring ownership, you can check out the model in the usual way, using either the Checkout command in the shortcut menu or the Open command in the Teamcenter menu. Once you have made your changes and checked in the model, users back at the remote site may use the Transfer Ownership command to return ownership to their site. The Rich Client’s Navigator application also makes it possible to transfer ownership with its Tools | Import | Remote command. Where Referenced The Where Referenced command performs a Teamcenter “Where Referenced” search on the selected row of the Open, Insert and Replace dialogs. The result is a new “Where Referenced” folder in the list of searches. Detecting Newer Model Versions Most integration dialogs can indicate whether a change has occurred since a model was exported from Teamcenter. As shown in preceding figures, three table columns display the icons described below when the local model has unsaved changes, or when a new dataset version or item revision is available in Teamcenter. The first column displays this icon when the model in the SolidWorks session has changes that have not been saved to Teamcenter. The second column displays a dataset icon when a newer version of the model’s dataset is available in Teamcenter. You may want to use one of the Update commands in the Teamcenter menu to fetch the new version of the model, although you should close your local copy in the SolidWorks session before doing so, otherwise the Integration will not be able to load the new version into the session. The third column displays an item revision icon when a later item revision is available in Teamcenter. If you want this later revision in your SolidWorks session, first close the current version in the SolidWorks session, then use one of the Update commands in the Teamcenter menu to find the model’s latest revision. This icon simply indicates a later item revision is available. It does not indicate whether that item revision also has a dataset for the SolidWorks model. A question mark appears in a column when the Integration does not have enough information to determine whether a change has occurred. For example, a question mark might appear if the model in Teamcenter was not saved with version 2.0 or later of the Teamcenter Integration for SolidWorks, or if cached information about exported models is not available. The Integration gleans several pieces of information from a model to determine whether a change has occurred since the model was last exported from Teamcenter. It does not compare 10 the contents of one SolidWorks file against another, so an icon should be treated as a hint that a change may have occurred, not as a guarantee that a model has or has not been modified. If the model is currently in the SolidWorks session, the information available to the Integration about that local version of the model is more up to date, but if the model is not in the current session, the Integration will attempt to use cached information collected the last time the model was saved to Teamcenter. Opening a SolidWorks Model Previously Saved to Teamcenter The Open command in the Teamcenter task pane displays a dialog that allows you to find a model in Teamcenter and open it in SolidWorks. You may choose to obtain a read-only copy, or you may choose to check out the model for modification. You must check out the model if you wish to save it back to Teamcenter at a later time. While the model is checked out to you, Teamcenter will not allow others to modify the model, although they may obtain read-only copies. The dialog displayed by the Open command is shown in Figure 8. At the top of the dialog is the Search box, which you can use to query Teamcenter for SolidWorks models. The table below the Search box displays the contents of your Teamcenter folders or search results. Your folders may contain a variety of Teamcenter objects, but the table will show only items, item revisions, SolidWorks models and other folders. At the right side of the dialog is a summary pane that includes a preview of the model, if available, and a table of details. Figure 8 the Open Dialog 11 The Open Dialog The Open dialog initially shows your Teamcenter home folder, or if you started SolidWorks from the Teamcenter Rich Client, it shows the model you selected in the Rich Client in a folder named From Rich Client. To find a model in Teamcenter and open it in SolidWorks, follow these steps. Find the top level model Browsing Teamcenter Folders and items Double-clicking on a folder, item, or item revision icon opens it and displays its contents in the table. If items are added to a folder or removed after you have opened it, click the Refresh button to display the folder’s current contents. Browsing the Rich Client Selection If you started SolidWorks from the Teamcenter Rich Client, clicking the From Rich Client button in the Search box at the top of the dialog will re-display the model you selected in the Rich Client. The model you selected in the Rich Client will appear in a folder named From Rich Client. Searching Teamcenter You can search for a model by entering its item ID into the text field. Figure 9 Searching by Item ID Click on the item icon to switch to a model name search. Figure 10 Searching by model name More advanced searches are available by selecting the Advanced Search button. The search results are put into a temporary folder within the Search Results folder, located near the top of the table. Each search adds another temporary folder to Search Results. All of these temporary folders will be discarded when your SolidWorks session ends (these folders are not available in the Rich Client). The Advanced Search dialog consists of two panels. In the Search panel you can search for a model by entering its item ID, revision, model name, and/or dataset type in the Search box and clicking the Search button. Each dataset type corresponds to a SolidWorks model type. You can use * to match zero or more characters and ? to match any single character. A blank field is the same as entering * to match anything. 12 Figure 11 The Advanced Search dialog The Teamcenter Search panel uses the saved Teamcenter queries. At the top of the Teamcenter Search panel is a menu of Teamcenter queries. Under the menu are the selected query’s fields that can be configured for your search. Enter as much as you know about the model(s) you want to find, then click the Search button to execute the query. The Advanced Search Dialog will close and the search results will be added to the Open dialog’s Search Results folder. Select the top level model Select a specific item, item revision or model row in the table by clicking on the row. Once selected, a preview image and details for the selected CAD model will appear in the summary pane. The preview only appears if the preview had previously been saved to Teamcenter. When multiple rows are selected, no image is displayed, and the image frame contains the text “Multiple Selection”. The preview pane may contain other text indicating specific conditions to the user: No Selection – The user has not yet selected an Item, Item Revision or Dataset in the table at left. A selection must be made before selecting the Open button. 13 No Preview – A preview does not exist in Teamcenter for the selection. Most commonly occurs for data saved before Teamcenter Integration for SolidWorks 8.1.0 was installed. If a specific dataset is not selected, the integration will infer the identity of the top-level model, based on the following logic: If an item is selected, the integration will select the highest-level CAD model under the latest item revision. If an item revision is selected, the integration will select the highest-level CAD model under the selected revision. The integration allows you to save multiple CAD models under a single item revision. Often this is done to group a drawing and its 3D models together, to simplify release management. The integration’s interpretation of “highest-level” CAD model is based on this hierarchy: SWDrw (highest) SWAsm SWPrt (lowest) Choose top level options If desired, select the Synchronize BOM Attributes check box on the Open dialog. This option will map a specified property or note2 from each component’s BOM line in the Teamcenter Bill of Materials to the ComponentReference property of the corresponding occurrence of that component within the top-level assembly3. This synchronization does have a performance impact on the load operation, and so users should apply it selectively. It is most appropriate when opening a SolidWorks assembly drawing containing annotations which are driven from the assembly components’ ComponentReference properties. Click the Open button at the bottom of the dialog and proceed to the Open Dependencies dialog. 2 The source property or note for this mapping is specified in the integration’s configuration file. See the Administration guide for more details. 3 This capability is only available when SolidWorks 2010 or a later version is used. 14 Figure 12 selecting the top-level model in the Open dialog Where Referenced: Searching for References to a Selected Model If you want to know whether any SolidWorks models in Teamcenter reference a model found in the Open, Insert or Replace dialog, right-click on the model’s row4, then select Where Referenced from the pop-up menu. The results of this “where referenced” search will be added to the Open dialog’s Search Results folder. The results include referencers of all models in the highlighted model’s item revision. For example, if an item revision contains a part and a drawing, highlighting the drawing and clicking the Where Referenced drop down will find referencers for both the drawing and the part. Using seed parts The Integration can create a new SolidWorks model when given an empty dataset to open. For example, you can start a new part by creating an item with a SWPrt dataset in the Teamcenter Rich Client, then sending the part to SolidWorks. The Integration will create a model for the part while opening it into SolidWorks. When creating a dataset in the Teamcenter Rich Client for a SolidWorks model, keep these points in mind: 4 You must select the model’s dataset in order to perform the “where referenced” search. The “where referenced” search is not available when the item or the item revision is the selected object. 15 The dataset name must be exactly the same as the name of the SolidWorks model it represents. If you are creating a dataset for a part to be named WIDGET, the dataset’s name must be WIDGET. Do not include a revision or type in the dataset name. For example, WIDGET/A and WIDGET.PRT should not be used as dataset names for SolidWorks models. If you add a SolidWorks file to the dataset, the file’s base name must match the dataset name. For example, if you create a dataset for a part file named widget.prt.1, the file’s base name is widget, so the dataset name should be WIDGET. A dataset for a SolidWorks model should be attached to only one item revision. If you copy a dataset from one item revision and paste it into another, the dataset will appear in both item revisions and changes made to one will appear in the other. It is usually better to create a new, empty dataset in an item revision rather than using copy and paste to add the dataset to the item revision. SolidWorks datasets should be attached to their item revisions using a specification relation (IMAN_specification). This is the default when the Rich Client creates a new SolidWorks dataset. To create a new item or revision for a SolidWorks model in the Teamcenter Rich Client: 1. Create the item or revision in the Rich Client as usual. When revising an item using the Teamcenter Rich Client, do not copy any existing SolidWorks datasets to the new item revision. Relationships to other SolidWorks models are not copied when datasets are copied. 2. In the Rich Client’s Navigator application, select the new item revision, then use the File | New | Dataset command to create a new SolidWorks dataset attached to that item revision. Give the new dataset exactly the name you want the new model to have, and use one of the following dataset types. Use This Dataset Type… For This Type of Model… SWDrw Drawing (.slddrw) SWAsm Assembly (.sldasm) SWPrt Part (.sldprt) 3. If you leave the dataset empty, the Integration will create a model of the appropriate type when you attempt to open the model in SolidWorks using one of the commands in the Teamcenter menu. Alternatively, you may wish to import a SolidWorks model file into the new dataset in the Rich Client, if you do not want the Integration to create the model from a default template. Remember that the file’s base name must match the dataset name. Multi-Site: Working with Models Owned by Remote Sites You can open SolidWorks models owned by remote sites if Teamcenter Multi-Site is installed and your administrator has replicated those models at your site. Replicated models can be 16 fetched and opened in the same manner as any other model. However, the Integration does not allow users to checkout models owned by remote sites. If you plan to modify and save changes to a model owned by a remote site, several additional steps are necessary. Transfer Ownership The simplest way to checkout and modify a SolidWorks model owned by a remote site is to transfer ownership of that model’s item to your site. Once your site has ownership of the item, you will have all of the normal access privileges allowed for locally owned SolidWorks models. You will be able to check models in and out of Teamcenter, and create new revisions. If the Integration was configured during installation to show a Transfer Ownership command in the shortcut menu, you can right-click on one or more models in the Open dialog, use the Transfer Ownership command to transfer remotely-owned items to your site, then proceed as usual to open them in SolidWorks. The Transfer Ownership command is also available in the Integration’s other dialogs. See the section on using the Shortcut Menu for more information about the shortcut menu and the Transfer Ownership command. If the shortcut menu has not been configured to show the Transfer Ownership command, you or your site administrator may be able to transfer ownership using the Teamcenter Rich Client. Remote Checkout It is recommended to use Transfer Ownership to gain modification privileges for any object owned by a remote site. This function is available from within the SolidWorks session, as well as the Teamcenter Rich Client. Should you choose to use Remote CheckOut instead, the check out must be performed in the Rich Client. Click on an object to select it, then use the Tools | Check-In/Out | Check-Out command to reserve the object. If you use remote checkout to reserve a SolidWorks dataset, do not simultaneously export the file. After checking out the dataset, its CO property should be Y, not Y/E. If you choose to use remote checkout, you must use the Rich Client to check out every object in the item revision that may be modified by the Integration when later saving the model back to Teamcenter. In some cases, it may also be necessary to check out the item. Check out this object… If… SolidWorks Dataset You are modifying the SolidWorks model. Auxiliary File Dataset The auxiliary file map imports files into other datasets in the item revision. BOMViewRevision (BVR) You are modifying a SolidWorks assembly. Form The attribute map copies SolidWorks properties to attributes in the form. This includes the Item Master form and the Item Revision Master form. 17 Check out this object… If… Item Revision You will be creating a new SolidWorks or auxiliary file dataset when saving the model to Teamcenter, or when the attribute map copies SolidWorks properties to item revision attributes. Item The attribute map copies SolidWorks properties to item attributes. After checking out the appropriate objects in the Rich Client, you can use the Integration to open the SolidWorks models and save them back to Teamcenter. The Integration will not release your reservation on any object that is owned by a remote site, even if you choose not to retain checkouts when saving models, or if you attempt to cancel checkouts using the Cancel Checkout command. When you are ready to release your reservations, use the Rich Client to check in the objects you previously checked out. If you want to create a new revision of an item that is owned by a remote site, you must first create the new item revision in the Rich Client: 1. Check out the item in the Rich Client. 2. Use the Rich Client’s File | Revise command to create the new item revision. 3. Check out the new item revision in the Rich Client. 4. Cut all SolidWorks datasets from the new item revision. 5. Use the Teamcenter Integration for SolidWorks to save the model to the new item revision. The Open Dependencies Dialog The Open Dependencies dialog will appear after the Open dialog closes. The Open Dependencies dialog shows the model you selected for opening, plus all of the models on which it depends. A check mark in the Fetch column means Teamcenter will put the model’s file in the destination directory. A check mark in the Checkout column means the model will also be reserved for you. If you intend to modify a model and save it back to Teamcenter, you must put a check mark in the Checkout column. You will not be able to check out a model that is already checked out, even if you are the user who reserved it. However, you can always fetch a read-only copy no matter who holds the reservation. 18 Figure 13 The Open Dependencies dialog The first three columns, to the left of the Fetch column, indicate whether a change has occurred in a model. For more information, see the section on Detecting Newer Model Versions. The icons to the right of the Checkout column indicate the type of model in each row. If you want to view the models’ relationships to each other, click the Tree button above the table. This button toggles between the ordinary table view and a hierarchical view. The configuration rule displayed at the top of the table determines which revisions are shown. 19 Figure 14 Tree View in the Open Dependencies dialog To open a model and its dependencies in SolidWorks: Configure the structure If you want to change the revision rule, use the Revision Configuration box, then click the Apply button to rebuild the table with your new configuration. See the Revision Configuration section for more information on how to use these settings. If you also want to apply a filter, use the Filters box before clicking the Apply button. See the section on Filters and the Filter Dialog for more information about filters. If a model contains additional unreferenced configurations, you can include them by clicking on the model’s row to select it, then clicking a Configurations | Add button. If no row is selected, these buttons affect every family table generic in the dialog. See Opening Configurations for more information. Select the actions to be applied Put a check in the Fetch column to tell Teamcenter that the model’s file should be placed in the destination directory. Put a check in the Open column if you want the model displayed in its own SolidWorks window. 20 Put a check in the Checkout column if you also want to reserve the model for modification. Lightweight If the Open as Lightweight checkbox is selected, the models will be opened lightweight in the same manner as SolidWorks opens with lightweight. Open in Lightweight will not synchronize attributes from Teamcenter to the lightweight SolidWorks models. The attributes can be synchronized later by resolving the models and using the Update Attributes button from the integration shortcut menu in the task pane. The Open as Lightweight button will be disabled if the user selected the Synchronize BOM Attributes checkbox on the Open dialog. Revision Configuration The Revision Configuration box contains a list of revision rules. The specific rules included in the list are determined by Teamcenter configuration. When the Open Dependencies dialog appears, the current rule is the default rule which is specified in the swim.properties configuration file, or in the user’s Teamcenter preferences. If you choose a different rule in the Open Dependencies dialog, click the Apply button to rebuild the table with the new rule. Opening the precise configuration of an assembly The precise configuration of an assembly is the set of component item revisions that the assembly was using the last time it was saved to Teamcenter. To open the precise configuration of an assembly, select the Precise Only revision rule, then press Apply. Filters When opening a model, the Integration by default also attempts to open all other models on which it depends. These models appear in the Open Dependencies dialog. However, by applying a filter, you can limit the Open Dependencies dialog to only models that satisfy certain conditions. A filter can also set the Fetch and Checkout checkboxes for these models. The Filters box in the Open Dependencies dialog contains several pre-defined filters. If a filter’s checkbox is marked in the Open Dependencies dialog, the Integration uses that filter when the Apply button is clicked in the Configure box. The pre-defined filters available by default are described below. Required Models required by the models selected in the Open dialog are added to the Open Dependencies dialog. Other models are excluded from the Open Dependencies dialog. Implied Models that are in the same item revision as other models in the Open Dependencies dialog are also added to the Open Dependencies dialog. For example, if Required is checked, Implied will add the drawings of required models to the Open Dependencies dialog, if those drawings are in the same item revisions as the required models. 21 Implied by Top This is similar to Implied, but it only applies to models at the “top” of the hierarchy of dependencies. For example, if Required is checked and a part is selected in the Open dialog, Implied by Top will add any drawings found in the part’s item revision, but drawings in other item revisions will not be included in the Open Dependencies dialog. Referenced by Top Models referenced by models at the “top” of the dependency hierarchy are added to the Open Dependencies dialog. For example, if Required is checked and an assembly is selected in the Open dialog, Referenced by Top adds to the Open Dependencies dialog all models that are directly referenced by the assembly, but only required models are added for sub-assemblies. No Drawings Drawings are excluded from the Open Dependencies dialog, other than those previously selected in the Open dialog. Filters are applied in the same left-to-right order in which they appear in the Filters box, so one filter may reverse the effect of another. For example, the Required filter might exclude a drawing from the Open Dependencies dialog, the Implied filter might add it back, and the No Drawings filter might exclude it again. Opening SolidWorks Configurations The configurations within a SolidWorks model may be saved as separate items in Teamcenter, as if they are distinct models. For example, if a model has a design table, each SolidWorks configuration might be a separate Teamcenter item. You can add such configurations to the dialog by clicking on the model’s row to highlight it, then clicking the Add Configurations button in the Configurations box. Those configurations that exist as separate items in Teamcenter will be added to the dialog. If no row is highlighted, every model in the dialog is examined for configurations that were saved separately. Creating a new Teamcenter item and SolidWorks model The Create command in the Teamcenter task pane creates a new Teamcenter Item and a new SolidWorks model simultaneously. You should use this function whenever creating a new SolidWorks model that will be saved to Teamcenter, whether immediately or at some future time. 22 Figure 15 The Create New Teamcenter Item dialog The Create dialog contains key attributes that must be provided whenever creating a new Teamcenter item. These include item type, item ID and item name. First, select the desired template part from the list. If your SolidWorks preferences define multiple template locations, you can switch between then using the drop-down list. Depending upon configuration, the choice of template part may determine the default item type that is selected. This may be changed by selecting a different item type from the list. The list of available types is controlled by your Teamcenter administrator. You may manually type an item ID, or ask Teamcenter to assign one, with the Item ID | New button. The format of the assigned ID will depend upon the selected item type. Click in the Item Name field to automatically copy the item ID to the item name and the model name. If you wish to change either or both these values, you may do so by manually typing in the fields. If desired, enter a Model Description. This value will be copied to the custom Description property within the newly created CAD model, for later use in attribute mapping. Finally, accept the default Work Folder (which is based on your session’s current working directory), or select an alternative Work Folder. When you press the Create button, a new SolidWorks CAD model of the specified name and type will be created in the specified directory. A new Teamcenter item will be created with the specified type, ID, and name. When the CAD model is later saved to Teamcenter, the integration will find the matching item revision and save the CAD model as a dataset attached to the item revision. Items created using the Create dialog always go into the Newstuff folder. 23 Saving SolidWorks models to Teamcenter Two commands are available for saving SolidWorks models to Teamcenter. The Save command will save the SolidWorks session’s current model, and optionally its dependencies, to Teamcenter. It also saves checked-out models on which the current model depends. Save displays the dialog shown in Figure 16, allowing you to assign an item ID and other properties associated with the model in Teamcenter. The Save All command also displays the Save dialog, but populates it with all models in the SolidWorks session. If a model to be saved depends on others in the SolidWorks session, those models will also appear in the dialog. Figure 16 the Save Dialog The Save Dialog Regardless of the command you use to save a SolidWorks model to Teamcenter, the Save dialog is the same. To save models to Teamcenter using the Save dialog: 1. Put a check mark in the Save column next to each model you want saved. You can save only models that are new to Teamcenter or models that you have checked out. When saving a model that depends on another, and the latter has never before been saved to Teamcenter, be sure to put a check mark in the Save column for both models. The relationship between the models cannot be saved unless both models are saved to Teamcenter. 24 If you save a configuration, you must also save its document. If you do not save the document, the file that contains the configuration will not be saved to Teamcenter and any modifications you may have made to the configuration will be lost. The three columns to the left of the Save column indicate whether a change has occurred. A save diskette icon will appear in the first column if the model has been modified. A new dataset icon will appear in the second column to indicate that a new dataset version exists in Teamcenter. An item revision icon will appear in the third column to indicate that a later item revision is available. Finally, if a checkbox does not appear in the fourth column, then the user has not checked out the dataset. See the section titled Detecting Newer Model Versions for more information on these columns. The icons to the right of the Save column indicate the type of model in each row. The Item ID/Rev-Item Name column shows the objects Item ID as well as the Revision and Item Name, if the object exists in Teamcenter. You can click on the Tree View button in the Item ID/Rev-Item Name column to toggle the display of the tree view for hierarchical display. Click the button again to return to flat view. You can click in the Item ID column and type an item ID into the cell, or, after highlighting the row by clicking on it, you can click the New button in the Item ID box to make Teamcenter generate a new item ID, or you can click the Replace button to open a dialog for changing the item ID using a pattern you define. Refer to the following section on Creating a New Item for more information about saving models to other item IDs, and a technique for starting new models from seed parts in Teamcenter. If you assign the same item ID to several models, such as a part and its drawing, they will be saved to the same item. If a model is new to Teamcenter, you can choose its item type. Click and hold in the Item Type column to display a menu of available types. Other Teamcenter attributes, such as Item Name and Description, may also be updated in the Save dialog, if their columns are displayed in the dialog. The Teamcenter Administrator controls which columns are displayed. If the item already exists in Teamcenter, changes to the Item Type column will be ignored, unless you generate a new item ID for the model. 2. Select the Teamcenter folder to store all new data in Teamcenter. The browse button enables the user to change the default folder. Once selected, the folder will be remembered throughout the session, until it is changed again. 3. Choose what you want done with the local model files after they have been saved to Teamcenter. From the “Work Folder After Save” , select one of the following: Delete Files after Save After saving the models, Teamcenter deletes their local files. The models are no longer checked out after they are saved. 25 Retain Files after Save After saving the models, the local files are left where they are. The models are no longer checked out after they are saved. Retain Read-Only Copies after Save After saving the models, Teamcenter changes their local files to read-only. The models are no longer checked out after they are saved. Retain Checkouts after Save The models remain checked out to you after they are saved to Teamcenter. 4. Click the Save button at the bottom of the dialog. This saves the models that have a check in the Save column. Updating Model Names while Saving If a model is renamed in Teamcenter after it has been opened in SolidWorks, the local copy must be updated with the new name before it or any models that reference it can be saved back to Teamcenter. If the Integration finds models in the Save dialog whose local names no longer match their names in Teamcenter, a prompt similar to the one shown below will appear when the Save button is clicked. The Details button displays a list of the models whose names have changed in Teamcenter. A model must remain in the directory where it was placed when fetched from Teamcenter. If you move the model to another directory, the Integration will no longer know where the model came from in Teamcenter except by matching the model’s name to a dataset, so if the Teamcenter dataset has been renamed, the Integration may assume the local model is new. The Rename All button renames models in SolidWorks to match their current names in Teamcenter, then proceeds with saving the models selected in the Save dialog. The Rename None button saves models to Teamcenter without renaming any in SolidWorks. The Rename None button will not be available if any model being saved requires renaming or references a model that requires renaming. Click Cancel to return to the Save dialog. Figure 17 Renaming in-session models to synchronize with Teamcenter Creating a New Item You can make the Integration save a model to another item by changing its Item ID column in the Save dialog. You also have the option of renaming the model in the SolidWorks session to match its new item ID. 26 If the model is checked out to you, saving the model to a new item does not affect your reservation on the model in the “old” item. The dataset in the original item will remain checked out to you. Click on the model’s Item ID in the Save dialog to select it, then use one of the following techniques to enter a new item ID. Type the new item ID into the selected table cell. Choose an appropriate type in the Item Type column and click the New button in the Item ID box above the table to have Teamcenter generate the next available item ID. Click the Replace button in the Item ID box to open the Replace Item ID dialog. Refer to the section on The Replace Item ID Dialog for more information. If the original ID in the Item ID column referred to an item that already exists in Teamcenter, you will be asked to confirm that you want the model saved to a different item. A typical prompt is shown below. Click Yes to confirm that you want to assign a new item ID to the model. Click No if you do not want the model saved to a different item. No will also restore the previous item ID and discard any new value you might have entered in the Item ID column. Figure 18 Confirmation dialog when assigning a new item ID If more than one row is selected, you may receive this prompt several times. The Yes to All and No to All buttons have the same meaning as Yes and No, respectively, but they also apply your response to the remaining models in the selection. For example, if you want to assign item IDs only to models that do not yet exist in Teamcenter, click No to All. This prevents Teamcenter from generating new item IDs for rows that already refer to existing items and allows it to complete the assignment of item IDs to rows that refer to new items, without further prompting. The Cancel button stops Teamcenter from assigning any more IDs to the selected models, but it does not discard IDs assigned before the prompt. If only one row is selected, Yes and Yes to All are equivalent, and No is the same as No to All or Cancel. If you change an item ID, the Integration will also offer to rename the model to match the new item ID. For example, if you assign the item ID MID_SECTION_1P477 to a model named CENTER_SECTION_1P477, you would receive the prompt shown below. Click Yes if you want the model renamed in the SolidWorks session to match the new item ID. Click No if you do not want to rename the model. 27 Figure 19 renaming the model to match the assigned item ID If more than one row is selected, you will receive this prompt several times. The Yes to All and No to All buttons have the same meaning as Yes and No, respectively, but they also apply your response to any remaining models in the selection, if their item IDs are also changed. The Cancel button stops Teamcenter from assigning any more IDs to the selected models, but it does not discard IDs or change model names assigned before this prompt appears. If only one row is selected, Yes and Yes to All are equivalent, and No is the same as No to All or Cancel. Renaming a model in the Save dialog immediately renames it in the SolidWorks session. The SolidWorks session will continue to refer to the model by its new name even if you cancel the Save dialog. You will not be prompted to rename a model if its item ID does not change. If a model was previously saved to Teamcenter, renaming it in the Save dialog does not rename it in Teamcenter. The Integration will save the renamed model under its new item ID without affecting prior copies of the model stored in other items or under another name. The Replace Item ID Dialog The Replace button in the Save dialog’s Item ID box displays the Replace Item ID dialog shown here. This dialog changes item IDs according to one of the following patterns. 28 Figure 20 The Replace Item ID dialog Add Prefix adds text to the beginning of every item ID highlighted in the Save dialog. The prefix text is whatever you type into the Add Prefix box. For example, if the Add Prefix box contains NEW_, an item ID 1234567 will become NEW_1234567. Alternatively, if New Item ID is checked, the Add Prefix box is ignored and the prefix is a new item ID generated by Teamcenter. Add Suffix is similar to Add Prefix, but adds text to the end of every item ID highlighted in the Save dialog. For example, if the Add Suffix box contains _OLD, an item ID 1234567 will become 1234567_OLD. Find attempts to match the contents of the Find box to text within each highlighted item ID in the Save dialog. If a match is found in an item ID, the matching text is replaced with the contents of the Replace With box. For example, if the Find box contains 345 and the Replace With box contains XYZ, an item ID 1234567 would be changed to 12XYZ67. Alternatively, if New Item ID is checked, the Replace With box is ignored and matching text is replaced with an item ID generated by Teamcenter. Only the last match is replaced in each item ID, so an item ID 345345 would be changed to 345XYZ. Wildcard characters have no special meaning in the Find box, so entering * or . in the Find box will exactly match those characters. Advanced opens the Advanced Replace Item ID dialog, which may be used for more complex patterns, including wildcard characters. See The Advanced Replace Item ID Dialog section in the appendix for more information. To change item IDs using a pattern: Choose one of the three pattern types in this dialog and enter text in the appropriate box for your choice, or click the Advanced button to open the Advanced Replace Item ID dialog. Click the Preview button to see how the item IDs in the Save dialog will change. If you have checked New Item ID to make Teamcenter generate new item IDs, a placeholder value will be 29 substituted wherever a new item ID would appear. New item IDs will not be generated until the OK button is clicked. Click the OK button to change the highlighted item IDs in the Save dialog. Creating a New Item Revision You do not have to check out a model to revise it, but the model must be in the SolidWorks session. To create a new revision of a model, use the Save command to display the Save dialog, then: Click on the model’s Revision column in the Save dialog to select it and use one of the following techniques to enter a new revision ID. o Type the new revision ID into the selected table cell. o Alternatively, click the New button in the Revision box above the table to generate the item’s next available revision ID. The new revision will be created when you click the Save button at the bottom of the Save dialog. When the Integration creates a new revision, it creates new datasets and new BOMs instead of copying the previous revision’s contents to the new item revision. The new item revision’s contents are derived solely from what you check in with the Save dialog, so models that are not saved during this operation, and nonSolidWorks datasets and BOM lines, will not appear in the new revision. Saving Configurations and Design Tables SolidWorks configurations can be saved as separate items in Teamcenter. This is possible for any configuration in a part or assembly document, including configurations that are created from a design table. For example, a part document might define a family of bolts in a design table. Each bolt should be treated as a distinct part in Teamcenter so it can be included in a bill of materials, with its own item ID and revisions. The Save dialog and several user preferences make this possible5. If you want to create separate items for a model’s configurations, you can add the configurations to the dialog by clicking on the model’s row to highlight it, then clicking the Add button in the Configurations box. If no row is highlighted, configurations from every model are added to the dialog. Configurations that are not resolved, or are otherwise not in the SolidWorks session, will be brought into the session when the Add button is clicked. If you want to remove a configuration so a separate item is not created for it, click on the configuration’s row to highlight it, then click the Remove button in the Configurations box. 5 See the Administration Guide for more details on user preferences. 30 Exclude from bill of materials Flag The SolidWorks component has a flag which marks a model to be excluded from the SolidWorks BOM. The SolidWorks integration to Teamcenter honors the flag, excluding the component from the Teamcenter BOM for the assembly during save. Instead of creating a SWIM_Dependency relation for the component, a SW2BOM_exclusion relation is created. During open, SW2BOM_exclusion relations are considered required, so they appear in the open dependencies dialog even when the required filter is selected. If a model which has “exclude from bill of materials” selected is also suppressed at the time of save, then the model will not be in the BVR and will be stored as a SWIM_Suppressed_Dependency. As a suppressed component, the model will not be considered as required during the assembly load operation. Figure 21 SolidWorks Exclude from Bill of Materials setting Saving Auxiliary Files If the Integration has been configured to save auxiliary files, a set of checkboxes may appear across the bottom of the save dialog. Auxiliary files might be derived from your SolidWorks models, such as JT files for visualization in the Teamcenter Rich Client or PDF files of drawings, or they might be other files that you want to associate with your models. Checkboxes in the Auxiliary Files box allow you to choose the kinds of auxiliary files to save. The Save SolidWorks Models checkbox is always on by default. If you turn off this checkbox, the Integration will not save your models to Teamcenter, but it will still save auxiliary files for the models that have a check in the table’s Save column. Turn off the Save SolidWorks Models checkbox if you are using the Save dialog to save only auxiliary files to Teamcenter without their models. If Save SolidWorks Models is off, models will still be saved from the SolidWorks session to the local file system, in case an external program must be executed to create auxiliary files from your models. If a Save JT Files checkbox is shown, a check tells the Integration to save JT files to Teamcenter. Turning off the check prevents the Integration from saving JT files. 31 Additional checkboxes may be shown in the Auxiliary Files box, depending on how the Integration has been configured at your site. Adding Items to a Teamcenter Folder All models saved to Teamcenter are put into a folder. The first time you save models to Teamcenter, the destination folder is set to “Home\Newstuff” by default. You can change the destination by clicking the Browse button, then selecting a different folder, or creating a new folder. For the remainder of the SolidWorks session, your last folder selection is retained so that subsequent saves will reuse that folder, unless you once again change the destination. The destination folder can only be controlled for models being saved to new items in Teamcenter, that is, being saved for the first time. Once a model and its item have already been saved, they are in a folder, and the Integration will not attempt to move or copy them to a different folder, regardless of what the user selects. However, the integration may create links to additional selected folders, if the Teamcenter Administrator has configured the system to do so. If you do not wish to explicitly select a folder destination for the new items, then you may select the top-level Teamcenter folder in the folder selection dialog: Figure 22 Selecting the Teamcenter pseudo-folder This is an abstract pseudo-folder that does not exist in Teamcenter, but serves as a placeholder for the Teamcenter database itself. When you select this folder as the destination, then the actual destination will be determined by a Teamcenter preference, which is documented in the Integration’s Admin guide. Submitting Items to a Teamcenter Workflow The integration can submit selected item revisions to a designated Teamcenter workflow, during save to Teamcenter. The save dialog includes a column with a Submit to Workflow icon heading: 32 Figure 23 Submitting an item revision to a workflow The default workflow is determined by your Teamcenter Administrator, but can be changed by selecting a different workflow from the drop-down list in the Workflow column. You can submit all saved models to a workflow, or a subset of them, by selecting the checkboxes under the Submit to Workflow column on the left. The integration will submit the item revisions for the selected models to the designated workflow(s), but will not track their workflow status, and will not report errors that occur within the workflow, after the initial submission. Managing models in session The integration provides several functions for monitoring the status of in-session models, and for updating models with newer versions or revisions from Teamcenter. All of these functions are available in the Teamcenter task. Detecting updates in Teamcenter While a user is working on an assembly in SolidWorks, other users may check in new versions or new revisions of components which are used by that assembly. This creates an “out of date” or “superseded” condition which must be recognized and managed. Each user should periodically press the Refresh button in his Teamcenter task to check for updates in Teamcenter6. When one or more of his models has become superseded, the integration will display a warning icon at the top level of the model tree: 6 The integration will automatically refresh the Teamcenter task after every Teamcenter operation is performed. But the user can work for long intervals of time in SolidWorks, without interacting with Teamcenter. Therefore it is important to explicitly refresh the session regularly. 33 Figure 24 Top level out of date warning This is simply an indication that something has been updated in Teamcenter, and that he should expand his model tree to see more details. When he expands the tree, he will see the same warning icon next to each superseded model, as shown below. By hovering his mouse over the icon, he can learn whether his in-session model has been superseded by a new version, or by a new revision: Figure 25 Model is superseded by a new version In many cases, the user will only want to perform an update when new versions are available. A new revision implies that a more formalized change has taken place, and he will want to close, then reopen, his top-level assembly with the appropriate revision rule. Updating in-session models from Teamcenter When the user has decided to perform an update, he can select an assembly at the desired level in the structure (note that in the above example, the new version is a component of the top-level assembly, so he must update at the top level), and then select Update Model from the right mouse button pop-up menu: 34 Figure 26 Updating the top-level assembly This function displays the Update Models dialog, which contains a list of all superseded models. All version-superseded models are pre-selected for update, so that the user can simply press the Update button, to get all the latest versions. Figure 27 The Update Models dialog, with versions pre-selected If he wishes to also update to later revisions, he may do so. But for each revision-superseded model, he must select the desired revision from the drop-down list. There is no configuration context in this dialog and so the integration cannot predict which, of potentially many, revisions 35 he wants to retrieve. Note that when updating to a later revision, he must also select the Update check box, because new revisions are not automatically pre-selected: Figure 28 Updating to a newer revision After the update has completed, his Teamcenter task will be automatically refreshed to remove the out of date warning icons: Figure 29 Up to date session 36 Inserting models from Teamcenter While working with an assembly, the user can conveniently locate a part in Teamcenter and add it to his assembly, without opening it into a separate window. This is done by selecting the assembly to which the new model should be added, then selecting Insert Model from the right mouse button pop-up menu: Figure 30 Adding a new model to a selected assembly The Teamcenter Insert dialog is displayed, allowing the user to navigate to, or search for, the desired model. 37 Figure 31 The Teamcenter Insert dialog Once he selects the desired model, pressing Open will display the Teamcenter Insert Dependencies dialog: Figure 32 the Teamcenter Insert Dependencies dialog Here he can change the revision rule, change filter options, and perform all the other configuration tasks which are available in the Teamcenter Open dialog. 38 Finally, when he presses the Open button, the selected model, and its dependencies, will be fetched from Teamcenter and displayed in the SolidWorks Insert Model dialog, from which he can use standard SolidWorks functionality to drag and drop the model into his assembly: Figure 33 Inserting the model from Teamcenter Replacing models from Teamcenter The user can replace a selected component within his assembly with a substitute component from Teamcenter. He selects the component to be replaced, in the Teamcenter ask, then selects Replace Model from the right mouse button pop-up menu: 39 Figure 34 Selecting a model for replacement The Teamcenter Replace dialog is displayed, which allows him to search for the substitute model in Teamcenter: 40 Figure 35 Searching for the substitute component When he presses Open, the Teamcenter Replace Dependencies dialog will appear. If the substitution model is an assembly, he can change the revision rule, modify filter options, and perform all other configuration tasks which are available in the Teamcenter Open dialog: Figure 36 Replacing one part with another from Teamcenter When Open is pressed in the Teamcenter Replace Dependencies dialog, the selected model will be fetched from Teamcenter and displayed in the SolidWorks Replace Component dialog, from which the user can select options for the replace operation: 41 Figure 37 The SolidWorks Replace Component dialog When he proceeds with the replacement, standard SolidWorks functionality allows him to manage assembly constraints such as mates: 42 Figure 38 The SolidWorks Mated Entities dialog And the component is replaced in the assembly. The success or failure of the replace operation, within the CAD session, is not under the control of the Teamcenter integration. It is dependent upon the similarity of the CAD models, and the compatibility of the substitution model with the parent assembly. As illustrated in this example, only the first occurrence of a selected component will be replaced. This is because the Teamcenter task shows “packed” occurrences, and it is not possible to select an individual occurrence for a replacement. If the user wishes to replace all occurrences of the component, he must do so using standard SolidWorks functionality, by selecting each remaining occurrence and performing the replacement operation. 43 Figure 39 Only the first of 4 occurrences is replaced Managing Work Directories Two commands are available for updating local copies of SolidWorks models when newer versions become available in Teamcenter. The Update Directory command displays the Update dialog shown below, which initially shows models in the current directory. You can browse to other directories on your file system, update models to export their latest versions from Teamcenter into the directory, open models in your SolidWorks session, or delete files from the directory. The Update Dialog The Update Directory command displays the contents of a directory. The Update dialog shows the models in the directory, but it does not show relationships between the models, so the Tree button gives only a flat view of the directory’s contents. Also, only SolidWorks documents will be shown. Configurations will not be visible in a directory. 44 Figure 40 The Update Directory dialog Browsing and Updating Files To update model files with their latest versions from Teamcenter: 1. Check the columns that apply to what you want to do: Put a check in the Fetch column to indicate that the latest version of the model’s file should be exported from Teamcenter to the directory. Models that do not exist in Teamcenter will not have a checkbox in this column. Put a check in the Open column if you want to open the model in SolidWorks after its file is updated. Models which are already open in the SolidWorks session cannot be fetched or opened. Put a check in the Checkout column if you also want to reserve the model when the file is exported. You can put a check in the Open column without checking the Fetch column if you want to open the model without updating its file. The model will be opened when you click the Update Files button. 45 The first three columns, to the left of the Fetch column, indicate whether a change has occurred in a model. By default, a check will appear in the Fetch column if a newer version of the model is in Teamcenter and no unsaved changes have been detected in your local copy of the model. For more information on these columns, see the section on Detecting Newer Model Versions. The icons to the right of the Checkout column indicate the type of model in each row. 2. If you want to update your model with a file from a different item revision, click on the model’s cell in the Revision column to choose from a menu of the available revisions in Teamcenter. If a model you have selected to update has new dependencies in Teamcenter, the Dependencies dialog will appear later with all of these models in it. If you want to change the rule that selects revisions before the Dependencies dialog appears, select the rule from the menu in the Revision Configuration box. A filter may also be configured for use by the Dependencies dialog by clicking on any checkbox in the Filters box. The Revision Configuration box is described in the section on The Open Dependencies Dialog, and filters are described in the section on Filters. If you are updating a directory, the Teamcenter Integration for SolidWorks will look for dependencies in that directory before attempting to fetch them from Teamcenter. If you are updating models in the SolidWorks session, the Integration will look for dependencies in the SolidWorks session. Models that are locally available elsewhere could be overlooked and fetched again from Teamcenter. 3. Click the Update Files button at the bottom of the dialog to update the model files, reserve models in Teamcenter, and open models in SolidWorks. Unlike other Integration dialogs, the Update dialog does not close after you click the Update Files button, unless Close This Dialog After Update is checked. When the files have been updated, you can browse to another directory by clicking the Browse button in the dialog’s top row of buttons. The directory’s contents will appear in place of the contents previously shown in the Update dialog. 4. When you are finished with the Update dialog, click the Close button at the bottom of the dialog. Deleting Files When the Update dialog displays the contents of a directory, the Right Mouse Button Delete can delete models from that directory. 1. Click on a row in the dialog’s table to highlight it. More than one row may be highlighted if you want to delete several models at one time. 2. Select Delete from the RMB popup menu to delete the highlighted models from the directory. 3. When you are finished with the Update dialog, click the Close button at the bottom of the dialog. 46 Canceling a Checkout The Cancel Checkout command displays the Cancel Checkout dialog shown below. The table in this dialog lists all of the SolidWorks models that you have checked out for modification. A model need not be open in the SolidWorks session to appear in this table. If you put a check in the Cancel column, your checkout of that model will be canceled when you click the OK button. Canceling a checkout means you can no longer save the model back to Teamcenter. Other users may checkout the model for modification after you cancel your checkout. If a model shown in the table is in the SolidWorks session, the first three columns indicate changes that may have occurred to it. For models that are not in the SolidWorks session, the icons shown in these columns depend on information gathered when the models were previously saved to Teamcenter. For more information, see the section on Detecting Newer Model Versions. Figure 41 The Cancel Checkout dialog To cancel the checkout of one or more models: 1. Put a check mark in the Cancel column for each checkout you want to cancel. When canceling the checkout of a document that has separately checked out configurations, put a mark in the 47 Cancel column for all of the configurations that are checked out, too. 2. Click the OK button at the bottom of the dialog. Local copies of the models are not affected by canceling checkouts. If you want to replace them with current versions from Teamcenter, use the Open command to fetch the models of interest after canceling checkouts. Changing User Settings The User Settings command displays your current user name, group, and role in Teamcenter and allows you to select a different group or role for subsequent operations. Changing Group and Role To change your group and role: 1. Select the group to which you want to change, using the Group pull-down. This may change the roles that are available in the Role pull-down. 2. Select a role from the Role pull-down. 3. Click the OK button to close the User Settings dialog. Figure 42 The User Settings Dialog Integration to Teamcenter Rich Client Customers may use the Teamcenter Rich Client to perform a limited set of functions on SolidWorks data. Several of these functions are also available from within the CAD session. 48 Launch to SolidWorks Button The integration installation process adds the button into the toolbar of the Teamcenter Navigator application. In the Navigator, if a user selects an Item, Item Revision, or Dataset, and then selects the button, the object will be sent to Solidworks. If no session is running, a new Solidworks session will automatically be started, and the integration’s Login dialog will appear, followed by the Open dialog. If SolidWorks is already active, the Open dialog appears immediately, without requiring a new login. In both cases, the Open dialog will display the model sent from Teamcenter, and will automatically select it. In most cases, the user only has to press the Open button to proceed to the Open Dependencies dialog. Figure 43 The Open dialog displaying an drawing sent from Teamcenter Revise SolidWorks items may be revised from the Teamcenter Rich Client client, just like any other item. The integration manages the new revision’s dataset and its CAD dependencies so that the new revision may be opened into SolidWorks successfully. Save As The Teamcenter Rich Client may be used to save an existing item to a new item with a new item ID. SolidWorks references are maintained such that the new assembly or drawing may be opened in SolidWorks, however the dataset belonging to the new item retains its name; it is not automatically renamed to match the new item ID. Baseline The Teamcenter Baseline function may be used on assembly structures that contain SolidWorks data. After the baselined item revision is created, it can be opened into SolidWorks for 49 reference. It cannot be checked out because by definition a Teamcenter baseline is frozen. It is recommended to always create precise baselines for structures containing SolidWorks data7. Appendix Configurations Every SolidWorks part or assembly has one or more configurations. Not all configurations are used the same way. The intent of the configuration affects how the configuration and its associated document should be managed. Configuration intended usage: 1. Product – A configuration which is intended to be a product, component of product or tool. a. Family Member – The document as a whole is a family of parts or assemblies (products) which have a common definition and usage. The intent is that each member of the family is to be manufactured. Often family members are defined in a design table. A Family Member is a product, so it aligns with the definition of “Product”, and the term “Family Member” will not be used again in the Configuration text that follows. 2. Representation a. Simplified Representation – Usually an assembly configuration, which is not intended for manufacture. The representation is used to simplify to work on a specific aspect of the structure during design b. Visualization – Usually an assembly configuration, which is intended to show what a structure looks like in specific orientations or component positions Managed and Unmanaged The integration enables configurations to be managed or unmanaged. Managed equates to deserving of an Item ID in Teamcenter. In general product configurations should be managed and representation configurations should remain unmanaged. The integration provides preferences and buttons on the save dialog to establish whether a configuration is managed. Save Dialog Buttons Also see the documentation of these buttons in the save dialog section of this document. Add – The Configuration Add button is used to add the non-active and non-referenced configurations of one or more documents to the save dialog. Remove – The configuration Remove button is used to remove a configuration from the save dialog. When removing an assembly configuration, the assembly’s relationships are merged back to the assembly document. Recommendations for working with configurations 7 Limit use of the Configuration Add button on the save dialog. Add should be used when multiple configurations in a document must be managed, and the document is being saved to Teamcenter for the first time. See the Teamcenter documentation for more information on baselines. 50 Users should never remove or rename managed configurations from a document saved in Teamcenter. Doing so will result in a configuration which cannot be opened. If a rename is required, the recommendation is to create a new configuration and leave the old or to use swimrename. Users should never remove “Master Configurations” from an assembly document which has been saved to Teamcenter. Doing so can corrupt BOMs. The assembly configurations of a document often have different component relationships (a component may be suppressed in one configuration and not in another, or a component referenced within a configuration can be different) thus resulting in different BOM structures to be managed. o Assembly documents are best managed without “Master Configurations”. In this way all managed configurations will have their own Items and therefore BOMs are not subject to changes in other configurations. o If the assembly does contain a “Master Configuration” it is preferred that the “Master Configuration” does not have any suppressed components. If the “Master Configuration” does not have suppressions, then the document can be opened from Teamcenter and user can switch to any configuration as all data will be fetched. o If all the configurations of an assembly document have the same relationships it is acceptable for the document to contain a Master Configuration. o If an assembly document has been managed in Teamcenter with a Master Configuration, do not remove the Master Configuration or BOMs may become corrupted within Teamcenter. o Configurations with the same name as the document are not recommended for assembly documents. o While saving an assembly, if a configuration appears (either during generation of the save dialog or from selecting Add button) it is best not to use the configuration Remove button. Use of the remove button is best for part configurations. Toolbox Parts SolidWorks toolbox is a library of fasteners, nuts, bolts, screws, bearings, and more. The toolbox is highly integrated into SolidWorks. SolidWorks enables the sizing of the components at the time of instantiation into SolidWorks assemblies. The toolbox is a powerful tool, and its files are best not managed by Teamcenter, but left to SolidWorks to manage. On the other hand, Teamcenter requires Items to exist for the toolbox parts, for life cycle management within Teamcenter. To enable Teamcenter knowledge of the toolbox parts, the SolidWorks integration to Teamcenter creates items, item revisions, and datasets for toolbox configurations, but does not store the files. A sw2Tbx dataset type is used to represent the toolbox parts. The associated items appear in the BVR of parent assemblies. Toolbox parts are represented by the icon in the integration dialogs. Toolbox parts are managed similar to assemblies and parts, with the following exceptions: 51 1. Configuration of the toolbox directory is required to recognize toolbox parts. Configuration is accomplished by specifying the sw.toolbox.dirs in the swim.cfg file. 2. The open command only opens toolbox parts within an assembly. A toolbox part cannot be selected for open or fetch in the open dialog. 3. JT files cannot be generated via Teamcenter Dispatcher. The only means to generate JT files is during the save operation. 4. Toolbox parts cannot be duplicated or renamed by the integration. The model name must remain unchanged. a. If a toolbox part has not yet been saved to Teamcenter, then the new item id and new replace buttons on save dialog will allow the toolbox item id to be set, but the model name cannot be changed. b. If a toolbox part has been saved to Teamcenter, then new item id and new replace buttons on save dialog will ignore toolbox files to avoid duplication of item ids and renaming of the models. c. The swimrename utility will not rename sw2Tbx datasets d. Sites should avoid having multiple items containing the same toolbox part. e. Once saved, the rename of the toolbox part item id can be performed within the Teamcenter Rich Client. 5. It is recommended that toolbox parts have world read access in Teamcenter to ensure that they can be accessed by all projects. 6. In a multi-site environment, it is recommended that sw2Tbx datasets be pushed to all sites as soon as they are created. Doing so will avoid the risk of duplicates in the database. 7. Revise of toolbox parts is allowed within Teamcenter, but it is not expected that a site would want to revise a toolbox part. The recommendation is to release toolbox parts once they are saved to Teamcenter and correctly contain all associated documents such as JT files. 8. Attribute mapping of toolbox parts is only supported in cadtopdm direction. When a sldtbx model is included in a “both” or “cadtopdm” direction mapping, the mapping will be silently ignored during the operation performing the PDM to SolidWorks attribute mapping. 9. Auxiliary files must be placed into the toolbox for the integration to load them into Teamcenter. 10. The swimexport utility does not export files for toolbox parts stored as sw2Tbx datasets. An assembly exported by swimexport must be opened with a SolidWorks installation having access to the toolbox. 11. The swimimport utility must be executed on a system with the toolbox for the sw2Tbx datasets to be created for the Toolbox parts. SolidWorks toolbox has three modes, “Create Configurations”, “Create Parts”, and “Create Parts on Ctrl-Drag”. Each of these methods has subtle differences which sites should consider carefully and establish design practices. 52 Usage Create Configurations Create Configurations is the preferred mode for the integration to utilize. If possible, set design practices to only use “Create Configurations” and to only save assemblies that are using “Create Configurations” to Teamcenter. Create Parts To manage “Create Parts” as SW2Tbx datasets in Teamcenter, the “Create parts in this folder” path must be included in the sw.toolbox.dirs path in swim.cfg. The “Create Parts” path must be the same for all users because SolidWorks stores the path in the referencing models. The “Create Parts” path must be shared on the network for all users a. Failure to make the path shared will result in assemblies that cannot be opened by all users. If sharing data across multiple sites, the “Create Parts” path must by synchronized outside of Teamcenter. Failure to synchronize the “Create Parts” directories will result in failures to open data. Create Parts on Ctrl-Drag As stated earlier, it is recommended that designers always use “Create Configurations” “Create Parts on Ctrl-Drag” enables users to use both the “Create Configurations” and “Create Parts” methods of Toolbox. Sites should manage both types of toolbox data as outlined above. If the “Create Parts” directory is not available and synchronized to all users, then some toolbox parts could be changed from “Create Parts” to “Create Configurations”. These changes could be problematic for users. Create Parts as SWPrt It is possible to manage “Create Parts” as regular part files. To do so, do not include the “Create Parts” path in the sw.toolbox.dirs in swim.cfg The integration will interpret the “Create Parts” as parts, and the mappings for sldprt will apply, instead of the mappings for sldtbx. Sites would want to set sw.configurations.hide.document.name = true The “Create Parts” path must not be a network path, and should not be synchronized between sites. The path should be local to the users’ system. If managed as parts, the data files are saved to Teamcenter, and will therefore be fetched from Teamcenter during open. When saving “Create Parts” as SWPrt, the integration does not protect against designers changing the model name or creating duplicate items of the same toolbox part. The part icon, not the toolbox icon will be displayed in the integration dialogs and task pane for “Create Parts”. If modifications are made to a “Create Part” while inserting, it is possible that the resulting toolbox document will contain a PreviewCfg configuration a configuration which most sites will not want to manage. The recommendation is to add PreviewCfg to 53 sw.configurations.hide preference to avoid multiple PreviewCfg datasets in Teamcenter. PreviewCfg may not be the name for all locales. Duplicating Items and Structures Using the integration client a user can duplicate items which are already in Teamcenter. The process is referred to as “In-Session Duplicate” The term duplication refers to making a copy of an item, and selected child items, for example a complex assembly. The process of duplication is commonly used when a new design is to be created, based on an existing design. In such a case the existing design is duplicated to create the initial new design. The new design is then modified to finalize the design. In-Session Duplicate The in-session Duplicate function uses the integration Open and Save All dialogs to load all models into SolidWorks session from Teamcenter, duplicate the models in session, then save the models as new Item IDs to Teamcenter. Here are the steps: 1. Configuration: In the swim.properties file, it is recommended that the site replace the “No Drawings” filter option in the filters.checkout.choices preferences with “Include Drawings”. When checked, the “Include Drawings” filter will force all drawings referencing any models in a structure to be included in the open dialog. In addition this option will force the format files for the included drawings to also be included. For more details pertaining to this preference, refer to the swim.properties file. 2. Start a new session of SWIM and SolidWorks. Since large assemblies and their information may take up a large amount of memory. There should only be one session running and minimal other activity on the client computer. 3. Use Teamcenter | Open to search for a structure to be duplicated. This is usually a drawing or assembly with many children. Once the search is complete, the user should select both fetch and open into session checkboxes of the object to be duplicated. 4. For the duplicate to be successful, the user must ensure that all desired models will be loaded into the session. Thus the following should be checked or not checked. a. In the main panel, select both the fetch and open in session checkboxes for the selected top level item b. In the Filter panel, the Required filter must not be selected, to ensure all relationships are traversed (such as part to part or part to assembly) c. Also in the Filter panel, the Include Drawings filter checkbox must be selected to include all drawing for all models of the structure8. d. Do not select the “Lightweight” checkbox. 5. Set the destination directory to a new or empty directory to avoid conflicts 6. Select the open button 8 Drawings that reference models outside of the structure being opened are excluded, to prevent uncontrolled traversal of external references. 54 7. On the open dependencies dialog verify that all models (items) to be included in the duplication are present. 8. Once the models are loaded into session, verify that all models to be duplicated are resolved in session. Lightweight models will not be duplicated. 9. Once the models to be duplicated are resolved in the SolidWorks session, select Teamcenter | Save All . 10. Click the Configurations | Add button. Failure to do so will result in two documents within Teamcenter that contain configurations with the same names. The name clashes will degrade the performance of the integration. 11. Select all of the models in the save dialog () then use the Item ID | New or Item ID | Replace buttons to change the names of the models. When prompted to rename the items, click “yes to all” and for the prompt to rename the models, click “yes to all”. The files are now renamed within the session. 12. All models should now be selected for save. Click on the save button to complete the operation. The above procedure is the recommended process to duplicate all objects in a structure inside the SolidWorks session. Some users may want to modify the procedure for specific situations by choosing different filter options, setting models to lightweight or unselecting objects in the open or save dialogs. A common procedure would be to unselect toolbox parts (nuts, bolts) when assigning new Item IDs in the save dialog. Partial duplicates or bottom up duplicates are supported. If a user knows that five parts and their parent models are to be duplicated, then the user can use an iterative process, as described below, for step 11: 1. Select the five parts and assign new IDs and model names via Item ID new or Item ID replace buttons. 2. After the model names are changed, the modified hint will appear in the left column for the five models and the parent assemblies that reference them. The five models will have checkboxes in the save column and the modified parents will not. 3. Select the modified parents, and use Item ID new or Item ID replace buttons to assign new IDs and model names. 4. Repeat steps 2 and 3 until no more models have a modified hint without the save checkbox selected. If a parent model is included in a duplicate, but a child model is not, then the duplicated parent will reference the original child. This presents a problem where circular relationships are involved, because the parent will know the original child, but the original child will not know the duplicated parent. For this reason, it is recommended that all data in a structure be included in duplication. 55 The Advanced Replace Item ID Dialog The Advanced button in the Replace Item ID dialog displays the dialog shown below. This dialog provides more sophisticated capabilities for finding and replacing patterns in item IDs. Figure 44 The Advanced Replace Item ID dialog The pattern, under If Item ID Matches, is built from elements selected from the Available to Match list. The replacement, under Replace With, is built from elements in the Available to Replace With list. If a highlighted model in the Save dialog has an item ID matching the pattern, the replacement becomes the model’s new item ID. Figure 45 A Text element used in a pattern. Each element in the pattern and in the replacement has two parts, a title and a value, which are displayed with the title above and the value immediately below it. The title identifies the type of element and the value is data you have entered. For example, the preceding figure shows a Text element used in a pattern. Its title is Text (pattern elements may also include a number in their title as an aid in locating them within the pattern; replacement elements are not numbered), and 56 its value is the literal text _00 that this element of the pattern should match. You can modify an element’s value by clicking on the value, if the element has a modifiable value. Elements can be rearranged by dragging their titles left or right to a new location. To change item IDs using the Advanced Replace Item ID dialog: 1. Create a pattern from elements in the Available to Match list. Click on an element in the list to select it and click the Add button to append it to the end of the pattern, or doubleclick the element in the list. Drag the element by its title if you want it in a different location in the pattern. An element can be removed from the pattern by clicking its title to highlight it, then clicking the Remove button. 2. Create a replacement from elements in the Available to Replace With list. Click on an element in the list to select it and click the Add button to append it to the end of the replacement, or double-click the element in the list. Drag the element by its title if you want it in a different location in the replacement. An element can be removed from the replacement by clicking its title to highlight it, then clicking the Remove button. 3. Click the Preview button to see how the item IDs in the Save dialog will change. If the replacement includes a New Item ID element, a fictitious value will be substituted wherever a new item ID would appear. New item IDs will not be generated until the OK button is clicked. 4. Click the OK button to change the highlighted item IDs in the Save dialog. Pattern Elements The elements that can be used to build the pattern are found in the Available to Match list. To add an element to the If Item ID Matches pattern, click on the element in the list to select it, then click the Add button above the list. Double-clicking an element in the list is an alternative way to add it to the pattern. Once an element has been added to the If Item ID Matches pattern, you can remove it by clicking on its title to highlight it, then clicking the Remove button above the Available to Match list. Characters specifies a set of characters, any one of which may be matched. For example, you might want to match any digit, or any character in the set ABCD, or any character except those specified. You can also specify the number of characters to match, such as zero or more, one or more, exactly five characters, and so on. A Characters element is modifiable, so you can click on its value to change it once you have added it to the pattern. Group is really two elements that you can arrange to enclose other pattern elements. The resulting group can be treated as a single pattern element for certain purposes. A Group element by itself has no value that can be modified. Or creates a choice between two pattern elements. Drag an Or element between two other pattern elements to create a pattern that matches either the element to its left or the element to its right. For example, if you want a pattern to match either XYZ or 345, you can create two Text elements, one in which the value is XYZ and the other in which the value is 345, then create an Or element and drag it between the two Text elements. You can also leave one side of the Or empty if you want to match nothing. For example, if 57 you want a pattern to match an item ID that may or may not contain the text XYZ, you can create a Text element in which the value is XYZ, then create the Or and place the Text element on one side of it (you may need to enclose these two elements in a Group to use them within a larger pattern). An Or element by itself has no value that can be modified. Text specifies a string of text that is to be literally matched. A Text element is modifiable, so after adding it to the pattern you can click on its value to enter the text to match. None of the characters entered in a Text element have special meaning, so * and . match exactly those characters. Wildcard . matches any single character. It has no value that can be modified. Wildcard * matches any text of zero or more characters. It has no value that can be modified. Replacement Elements The elements that can be used to build the replacement are found in the Available to Replace With list. To add an element to Replace With, click on the element in the list to select it, then click the Add button above the list. Double-clicking an element in the list is an alternative way to add it to Replace With. Once an element has been added to Replace With, you can remove it by clicking on its title to highlight it, then clicking the Remove button above the Available to Replace With list. Copy copies text matched by a pattern element. After adding a Copy element to Replace With, click on its value to choose the pattern element to copy. You may want to use a Group in the pattern if you need to copy the text from more than one pattern element. New Item ID asks Teamcenter to generate a new item ID to insert in the replacement. The element’s value, which is optional, is a reference to a pattern element. New Item ID will re-use the same item ID every time the same text is matched by the pattern element. For example, suppose several models in the Save dialog have item IDs that begin with the same five-digit number, but end with different suffixes, such as 12345_00, 12345_01, 12345_02, and so on. The five-digit number should be replaced with a new item ID, but the suffixes should remain the same. You might create a pattern that uses a Characters element to match exactly five digits, then a Wildcard * element to match the remainder. The replacement can then use a New Item ID element whose value references the Characters element, followed by a Copy element that copies text matched by the Wildcard * pattern. When the first item ID containing 12345 is encountered in the Save dialog, the New Item ID element will ask Teamcenter to generate a new item ID. This might produce, for example, 67890, so the entire replacement might change 12345_00 to 67890_00. The next item ID in the Save dialog might be 12345_01, but since New Item ID has already asked Teamcenter to generate an item ID when 12345 was previously matched, it will re-use 67890 and change 12345_01 to 67890_01, and so on. If you do not assign a value to a New Item ID element, Teamcenter will generate a new item ID for every item ID you replace in the Save dialog. 58 Text specifies a string of text that is to be literally inserted into the replacement. A Text element is modifiable, so after adding it to Replace With, you can click on its value to enter the text to insert. Templates The pattern and replacement are initially empty, but several common patterns and replacements can be created by clicking a button in the Templates box. Each button in the Templates box clears the pattern and replacement, then adds elements as described below. Add Prefix creates a pattern that matches any item ID and a replacement that adds a prefix to the match. It is similar to Add Prefix in the Replace Item ID dialog. Add Suffix creates a pattern that matches any item ID and a replacement that adds a suffix to the match. It is similar to Add Suffix in the Replace Item ID dialog. Replace Prefix creates a pattern that matches the beginning of an item ID and replaces that prefix with a different prefix. Replace Suffix creates a pattern that matches the end of an item ID and replaces that suffix with a different suffix. Replace Text creates a pattern that matches text anywhere in an item ID and replaces it with some other text. It is similar to Find in the Replace Item ID dialog. 59
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Page Count : 64 Language : en-US Tagged PDF : Yes Title : Teamcenter Manager for SolidWorks User Guide Author : Bill Charlesworth Creator : Microsoft® Office Word 2007 Create Date : 2011:11:04 15:50:00 Modify Date : 2011:11:04 15:50:00 Producer : Microsoft® Office Word 2007EXIF Metadata provided by EXIF.tools