Classification Administration - Configuration and Best Practices

PLM World and Siemens PLM Software
Welcome.
Unrestricted Siemens AG 2013 All rights reserved.
Smarter decisions, better products.
Helmut Lohmueller / Teamcenter Architect
Classification Administration
Best Practices
Teamcenter
Simplifying PLM.

Page 3
Jun 3-6, 2013
Siemens PLM Software
Teamcenter
Platform

Page 4
Jun 3-6, 2013
Classification Admin Best Practices

Agenda
Introduction
How to get started

Managing attributes
The classification hierarchy
Protecting classification data
Sharing classification data
Multi-Site
Import & export
NX part family integration

Hierarchy evolution
Utilities supporting the administrator

Page 5
Jun 3-6, 2013
Introduction
This presentation will provide an overview on the most important things to
know / consider before you start implementing Classification
The topics are presented in a natural implementation order that will ensure
prerequisites are satisfied as you define your classification system
Typographical conventions
Background information in black
Best Practice in blue
NOTE: In general the recommendations are for a production database. Some,
such as access control, might not be required in a test DB

Page 6
Jun 3-6, 2013
Introduction
What is Classification for?
Organize your IP (e.g. parts) for reuse
Product structure independent
Classification Admin application
Create and maintain the classification
hierarchy
Classification (user) application
Access to classification objects (ICO)
Create and modify
Browse and search

Page 7
Jun 3-6, 2013
Introduction
Admin Object Overview
The following objects are the main building blocks for the classification system
and are maintained by the Classification administrator
Hierarchy
Dictionary
Attribute
Group
KeyLOV
Class (abstract)
Class
Attribute(s)
Classified Objects
Class (storage)
Class
Attribute(s)
View
View
Attribute(s)
Classification
Object (ICO)
ItemRev 001/A
Classification
Object (ICO)
Item4711
ICOs store the values for

the attributes defined in
the class

Page 8
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 9
Jun 3-6, 2013
How to get started

Example Hierarchy
Use MRM Resource Library as an example hierarchy
Import into test DB
Part of the Resource Manager
Provides a rich hierarchy using many aspects of the

classification system.
Not just a sample - production ready hierarchy
Import using:
%KIT_ROOT%/advanced_installations/resource_management/
setup.exe
and follow the instructions

Remove the kit:
smlutility delete class id=MRM recurse icos -wso
smlutility delete attribute id=*
smlutility delete keylov id=*

Page 10
Jun 3-6, 2013
How to get started

Documentation
Tdoc provides extensive coverage of
Classification under the following sections:
Classifying Data
Classification Administration Guide

Classification Guide
Thin Client Interface Guide
Managing classification data

Page 11
Jun 3-6, 2013
How to get started

Documentation
Additional Information can be found under
Preferences and Environment Variables Reference
Classification Administration preferences
Classification preferences
Utilities Reference
Classification utilities
Application Administration Guide
Configuring Teamcenter Integration for NX
Classification to Teamcenter Integration for NX attribute mapping
syntax
Localization Guide
Special considerations when localizing Teamcenter applications
Classification
Developer References for Customization

Integration Toolkit (ITK) Function Reference
ICS_...
Services Reference
Classification
Page 12
Jun 3-6, 2013
How to get started

Accessing classification admin data
OOTB access to Classification Admin
requires DBA group membership
Override with this preference
ICS_requires_dba = false
Before changing the preference initial
access control should be configured
A basic Classification Admin Access
Control List (ACL) should deny WRITE,
DELETE and CHANGE for world and grant
it to a dedicated user or group
The Class Hierarchy should be protected
using the Classification Admin application
Assign the Classification Admin ACL to
SAM Classification Root
Page 13
Jun 3-6, 2013
How to get started

Accessing classification admin data
The Attribute Dictionary and the KeyLOVs
should be protected by adding, for example,
the Classification Admin ACL to the
following OOTB rules
Dictionary attribute
Has Class( POM_object )
+ Has Class( POM_object )->System Objects
+ Has Class( POM_objects )->in-CLASS Objects
+ Has Class( unct_dict )->Classification Admin
KeyLOV
Has Class( POM_object )
+ Has Class( POM_object ) -> System Objects
+ Has Class( POM_objects ) -> in-CLASS Object
+ Has Class( stxt ) -> Classification Admin

Page 14
Jun 3-6, 2013
How to get started

