Teamcenter a Suite of Tools Developed by EDS PLM Solutions

Teamcenter

* Is a Suite of Tools Developed by EDS PLM Solutions.
* Provides the Collaboration of Tools Such As Teamcenter
Visualization, Teamcenter Manufacturing and Teamcenter
Automotive Engineering (TcAE).

Teamcenter Automotive Engineering (TcAE)/GM iMAN

* Is a Product Data Management (PDM) System for Information Required for the Design, Manufacture and Service of a GM Product.
* Is the Base or Commercial Product Providing a Business Modeler that Allows GM to Set up Unique Conditions Without Having to Write Custom Code.
* Provides a Standardized Environment to Manage Product Data, and
* Provides a Relatively Easy-to-use Interface for Daily Activities.
*TcAE also provides integrated, controlled, secure access paths to all information relating to the definition and development of product design. It allows the user to organize and track the status of the product design. In addition, TcAE provides an environment where simultaneous engineering can thrive. This means, given the appropriate level of permissions, others, such as suppliers and those involved in product assembly, can browse the data already created and make product development related decisions earlier in the VDP (Vehicle Development Process). This enables non-productive time and costs to be shaved, thus making GM's products more competitive in the marketplace. All the data generated by product design tools may be managed by TcAE.

The first interface of TcAE was Motif (A design that consists of recurring shapes or colors). The current interface is Portal. This class describes the TcAE Portal interface.

Product Management

TcAE is an application helping product data management. The TcAE application is a PDM system for information required for the design, manufacture and service of a GM product. TcAE manages this product data through the workflow management process.
TcAE Features and Functions

The features and functions of TcAE are:

- Data vault and file management
- Workflow and process management
- Product Structure Management (PSM)
- Part Classification






Data Vault and File Management
* All the Data Is Stored in a DATABASE
* All Data Exists One Time
* Data Is Pointed to Instead of Copied TcAE Database
* A Collection of Data Arranged for Ease and Speed of Search and Retrieval. One Big “Place”
*No Directories Visible to the User



Workflow and Process Management
 Establishes Process As a Sequence of Controlled Events
 Tracks Approvals and Authorizations
 Provides Electronic Approvals
 Provides Audit Trails
 Provides Secure Access to Product Data, Both In-house and From External Sites
Product Structure Management
- Provides Bills of Material (BOM)
- - Links product configuration with technical data



Product Structure (Assembly)
 Product Structure = Assembly
 Provides a Bill of Material
 Links Product Configuration With Technical Data
 Assembly Structure Can Be Viewed And/or Modified From the TcAE Product Structure Editor Application Without Opening Unigraphics NX
 Re-configuration of Assemblies Can Occur Instantly




TcAE Benefits:
* Maintains Relationships Among Product Life-cycle Data
* Provides an Audit Trail of All Product Life-cycle Data
* Supports Rules That Describe Data Flow and Work Processes
* Performs Notification and Messaging Functions
* Enables Users, Regardless Their Role, to Organize and Track the Status of a Product Design
*Improves Flexibility of Personnel Other Benefits
* Provides Controlled Access Via a Seamless Interface
* Provides Framework for Integration With Other Systems and Processes
Optimizes Use of Computing Resources
* Supports Concurrent Engineering by Enforcing Early, Often, and Maximum Sharing of Product Life-cycle Data Across the Distributed Organization




TcAE Can Help Me Do My Job
* By Maintaining All Master Data
* Providing the Appropriate Version of Data
* Notifying Users When Work Needs to Be Completed/reviewed

Potential Benefits of TcAE to GM
* Supports the Design Context Application to Allow for
Repeatable Digital Validation (RDV)
* Provides a Link to E2 and Part Reuse Systems
* Allows for Management and Configuration of Vehicle
Assembly Structure (VAS) Files
* Provides Information That Enhances the Filtering
Capabilities of .JT Files (Teamcenter Vis Products)
* Allows Viewing of an Assembly Structure Using the PSE
Without Launching Unigraphics NX
* Supports GM’s Fast to Market Objective
* Avoids Costs
* Reduces Error
* Allows Change Cycle Management
* Enables Integrated Product Development and Cross functional
Teaming
* Enables Implementation of Productivity and Process Improvement Measures
* Secures Information
* Reduces Design Searches



Teamcenter Automotive Edition (TcAE) is the new product replacing GM iMAN. Users logging into TcAE the first time will see a new user interface, Save, Save As and Create preliminary data functionality. That functionality has been replaced by TcAE Save As, Revise and Baseline functionality.

GM’s move to Team Center offers the following business benefits.
• Support for digital vehicle builds
• Improvements to iMAN Portal interface required for full RDV deployment.

• VDP acceleration
• Automatic Change Notification will enable parallel functions and downstream users of product math to be immediately notified when a part changes (Phase II).

• Structural cost reductions
• Previously GM-unique software, such as the custom Work Order, is now included in the commercial EDS/PLM software, reducing GM software maintenance costs while maintaining software capability (Phase II).

• Productivity and quality improvements
• Further integration with Releasing systems and Alias will enable future productivity improvements for engineers and designers.

TcAE Workflow
* Allows for Electronic Approval and Tracking of Parts.
* TcAE Will Set up a Series of Approvals or Signoffs Through Which the Object Must Pass.
* Allows the User to Choose From a Set of Pre-defined Process Templates That Must Be Followed in Order to Release Files with a valid release status.

TcAE Groups:
* Newly Created Objects Belong to the Group the User Is
Working in During Creation.
* During the Workflow Process Object Are Released in the
Group the User Is in During Initiation.
* If the User Has Access to More Than One Group They Need
to Pay Close Attention to Make Sure They Are in the Correct
Group During Object Creation and the Workflow Process.
TcAE Workflow Roles
* Creator (CRT)
Any Person Responsible for Creating, but Not Releasing, Math
Data Will Have the Role of Creator (CRT). The CRT Role Allows
the User to Modify and Approve, but Not Release, Design Work
Assigned to Them.
* Reviewer (RVR)
Any Person Responsible for Releasing Math Data Will Have the
Role of Reviewer (RVR). This Role Allows the User to Either
Assign Work to a Creator or to Perform the Work Them Self. The
User Must Have the Role of RVR to Release Parts Through
TcAE Workflow.
* VAS Coordinator
VAS Designers Have the TcAE Role of VAS Coordinator. This
Role Allows an Extra Sign off Step in the Workflow Process for
Installation Assemblies.
Job Processes
* The Objects Release Status is Determined By the Job
Process Selected.
Job Process Types
* Reviewer (RVR)
* The One Step Process is Used When the Reviewer Creates and
Approves His/her Own Work.
* Creator/Reviewer (CRT/RVR)
* Two Step Process is Used when the Reviewer Assigns Work to the
Creator.














TcAE accomplishes its goal by:

- Organizing, accessing, and controlling all product life-cycle data, regardless of its form.
- Providing immediate, secure access to product data, both in-house and externally.
- Maintaining relationships among product life-cycle data.
- Supporting the rules that describe data flows and work processes.
- Performing notification and messaging functions.
- Enforcing early, often, and maximum sharing of product life-cycle data across the distributed organization.
- Providing an audit trail of all product life-cycle data.

The TcAE database contains, or has access to, all design data created. TcAE organizes this data in such a manner that the data relates well to all product design responsibilities within GM. These responsibilities typically include individual, team, group, and product data functional responsibilities such as Database Administrator, Designer, Engineer, and Supervisor.

The TcAE tool will:

- Maintain all master data.
- Provide the correct data.
- Notify users when they must perform design work or review the work of others.



The most efficient method of designing products is through the use of concurrent or simultaneous engineering techniques.

TcAE enables concurrent engineering by making math data available throughout the organization for the entire Vehicle Development Process (VDP).

Having concurrent access to product design data early in the product life cycle greatly reduces the time required to bring a product to market.

By using concurrent engineering techniques instead of traditional linear methods, a finished product can yield:

- Higher quality
- Greater reliability and durability
- Lower production costs

Benefits of Controlled Early Data Sharing
All TcAE users benefit from the concurrent engineering TcAE offers. Specifically, Designers, Engineers, Design Engineers, and Supervisors, regardless of their physical location, have the ability to communicate and share product data.


For example, when developing a part for a vehicle, downstream users have the ability to see the design concept prior to its completion - the release of the part.

CONCURRENT ENGINEERING REQUIRES THAT PEOPLE SHARE EARLY AND SHARE OFTEN!

TcAE:
* Supports the Design Context Application to allow for Repeatable Digital Validation (RDV).
* Allows for management and configuration of Vehicle Assembly Structure (VAS) files, which contain entire Vehicle Platforms.
* Provides information that enhances the filtering capabilities of .JT files (Vis Products, formerly known as Product Vision).
* Allows viewing of an assembly structure, through the Product Structure Editor (PSE) without launching UG NX.
* Manages math in one common environment in support of The Design Analysis Process (DAP).
* Knows exactly where the vehicle is at any point in the VDP.
* Supports GM's Fast to Market objective.
* Avoids costs
* Reduces error
* Allows change cycle management
* Enables Integrated Product Development and cross-functional teaming
* Executes in a global virtual enterprise environment
* Enables for implementation of productivity and process improvement measures
* Secures information
* Reduces design searches


