Stability, Failure and Performance Diagnostics Using Teamcenter Doctor

Stability, Failure
and Performance
Diagnostics using
Teamcenter Doctor
Present er: Alok Rat hod
Unrestricted © Siemens AG 2018

Page 1 YYYY-MM-DD Siemens PLM Software
The disclosure of information, technical data, specifications and other contained herein
is deemed to be the proprietary intellectual property of Siemens PLM.
No reproduction, copy or use thereof may be made without the express written consent
of Siemens PLM. It is also understood and agreed that the disclosure of information
must be kept confidential. To ensure the protection of such information, it is agreed
that attendees limit disclosure of this document within its own organization on a need
to know basis and shall not be communicated or distributed. Lastly, the information
disclosed is forward looking based on Siemens PLM best estimates and may change
based on technical, financial or external factors. No commitments of deliverables or
timing can be asserted or assumed based on information disclosed.

Journey Of Teamcenter Doctor
Toolkit Framework lets have a loo

TC Doctor
Toolkit Framework Concept
Add custom
analysis tools
Tools
Environment Static Online

On Demand Action Recorders
Data Collectors Diagnostics
Processor/Analyzer Framework
Add custom
analyzers

TC Doctor Deployment Concept
Agents “listening” to Teamcenter

ace to access the collected agents data

Concept In Practice
Open Agents
dashboard
Access Agent

TC Doctor Flow Concept
Record Data Analyzer
Static configurations Process

Data
Agents Setup
Install Configure Scoped user actions Package Data

Agents Agents
Analyze Data
Online
usage

Preparing the TPBL Environment
1.Unzip MFG_XL.zip package
2. Used data:
3.Adjust XMLs to the environment conventions üEBOM - 4,096 Lines:

4. ü3,072 EBOM Items
ü1,024 Welds
5.Import the EBOM_XL.xml
6. üMBOM - 4,097 Lines:

ü1,025 MBOM skeleton lines
7.Import the MFG_XL_Import.bat
ü2,048 Assigned EBOM lines
8. ü1024 welds assigned
9.Final settings
üBOP - 3,072 Lines:
10. ü511 MEProcess lines
ü513 MEOP lines
11.Quick sanity check
ü2,048 MBOM consumed lines
12.


Few more tips on how to setup the

logs and how to collect the data


Setup TC Doctor Logs
Launch the TC Doctor UI

Seen is the Main UI screen that you will see
You can verify the installation directory to make sure you are connected to the correct TC Installation
Select the Online Diagnostics option in the menu on the left

The UI view will change to the view seen to the right
A message will be displayed if not diagnostic tools are installed above the log window

Installing the Online Diagnostic Tool

Tool can be installed by either selecting the screwdriver icon or
selecting “here” in the install statement above the log dialog box
This will open up the Log installation Dialog Box
Select the appropriate Server and Client Diagnostic Logs to turn on
For a 2 Tier setup, both client and server diagnostic logs will
be needed
For a server installation, only the Server logs are needed
For a 4 Tier installation, only the Client Logs are needed
Based on how the agent was connected, TC Doctor will assist in showing the
available logs that can be activated
A path for the global log can be defined (Make sure there are write permissions
within this folder)
Use the default configuration for log level detail
Use default for Dump file unless another option is required
Select the “Additional Log Options…” and proceed to the next slide

Additional Logs are required for a more detailed and in depth analysis
Logs are activated by selecting the check box next to each of the logs
Additional logs can be set up to only collect for specific TC users – Defined in the
lower section to the left
The Communication Monitor Log is turning on the communication monitor in TC RAC for
client-server communication performance view
The Profiler Log enables visibility to command clicks and their reflective triggered SOA calls
This activates a module within TC that allows user to scope actions
The Communication Log is a tcserver *.comlog which provides in-depth view to

the server
information in context of the SOA calls
The Performance Journal Log is basically enables the tcserver *.pjl log for in-depth
performance analysis using the Workbench
Optional: The Full Journal Log provides full details of the tcserver used SOA calls in the tcserver session
This log is only to be used in small well defined use cases as it has a large performance impact
Once all settings within the installation dialog are set, select apply, and the successful message
seen to the right will appear

How to Collect Logs
To collect the logs:

you first will select the save icon within the Online Diagnostic UI window
Located next to the install/uninstalled dialog button
You will verify that all selected/recorded log options are check in the dialog seen to the left and then select
save
Once all logs are saved, they will be packaged in a tdczlog file
For easy access to save this file, select the download

option in the dialog seen to the right
Select your download location and allow the tdczlog file to save


Now we are ready to run the TPBL


under TC Doctor


TPBL Cycles Flow Under TC Doctor
No No
Yes
Start 1. Calibration Cycles NoStable
Logs wait
Quick
time?
Cycles with required2.logs On Profiler Logsat least 2 Scoped cycles
Client
No Yes
Logs Reporting ?
Yes Journaling & Comlog for specific transactions

3. Performance
Sample execution efforts for phase 2

Average cycle per workflow – takes ~20-
30 minutes Save and download in TDCZLOG compressed
TC Doctor
folder
cleanup
3 cycles for per workflow
Per tested version – Total of 3 (cycles)
x 20(min) = 1 hrs

TC Doctor Calibration with TPBL Scenario
1.TC Logout
1.
1.Set the highlighted logs
1.
1.Restart warm servers to apply changes
1.
1.Ensure new servers have TC Doctor settings

1.TC Login
1.
1.Create Scope
1.
1.Run the heavy hitter
1.
1.Close Scope
1.
1.Create 1-2 more scoped actions
1.
1.Logout and save TC Doctor logs

1.TC Logout
1.
1.Save TC Doctor Package
1.
1.Download and open saved package
1.
1.Open Analysis view
1.
1.Open various reports
Open Analysis View
Run Analysis