L10N Localization
Classification supports the localization using the
same concept used throughout Teamcenter.
Hierarchy, Attribute and KeyLOV localization
TEM provides the Classification L10N
template that enables L10N support for all
possible properties like class or attribute
name
The Classification Admin UI provides access
to the standard translation dialog
L10N translation import/export
Use ICSL10NExport transfer modes
PLMXML import/export supports localized data

Classification properties can be marked as
localizable using Classification Admin
Page 15
Jun 3-6, 2013
How to get started

Classification preferences
Classification supports a number of preferences that allow the configuration of
the system behavior
All classification related preferences start with ICS_
Look up using EditOptionsIndex
The most important preference to
get started controls which business
objects can be classified
ICS_classifiable_types=
Item
ItemRevision
While the OOTB configuration

supports classifying both items and
item revisions it is recommended
to classify item revisions

Page 16
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 17
Jun 3-6, 2013
Managing Attributes
The attribute dictionary
Central attribute definition to be used in class definitions
Main goal is to ensure consistency on attribute definitions
across classes
Attributes represent characteristics with a well-defined semantic.
Attributes like Thread Diameter or Cutting Diameter should
be kept separate instead of just using Diameter
Semantic is important for:
Attribute based mapping
Reclassify
Value propagation
Generic API based access

Page 18
Jun 3-6, 2013
Managing Attributes
The attribute characteristics
Key characteristics of an attribute:
Attribute ID
Name
Format (Data type, Scale, Precision)
Unit
The Attribute ID, which is of type integer, uniquely identifies an attribute.
To avoid conflicts the following OOTB number ranges are defined:
<= -1000
reserved for Siemens PLM
-999 to +999 reserved for internal use
>= +1000
free to be used
Define number ranges to avoid conflicts

By domain
By site

Page 19
Jun 3-6, 2013
Managing Attributes
The attribute characteristics
Once an attribute is used in a class and values have been stored, the
following properties of an attribute cant be modified:
Format
Unit
Ensure the format specified supports the complete possible value range for all
usages across all classes (e.g. electrical resistance values range from
Milliohm to Megaohm)
Format and unit can be specified for metric and non-metric unit systems
The class will determine which unit system is used
If a non-metric unit is not specified, the metric unit will be used
Some properties can be overridden on class and/or view level
Default value
Min/max value
Optimized display

Page 20
Jun 3-6, 2013
Managing Attributes
Reference attribute
Reference attributes allow attributes from the Classified object to be displayed
as classification attributes.
Attribute sources
Classified object
Master form
Related form
Related object
Item
Show Item
Attribute option
Classified Object
Property 1
Property 2
Property 3
Property 4
ItemRev
Item
Master
Form
items_tag
Item_master_tag
IMAN_master_form
Prop
object_name: 04711"
IMAN_classification
revision_id: A
ICO
owning_user
For each category above,

the attribute from the underlying
POM class or the property from
the BO type can be selected
owning_group
Show Item master

Form Attribute
option
release_status_list []
IMAN_master_form
Item
Master
Form
Prop
Form
Prop
Display
Search
Runtime Property
POM Attribute
YES
YES
NO
Type Property
YES
PARTIALLY
YES
IMAN_specification
Master Form Attribute.
Prop
Referenced Form
Attribute
WSO
IMAN_specification
Prop
Prop
Referenced Object
Attribute

Page 21
Jun 3-6, 2013
Managing Attributes
Unit support
Classification provides support for unit
definitions
Units are assigned to attributes
Values will be stored according to the
selected unit (storage unit)
Provides a natural way to specify
values while creating or searching
Classification data
Typing value along with unit (e.g. 2 m)

Type the value and select the unit from the
unit menu
Data conversion
Select unit from unit menu while viewing

data to show the value in the desired unit
Optimized display
0.00001 mm 10 nm

Page 22
Jun 3-6, 2013
Managing Attributes
Unit Support
Units can be added like regular classification objects
Stored in class TcCls_UDC
Child of SAM Classification Root
Invisible to the Classification application
To modify / add units, move under ICM Classification Root
Units are grouped into measures, e.g. Length
Each measure is divided into metric and non-metric units
One unit is chosen as the base unit
Conversion factors will be specified
in relation to that base unit