NOTE:
• iMAN (Teamcenter) is to PDM as UG is to CAD.
• iMAN is the product created by EDS PLM Solutions - sometimes referred to as "base" iMAN. GM iMAN is the GM customized version of the same software, which is now known as Teamcenter Automotive Engineering(TcAE)
• The name GM iMAN will be changed to Team Center Engineering in Version 8.
Tools Overview
Object Types
An object-oriented relational database uses graphical icons (Objects) for user interface. These objects are created and manipulated by users to manage product data. GM iMAN includes base iMAN Objects as well as GM iMAN specific Objects.



Item and Item Revisions
Items are the fundamental objects used to manage information. For example, Items represent parts, tools, criteria or process plan. They may be used to maintain, change and audit information. Each Item has a unique identifier.

Item Revisions are used to reflect change iterations of an Item. IMAN provides a historical reference to an Item without changing the original Item and provides a historical data trail. Each Item Revision has a unique Item identifier.

Fact! Each Item will have at least one Item Revision.

In GM iMAN, Items are categorized in order to represent particular things. Examples of types include vehicle parts which are managed in GM iMAN as CORP_Part Items.


Datasets

Fact! Datasets are containers for data. They typically hold UG NX files but they are also capable of holding text, images, etc.

Datasets provide the capability to store information files created by applications. The Dataset type is used to categorize Datasets. Examples of Dataset types are UGMASTER (master file), UGPART (drawing format), and Text.


Forms and Folders
Forms

Forms provide the ability to view and edit text in a defined template. Forms are associated with an Item or Item Revision. Examples are:
- Item Revision Master
- Item Revision Alias

Folders

Folders are objects that contain other objects. Folders provide a method to group and organize data in GM iMAN.

Fact! Folders can reference other folders.
Fact! An object can be contained in multiple folders. Even in multiple folders there is still only one instance of an object.

BOMView and BOMView Revisions

BOMViews manage product structure information for an assembly Item. Opening a BOMView or BOMView Revision object will launch the Product Structure Editor, which is used to create, edit or view an assembly structure
Object Privilege Icons
Teamcenter uses the icons shown below to show the privileges associated with an object. These can be found at right hand corner, near to cue line


The symbols means:





















Jobs and Tasks
A job is a sequence of tasks required to obtain a release status. The two Job Objects of the GM iMAN Workflow Management Process are the Work Order Job and the Item Revision Job. The Work Order Job and the Item Revision Job are created in the Workorder Application.


Tasks:

Jobs are composed of tasks according to the GM iMAN Workflow Management Process. Tasks of a job are displayed in the user's Inbox. The system assigns each job a name. Tasks are completed by signing off in the Viewer tab



Geography of GM iMAN


Workspace

There are several different windows within the GM iMAN application. The most commonly used window in GM iMAN is the Workspace window, My Navigator. One example of a window is the Home workspace window, which is explained later. GM iMAN opens in the My Navigator Application. The user ID and the name of the group the user is a member of are displayed in the title bar of My Navigator. There are three primary roles in GM iMAN:

- Creator (CRT): creates and edits math data
- Reviewer (RVR): assigns and approves tasks
- VAS Coordinator: approves tasks that are in Workflow in programs using the Design Context Application.
The window also has a pull down menu bar and a toolbar containing icons. Icons are quick keys to access or perform tasks. The Home Workspace, Inbox, and PSE windows will be covered later in the class.



My Navigator

My Navigator is the basic series of windows presented by GM iMAN when a user first accesses the system.

FACT! Workspace windows contain only references to objects; therefore any number of references to other objects can be established in the GM iMAN database.

This window is used to create, delete and associate database pointers (objects). The window's title is displayed on the top panel or the title bar. The title bar also displays the UserID of the individual signed on, the user's group, and their current role within GM iMAN. Objects are shown on the left side of the window under the Home tab. The columns to the right contain additional information about each object under the Properties tab.


The Viewer tab allows a user to view Vis Product data when the Item Revision contains a 3-D Format .JT Dataset. It provides tools for measuring, section-cutting, image capturing, and printing. To use the Viewer, select an Item Revision or the .JT object within the Item Structure, and select the Viewer tab. To exit the Viewer, select the Properties tab.

The Referencers tab allows a user to perform Where Referenced (database links) and Where Used (in assemblies) functions. To use, select an Item or Item Revision under the Home folder, and select the Referencers tab. From the Where: drop down menu, select the type of inquiry (Where Referenced or Where Used). If Where Used is selected, a Where Used rule, for revision statuses may be applied from the drop down menu. Select the Depth of the inquiry you wish to perform from the Depth: drop down menu. Double click the Item or Item Revision in the viewing area to yield the results.



Three objects are always displayed in the Workspace:

Home:

- Home folder
- Mailbox folder
- Newstuff folder


Mailbox:

New GM iMAN mail will arrive in the Mailbox folder. GM iMAN mail can be sent two ways:
- Using the My Navigator pull down menu
- Using Mouse Button Three (MB3) on an object and selecting Send To.

Inbox:

The inbox contains all of the in-process work assignments. It lists all tasks for a user and provides visual notification of the arrival of new tasks. The Inbox can be accessed from the Workspace window by clicking the Inbox icon. In addition, the Inbox icon will appear next to the clipboard identifying new jobs in your Inbox.

The Inbox will display two folders: Tasks to Perform and Tasks to Track. All Tasks for which the user is the responsible party will be in the Tasks to Perform folder. All tasks the user initiated, but is no longer responsible for, will be in the Tasks to Track folder.

Cut, Copy, and Paste Functionality:

The copy/paste functionality is useful in arranging objects into folders and copying objects from other areas into your Home Workspace. The pull down menu, 3rd Mouse Button (MB3) or the Copy and Paste icons can be used to copy and paste objects. Using Edit | Cut does not remove an object from the database. Delete is the term that describes the removal of an object from the database. Cut only removes the references to that piece of data from the workspace. In other words, the data that is cut away will still remain in the database.

Note: The only way to retrieve data that has been cut will be through the use of the Search function and pasting the data into a folder, if desired. Pay special attention to the use of Cut vs. Copy. If a Dataset is highlighted and then cut from the workspace, it is removed to the clipboard. If that Dataset is not pasted back into the workspace somewhere before another cut or copy action is performed, then the references will be lost. The only way to retrieve it will be through the use of Search.

Alternately, it is preferred that Copy be used to prevent lost references. By using Copy, the object will remain in the workspace and a duplicate will be placed on the clipboard. Therefore, if an object that was copied to the clipboard is inadvertently replaced by another cut or copy command, there will still be a reference to that object within the workspace that can be copied.
Search:

Search is a function that exists in My Navigator. One use of Search is to locate an existing Item. A user will specify the search criteria. There are many types of searches for objects in a GM iMAN Work Order, Item Revision, Dataset, CR (Cascade Release) Job, Item Revision Alias, etc.


Product Structure Editor (PSE):

The PSE is a graphical user interface that allows users to create, view, or modify product structure.

This view displays an Item "parent/child" structure used for assemblies. GM iMAN includes the PSE used to create and modify product structure

GM iMAN Applications
GM iMAN applications can be accessed in three ways: the Application Manager, the Applications pull down menu, or by using MB3 on an object and selecting Send to




Application Manager:

The Application Manager allows the user to access different GM iMAN applications, such as My Navigator or the PSE. My Navigator is the recommended application that is launched upon entering GM iMAN.
The PSE application is where the assembly structure is created, edited and viewed. The PSE can be accessed three ways:

* Through the Application Manager
* Through the Applications pull down menu
* By highlighting a valid object, using MB3 on the object and selecting Send to.
in-CLASS/classification(TcAe):

in-CLASS is used to create and maintain a hierarchical classification structure based on the attribute values of your GM iMAN workspace objects. Currently this application is ONLY used by GM Europe (GME) Manufacturing.






Referencers:

Referencers allows you to perform both Where Used and Where Referenced searches in the same display.
Process Viewer/workflowviewer(TcAe):

Process Viewer allows you to view the progress of a Workflow process, even if you are not a participating member of that particular process.

GM iMAN Workorder/CM Viewer(TcAe):

The GM iMAN Workorder application allows a user to view and edit Work Orders. Authority to edit Work Orders is determined by a user's role, found under Edit ׀ User Setting ׀ Settings.

Design Context:

The Design Context application allows users to configure specific vehicle variations. It is what enables Repeatable Digital Validation (RDV).


NOTE:
If an error message window appears, select the red "X" to display detailed information about the error.


Item Structure:


Master Model Concept
The Master Model Concept is the separation of the derived data from the basic geometry of the part. It is a method of handling the way a part is defined. It means that there is one and only one primary definition of the part, the Master Model. In IMAN, this primary definition is the UGMASTER. Any other part definition is considered to be derived from the master. In GM iMAN, the derived data is typically stored as a nonmaster type Dataset.