When: Log Profiler, Communication Log and Performance Journaling logs are

TC Doctor Client Profiler Cycles
TC Doctor RAC client agent connection
1.Set Profile log only

1.
1. TC Login
1.
1.Create heavy hitters scopes & logout
1.
1.Repeat 2 more cycles
1.
1.Save profiler log cycles

TC Doctor Journalling and Comlog Deep Dive Cycles
TC Doctor TC server agent connection
1.Set comlog & PJL only

1.
1. TC Login
1.
1.Run only heavy hitters for additional analysis
1.
1.TC Logout
1.
1.Save TC Doctor package
1.

TC Doctor Data Processing
Load & analyze the saved packages for the client and the server

TC Doctor & TPBL KPIs
Use Case Name Data 11.2.3 11.2.3 Baseline

Bomlines/sec Time (sec) # Client Calls SQL Count
Search BOM 1024 lines found searching on 3071 307 10.0 15 932
Expand BOM 3071 lines expanded 212 14.5 19 184
Assign 1024 parts assigned 37 27.6 10 29,157
Remove Assigned 1024 parts removed 22 45.9 13 75,974
Consume 1024 parts consumed 18 57.8 12 88,436
Remove Consumed 1024 consumed parts removed 30 34.2 18 77,983
Display BOM 1330 JTs 26MB and 3071 lines 148
Accountability EBOM-MBOM 6143 expanded / returned 4100 108 20.8 164 3,618
Clear Accountability
56.8 22 44,259
4100 cleared NA
EBOM-MBOM 0.4 5 8
Load CC 10 lines showing 4
Expand BOP 1792 lines 103 2.9 66 800
Unpack BOP 256 lines unpacked 512 17.3 11 3,581
Pack BOP 256 packed 554 4.0 5 28
Search BOP 200 lines found searching on 2048 607 3.7 5 24
Accountability 2050 expanded / 1520 returned 75 5.1 14 1,767
BOM-BOP 27.4 26 7,462
Visual Assignment Check Not relevant NA
Clear Accountability MBOM-BOP 1520 lines 2254 0.0 2 0
Display BOP 1070 JTs 25MB 2048 lines 68 0.9 5 8
Create Operation 1 1 44.9 174 30,040
Create PV NA 73 0.7 32 429
Update PV NA 63 41.9 24 43,042
Export BOP 3072 process/consumed lines 16 49.0 20 27,289
Update Flows NA 37 194.0 9 196,978
Create DIPA 768 parts under DIPA 310
82.4 1,542 118,998
Display DIPA 770 DIPA lines /1065 JTs / 25MB 35 9.9 6 5,652
Assign Welds 1024 welds 14 22.2 24 10,106
Remove Assigned Welds 1024 welds removed 23
74.4 135 116,444
Consume Welds 1024 Welds consumed 20
44.0 11 93,383
Remove Consumed Welds 1024 consumed welds removed 28
51.2 9 84,539
Search Welds BOM 1024 welds found 71
Search Welds BOP 36.2 12 76,960
1000 welds found 46
57.8 2 97,363
Total 200 35.4 3 50,219
1,073.2 2,415.0 1,285,663.0

TC Doctor cleanup
1.Open TC Doctor UI
2.Go to Online Diag and make sure everything needed is saved
3.Open install/uninstall diag
4.Open additional logs
5.Turn off all additional logs
6.Select ok
7.Turn off server and/or clients logs
8.Select apply
9.Uninstall any business analyzer/CA
10.Close UI
11.Open task manager
12.Search for process called “tcdragent.exe”
13.End task
14.

Solutions Center
Join us in Booth #221
NX CAM & Tecnomatix Connection
Digital Machine Shop
Automate end-to-end part
manufacturing
Manufacturing planning
Take control of assembly processes
Virtual reality
Immerse yourself in the Digital
Twin
Business Process Connection
Industrialize additive manufacturing
Reimagine products
Reinvent manufacturing
Rethink business
#PLMConX
Thank You!

Stability, Failure and Performance Diagnostics Using Teamcenter Doctor

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stability, Failure and Performance Diagnostics Using Teamcenter Doctor

Uploaded by

Copyright:

Available Formats

Stability, Failure

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

Toolkit Framework lets have a loo

Unrestricted © Siemens AG 2018

Environment Static Online

Unrestricted © Siemens AG 2018

Agents “listening” to Teamcenter

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

Record Data Analyzer

Static configurations Process

Install Configure Scoped user actions Package Data

Unrestricted © Siemens AG 2018

1.Unzip MFG_XL.zip package

3.Adjust XMLs to the environment conventions üEBOM - 4,096 Lines:

6. üMBOM - 4,097 Lines:

Unrestricted © Siemens AG 2018

Few more tips on how to setup the

Unrestricted © Siemens AG 2018

Launch the TC Doctor UI

Select the Online Diagnostics option in the menu on the left

Unrestricted © Siemens AG 2018

Installing the Online Diagnostic Tool

Unrestricted © Siemens AG 2018

The Communication Log is a tcserver *.comlog which provides in-depth view to

Unrestricted © Siemens AG 2018

To collect the logs:

For easy access to save this file, select the download

Unrestricted © Siemens AG 2018

Now we are ready to run the TPBL

Unrestricted © Siemens AG 2018

Yes Journaling & Comlog for specific transactions

Sample execution efforts for phase 2

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

Open Analysis View

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

1.Set Profile log only

Unrestricted © Siemens AG 2018

1.Set comlog & PJL only

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

Use Case Name Data 11.2.3 11.2.3 Baseline

Unrestricted © Siemens AG 2018

Unrestricted © Siemens AG 2018

You might also like