Page 23
Jun 3-6, 2013
Managing Attributes
KeyLOV
Classification KeyLOVs provide a list of values to be consumed by attributes
Each entry consist of a key/value pair
Key
Stored in DB
Use short generic values (e.g. 01)
Value
Used for display
Cascading menu
Use to break down long lists or for
data like cities organized by regions
Hide keys option
Use for showing display value only
Deprecated entries
Use to disable new usage while
continuing support for search
Page 24
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 25
Jun 3-6, 2013
Classification Hierarchy
The classification hierarchy is the primary entry to
the classification data
Guides users to find and create reusable objects
Ensure that the hierarchy is understood by the

user community by using common terminology
SAM Classification Root (id = SAM)
SAM := System Administration Module

Root of the classification hierarchy
Only visible in Classification Admin
Children are hidden to users
Classification Root (id = ICM)
Root for the Classification Application

Child of SAM

Page 26
Jun 3-6, 2013
Groups
Folder-like high level structure

No search supported
Classes
Provide ability to add attributes

Support attribute inheritance
Can be searched
Abstract classes
Define common attributes valid for all children

Supports searching across all children
Storage classes
Typically leaf classes of the hierarchy

Used for storing ICOs

Page 27
Jun 3-6, 2013
Make intensive use of abstract classes and
attribute inheritance
Helps user to select the right level of detail he is
interested in while searching.
(e.g. Searching for Face Mill but not interested
in which exact style )
Allows admin to provide detailed characteristics
required to distinguish individual objects and as
required by applications (e.g. CAM)
Avoid flat hierarchies
Make navigating and searching more timeconsuming
Avoid generic classes that aggregate attributes to
support a wider range of object types
Doesn't work well with part families
Page 28
Jun 3-6, 2013
Each class can define the unit system its instances (ICOs) values will be
stored in.
Metric
Non-metric
Both
It is recommended to use Both for flexibility
A class supports both a class Id and a class name
The Class Id is the unique identifier of a class
Consider as internal but still usable by the user (e.g. for search)
Keep it simple. Prefer using auto generated strings like ICM0101
Avoid using special characters
Invisible for the user; used to access a class through API
The Class Name is used to display the class in the UI

Use descriptive names that are easily understood by users
No uniqueness required
Localizable
Page 29
Jun 3-6, 2013
Class icons and images
Class icons
Used in the Hierarchy view (scaled)
Also used in the tooltip (original size)
Requires GIF, JPEG or PNG
Optimize size for tooltip
Class image
Used to visualize the class
Identifies the properties based on annotations
Multiple images supported
All formats are supported including JT
Use GIF,JPEG or PNG for groups and abstract
classes
Use scalable formats like CGM for storage classes
Class Icon
Class Image

Page 30
Jun 3-6, 2013
Views help configure the appearance of a class
Attribute order and layout
Attribute configuration
Hidden
Protected
Mandatory
User/group/role/default view
Only visible in Classification Admin
hierarchy
In the Classification Application the
right view will be selected
automatically and helps to tame the
complexity of information provided by
a class for a particular user

Page 31
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 32
Jun 3-6, 2013
Protecting your Classification data

Hierarchy protection
The access control capabilities
Classification provides are based on the
general Access Manager capabilities
Hierarchy protection
Each group and class in the hierarchy
can be protected individually
Access control settings are inherited
until overridden
Control who can classify in a particular
class using WRITE_ICOS
Embedded Access Control panel for
current group or class
Rules are also visible in AM rule tree but
must not be modified there.
Page 33
Jun 3-6, 2013
Protecting your Classification data

Classification object protection
Protection of classification objects
Standalone ICOs
Controlled by the class
Classifying ICOs
Controlled by the classified object
WRITE_ICO privilege
Overrides the WRITE and DELETE
privileges for the ICOs
Enables write access on ICOs even
if the classified object is read-only
To enable classifying released objects set
WRITE_ICO on VAULT ACL

Page 34
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 35
Jun 3-6, 2013
Sharing Classification Data

Using Multi-Site
Classification supports sharing data using
classic Multi-Site
Hierarchy, attributes and KeyLOVs will be
pushed to selected sites.
ICS_synchronize_sites= Site1, Site2, Site3
Changes to shared objects can be

automatically synchronized
ICS_synchronize_automatically= true
Remote Site B
ICM
Design
Class 001
Master Site A
Class 001.001
Non-classifying ICOs cant be shared
Modification constraints on shared data

Modifiable on the owning site only
Limited ability to add and remove attributes
1234
ABC
XYZ
1234
ABC
XYZ
ICM
Mechatronic
Design
ICOs will be shared along with the objects they