FACT! The Master Model Concept is integrated in the DCS (Data Creation Standards) and is used in the GM product design community



Items
Object Properties as Displayed in the Properties Dialog Box

Properties of Objects can be displayed in the Properties dialog box. Each Object will have its own unique dialog box. Highlight an Object and select the Properties icon.


Items are the fundamental Objects used to manage information. They can represent physical or conceptual entities that an organization uses to maintain, audit and change information. Items can be identified by an 8 character Item ID, then the FNA (Functional Name Address). An Item provides access to all information related to the design of a part and contains all of its revisions



There are eleven Item types:

Corporate Part (CORP_Part) is used for EPL (Engineering Parts List) part geometry and drawings of both GPDS (Global Product Description System) and Alphanumeric part representations. This Item type will be used in product design.

Corporate Installation (CORP_Install) is used for Installation Assemblies. This Item type will be used in product design.

Corporate Process Plan (CORP_Proc_Plan) is used for Product Assembly Documents (PAD), measurement points, weld points, datums, and data that describe a GM manufacturing process. It is also utilized for Vehicle Partition and Product Structure (VPPS) Level 1 and Level 2 files, within the Vehicle Assembly Structure (VAS). This Item type is used in product design and Manufacturing.

Corporate Vehicle (CORP_Vehicle) -is used for Total Vehicle Files. They are the highest level of file in a VAS. This Item type is used in product design.

Corporate Criteria (CORP_Criteria) is used for vehicle criteria and Studio Surface Releases. This Item type is used in product design.

Corporate Equipment (CORP_Equipment) is used for equipment such as Die presses, conveyors, and robots. This Item type is used in Manufacturing.

Corporate Facility (CORP_Facility) is used for Whole Plant Layouts, and also by the World Wide Facility Group (WFG). This Item type is used in Manufacturing.

Corporate Process (COPR_Process) is used for process oriented layout views such as Bill of Process (BOP) Layouts. This Item type is used in Manufacturing.

Corporate Simulation (CORP_Simulation) is used for 2D and 3D graphical simulation, primarily for detailed robot, operator, and workplace analysis. This Item type is used in Manufacturing.

Corporate Tool (CORP_Tool) is used for GM Tools, Dies or Fixtures. This Item type is used in Manufacturing.

Corporate Analysis (CORP_Analysis) is used for all analysis models, such as vehicle synthesis, analysis and simulation. This Item type is used in product design.




Item Revisions

Items house Item Revisions. There must be at least one Item Revision for each Item. The Item Revisions and related Objects are released in GM iMAN. Upon release an Item Revision receives a release status. A new Item Revision must be created if additional changes must be made to the data. Select the "+" symbol to the left of the Item to expand it. The Item Revisions are listed below.

To view the Objects associated to an Item Revision select the "+" symbol to the left of the Item Revision..




To view the Product Structure Editor (PSE) of an Item Revision highlight it, then using the third mouse button select send to PSE


Item Revision Master Form


The Item Revision Master Form contains Change Description fields that are populated with the change between the current Item Revision and the prior Item Revision. The form population is a manual effort. Item Revision Master Forms are assigned the same release status as their owning Item Revision.





To open the CORP_Part Revision Master Form double click on the object. Each Revision Level will have its own Master Form. The change description is only for alterations made to this Revision Level.


Standards for Filling out an Item Revision Master Form
Design will add revision history statements to the Item Revision Master Form to reflect the changes for a particular release. Changes to parts using common data files are recorded in the files that represent the complete part. Revision statements are not used in Common Data Files.

When There is No Drawing in the Item Revision
* Record changes to the part or assembly in the master form.
* The Item Revision that has the drawing for this part will be revised to reflect the change only when GD & T is affected..

When a part and a drawing are stored in the same Item Revision:
* Only changes to the math data are recorded in the master form and drawing changes are shown on the drawing when GD&T is affected.
* If there is a drawing only change, a new Item Revision shall be created and the revision statement in the master form is "NO MATH CHANGE SEE DRAWING".

When the Item Revision Only Has a Drawing
* Record changes in the drawing format. In the master form add "SEE DRAWING".
*Changes that are only shown on the drawing are not noted in the math data file.

Information is added, revised or removed to parts, assemblies, and/or drawings.

The information being changed may include (but is not limited to):
* Part features
* Quantity and/or position
* Administrative data
* Material specifications, general notes
* Tolerances, datums, Key Product Characteristics (KPC)
* Views, sections, etc.

Revision statements should list affected information (noun descriptive). First list the type of change (past tense verb such as added, revised, removed, etc.) and then any qualifiers last. Abbreviate statements when possible without confusing the statement meaning. Using this rule should address most revision instances


BOMView Revision

The BOMView is a Bill of Material for an assembly. The assembly structure of an Item Revision is contained in the BOMView Revision. If the Item Revision is an assembly then there will be a BOMView Revision. The BOMView Revision is created upon saving an Item Revision in UG.

Each Item Revision has its own BOMView Revision in order to document the assembly structure at the time of that release. Highlighting the BOMView Revision, using the 3rd mouse button (MB3), and Send to | PSE, opens the PSE application. (fig 1&2)


One of the features of the PSE application is the ability of the user to view Product Structure (UGMASTER only) without opening the part or assembly in Unigraphics. Refer to the Product Structure Management unit, in this manual, for additional features and information.



BOMView

Product Structure is associated to an Item by the BOMView. This view displays an Item "parent/child" structure used for assemblies. Sending the BOMView to the PSE Application displays the BOMView Revision that matches the default Revision Rule













(GM Work Order Form)/CM viewer(TcAe)

Technical requirements for a part are recorded electronically on the GM iMAN Work Order Form. GM iMAN automatically places a GM iMAN Work Order Form Object into the Requirements Relation of the Item Revision that is affected by the Work Order.

The GM Work Order form contains work instructions and lists the parts and the Revision levels (Item Revisions) that will be affected by the order. To view a GM iMAN Work Order highlight the object, using mouse button three (MB3), Send to the GM iMAN Work order Application.

GM iMAN is linked to E2 to allow viewing of Work Order information and the transfer of Work Order elements directly to GM iMAN. E2 is directly related/linked to the EWO system that is found within the parts list information located in GPDS. This connection provides Work Order.



information such as a Part Design Level Suffix (DLS), and Parts numbers and release levels, and the Work Order instructions. To access this link create a GM Work Order Form and send it to GM Work Order Application | Tools | E2 /EWO Info




Dataset Types

Datasets are used to store information from other applications. They are containers for data (math data, text, image, etc.) They provide pathways to other applications (such as UG).

UGMASTER Dataset (Master Part File)
CORP_Part - The UGMASTER Dataset contains the master geometry for the part as manufactured. For drawing items (Chart drawing, LH/RH drawing, etc), the UGMASTER collects the parts to be shown on the drawing.

Unigraphics math model Dataset is a UGMASTER type. Only one UGMASTER per Item Revision is allowed. Highlight the Dataset and select the UG icon to open a Dataset in Unigraphics.


Other Item Types - The UGMASTER Dataset contains the 3D master geometry for the item

UGPART Dataset (Non-master Part File)

CORP_Part and Other Item Types - UGPART Dataset types are used to store drawings. They derive their data from a master.


They are often used to reference geometry of a UGMASTER in a master model environment. When the user opens a Dataset, GM iMAN automatically opens the file and launches the application that created the file. UGPART datasets may not be referenced by an assembly.


UGALTREP Dataset (Non-master Part File)
CORP_Part - UGALTREP represents part deformations. A deformation is a part that changes shape when installed on a vehicle, such as cables, hoses, etc. If no manufactured state is required then the first used instance is the UGMASTER.

Other Item Types - UGALTREP contains any necessary alternate representations of the geometry


Other Dataset Types (Non_UG)
Direct Model- A Direct Model (.jt) dataset is a lightweight translation of the UG Master Model. They are used to view files using the Portal Viewer.

ALIAS_PROJECT-Used for Alias files
CGSWs-Used for CGS files.
AUTOCAD-Used for Autocad files.
UGMX_PART-Used for UGMX files.
TEXT - the TEXT Dataset type contains a file in UNIX or OL2Ke text file format (.txt). OL2Ke text files are normally Notepad files, while UNIX text files are normally Text Editor files. The use of Text Datasets is not permitted for UG files. To open a TEXT dataset you highlight the dataset and select File | Open and select the program you wish to view the dataset in.

Dataset Context

The Dataset Context names the Dataset. The following image describes their naming convention.


During creation the user is prompted as shown in the following screens to accept the default Dataset Context or specify an alternate by selecting the pull down menu.


Notice that the choice of alternate Dataset Contexts changes depending on the Dataset Type.



The context tells the user what type of data will be found in that Dataset. In this example, the user will find geometry in its final state – GEO_FIN.


The Dataset Context is chosen by the site defined Dataset Validation List of Values form or it can be changed as needed