classify
1234
ABC
XYZ
Class 001
Class 001.001
MeClass 001
1234
ABC
XYZ
MeClass 001.001
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
Manufacturing
MfgClass 001
MfgClass 001.001
Mechatronic
MeClass 001
MeClass 001.001
1234
ABC
XYZ
1234
ABC
XYZ
Remote Site C
Test
ICM
Test Class A
Test Class A.1
Test Class A.2
1234
ABC
XYZ
Design
Class 001
Class 001.001
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
Manufacturing
MfgClass 001
MfgClass 001.001
1234
ABC
XYZ

Page 36
Jun 3-6, 2013

Central master site
To limit the impact on the hierarchy
maintenance, a hierarchy should be
maintained at a master site
Hierarchy master site
ICS_classification_master_site = true
Only the owning site can add children

Supports adding new attributes to
parent classes
Remote Site B
ICM
Design
Class 001
Master Site A
Class 001.001
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
ICM
Mechatronic
Design
Class 001
Class 001.001
MeClass 001
1234
ABC
XYZ
MeClass 001.001
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
Manufacturing
MfgClass 001
MfgClass 001.001
Mechatronic
Classification data master site

Enables all hierarchy modification
options to a shared hierarchy
Use prevent remote ICO creation
option
MeClass 001
MeClass 001.001
1234
ABC
XYZ
1234
ABC
XYZ
Remote Site C
Test
ICM
Test Class A
Test Class A.1
Test Class A.2
1234
ABC
XYZ
Design
Class 001
Class 001.001
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
Manufacturing
MfgClass 001
MfgClass 001.001
1234
ABC
XYZ

Page 37
Jun 3-6, 2013

Distributed master site
Separate branches can be mastered at
different sites
Branch root should be created at the
master site and ownership transferred
to the owning site
Remote Site B
ICM
Design
Master Site A
Class 001
Class 001.001
ICM
Dictionary attributes and KeyLOVs

should be shared to all sites
Apply name spaces to avoid
conflicts while sharing
Use a central master site as much as

possible. Branches can be distributed
later as required.
1234
ABC
XYZ
1234
ABC
XYZ
Design
Class 001
Class 001.001
Mechatronic
1234
ABC
XYZ
Mechatronic
ME Class 001
1234
ABC
XYZ
ME Class 001.001
1234
ABC
XYZ
1234
ABC
XYZ
Manufacturing
Class 001
Class 001.001
Test
Use distributed master site if certain

areas of the classification hierarchy are
primarily used at specific sites
1234
ABC
XYZ
Test Class A
Test Class A.1
Test Class A.2
1234
ABC
XYZ
1234
ABC
XYZ
Remote Site C
ICM
Design
Class 001
Class 001.001
Manufacturing
1234
ABC
XYZ
1234
ABC
XYZ
1234
ABC
XYZ
Class 001
Class 001.001
1234
ABC
XYZ

Page 38
Jun 3-6, 2013

Import & export
Classification supports three text file formats to import and export data
Legacy Formats:
SML (Pipe separated multiline text format)
XML (Standalone XML format)
Avoid using the legacy formats
PLM XML
The main format to import and export classification data with all details
Extension to Teamcenter PLM XML format and PLM XML SDK
Embedded into PLM XML import/export framework (PIE)
Combined product and classification data
Export:
OOTB Transfer Modes (ICS e.g. ICSExportHierarchy )
Import:
Use incremental import transfer mode
Page 39
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 40
Jun 3-6, 2013
NX Part Family Integration

The part family support in Classification provides the ability to associate
classification classes with NX part family templates.
Part family template assignment
Assign a part family template to a class
Attribute mapping
Define how part family expressions
are mapped to class attributes
Part family member import

Create classification objects for
all members defined in the template
Part Family Template

Class (storage)
Class
Attribute(s)
mapping
Member creation (user task)

Create new member from
standalone ICOs
ID D L W H M
Classification
Object (ICO)
Part Family Member

Page 41
Jun 3-6, 2013
NX Part Family Integration

Assignment, mapping and member import will be done in the Graphics Builder
sub panel of the class definition
New member creation is initiated from the Classification application
Using annotation as part expression

will support auto-assign
All part family attributes from the
spreadsheet need to be mapped.
Review part family while planning

the class as it has strong influence
on the list of required attributes.

Page 42
Jun 3-6, 2013
Part Family Support

Graphics Builder
The NX part family support is based on the Graphics Builder, an NX based
background process.
Requires NX installation on TcServer system
Configuration through TEM