Data Context for CORP_Part Items

The following contexts are commonly used in product design:

GEO_FIN (Geometry Final)
This context is used to describe an Item as manufactured or installed on the vehicle. The geometry can be at various stages of completeness.

PR_STAT (Process State)
This context is used to describe the state of a part in a specific stage of the manufacturing process. It is also used for common data files.

GEO_ENV (Geometry Envelope)
This context contains geometry defining the part envelope such as the exterior shape of a Part without internal details.

DRAWING
This context is used when the Dataset contains a drawing format.

SIMULAT
This context is used to capture derived data that represents simulation data. SIMULAT is used for motion files.

BOMSNAPSH
This context is used for a TEXT Dataset type, specifically for BOM View Revisions.
REPORT
This context is used for a TEXT Dataset type.

Dataset Context for Other Item Types
GEO_FIN
This context is used to describe an Item in its finished/final state.

GEO_ENV
This context contains geometry defining the part envelope such as the exterior shape of a Part without internal details.

DRAWING
This context is used when the Dataset contains a drawing format.

PR_STAT
This context is used to describe the state of a part in a specific stage of the manufacturing process. It is also used for common data files.

SIMULAT
This context contains derived data that represents simulation data.

NCDATA
This context contains geometry used for Numerical Control (NC), such as inspection data files.

INSPECT
This context is used for Coordinate Measuring Machine (CMM) data files.

GEO_PAD - contains geometry defining an Item at a specific step and/or breakpoint within a product assembly or manufacturing process.

Relationship Between Objects

In GM iMAN an Item Revision can contain data from several GM iMAN objects. For the data to be clearly understood and useful, it must be associated in a meaningful way to the Item Revision. This association is accomplished by using the concept of Relations. Relations provide a way to establish a connection between different object types (product information). A Relationship describes how the data is associated to an Item Revision.

The following relationships are commonly used in GM iMAN:
Requirements (GM Work Orders) does not allow addition or removal of objects after release of the Item Revision.
References (All other Objects) allow the addition or removal of objects after the release of the Item Revision.
Altreps (UGALTREP) allows the addition of objects but not the removal of objects after the release of the Item Revision.
Manifestations (UGPART) allow the addition of objects but not the removal of objects after the release of the Item Revision.
Specifications (UGMASTER) do not allow the addition of objects after the release of the Item Revision.

Some objects, when created, are automatically assigned a relationship. For example, a GM Work Order Form is automatically assigned a Requirements Relationship to the Item Revision that is associated with the Work Order.


How to Create Relationships

Relationships between GM iMAN Objects are established by using one of two methods:
- When an Object is initially created; a user can assign a relationship at that time.
- A user may also establish a relationship by copying the Object into a relationship using Edit | Paste… and selecting the relationship. For example, when adding a new UGMASTER to the Item Revision the required Relation is Specification. This is the system default.

Content and Behavior of Relationships
Objects located in a relationship must follow the rules set up for that particular relationship.


Specification Relation
The Specifications relationship is intended for Datasets that define the product (i.e. master model and/or drawing). A user with write access to the Item Revision may add or remove Datasets from this relation as long as the Item Revision has not been released.


Rules for the Specifications Relation:
- Locks upon approval of the IR (Objects cannot be added or removed without write access)
- Each IR will have only one UGMASTER Dataset as a Specifications Relation to that IR
- Objects in this relationship are visible from UG


Requirement Relation
The Requirements Relationship is intended for data that is input to the product design. Technical Requirements for a part placed in this relationship are associated to the Item Revision.

Rules for the Requirement Relation:
- Locks upon approval of the IR (Objects cannot be added or removed without write access)
- Objects in this relationship are not visible from UG

Manifestation Relation

A GM iMAN object (Item Revision or Dataset) can be associated to an Item Revision by placing the object in the Manifestations Relationship of the Item Revision. Objects placed in the Manifestations Relation are intended to be used by downstream' users, such as manufacturing. It allows for associative UG data (such as CAM or CMM files) to be added to the Item Revision after its approval. Objects placed in this relationship are subject to its rules.

Rules for the Manifestations Relation:

- The UGPART Dataset will reside in this relationship.
- Locks one way upon release of an Item Revision. The addition of Datasets is allowed but the removal is not.
- A form or Dataset can be placed in this relation

Reference Relation

An object (Items, Item Revisions, Datasets, Forms or Folders) can be associated to an Item Revision by placing the object in the References Relationship.

Rules for the Reference Relation:
- Does not lock (Objects can be added or removed with or without write access)
- Objects in this relation are not visible from UG
- Objects located here can include background data, finite element analysis data, and ad hoc assemblies

Altrep Relation
The Altrep Relationship is for the UGALTREP Datasets. The UGALTREP Dataset type is a special type of non-master UG Dataset that is used to create an alternate representation of a part such as the deformation of a part, or a simplified envelope of the part.

Rules for Altreps Relation:

- Locks one way upon release of an Item Revision. The addition of Datasets is allowed but the removal is not.

NOTE:
• The Manifestations Relationship is intended for UGPART (drawing) Datasets or for Datasets derived from the master model that are not primary definitions of the product.
• UGALTREP Datasets may be used as components in a UG assembly.



Search
Finding Basic Objects
There are many different types of searches in GM iMAN. Some of the common searches for object types include: Item, GM Work Order, Dataset, and CR (Cascade Release) Job.

Finding an Item

Select the Search icon.

The following are Search options:

Item ID:

Use this field only when searching for Items.

Wild Cards:

- Wild Card "*" may be used in all fields, along with other valid characters.
- Blank fields are treated as wild cards.

Process: Finding an Item:

1. In My Navigator, choose the Search icon. The Select a Query drop down menu appears in the Workspace. Select the down arrow. The words Select a Query only appear the first time the Search icon is selected. The name of the most recent search will show in the Search title bar thereafter.

2. Select Item from the drop down menu.

3. Enter the Item ID in the Item ID field.

4. Click the Execute icon.




A new tab is added to the Workspace area.

Note: To search with more criteria, select More…

5. To remove a tab, select MB3 | Close on the individual tab.


Refresh vs. Execute

You may choose to use the Refresh icon to re-execute a search using different criteria, or to see if the object has changed since the last search. Refresh will re-execute a search and display the results in the same tab.


Execute will perform a new search and produce a new tab.




Finding a GM Work Order/CM vieweer


Select the Search icon to locate a GM Work Order.

Process: Finding a GM Work Order

1. Select the Search icon.

2. Select General from the Select Inquiry drop down menu.


3. Enter the GM Work Order number in the Name field (wildcards may be used).

4. Click on the down arrow to the right of the Type field. The Object Selection dialog box appears.


5. Click on the down arrow until GM Work Order is displayed.


6. Highlight the GM Work Order from the list of options.

7. Select the Execute icon.

The find results are displayed in a tab in the Workspace area


Finding a Dataset

Select the Search icon to find a GM Dataset in GM iMAN.

Process:


1. From My Navigator select the Search icon. The Select a Query drop down menu appears.

2. Select General from the dropdown menu.

3. Enter the full Dataset name (or partial with wildcards) in the Name field.

4. Click on the arrow to the right of the Type field. The Object Selection dialog box appears.

5. Scroll down until the Dataset type (UGMASTER, UGPART, etc.) is displayed.

6. Highlight the Dataset type (UGMASTER, UGPART, etc.).

7. Select the Execute icon.

Utilize Dataset Versioning by reverting to a previous save of a Dataset.

Process: Restoring to Previous UG Save

1. Close all parts in UG.

2. Quit UG.

3. Choose the Options button at the bottom right corner of the Search Workspace.



4. The Options dialog box appears

5. Select the Query Options tab.

6. Toggle Latest Dataset Versions off.



7. Close the dialog window with the x.

8. Choose the Search icon.

9. Select General from the dropdown menu.

10. Enter the 8 digit Item ID with an * (example: 12345678*), in the Name field.

11. Choose the arrow next to the Type field.

12. Scroll down and choose UGMASTER.

13. Select the Execute icon.

14. The Search results tab appears with all versions of that Dataset.

15. Double click on the Dataset version you wish to view in Unigraphics.

16. Verify that the data loaded is the desired information.

17. Save the Part in UG.






Finding a Job

Select the Search icon to contain, within the context of GM iMAN Workflow, the release procedure used to monitor and manage the execution of each task whether it is a sign-off task or a task which invokes a handler procedure. A Job is made up of tasks. The two different types of Job searches include: GM Work Order Job, and Item Revision Job. The process is the same; however, the search name information entered will be different.

Process: Finding a Job

1. Choose from My Navigator the Search icon.

2. Select General from the dropdown menu.

3. Enter the job information (Work Order, Item Revision or Dataset) in the Name field.

4. Click on the arrow to the right of the Type field.

5. Click on the down arrow until CR Job is displayed.

6. Highlight CR Job from the list of options.

7. The General dialog box reappears. Type is specified for a CR Job search.

8. Select the Execute icon. The find results will appear in a new tab.


NOTE:
• Since CORP_Part is a term used to represent a type of Item, it can be used in place of the word Item. For example, Item Revision = CORP_Part Revision.
• Wildcard "*" may be used in all fields, along with other valid characters.
• Blank fields are treated as wildcards.
• After selecting a down arrow, e.g. the arrow next to the Type field, begin typing the name of what you are looking for and the list will filter.
• The number after the semicolon is the Dataset version number. If versions do not display, you have the option of turning them on. To turn the versions on, choose the Options button in the bottom right corner of the Search Workspace. Select the Query Options tab and uncheck the Latest Dataset Versions box.
• When viewing results of a dataset version search, it is recommended that the following columns be added under the properties tab, Object, Version Number and Date Modified.

- The Object column will show the version number after the Name.
- The Version Number column shows only that.
- The Date Modified column shows chronology.

Referencers Application

Where Referenced
Objects can have relationships with other objects. Your workspace may not display all the relationships an object has within the system. The Where Referenced function is used to find and list these relationships.

Where Referenced function can be used with any GM iMAN Workspace object including:


- Datasets
- GM Work Orders
- Items
- Item Revision Masters
- Item Revisions

The referenced Objects can be copied into a workspace or sent to another application.
Where Used
The Where Used function locates every instance where an Item or Item Revision is used by other Items or Item Revisions, in components, sub-assemblies, or assemblies. For example, engineers contemplating making a change (Revision) to one of the parts (Items) for which they have design responsibility, might want to assess the impact of the proposed change relative to assemblies, sub-assemblies as well as individual stand-alone part applications. Using the Where Used function gives the user information to help him or her make informed decisions as to the impact of the timing of the revision to the part. The Engineer uses the Where Used function of GM iMAN to discover potential areas of impact prior to revising the part.


The Where Used function can be used with the following GM iMAN objects:

- Items
- Item Revisions

The Where Used function will not work with the following GM iMAN objects:

- Item Masters
- Item Revision Masters
- GM Work Orders
- Datasets
Using the Referencer Application: Where Referenced/Where Used

To access the Referencers application, highlight an object, right click (MB3) on the object and select Send to Referencers.


For less detailed results, Where Referenced or Where Used searches can be performed on an object, from the home workspace, by highlighting an object and selecting the Referencers Tab.

This application allows for the display results for both the Where Used and Where Referenced functions at the same time, for different objects. Once the initial object's search results appear, highlighting an object from this list, and selecting a function will provide additional results. Notice that red output lines follow the object to the display results for the Where Used function, and yellow output lines follow the object to the display results for the Where Referenced function.





Process: Using the Where Referenced Function


1. Highlight the object to be referenced.

2. Using the 3rd Mouse button (MB3) select Send to | Referencers.


3. Select the Referenced (User) function from the pull down menu.

It is not possible to set the Revision Rule for the Where Referenced function. For the Depth of the Report, select a level to specify how far down to search. Specify the desired Layout of the Display.


4. Double click on the object and the Where Referenced list appears.


5. Double clicking on additional objects provides more search results. (optional)




Process: Using the Where Used Function

1. Highlight the Item or the Item Revision.

2. Using the 3rd Mouse button (MB3) select Send to | Referencers .

3. Select the Where Used function from the pull down menu. Select the Revision Rule. For the Depth of the report, select a level to specify how far down to search. (Selecting All Levels uses excessive computer resources and is not recommended unless necessary.) Specify the desired layout of the Display.


4. Double click on the object and the Where Used Report list appears.


5. Double clicking on additional objects provides more search results. (optional)


Preliminary Data Indicator/Baseline(TcAe)

A PDI (Preliminary Data Indicator) is a type of Item Revision often created for data sharing. Data sharing is required as parts are being developed. PDI releases are required at least every 2 weeks if the math file is still changing. This type intentionally indicates that this part is preliminary by reflecting a release status containing a X for experimental. The status is immediately granted to a PDI Item Revision, without prior approval.

A PDI can be created by anyone who has Write access to the Item Revision. When an Item Revision is in the workflow process, the owner of the Item Revision can create a PDI. The Item Revision must be a Work In Process (WIP) in order to create a PDI.

Here are two possible reasons to create a PDI:

- When WIP data is sent to someone outside of the GM iMAN system, a copy is sent and is also kept in the system for reference.
- To have a static copy that can be used by another internal GM iMAN user
PDI Dataset Carryover

All Datasets with a Requirements, Specifications, Manifestations and Altreps relation to the working Item Revision will be saved as new Datasets in the PDI Item Revision.

Each of the objects carried over will receive a Release Status containing a X. If a user does not have copy access to one or more Datasets in the working Item Revision, a warning message will be displayed; however, the PDI Item Revision will still be created.

All objects other than Datasets (e.g., Work Orders, Item Revisions, etc.) that have a Requirements or Specifications relationship to the working Item Revision will be copied and pasted in the new PDI Item Revision.

If the Item Revision has a release status, then a user will not be allowed to create a PDI Item Revision
Creating a PDI

The following are prerequisites for creating a PDI:

- You must have a WIP Item Revision.

- You must have write access to the Item Revision if it is not in Workflow.

- The file must be DCS compliant and pass file checker.

- To PDI an assembly and its WIP components create PDIs from the bottom up.

- It is desirable that PDIs be Precise (must be Precise for RDV programs).

- PDIs for export must be Precise.

- PDI Revisions may not be created for a revision level once that revision level has been released.

- The identifier is a three-digit numeric revision level plus a four-digit numeric PDI, separated by a period. For Revision 001, the first PDI Revision would be 001.0001



Process for Creating a PDI(TcAe):

1. Expand the Item.

2. Highlight the Item Revision.

3. Choose Tools | Baseline



4. Verify that the Create PDI dialog box appears.

5. Enter the reason for the creation of the PDI and any other desired information in the Baseline Template field.

6. Select Status: X.


7. Click OK.



Check Out and Check In

Check Out/Check In deals specifically with write privilege. It ensures that no two users have write privilege to an object at the same time. Only one user is allowed modification until they decide to relinquish write privilege by signing off on a part, transferring write privilege (transferring checkout) to another user, or by checking in the part.

When a Check Out is performed, it reserves an object in the database. The object can only be modified by one user. When a Check In is performed, the system clears the Check Out flag. Now the object is unreserved by any user.

Here are the types of Check In and Check Out that will be discussed in this unit:
- Implicit
- Explicit
- Transfer
- Cancel

Before starting a Job on an object, the object, as well as the targets of the Job, must be checked in or an error will occur.


Explicit Check Out and Check In


Explicit Check Out/Check In functionality allows the user to have exclusive write privilege to an object for an indefinite length of time. This is a manual effort achieved by selecting menus in the Workspace or using MB3.

Explicit Check Out/Check In is a type of Check Out that requires manual user intervention. This type reserves the file indefinitely. Explicit Check Out/Check In is a manual effort. There are a few different methods that will achieve Check Out in both UG and GM iMAN:

- (From any GM iMAN Workspace) Highlight Object and select Tools | Check In/Out | Check-Out.
- (From any GM iMAN Workspace) MB3 over the Object | Check-In/Out | Check-Out.
- (From the UG Assembly Navigator) MB3 over the part Check Out | Save




Implicit Check Out and Check In

Implicit checkout prevents two users from simultaneously modifying the same object. It locks the part file when it is first modified in UG. Any object which is not Explicitly Checked Out is a candidate for implicit Check Out if opened. It is the system default to allow write privilege only to the active user of that object. When the user is no longer modifying that file, the part is implicitly Checked In. Implicit Check Out/Check In is a type of Check Out where the system grants write privilege to the active user of a part while in the application (for example, UG). This type grants a user write privilege to the file until they close the part. This works only when no other type of Check Out is in place. Once it is Checked Out, it remains locked until it is saved or closed. No one else may modify it until it is Checked-In.

While the files are locked, there are several checks done by GM iMAN:
- Initial Access Check - GM iMAN locks the part file when it is first modified; if the user does not have write access to a file, a warning message will be displayed and the Dataset will not be Checked Out.
- Check For A Newer Version - GM iMAN checks the part file before locking it or saving it to verify it is the latest opened version, in case someone created another version.
- Write Access Check On Save Or Close - when a part file is saved or closed, it checks to see if the user has write access.
- Saving Component Parts - when an assembly is saved, UG will save all of the components with changes made to them.
When Does Implicit Check Out Occur?
UG Datasets - When the part file is modified and the word modified appears above the graphics display area.
Non-UG Datasets - The Dataset is Checked Out by the first user to open the Dataset
When Does Implicit Check In Occur?
UG Datasets – When the part file is closed.
Non-UG Datasets - When the Dataset is closed
Cancel Check Out

Cancel Check Out is a command only available to Datasets. It cancels the last Check Out and reverts the part to the state it was in at the time of that Check Out.

Be careful! This function may produce unexpected results.

Once a Check Out is cancelled, all changes made to a Dataset (saved or not) are gone.