Feature Maintenance
NX Integration
NX Graphics Builder
Invoked for first command
Server
TCServer
Graphics
Builder
NX/Manager
TCServer

Page 43
Jun 3-6, 2013

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution

Page 44
Jun 3-6, 2013
Hierarchy Evolution
Supported modifications
The classification hierarchy can be maintained while users are in
classification.
Some operations require access to all descendant classes and their ICOs
Multi-Site limits the ability to modify the hierarchy
Classes can only be modified at the owning site
Local
Shared
Remote Children
Shared Remote ICOs
Shared No Remote ICOs
Add new class
YES
YES
YES
YES
Add Attribute to leaf class
YES
YES
YES
YES
Add attribute to parent class

(new to branch)
YES
NO
YES
YES
Add attribute to parent class

(exists in branch; move up)
YES
NO
NO
YES
Re-parent to new group
YES
YES
YES
YES
Re-parent to new class
YES
NO
NO
YES
Remove Attribute
YES
NO
NO
YES
Modify class properties
YES
YES
YES
YES
Modify class attribute properties
YES
YES
YES
YES

Page 45
Jun 3-6, 2013
Hierarchy Evolution
Modify the production system
All changes to the classification hierarchy are effective immediately
Refresh required to see new classes if branch was already expanded
Use Access control (deny READ access) to hide
classes until ready for use
Modifications that require access to all ICOs
might fail if users are actively modifying
affected ICOs
Perform in off hours
All options to modify the hierarchy are available
1. Import from PLM XML
2. Interactive modifications
3. Command line scripts
PLMXML
PLMXML
1
2
Classification
Admin
Dev
Dev DB
DB
Site
Site AA
IMPORTANT: Changes cant be undone

Page 46
Jun 3-6, 2013
Script
Script
Hierarchy Evolution
Using Development Environment
Using a development system allows testing any changes to the hierarchy
before being applied to the production system
Requires separate deploy step
Ensure that the development system is in sync with production system

Classes and ICOs
Multi-Site configuration
Modification sequence dependencies
Attributes must be added to the production

system in same order as applied to the
development system
Export new classes
PLMXML
PLMXML
Use PLM XML to deploy new classes

PLM XML import has limitation on certain
modification operations
Use command line scripts to modify

existing classes
Page 47
Jun 3-6, 2013
import
PLMXML
PLMXML
2
Classification
Admin
apply
Product
Product DB
DB
Site
Site AA
Dev
Dev DB
DB
Site
Site AA
Script
Script
Script
Script

Agenda
Introduction
How to get started

Managing attributes
Multi-Site
Import & export

Hierarchy evolution
Utilities supporting the
administrator

Page 48
Jun 3-6, 2013

The classification module comes with a number of utilities that allow the
automation of administrative tasks.
smlutility
Provides a large number of important functionalities supporting the following
tasks
Basic reporting
Data modifications
Cleanup
Multi-Site
ics_connect
is a special purpose utility to support the import of data from external sources
Connect imported ICOs with existing objects (e.g. item or item revision)

Page 49
Jun 3-6, 2013

smlutility list_hierarchy
Print hierarchy report
smlutility -list_hierarchy -id=FIXT attr reportFile=hierarchy.txt
-reportFile=<filename>
Send output to file
-summary
Print hierarchy statistics
-noextended
Hide some info for better diff view
-views
List views
-pft
List associated part families
Use the output to compare hierarchies of
different sites
Group(FIXT\gYTFVP7joJxgDD) "Fixtures"
000 Group(FIXT01\gwZFVP7joJxgDD) "Assemblies"
001 Class(FIXT02\wAbFVP7joJxgDD) "Components"
|1/1 -1102 Vendor
|2/2 -1200 Description
|3/3 -1210 Comments
|4/4 -7781 Material
|5/5 -7782 Weight
|6/6 -7783 Order Number
000 Class(ugfc0101\wgUFVP7joJxgDD) "Base Plate"
|7/7 -7701 Diameter Hole
|8/8 -7702 Diameter Thread
|9/9 -7711 Distance b/w Holes (Length)
|10/10 -7712 Distance b/w Holes (Width)
|11/11 -7721 Number Of Holes (Length)
|12/12 -7722 Number Of Holes (Width)
|13/13 -7510 Thickness
000 StorageClass(ugfc010101\AFWFVP7joJxgDD) "Rectangular Base Plate"
|14/14 -7501 Length
|15/15 -7502 Width
|16/16 -7506 Length Of Chamfer
|17/17 -7507 Width Of Chamfer
|18/18 -7713 Pos.Of First Hole (Length)
|19/19 -7714 Pos.Of First Hole (Width)
001 StorageClass(ugfc010102\gReFVP7joJxgDD) "Round Base Plate"
|14/14 -7504 Diameter