This function in GM iMAN may be menu suppressed or unavailable at your site.

Note: Cancel checkout is used to cancel an explicit Check Out.

During an explicit Check Out, the Dataset version will be retained until Check In or Cancel Check Out takes place. Cancel Check Out will restore the retained Dataset version to the current Dataset version. In other words, what was old - possibly empty - is now current.

Using Explicit Check Out for UG Datasets
Use explicit Check Out for UG Datasets to ensure other users are not able to modify the UG Dataset. To Explicitly Check Out an object, the following conditions must be satisfied:
– The user must have write access.
– The object cannot be archived

Process: Using Explicit Check Out for UG Datasets

Once the above conditions are satisfied, the following steps are used to explicitly Check Out a UG Dataset:
1. From the workspace, highlight the UG Dataset to be Checked Out.
2. Choose Tools | Check-In/Out | Check-Out. The Reserve dialog box appears.
3. Enter reason for Check Out in the Comments field.
4. Click YES in the Reserve dialog box.
5. Choose View | Properties. Verify a Y is listed under the ExCO – Explore Checked Out field.

Process: Using Explicit Check In for UG Datasets

1. Highlight the Checked Out Dataset.

2. Select Tools | Check-In/Out | Check-In. Verify Check Out flag is removed. The only confirmation of this action is the flag (Y) will no longer appear in the My Navigator | Properties | CO - Checked-Out column.



Determining Who an Object is Checked Out To
To find out who an Object is Checked Out to, attempt to Check In the Object. Select the red X to display the name and user id of the person who has the Object checked out. An error message appears listing the person to whom the Object is Checked Out.

A second way is to highlight the object, then choose Tools | Check-In/Out | Check-Out History. The Check-Out History dialog box appears, listing the person to whom the object is Checked Out.

Transfer Check Out

Transfer Check Out is a shift in write privilege from one user to another. A Transfer of Check Out occurs when a user wishes to grant their write privilege to another user. When this action is performed, the Check Out or write privilege is immediately granted to the selected user.

This type grants the new user write privilege to the file indefinitely.

From any GM iMAN workspace, highlight the object to transfer and select Tools | Check-In/Out | Transfer Check-Out.

Note: This command only transfers Check Out, not sign-off.
NOTE:
• When you go to the library, you have the ability to Check Out a book and take it home (explicit) or sit at a table in the library and read it (implicit).
• If an object is Checked Out in the system, the letter Y will appear in the CO - Checked Out Column in the My Navigator Properties tab.
• Implicit Check Out is a temporary state that is only valid while the user is working on the file.
• Implicit Check Out locks the part file when it is first modified in UG. Although several other users may open the same part file at the same time, Check Out only begins when a user starts to modify it. Being Implicitly Checked Out will prevent others from modifying the same part file at the same time.
• Other users with write access are prevented from writing to this object when it is Checked Out.
• Other users with write access are able to write to this object when it is Checked In.
•
Product Structure Management
Product Structure Management
Is the GM iMAN functionality that deals with all aspects of assembly configuration
Product Structure Editor (PSE)
Is the GM iMAN application that is used to view, configure and edit iMAN assembly structures.

Product Structure or Assembly Product Structure Management (Assembly Management) is the functionality that manages the configuration of an assembly. In GM iMAN, Product Structure Management is represented by an object called BOMView. The BOMView captures and displays assembly and component relationships between Items or Item Revisions. The BOMView launches the PSE. On the GM iMAN side, it is possible to edit assembly configuration within the PSE. GM iMAN Product Structure in the BOMView is synchronized with assembly and component relationships in UG NX. Therefore, any changes made to an assembly in UG NX, will be shown on the GM iMAN side within the PSE.

.
Product Structure
For the Unigraphics user, Product Structure is also referred to as Assemblies and Components. The Assemblies function in Unigraphics allows users to utilize the Master Model concept (see the Item Structure unit). Product Structure can contain components or sub-assemblies

GM iMAN allows you to view an assembly in two ways:

- The Unigraphics assemblies function
- The Product Structure Editor (PSE)

The benefits of using the PSE include:

- Browsing the assembly without the use of Unigraphics
- Access to the Where Used function that reports all assemblies where a part is used
- The ability to easily configure and compare product structure

Note:
One of the benefits of using UG NX assemblies with GM iMAN is that when a change is made to a component it will be reflected in all assemblies using that component. To see whichassemblies will be affected by your change, perform a Where Used report on the component to be modified.

Note:
On an OL2Ke (EC2K) workstation with Motif and on all workstations with Portal, DO NOT close iMAN while UG NX is running. If this occurs the user will no longer be able to save any files, nor will they be able to open any new files. The user must close UG NX and open a new GM iMAN and UG NX session to continue working

BOMView in the Product Structure Editor Application
The BOMView/BOMView Revision displays the component structure of an Item that is an assembly. A new assembly Item will not have a BOMView until components are added to the assembly, and saved. The Assembly (BOMView or the BOMView Revision) can be viewed with the PSE Application using the following method:
- Right click on the Item Revision or BomView Revision and select Send To | PSE. That will display the PSE with the BOM of the selected Item Revision.



Imprecise Assemblies

An Imprecise Assembly is one in which the exact revisions of its components are determined at runtime. It is an assembly that may be configured by Revision Rules (described below).

With an Imprecise Assembly, an Item is a component of an assembly. The exact Item Revision of the component used in the assembly is determined by which Revision Rule is selected by the user. Once an assembly Item Revision is released, it cannot be toggled Precise or Imprecise and saved again. Revision Rules are based on the Release Status (or lack) of the component Item Revision. For example, Latest Working or Latest with any release status. GM iMAN always uses the most recent Item Revision for the component, to satisfy the Revision Rule.

Unless that update is an addition, removal or reposition, no manual effort is required (with an Imprecise assembly) to update an assembly when a new revision of a component is created and/or released. As a dynamic entity, no historical records of which Item Revisions are loaded in an Imprecise Assembly are automatically retained.

Precise Assemblies A Precise Assembly is one where the exact Item Revisions for its components have been stored prior to runtime. A Precise assembly (when not overridden) knows which Item Revisions of the components to load.

It is a simple manual effort to convert an assembly (Imprecise) to a Precise assembly. A Precise assembly ensures that downstream users see the exact revisions as the original designer intended. The latest parts are not a factor with Precise assemblies as it will load the parts specified by the user prior to toggling to Precise.

The only way a Precise assembly can maintain an exact historical record is if all sub assemblies are Precise as well. The Precise relationship is established between a single assembly and its components. Precise must be applied to each level of an assembly in order for it to be truly Precise. It is possible, but usually undesirable, for an assembly to have some subassemblies configured as Precise and some subassemblies as Imprecise.

The exact configuration of an assembly Item Revision can be defined as truly Precise only if all of its subassemblies at all levels are configured as Precise. Once an assembly Item Revision is released, it cannot be toggled Precise or Imprecise and saved again. In order to update a released Precise assembly Item Revision, it must be saved as a new Item Revision. Creating a Precise assembly is the only way to create a historical record of the configuration of the assembly showing the exact revisions of components. To view a Precise assembly as if it were Imprecise, simply use the appropriate Revision Rule.
Revision Rules
Revision Rules determine which revision of a UG NX Component an assembly loads. They are set by the user before loading an assembly. There is always a Revision Rule set. If a revision rule is not set by the user, the default is used.

Revision rules are pre-defined by the database administrator. The GM iMAN user selects one of the pre-defined revision rules to use in his or her GM iMAN or UG NX session.

This Unit is designed to explain the functionality of Revision Rules. How Revision Rules are applied to your specific job function are explained in the VAS class.
Revision Rule Settings
If the default Revision Rule is set in GM iMAN My Navigator through Edit | Preferences | PSE | Default Revision Rule, then that default Revision Rule will be applied the first time the PSE is opened. Further changes to this setting will be ignored as long as any BOMView Revision remains open in the PSE.

If the current Revision Rule is set in the PSE, that Revision Rule will be used when UG NX is launched. Further changes to the PSE Revision Rule setting will be ignored as long as the UG NX session is open.

If the Revision Rule is set in Load Options from UG NX, and the file is opened from UG NX, then all other Revision Rule settings in GM iMAN My Navigator and the PSE will be ignored. A Save of the Load Options will cause the default Revision Rule for the PSE to change.

Choosing Revision Rules

1. From the PSE application choose Tools | Revision Rule | View/Set Current. The View/Set Current Revision Rule dialog box appears with a list of preset Revision Rules set up by the System Administrator.

2. Select the required rule. Highlighting a Revision Rule displays the details of the order the system searches for files.

3. Click OK.
UG NX Load Options and Revision Rules

Revision rules can be set in Unigraphics under File | Options | Load Options. An assembly opened through UG NX using File | Open will observe the Revision Rules set in the Load Options. However, an assembly opened in UG NX from GM iMAN (either using the Open In UG NX icon, or by double-clicking a dataset) will follow the Revision Rules set in GM iMAN, and overwrite the Load Options set or saved in UG NX.

Revision Rules
The following are Basic Revision Rules:

- Latest Working

- Latest Released

- Override Precise Latest Working

- Override Precise Latest Released

- Set Override/Released

Latest Working

The Latest Working Revision will load a WIP Item Revision. If a WIP does not exist, the Latest Released will load. This Revision Rule will not change the configuration of a Precise assembly.

Latest Released

Under this Revision Rule, the most recently released (by date/time) revision of a component will be the one that is loaded into the assembly. This may include PDIed files. If there is no released revision of a component, the PSE will consider the component to be unconfigured. An unconfigured component is represented by ??? instead of a revision level.

Override Precise Latest Working

This will apply the Latest Working Revision Rule to a Precise assembly.

Override Precise Latest Released

This will apply the Latest Released Revision Rule to a Precise assembly.

Set Override/Released
This will allow the use of an Override folder that contains specific revisions to be loaded before a Revision Rule is applied.

G)VDP Specific Revision Rules
Vehicle Assembly Structure (VAS)

The Vehicle Assembly Structure (VAS) is a GM iMAN template used to organize product based math data. Parts are represented in the VAS by the Installation Assembly (IA) files and their components.

Release Statuses of IAs work hand-in-hand with Revision Rules. Revision Rules allow us to view an assembly in a specific configuration. When working with released parts, it is only the revision of IAs that is important. Released IAs, being Precise, will specify the revisions of components that should be used

GVDP Specific Revision Rules

GM recently made a significant decision to save money by eliminating the physical builds done for what was previously called Alpha 1 and Alpha 2. At that time there was no way to look at the math data and know its intended usage (i.e., is this the revision of the math I need for Alpha 1 or Alpha 2). The only way to integrate specific revisions of math into an intended Vehicle build (virtual or physical) was to use build folders. The build folder process was not consistently followed, and often not understood across different vehicles. The new revision rules work hand-in-hand with the new Job Release Statuses to eliminate the need for GVDP build folders (build folders do still have other valid uses at this time). The Alpha1/CVER and the Alpha 2/SVER are virtual builds. The Beta/IVER is the first physical build.
.

GVDP Specific Revision Rules

The following are the current Revision Rules:

Mule w/o pdi
Mule w/pdi
Mule w/pdi w/my wip
Mule w/pdi w/group wip

Alpha1/CVER only w/o pdi
Alpha1/CVER or less w/o pdi
Alpha1/CVER or less w/pdi
Alpha1/CVER or less w/pdi,my wip
Alpha1/CVER or less w/pdi,grp wip

Alpha2/SVER only w/o pdi
Alpha2/SVER or less w/o pdi
Alpha2/SVER or less w/pdi
Alpha2/SVER or less w/pdi,my wip
Alpha2/SVER or less w/pdi,grp wip

Beta/IVER only w/o pdi
Beta/IVER or less w/o pdi
Beta/IVER or less w/pdi
Beta/IVER or less w/pdi w/my wip
Beta/IVER or less w/pdi,grp wip

Prod only w/o pdi
Prod or less w/o pdi
Prod or less w/pdi
Prod or less w/pdi w/my wip
Prod or less w/pdi w/group wip

The following are the five (G)VDP release statuses:

- Mule

- Alpha1/CVER

- Alpha2/SVER

- Beta/IVER

- Production

Each one of these release statuses has a set of Revision Rules associated to it.

The five Revision Rule variations are:

- Only w/o pdi

- Or less w/pdi

- Or less w/o pdi

- Or less w/pdi, my wip
- Or less w/pdi, grp wip

Combining the GVDP release statuses with the five rev rule variations we get:

- (G)VDP Status) Only w/o pdi

- (G)VDP Status) Or less w/pdi

- (G)VDP Status) Or less w/o pdi

- (G)VDP Status) Or less w/pdi, my wip

- (G)VDP Status) Or less w/pdi, grp wip

(G)VDP Status) Only w/o pdi

An "Only" revision rule has been defined for each VDP Stage (with the exception of Mule) that will load the most recent revision of Installation Assemblies released with a status corresponding to that VDP Stage without PDIs. If no such revision is found, the item is left unconfigured.

(G)VDP Status) Or less w/o pdi

This revision rule will configure the most recent revision of Installation Assemblies released with a status corresponding to that VDP Stage without PDIs. If no such revision is found, the most recent revision released with status corresponding to the previous VDP Stage is loaded. The rule continues searching backwards through all prior VDP Stages until a revision is found or VDP Stages are exhausted.

(G)VDP Status) Or less w/pdi
(G)VDP Status) Or less w/pdi, my wip
(G)VDP Status) Or less w/pdi, grp wip

There are two types of development work, Preliminary Data (PDI) and Work-In-Process (WIP). These Revision Rules configure the latest revision of PDI, or the latest revision of WIP. Additionally, WIP data is categorized by ownership, so that the selection of WIP data can be restricted to either WIP data owned by the user or WIP data owned by the user's group.
NOTE:
• Assemblies can still be created in UG NX. That functionality has not changed.
• All GPDS (Global Product Description System) assemblies are UG NX assemblies, however, all UG NX assemblies are not GPDS assemblies.
• Every Item Revision that is an assembly has a BOMView revision.
• The system administrator sets up pre-defined Revision Rules.
• PDIs are considered released.
• The Revision Rule is selected before loading the assembly.
• An Imprecise assembly references Items – not specific revisions of those Items.
• Latest refers to time/date.
• If a Precise assembly contains a component that has a work-in-progress version in one part of the assembly and a released version in another part of the assembly, both occurrences will contain whatever version is specified in the Override Folder
VAS Overview
The VAS is a common template for each vehicle. Each VAS includes every part and the available options for that vehicle. These parts are located in the Mainstream Module of the Total Vehicle file.





What is Repeatable Digital Validation?
Repeatable Digital Validation (RDV) is a process and system capability where an accurate computer math data (digital) model of a product family is created, validated, and maintained to enable math based product configuration.
Configuration provides an assortment of math based data using GM iMAN, VisMockUp (VMU—formally known as Product Vision), and Unigraphics (UG) functionality.




Product Family - also referred to as platform and is used to identify a family of vehicles.
Configuration - a series of choices that display parts of interest in the context of the appropriate product family.

RDV provides multiple ways to display product configuration:
- Unconfigured Product BOM
- Configured Product BOM

RDV provides access to design geometry for a specific vehicle configuration consistently and repeatably.
RDV is a process that integrates a digital representation of the product in the GVDP (Global Vehicle Development Process) to increase the rate of communication.
VAS Designers, product data creators, and product data consumers can use RDV, along with analytic tools, to facilitate communication, learning and decision-making.
GVDP - GM's focus on improving vehicle program's timing, cost, and vehicle quality while reducing the vehicle development time.

VAS Designer - The VAS Designer owns all the Modules including the top level file which carries a GM iMAN Item name of Total Vehicle. Additionally, they own the Level 1 files within the Mainstream Module.




RDV Enabling Software and Processes
ULink:
RDV has an enabling software application called Usage Link, or ULink. It brings GPDS usage information into GM iMAN and allows Engineering Business Rules (which add model/option info) to be used in the design and analysis environment. GM iMAN Options are generated by the ULink Application for the Options and Models available in a Product Line. The typical data creator or consumer does not use the ULink application. Rather, the VAS Designer role will use ULink. All data creators and consumers benefit from the resulting information generated from ULink.

Quick Product Locator (QPL):
The QPL contains cached Proximity, Attribute and Zone information about all released files (hard release or PDI release) within the VAS. Referencing this information allows the Design Context application the ability to quickly determine which parts should appear in the vehicle context to satisfy the Proximity, Attribute and Zone filters that have been applied. Given the dynamic nature of the Vehicle Assembly Structure, the QPL cache is updated on a nightly basis (assuming something has changed in the VAS since the last previous update). Because the QPL does not contain any information about WIP files, it is necessary to create a PDI of any new data that you wish to make available for Design Context to use the next day. For example, if you wish to have your latest data available for a design review, a PDI must be created the previous day so the QPL will be updated with your latest information.

RDV/GM iMAN job processes for Installation Assemblies
Installation Assemblies for vehicle programs that use RDV have a different set of Job Procedures than non-RDV vehicle programs. The non-RDV IA Job Procedures are the 400-level procedures, and the new RDV Job Procedures for Installation Assemblies are the 600-level procedures. The 600-level procedures add the VAS Designer as an additional task in workflow, so the VAS Designer can use ULink to add GPDS usage information to the occurrence of the part.

Vehicle Assembly Structure (VAS)
The Vehicle Assembly Structure is a common, templated, GM iMAN based organization of product based math data used to develop the vehicle. RDV works hand-in-hand with the VAS to determine the necessary files needed to configure the vehicle context. Any files that are not released into the VAS by using the correct standards and processes may not be properly configurable by RDV.






















Quick Reference:
Objects within an Item Structure
Item Structures may have up to six different types of objects:
• Items
• Item Revisions
• Datasets
• IR Masters
• BOMView Revisions
• BOMViews
The following pages will explain the main features of each type of Object
Item:




Item Revision (IR)

Item Revision Master Form (IR Master)


UGMASTER Dataset



BOMView Revision






Item Information
When a new Item needs to be created, TcAE provides an Item Creation Wizard to guide the user. The following steps in the wizard are used to create an Item. Depending on the type of Item being created, users may not need to complete all the steps. All fields with red asterisks are mandatory.
Unless you highlighted the Home folder, the newly created Item is now in your Newstuff folder.
The Item information fields have small red asterisks above them to indicate that these must be completed in order to proceed.
Enter Item Information requires three pieces of Item information. The Item ID can be an eight digit part number from E2 or an alphanumeric number that is assigned using the Assign button. A revision level and name also must be provided.
Once all the required information is given, the Finish flag will become available. Select the Finish button to create the Item.
Button Functions
The Finish Button in the Item Creation Wizard will create the Item and paste it in the highlighted folder in My Navigator. If a folder is not highlighted, the Item will be placed in the Newstuff folder. The Wizard window will stay open and take you back to the first step in the process, Select Type.
Home Button
The Home Button in the Item Creation Wizard will return you to the Select Type step. Changes to the Select Type and Enter Item Information can be made any time before your Item is created.
Only two steps in the New Item Creation Wizard are mandatory. Select Type and Enter Item Information. The following additional steps may be performed as needed.
Item Rev Master Form
Enter Rev Master Form Information allows you to add Change Descriptions to the Item Revision Master Form of the new IR. The forms are different for each type of Item created. We will be defining the CORP_Part Item type.
When Enter Rev Master Form Information is selected from the Steps column, a message window appears. To proceed, the Yes button must be selected.
Yellow Pencil
Selecting the little yellow pencil expands the text window. Descriptions are typed in the text window. Using the + button adds text to the Change Description field. The – button removes highlighted text that is in the Change Description window. Up and down arrows are used to scroll through highlighted text.
Small Key
The Small Key is a button used to modify a Change Description. It replaces the highlighted text in the Change Description Window with text located in the field below.
AZ Button
The AZ button puts lines of text in alphabetical order and number text in numerical order.
DLS
Design Level Suffixes (DLS) can be added using the pull down arrow.
Note: All the other fields in the Item Rev Master Form step can only be filled by using the design log in UGNX. The file must be saved.
Open on Create
The Open On Create toggle that was located at the bottom of the New Item dialog in v8 TcAE, can now be found in the Define Options Step of the New Item Creation Wizard for v9 TcAE.
Other Item Types
The type of Item used depends on the information it contains. The following screens describe the Product Design Item Types currently used by GM:
• Corporate Part (CORP_Part)
 Most commonly used Item type.
 Used for MPL (Master Parts List) part geometry and drawings of both GPDS (Global Product Description System) and Alphanumeric part representations.
 Used for MPL (Master Parts List) part geometry and drawings of both GPDS (Global Product Description System) and Alphanumeric part representations
• Corporate Installation (CORP_Install)
 Used for Installation Assemblies.
 Used for Installation Assemblies.
• Corporate Process Plan (CORP_Proc_Plan)
 Used for Product Assembly Documents (PADS), measurement points, weld points, datum, and data that describe a GM manufacturing process.
 Also used for some of the template files within the Vehicle Assembly Structure (VAS).
 Used in product design and manufacturing.
• Corporate Vehicle (CORP_Vehicle)
 Used for Total Vehicle Files (the highest level of file in a VAS).
 Used in product design
• Corporate Criteria (CORP_Criteria)
 Used for vehicle criteria and Studio Surface releases.
 Used in product design
• Corporate Analysis (CORP_Analysis)
 Used for all analysis models, such as vehicle synthesis, analysis, and simulation.
 Used in product design..

Dataset Characteristics
. Datasets have the following characteristics:
• Used to store information from other applications
• Used as containers for data such as:
o Math data
o Text
o Image
• Double-clicking the Dataset will first launch the application, and then load the contents of the dataset.
The Dataset naming conventions are detailed in the image below.
Please point to each segment of the name for additional information

Dataset Types
We will consider three Dataset Types:
• UGMASTER Dataset (Master Part File)
• UGPART Dataset (Non-master Part File)
• UGALTREP Dataset (Non-master Part File)
The following screens contain definitions of each Dataset type
UGMASTER Dataset (Master Part File)
 Contains the master geometry for the part as manufactured.
 Collects the parts to be shown on the drawing for drawing Items (Chart drawing, LH/RH drawing, etc.)
 Contains the 3D master geometry for the Item. Only one UGMASTER per Item Revision is allowed.
UGPART Dataset (Non-master Part File)
 Used to store drawings. They derive their math data from a UGMASTER Dataset.
 Often used to reference geometry of a UGMASTER in a master model environment.
 UGPART Datasets should never be referenced by an assembly.
UGALTREP (Alternate Representation)
 Used to store part deformations such as the installed state of cables or hoses.
 UGALTREP Datasets may be used in an assembly.
 Contains 3D deformation geometry.
 Multiple UGALTREP Datasets are allowed.

Dataset Context
The following Dataset Contexts are commonly used in product design for CORP_Part type Items
GEO_FIN (Geometry Final): Used to describe a Dataset as manufactured or installed on the vehicle. The geometry can be at various stages of completeness. This Dataset Context is the default for the UGMaster when you create a new Item.
PR_STAT (Process State): Used to describe the state of a part in a specific stage of the manufacturing process. Also used for common data files.
GEO_ENV (Geometry Envelope): Used on Datasets containing geometry defining the part envelope such as the exterior shape of a part without internal details.
DRAWING: Used when the Dataset contains a drawing format.
SIMULAT: Used to capture derived data that represents simulation data. SIMULAT is used for motion files.
REPORT: Used for a TEXT Dataset type.
The Dataset Context indicates the type of information the Dataset contains. Upon creation of the Dataset, the user chooses a Dataset Context based on their knowledge of what the Dataset will hold. During Dataset creation, the user can accept the default Dataset Context or specify another by selecting the pull down menu. The choice of Dataset Contexts changes depending on the Dataset Type.
Dataset Contexts for Other Item Types
These contexts vary from those used for CORP_Part Items.

NCDATA
Contains geometry used for Numerical Control (NC), such as inspection data files.
INSPECT
Used for Coordinate Measuring Machine (CMM) data files.
GEO_PAD
Contains geometry defining an Item at a specific step and/or breakpoint within a product assembly or manufacturing process.
Non-UG Dataset Types
Direct Model (.jt): Datasets are (tessellated) translations of the UG Master Model. They are used to view files using the Portal Viewer.
ALIAS_PROJECT: Used for Alias files. Alias Datasets can only be created for Corp_Criteria and Corp_Install Item types.
TEXT: Contains a file in UNIX or OL2Ke text file format (.txt). OL2Ke text files are normally Notepad files, while UNIX text files are normally Text Editor files.
MSWord: Used to hold Microsoft Word files and may only be used on the OL2Ke platform.
MSExcel: Used to hold Microsoft Excel files and may only be used on the OL2Ke platform.
PowerPoint: Used to hold Microsoft PowerPoint files and may only be used on the OL2Ke platform.
Baseline/Preliminary Data Indicator (PDI)
• A PDI (Preliminary Data Indicator) is a static copy, a snapshot in time, of an Item Revision often created for data sharing.
• Data sharing is required as parts are being developed.
• A PDI indicates that a part is potentially incomplete and unfinished.
• Release Status is "X" for experimental or X-Restrict for Design Center.
• The preliminary data is quickly identifiable by the additional four digits.

Q&A:
What part of the Item Structure contains objects specific to a particular iteration or version of a part?
Item Revision (IR)
If a part is an assembly with components, what object will be contained beneath the Item Revision?
BOMView Revision (BVR)
What is the most common Item Type?
CORP_Part
What type of information is stored in a UGMaster dataset?
UGNX 3D master geometry
Which tab displays an information table related to what is highlighted in your Home workspace?
The Properties tab
If you need to modify a part, what type of access would you need?
Read/Write access
What is the state of an object that has a checkered flag symbol next to it?
Released
If you wanted to find out if/where a part was used as a component in an assembly, which function would you use in the Referencers application?
Where used
What type of Check-Out ensures you have exclusive Write privilege to an object for an indefinite period of time?
Explicit
What type of Check-Out prevents multiple users with Read/Write access from simultaneously modifying the same object?
Implicit
How can you find out what the authority is for a particular part iteration?
Do a Where Referenced on the Item Revision
When changing an existing part to a new part number, which option should be used: File | New, File | Revise, or File | Save As?
File/Save As
When are Revise & Save as commonly used?
• Revise – new Item Revision for an existing Item
Same part number
• Save As – new Item
o Different part number
What is the TcAE application used to view the components and sub-assembly which make up an assembly?
Product Structure Editor (PSE)
Which objects indicate that there is an assembly?
BOMView/BOMView Revision