Page 50
Jun 3-6, 2013

smlutility -delete
Delete class or hierarchy
smlutility delete class id=MRM recurse
removes the complete hierarchy starting with the group MRM
Delete/purge attributes
smlutility delete attribute id=*
removes all attributes from the dictionary that are not referenced by any class
Delete/purge keyLOVs
smlutility delete keylov id=*
removes all KeyLOVs that are not referenced by any attribute
Delete classification object (ICO)

smlutility delete ico id=000001
removes the ICOs with the id 000001
smlutility delete ico cid=ClassId
removes all ICOs of the given class

Page 51
Jun 3-6, 2013

smlutility / modifications
The following commands support you in modifying your classification hierarchy
from the command line
NOTE: all commands are shown without specifying user name and password
Use smlutility <command> without additional parameters to see further help
Add or modify dictionary attributes
smlutility -add_dict_attr attr_id=45678 name=Test format=25
smlutility -mod_dict_attr attr_id=45678 name=Modified
Modify a class
smlutility mod_class cid=ICM01 short_name=Short Name
Add or modify class attributes

smlutility add_class_attr cid=ICM01 attr_id=45678
smlutility add_class_attr cid=ICM01 attr_id=45678
mandatory=true
Add or replace class images or icon

smlutility add_class_image cid=ICM01 classImagePath=c:\cls.png
smlutility add_class_image cid=ICM01 iconImagePath=c:\icon.png
Page 52
Jun 3-6, 2013

smlutility / modifications
Add or modify view attributes
smlutility add_view_attr cid=ICM01::MyView attr_id=45678
smlutility add_view_attr cid=ICM01::MyView attr_id=45678
user1=User Text
Remove attribute from view

smlutility remove_view_attr cid=ICM01::MyView attr_id=45678
Run multiple commands together

smlutility batch inputfile=c:\MyFile.txt
MyFile.txt contains the commands as shown above (dont specify username/password)
MyFile.txt
smlutility
smlutility
smlutility
smlutility
smlutility
-add_dict_attr attr_id=45678 name=Test format=25

add_class_attr cid=ICM01 attr_id=45678mandatory=true
add_class_image cid=ICM01 classImagePath=c:\cls.png
add_class_image cid=ICM01 iconImagePath=c:\icon.png
add_view_attr cid=ICM01::MyView attr_id=45678

Page 53
Jun 3-6, 2013

smlutility / Multi-Site
smlutility provides the following options to support the multi-site functionality
-add_shared_sites
Share classification definition to a new site.
Use for sharing multiple objects (e.g. a complete hierarchy branch) to
another (new) site
-update_shared_sites
Update shared sites.
Use if the name of a site has been changed or a site has been removed
-sync
Synchronizes classification definition data with remote sites.
-ask_shared_sites
Shows the shared sites of the selected objects.
-list_local_icos
Lists all ICOs that are owned locally.
Page 54
Jun 3-6, 2013
PLM World and Siemens PLM Software
Thank you.

Classification Administration - Configuration and Best Practices

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Classification Administration - Configuration and Best Practices

Hochgeladen von

Copyright:

Verfügbare Formate

PLM World and Siemens PLM Software

Unrestricted Siemens AG 2013 All rights reserved.

Smarter decisions, better products.

Helmut Lohmueller / Teamcenter Architect

Smarter decisions, better products.

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

Classification Admin Best Practices

How to get started

NX part family integration

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

ICOs store the values for

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

Classification Admin Best Practices

How to get started

NX part family integration

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

How to get started

Provides a rich hierarchy using many aspects of the

and follow the instructions

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

How to get started

Classification Administration Guide

Managing classification data

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

How to get started

Developer References for Customization

Jun 3-6, 2013

Siemens PLM Software

How to get started

Jun 3-6, 2013

Siemens PLM Software

How to get started

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013

Siemens PLM Software

How to get started

PLMXML import/export supports localized data

Jun 3-6, 2013

Siemens PLM Software

How to get started

While the OOTB configuration

Unrestricted Siemens AG 2013 All rights reserved.

Jun 3-6, 2013