SIMATIC Project Insight DEMO-V1.0.3.0 DOC EN

SIMATIC Project Insight
Siemens
DEMO Version Service Pack 3 Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/109818320 Support
Legal information
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several components in
the form of text, graphics and/or software modules. The application examples are a free service by Siemens AG
and/or a subsidiary of Siemens AG ("Siemens"). They are non-binding and make no claim to completeness or
functionality regarding configuration and equipment. The application examples merely offer help with typical
tasks; they do not constitute customer-specific solutions. You yourself are responsible for the proper and safe
operation of the products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable, and non-transferable and time-limited right to have
the application examples used by technically trained personnel until December 31, 2024. After the license period
the use of the application examples is prohibited and technically not possible anymore. After this period Siemens
may at its own discretion stop distribution of this application examples, provide new application examples free of
charge/ fee-based and/or offer a product which contains the functionality of the application examples Any change
to the application examples is your responsibility. Sharing the application examples with third parties or copying
the application examples or excerpts thereof is permitted only in combination with your own products and only
during the license period. The application examples are not required to undergo the customary tests and quality
inspections of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not result in property
damage or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for
the usability, availability, completeness and freedom from defects of the application examples as well as for
related information, configuration and performance data and any damage caused thereby. This shall not apply in
cases of mandatory liability, for example under the German Product Liability Act, or in cases of intent, gross
negligence, or culpable loss of life, bodily injury or damage to health, non-compliance with a guarantee,
fraudulent non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for damages
© Siemens AG 2024 All rights reserved
arising from a breach of material contractual obligations shall however be limited to the foreseeable damage
typical of the type of agreement, unless liability arises from intent or gross negligence or is based on loss of life,
bodily injury or damage to health. The foregoing provisions do not imply any change in the burden of proof to
your detriment. You shall indemnify Siemens against existing or future claims of third parties in this connection
except where Siemens is mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond
the liability provisions described.
Other information
Siemens reserves the right to make changes to the application examples at any time without notice. In case of
discrepancies between the suggestions in the application examples and other Siemens publications such as
catalogs, the content of the other documentation shall have precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with industrial security functions that support the secure operation of
plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement –
and continuously maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and
solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks.
Such systems, machines and components should only be connected to an enterprise network or the internet if
and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls
and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly
recommends that product updates are applied as soon as they are available and that the latest product versions
are used. Use of product versions that are no longer supported, and failure to apply the latest updates may
increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under
https://www.siemens.com/cert.

Entry-ID: 109818320, DEMO Version 1.0.3.0 (Service Pack 3), 04/2024 2
Table of contents
Table of contents
Legal information ......................................................................................................................... 2
1 Introduction ........................................................................................................................ 5
1.1 Overview ............................................................................................................... 5
1.2 Mode of operation.................................................................................................. 6
1.3 Components used ................................................................................................. 7
2 Navigation........................................................................................................................... 8
2.1 Navigation ............................................................................................................. 8
2.2 Call Structure....................................................................................................... 11
2.3 Sequence Analytics ............................................................................................. 12
2.4 Signal Flow.......................................................................................................... 13
2.5 UDT Dependencies ............................................................................................. 14
2.6 Query Builder ...................................................................................................... 15
2.7 Unit Relations View ............................................................................................. 16
2.8 Project Structure.................................................................................................. 17
2.9 Global Objects Dependencies.............................................................................. 18
2.10 Scheduling Tasks for Batch Export ...................................................................... 19

2.11 SIMATIC Profiling Tool ........................................................................................ 21
3 Engineering ...................................................................................................................... 22
3.1 Hardware setup ................................................................................................... 22
3.2 Pre-requisites ...................................................................................................... 22
3.3 Performance........................................................................................................ 22
3.4 Operation ............................................................................................................ 22
3.5 Error handling ...................................................................................................... 22
4 Functions.......................................................................................................................... 23
4.1 Call Structure....................................................................................................... 23
4.2 Sequence Analytics ............................................................................................. 26
4.3 Signal Flow.......................................................................................................... 27
4.4 UDT Dependencies ............................................................................................. 28
4.5 Query Builder ...................................................................................................... 30
4.6 Unit Relations View ............................................................................................. 35
4.7 Project Structure.................................................................................................. 35
4.8 Global Object Dependencies ............................................................................... 36
4.9 Export of Data Points Logs .................................................................................. 37
4.10 Scheduling Tasks for Batch Export ...................................................................... 38
4.11 Telemetry ............................................................................................................ 42
4.12 Namespaces & Units Analysis ............................................................................. 42
4.13 Multi-User Projects .............................................................................................. 43
4.14 Feedback & Crash Handling ................................................................................ 43

Table of contents
4.15 Know-How Protection Blocks Analysis ................................................................. 43

4.16 Application Usage Time-Boxing ........................................................................... 43
4.17 SIMATIC Profiling Tool ........................................................................................ 44
4.18 Specific functionality ............................................................................................ 58
4.19 Known Issues ...................................................................................................... 58
4.20 Restrictions ......................................................................................................... 59
4.21 Alternative solutions ............................................................................................ 59
5 Appendix .......................................................................................................................... 60
5.1 Service and support............................................................................................. 60
5.2 Industry Mall ........................................................................................................ 61
5.3 Links and literature .............................................................................................. 61
5.4 Change documentation ........................................................................................ 61

1 Introduction
1.1 Overview
SIMATIC Project Insight application example is a smart engineering data analytics solution that
helps to uncover the anomalies of complex engineering projects. It helps Standardizers, PLC
engineers, maintenance engineers, and data scientists with static analysis of engineering
projects to enable faster orientation and quality improvements, thus saving time.
SIMATIC Project Insight (Figure 1-1) analyzes TIA Portal V14 SP1, V16, V17, V18 and V19
versions of projects, accepts TIA Portal Engineering projects as inputs and helps users to
understand the complexity and poor design of the engineering projects by providing insights in
the form of visualizations. The same insights can also be exported in the form of JSON for
further downstream analysis.
Customer Benefits:
• Quick insights on the engineering project.
• Better understanding on the anomalies of the engineering project.
• Helps to uncover the complex design of the engineering projects.
Figure 1-1: SIMATIC Project Insight - Overview

1.2 Mode of operation
Call Structure
Enables the user to explore the blocks "called from" and blocks "called to" Organization Blocks
(OBs). The blocks can also be filtered to understand the sub-structure of the blocks being
analyzed, see Figure 4-1.
Sequence Analytics
Visualize the STEP 7 GRAPH (S7-GRAPH) transitions as a tree structure for the given PLC and
can be exported in the form of JSON for downstream analysis, see Figure 4-2.
Signal Flow
Helpful when the UDTs datapoints or the UDTs itself are treated as real-world materials/object
in the automation line. The signal flow visualization helps to understand the flow of the UDTs
datapoints as parameters across blocks which are calling the UDTs. The datapoints of the
signal flow can also be exported in the form of JSON for downstream analysis, see Figure 4-3
UDT dependencies
The type dependencies, Instance dependencies of the UDT and the data points which are
read/written by the UDTs are visualized. The datapoints of the interest of the UDTs can also be
exported in the form of JSON for downstream analysis, see Figure 4-4.
Query Builder
The user is allowed to write his/her own queries targeting a custom search in the engineering
project concerning plc data points. The queries can be saved, opened for later use and the data
points queried can be exported in the form of JSON for downstream analysis, see Figure 4-5.
Unit Relations View

Visualize the dependencies between units, global data blocks and technology objects,
see Figure 4-11.
Project Structure
Export all the engineering objects (such as organizational blocks, function blocks, function calls,
data blocks, user defined types and tags), in the form of JSON for further analysis,
see chapter 4.9.
Global Object dependencies

The data blocks and tags dependencies w.r.t other blocks are visualized. The datapoints of the
interest can also be exported in the form of JSON for downstream analysis, see Figure 4-12.

1.3 Components used
This application example has been created with the following hard- and software components:
System requirements
The recommended hardware and software are listed in the following table.
Table 1-1: System requirements

Component Number Article Note
number
Processor Intel® Core™ i5-8400H (2.5 up to 4.2 GHz)
RAM 16 GB (min. 8 GB, 32 GB for large projects)
Hard disk SSD min 50 GB free storage space
Network 1 Gbit
Monitor 15.6" Full HD Display (1920 x 1080 or more)
Operating system* Windows 10 (64-bit)

• Windows 10 Professional Version 21H1
• Windows 10 Professional Version 21H2
• Windows 10 Enterprise Version 2009/20H2
• Windows 10 Enterprise Version 21H1
• Windows 10 Enterprise Version 21H2
Windows 11 (64-bit)
• Windows 11 Home Version 21H2
• Windows 11 Pro Version 21H2

• Windows 11 Enterprise 21H2
Windows Server (64-bit)
• Windows Server 2016 Standard (full installation)
WebView2 Runtime Version 107.0.1418.52 (Any version greater than the mentioned
version)
.Net Core V8.0
.Net framework V4.8
Tia Portal Professional Standard

Version 14.1, 16, 17, 18 & 19 (.ap14, .ap16, .ap17, .ap18 & .ap19)
Projects
Tia Portal Professional Multi-User
Version 17, 18 & 19 (.als17, .als18 & .als19)
Projects

2 Navigation
2.1 Navigation
• SIMATIC Project Insight opens in local PC as a standalone application where TIA Portal
Professional is installed.
• The application example user can select TIA Portal project for analysis from the project
extractor page.
• The project once extracted is ready for analysis in SIMATIC Project Insight.
• The SIMATIC Project Insight analyzer page opens-up when the user presses the "Start
Analysis" button.
• Select the required PLC for analysis from the drop down in the SIMATIC Project Insight
Analyzer page.
• The help file is available as a link in the bottom of the page for reference.
• All functionalities described in the functions are available, the user can interact with the
application example with the help of mouse and keyboard.

Before the extraction the view looks like Figure 2-1 and after the view changes to Figure 2-2.
The related steps are described at the following page.
Figure 2-1: Navigation – User interface before TIA Project extraction
8
The result after the extraction you find in Figure 2-2 on the next page.
1. Browse for the TIA project that needs to be analyzed.

2. Include Know-How protected blocks for analysis.
3. Press the "Start Extraction" button to extract the project.
4. Filter the logs only for warning.
5. The purpose for which the application is used can be selected or entered by the user.
6. Once, the extraction is done, the project can be selected for analysis.
7. Press the "Start Analysis" button to analyze the project.
8. Use the link present in the bottom to provide feedback and access help file.
9. Enable/disable telemetry data that would be sent back to Siemens for improvement of the
product.

Figure 2-2: Navigation – User interface after TIA project extraction
In the next Figure 2-3, you see the available functions for the TIA Project after extraction.
Figure 2-3: Navigation – Available functions for the TIA project
1. The required PLC that needs to be analyzed is selected from the drop-down.
2. The functions are available as tiles.
3. The functions are available in the carousels.
4. It is easily to understand the internal background actions via the logs.

2.2 Call Structure
Figure 2-4: Navigation – Call Structure
1 8
5
1. The call structure can be centered, fit to screen & the highlighted nodes can be reset.
2. All the functions which are available for analysis can be viewed by clicking the logo of the
application.
3. The views provide user with options to view the full call structure/sub call structure, the user
can also type the block name to view the sub call structure of the block.
4. The "Block Criticality" toggle enables the view of blocks ranked based on the criticality with
Top 10 critical blocks displayed on the top right. The uncalled blocks in the call structure are
also listed here.
5. The legends represent the color of the blocks in accordance with the TIA portal block colors.
6. A different project can be analyzed using the link "Change Project".
7. The blocks can be hovered and selected to understand the block properties and
highlighting.
8. The logs, top 10 critical blocks are available for the user at the top right of the application.
NOTE The functions of the "Call Structure", you find in chapter 4.1.

2.3 Sequence Analytics
Figure 2-5: Navigation – Sequence Analytics
6
application.
2. The expand button is used to expand the blocks of the PLC.
3. The collapse button is used to collapse the blocks of the PLC to parent level.
4. The TIA PNV objects are displayed in tree form.
5. All nodes starting from parent nodes to child nodes are displayed.
6. The S7-GRAPH blocks sequences and transitions are visualized in tree form.
7. The datapoints obtained are added to the export cart.
8. The datapoints visualized are exported in the form of JSON file using the export cart.
9. A different project can be analyzed using the change project link.
NOTE The functions of the "Sequence Analytics", you find in chapter 4.2.

2.4 Signal Flow
Figure 2-6: Navigation – Signal Flow
4
application.
2. The User Defined Datatype (UDT) that needs to be analyzed is selected from the drop
down, a partial name of the user defined type can also be typed in to get all the types
matching the name.
3. Press the Arrow button to start analyzing the UDT.
4. The UDT datapoints which are used as Input parameters to the blocks are visualized here.
5. Hover on the block to understand the properties of the block.
6. All signal flows can be visualized using this option.
7. Individual signal flows can be visualized using this option.
8. The datapoints can be added to the export cart for export.
NOTE The functions of the "Signal Flow", you find in chapter 4.3.

2.5 UDT Dependencies
Figure 2-7: Navigation – UDT Dependencies
4 5 7
6 8
application.
2. The User Defined Datatype that needs to be analyzed is selected from the drop down, a
partial name of the user defined type can also be typed in to get all the types matching the
name.
3. Press the arrow button to start analyzing the UDT.
4. The type dependencies of the UDT that uses the UDT and the UDTs that are dependent on
this UDT are shown here.
5. The datapoints of the UDT that are read as members in blocks are shown here.
6. The datapoints of the UDT that are written as members in blocks are shown here.
7. The blocks which read the UDTs datapoints are shown here.
8. The blocks which write the UDTs datapoints are shown here.
9. The UDTs datapoints visualized are exported in the form of JSON file using the export cart.
NOTE The functions of the "UDT Dependencies", you find in chapter 4.4.

2.6 Query Builder
Figure 2-8: Navigation – Query Builder
3
2
5
application.
2. The Query Builder syntax guide helps the user to understand object types, filter expression,
operations, and value to query the information from PLC.
3. Enter the required query in the query editor.
4. Execute the query.
5. The results are displayed in the tabular form and the text from the table can be copied using
context menu.
6. The query can be saved and opened for a later point of use.
7. The data points displayed in the tabular form can be added to export cart.
NOTE The functions of the "Query Builder", you find in chapter 4.5.

2.7 Unit Relations View
Figure 2-9: Navigation – Unit Relations View
5
3
application.
2. The unit that needs to be analyzed is selected from the drop down, a partial name of the
unit can also be typed in to get all the types matching the name.
3. The units visualized are clickable and user would be able to view the published blocks and
UDTs.
4. The technology objects related to the units are visualized here.
5. The data blocks related to the units are visualized here.
NOTE The functions of the "Unit Relations View", you find in chapter 4.6.

2.8 Project Structure
Figure 2-10: Navigation – Project Structure
4
application.
2. Select the required PLC for which the project structure needs to be exported.
3. The project structure functionality can be selected via carousel or the tile.
4. The export progress is shown by the cascading tooltip.
5. The cascading tooltip is shown once the export of the project structure is completed.
NOTE The functions of the "Project Structure", you find in chapter 4.7.

2.9 Global Objects Dependencies
Figure 2-11: Navigation – Global Object Dependencies
4 5 7
6 8
application.
2. The data blocks that need to be analyzed is selected from the drop down, a partial name of
the data block can also be typed in to get all the types matching the name.
3. The tags that need to be analyzed is selected from the drop down, a partial name of the tag
can also be typed in to get all the types matching the name.
4. The data block or the Tag is visualized here.
5. The data block members or the datapoints that are read from blocks are visualized here.
6. The data block members or the datapoints that are written from blocks are visualized here.
7. The blocks which read the UDTs datapoints are shown here.
8. The blocks which write the UDTs datapoints are shown here.
9. The datapoints obtained are added to the export cart & the datapoints visualized are
exported in the form of JSON file using the export cart.
NOTE The functions of the "Global Objects Dependencies", you find in chapter 4.8.

2.10 Scheduling Tasks for Batch Export
The tasks can be scheduled by clicking the link "Schedule your tasks here" in the extractor page
Figure 2-12: Schedule your tasks here

1. The Tasks scheduler UI consist of 2 tabs namely 1) Schedule Tasks 2) Reports

2. The left arrow marking is used to go back to the project extractor page
3. The image on the right explains the working of the Task Scheduler
4. The tasks can be configured using the task configuration fields and options
5. The workflows can be added using the ‚+‘ icon, the workflows can be deleted using the
delete icon to the right of the workflow
6. New tasks can be added using the ‚+‘ icon, the newly added tasks can be deleted using the
delete icon to the right of the task
7. The toolbar options are available to the user

Reports
1. The batch execution results of the workflows are displayed in the reports tab, the reports
can be filtered.
All Time - Shows all reports
Today - Shows reports generated today
Yesterday - Shows only yesterday’s report
Last 7 days - Shows last 7 days report
Custom Range - User can select a custom date range
2. The task details are shown in this area, the available fields are
Task Name - Name of the task that is executed
Status - Task completion status
Total Time - Total time of execution of the task
Date - Date of execution of the task
Export Path - Export path of the JSON and task logs
Remarks - Extended comments and reasons of failure, if any
3. : Updates the reports with the latest available data
Figure 2-13: Scheduling tasks for Batch Export

NOTE The functions of the "Scheduling tasks for Batch Export", you find in chapter 4.10.

2.11 SIMATIC Profiling Tool
The PLC Profile tool can be opened by clicking the link „Analyze PLC Profile here“ in the
extractor page
Figure 2-14: Analyze PLC Profile


3 Engineering
3.1 Hardware setup
No special hardware setup is required.
3.2 Pre-requisites
• User using SIMATIC Project Insight in the PC should be part of "Siemens TIA Openness"
group.
• Users trying to analyze TIA Portal know-how protected blocks should know the passwords
of the blocks, the know-how protected blocks are ignored for analysis if the passwords are
not provided.
• Compile (rebuild all) and make TIA project consistent (save the project) before importing to
SIMATIC Project Insight.
Un-Supported Environment:
• TIA Portal project protected by UMAC.
3.3 Performance
• There will be considerable time taken by SIMATIC Project Insight for analysis which is
indicated to the user.
• The analysis of the project is dependent on the size of the project/number of blocks in the
project the data points present in the project/ the relationship amongst objects in the project.
3.4 Operation
Know-How Protection:
1. The user will be prompted to provide Know-how protection passwords, if the user chooses
to analyze know-how protected blocks.
2. SIMATIC Project Insight does not store the know-how protected blocks passwords but uses
to extract the content of the know-how protected blocks.
Telemetry:
1. The user chooses to provide telemetry (non-sensitive SIMATIC Project Insight usage) data
back to Siemens.
Feedback:
1. The user is provided with an option to send back feedback to Siemens SIMATIC Project
Insight team in case of a crash.
Uninstallation:
1. Un-installation of SIMATIC Project Insight is done via standard windows uninstallation
mechanism.
2. Remove SIMATIC Project Insight folder if any in the installation path after un-installation (to
avoid further problems during next installation).
3.5 Error handling

1. TIA Project Extractor shows error if TIA project is not consistent to extract information.
2. Any unforeseen crash is handled, and the user is provided an option to send back the crash
report and feedback via e-mail.

4 Functions
4.1 Call Structure
Enables the user to explore the blocks "called from" and blocks "called to" organization blocks
(OBs). The blocks can also be filtered to understand the sub-structure of the blocks being
analyzed.
Figure 4-1: Functions – Call Structure

NOTE The navigation for the "Call Structure", you find in chapter 2.2.

4.1.1 Block Criticality View
Enabling the block criticality view to classify all the blocks present in the call structure according
to the criticality, the blocks are classified into three categories with stars as denoted,
★★★ – Highly critical block
★★ – Medium critical block
★ – Low critical block
The criticality is calculated considering various parameters like the number of times the block is
called, number of data points accessed inside the blocks. On hovering the block, the user gets
to know the reason for the criticality of the block, if the block is highly critical. The organization
blocks are not considered for criticality calculation.
4.1.2 Uncalled Blocks
The blocks that are uncalled in the runtime execution system are listed in the form of a list.
The uncalled list of blocks might have been called from non-supported languages like STL or
there can be usage of the block data points through their instances.
4.1.3 Call Structure – Coloring
The blocks are colored to match with TIA portal,

Organization blocks: Purple,
Function Blocks: Blue

Function Call: Green,
Incomplete Blocks: White
4.1.4 Call Structure – Filters
The Call Structure has 3 filters.

• Full view: Shows the entire call structure of the blocks inside the PLC.
• Only OBs: Individual OB blocks can be selected for sub call structure analysis.
• All blocks: Any block can be selected for sub call structure analysis.
Call structure can visualize the blocks that are widely used, blocks that are seldom used and the
blocks that are never called by any other block in the PLC.
Mouse hover on a block displays the properties of the block.
Selecting a block for analysis displays the blocks in red color and the blocks that are called by
the block and the blocks that are calling the block selected in green, blue, and purple to
highlight the call structure of the block being selected.

4.1.5 Call Structure – Options
Table 4-1: Call Structure – Options
Icon Function Description
Center icon Clicking the center icon reset the call structure visualization to the
center of the screen.
Fit to screen Clicking the fit to screen icon fits the entire call structure of the PLC
to the screen size
Refresh Clicking the refresh icon resets the nodes highlighted to the default
color of the entire call structure
Logs User understands the background process while the call structure
generation happens
Critical blocks The top 10 critical blocks of the entire PLC is displayed,
irrespective of the call structure view showing sub call structures
Uncalled The blocks that are never called in the runtime execution system
Blocks are listed.
4.1.6 Call Structure – View Options

Table 4-2: Call Structure – View Options

Function Description
Namespace Groups blocks based on the namespace clusters the blocks belong
to
Units Groups blocks based on the units clusters the blocks belong to
Ungroup Remove namespace & units view for sub call structure if filtered
based on the OBs or all blocks call structure filter
Full View Shows the entire call structure of the blocks inside the PLC
Block Criticality Turn On/Off the block criticality functionality
4.1.7 Call Structure – Context Menu Options
Table 4-3: Call Structure – Context Menu Options

Copy The block name is copied to the clipboard

Get call structure The sub-call graph of the block is visualized
If the call structure is too big to visualize, SIMATIC Project Insight automatically shows the
blocks that cannot be visualized in white in color, so that the users can use filters to visualize
sub call structure, also a message:
"The call structure is incomplete due to its size. Please refine the search based on
individual blocks." Is shown to the user on the left side pane of the call structure.

4.2 Sequence Analytics
Visualize the S7-GRAPH transitions as a tree structure for the given PLC and can be exported
in the form of JSON for downstream analysis.
Figure 4-2: Functions – Sequence Analytics

NOTE The navigation for the "Sequence Analytics", you find in chapter 2.3.
4.2.1 Sequence Analytics – Options
Table 4-4: Sequence Analytics – Options

Expand all Expand all the nodes of the PLC

Collapse all Collapse all the nodes of the PLC
Add to export Used to export all the required data points in the form of JSON file
Export cart Export cart checkouts the required datapoints

Logs User understands the background process while the sequence
generation happens.

4.3 Signal Flow
Helpful when the UDTs datapoints or the UDTs itself are treated as real-world materials/object
in the automation line. The signal flow visualization helps to understand the flow of the UDTs
datapoints as parameters across blocks which are calling the UDTs. The datapoints of the
signal flow can also be exported in the form of JSON for downstream analysis.
Hovering on a block/datapoint displays the properties of the block/datapoint.
Figure 4-3: Functions – Signal Flow

NOTE The navigation for the "Signal Flow", you find in chapter 2.4.
4.3.1 Signal Flow – Options
Table 4-5: Signal Flow – Options

Center Clicking the center icon reset the signal flow visualization to the
Fit to Screen Fits the visualization to the screen size

Add to Export Used to export all the required data points in the form of JSON file
Export Cart Export cart checkouts the required datapoints
Logs User understands the background process while the signal flow
generation happens.
All signal Displays all available signal flow for the selected UDT.
flows

4.4 UDT Dependencies
The type dependencies, Instance dependencies of the UDT and the data points which are
read/written by the UDTs are visualized. The datapoints of the interest of the UDTs can also be
exported in the form of JSON for downstream analysis.
Figure 4-4: Functions – UDT dependencies

NOTE The navigation for the "UDT dependencies", you find in chapter 2.5.

4.4.1 UDT Dependencies – Filters
The "UDT Dependencies" has 3 filters.
Table 4-6: UDT Dependencies – Filters

All dependencies Visualize the type and instance dependencies

Type dependencies Visualize the UDT dependencies with other UDTs
Instance Visualize the dependencies of the UDT datapoints that are read from
dependencies blocks/written to the blocks of the PLC
The UDT cluster shows the linkage of the UDT selected for analysis with other UDTs.
The datapoints Read From cluster shows all the datapoints of the UDT that are being read from
blocks.
The datapoints Written To cluster shows all the datapoints of the UDTs that are being written to
blocks.
The reader blocks clusters show all the blocks from which the datapoints of the UDT are read
from. The writer blocks clusters show all the blocks to which the UDT datapoints are written to.
4.4.2 UDT Dependencies – Options
Table 4-7: UDT Dependencies – Options

Center Clicking the center icon reset the UDT Dependencies visualization
to the center of the screen.

Add to Export Used to export all the required data points in the form of JSON file
Export Cart Export cart checkouts the required datapoints

Logs User understands the background process while the UDT
visualization generation happens.

4.5 Query Builder
The user is allowed to write his/her own queries targeting a custom search in the knowledge
graph. When a data scientist wants to have a multifaceted view of the project data, it is possible
to get this view from the knowledge graph and export it into a JSON format. The query format
currently conforms to a Structured Query Language (SQL) format.
The query allows for a user to filter and search for datapoints according to specific conditions,
such as by name or by datatype. This search can be performed over either the instance data
blocks, PLC tags, UDTs or all data blocks.
Figure 4-5: Functions – Query Builder

NOTE The navigation for the "Query Builder", you find in chapter 2.6.

4.5.1 Query Builder – Syntax
<Select_Query> : Select * from <Object_Type> Where <Filter_Expression> ;

<Filter_Expression> : <Tag_Property> <operation> <value> ;
WHERE clause is optional in select query. Multiple <Filter_Expression> can be applied using
comma(,). The (,) represents logical AND operation across the filters applied in the WHERE
clause.
E.g.: Select * from All_Array_DB where DataType Contains "Bool", Comment StartsWith "Pos";
Table 4-8: Query Builder – Syntax – Object Types

Object Type Description Example
All_OB Retrieves data points from all organization Select * from

blocks All_OB;
All_FB Retrieves data points from all function blocks Select * from All_FB;
(FBs)
All_FC Retrieves data points from all functions Select * from All_FC;
All_Program_Blocks Retrieves data points from all FBs, FCs & OBs Select * from
All_Program_Blocks;
All_Instance_DB Retrieves data points from all instance DBs of Select * from
function blocks All_Instance_DB;

All_Array_DB Retrieves data points from all array DBs present Select * from
in the PLC All_Array_DB;
All_Global_DB Retrieves data points from all global DBs Select * from
All_Global_DB;
All_DB Retrieves data points from all DBs, DBs include Select * from
instance, array and global DBs All_DB;
All_Blocks Retrieve data points from all Blocks including FBs, Select * from
FCs, OBs, DBs All_Blocks;
PLC_Tags Retrieves data points from all tags inside the PLC Select * from
PLC_Tags;
All_Objects Retrieves data points from all FBs, FCs, OBs, DBs, Select * from
plc tags & technology objects All_Objects;
"Block Name" Retrieves all data points from the block name Select * from "Main";
provided

Table 4-9: Query Builder – Syntax – Tag Propertys
Tag Property Description Example
Datapoint_Name Retrieve data point matching the name Select * from All_FB where
Datapoint_Name StartsWith
"main";
DataType Retrieve data point matching the data type Select * from All_Objects
where DataType contains
"Bool";
Address Retrieve data point matching the address Select * from

All_Program_Blocks where
Address EndsWith "Pos";
Comment Retrieve data point matching comment Select * from
All_Program_Blocks where
Comment Equals "Pos";
Datapoint Property used to retrieve the unused Select * from plc_tags where
datapoint datapoint isUnused;
Table 4-10: Query Builder – Syntax – Operations

Operation Description Example
Contains Retrieve data point matching the name Select * from All_FB where
"main" as a starting sub string in the name Datapoint_Name StartsWith
of the datapoint as shown in example "main";
StartsWith Retrieve data point matching the data type Select * from All_Objects
"Int" as a sub string from all objects as where DataType contains
shown in the example "Int";
EndsWith Retrieve data point matching the address Select * from
ending with "Pos" from all program blocks All_Program_Blocks where
Address EndsWith "Pos";
Equals Retrieve data point matching the exact Select * from

word "Pos" in the comment section of the All_Program_Blocks where
datapoint Comment Equals "Pos";
NotEquals Retrieve data points other than the word Select * from
"Pos" in the comment section of the All_Program_Blocks where
datapoint Comment NotEquals "Pos";
Regex Retrieve data points from all program Select * from
blocks matching the regular expression All_Program_Blocks where
pattern that begins with the word "Pos" datapoint_name regex
"^Pos";
IsUnused Retrieve all data points from PLC which Select * from plc_tags where
were never read/written in any block in the datapoint isUnused;
PLC through symbolic access

The user interface Figure 4-5 is intuitive and enables the user to enter an SQL-style query to
filter and choose the kind of datapoints that must be chosen from among the datapoints
extracted by SIMATIC Project Insight. A real time and quick style guide that combines syntax
highlighting and a Query Builder guide that provides suggestions help the user construct a well-
formed query.
There are multiple ways to form these queries by the user.

For example, a simple query could look like the following – where one can list all PLC tags.
Figure 4-6: Query Builder – simple query

Another example is where the user can filter by datatype, from a given subset of datapoints.
Yet another example of the query is that of using regular expressions where the user can use
well-known patterns to make a very specific search.
Figure 4-7: Query Builder – expanded query

SIMATIC Project Insight also offers a utility for the users to save their frequently used and
important queries. The users can save a query by giving it a unique and relatable name.
Figure 4-8: Query Builder – save query by name
The saved queries can be loaded with the option to load only the current device related queries
or from all queries saved until now.
Figure 4-9: Query Builder – open an existing query
The dynamic user query currently does not support some of the features that are common
with SQL queries – such as joins and sub-queries.
NOTE
The Query Editor window also does not support features such as intellisense, autocomplete,
undo and redo actions.
It is possible to turn off syntax highlighting when the user does not need it, for example, when
making multiline queries – otherwise syntax highlighting might not work as intended when a
newline is entered by the user. To turn it off, use the settings icon.
Figure 4-10: Query Builder – Highlight Syntax

4.6 Unit Relations View
The units and their relationship with technology objects and global data blocks are visualized
here. The unit’s visualization can be filtered to better understand the sub graph of units.
Figure 4-11: Functions – Unit Relations View

NOTE The navigation for the "Unit Relations View", you find in chapter 2.7.
4.6.1 Unit Relations View – Options
Table 4-11: Unit Relations View – Options

Center Clicking the center icon reset the Units relations visualization to the

Logs User understands the background process while the UDT
visualization generation happens.
4.7 Project Structure

Export all the engineering objects (such as organizational blocks, function blocks, function calls,
data blocks, user defined types and tags), in the form of JSON for further analysis.
NOTE The navigation for the "Project Structure", you find in chapter 2.8.

4.8 Global Object Dependencies
The global objects dependency’s view provides a clear visualization on global data blocks and
tags and their dependencies with blocks.
Figure 4-12: Functions – Global Object dependencies

NOTE The navigation for the "Global Object dependencies", you find in chapter 2.9.
Table 4-12: System requirements

Center Clicking the center icon reset the data blocks & tags visualization to
the center of the screen.
Fit to screen Fits the visualization to the screen size
Add to export Used to export all the required data points in the form of JSON file
Export cart Export cart checkouts the required datapoints
Logs User understands the background process while the Data blocks &
Tags visualization generation happens.

4.9 Export of Data Points Logs
4.9.1 Logs
All functions of SIMATIC Project Insight have logging feature built in. All background process of
the functionalities is logged in the form of logs which are available for viewing to the user in the
top right corner of SIMATIC Project Insight.
4.9.2 Export of DataPoints
The functionalities "UDT Dependencies", "Signal Flow", "Query Builder" & "Project Structure"
allows the required data points to be exported in the form of JSON file.
1. The required data points from all the functionalities are added to the "Export Cart" by
clicking the "Add to Export" button,
2. the JSON file is exported by clicking the "Check out" button in the "Export Cart".
3. The datapoints in the export cart can be removed by pressing the "Clear Cart" button.
Figure 4-13 shows a sample (left) for an empty "Export Cart" and (right) for an "Export Cart" with
datapoints.
Figure 4-13: Export Chart for exporting DataPoints


4.10 Scheduling Tasks for Batch Export
SIMATIC Project Insight provides users with option to schedule automatic tasks to export
JSONs from the Sequence Analytics, UDT Dependencies, Signal Flow, Query Builder and
Global Object Dependencies.
Figure 4-14: Schedule automatic tasks to export


The scheduled tasks runs without opening SIMATIC Project Insight. The user is provided with
task execution status report for better understanding on the execution status of the tasks.
The tasks if failed are elaborated with appropriate error for the failure.
Figure 4-15: Error for the failure
1. The Task can be made active or inactive for task execution in the scheduler using the
checkbox as shown in the above figure
2. All tasks can be made active or inactive using the "Activate all tasks" checkbox
3. The task name is editable
4. The workflow name is editable
A maximum of 75 tasks can be configured in the UI.

A maximum of 50 tasks can be made active tasks to be scheduled in the windows task
scheduler.
The tasks can be configured using the task configuration fields and options
Export Path – Path where the JSONs should be exported
Project Import Path – Path from where the TIA projects should be imported
Execution Time – Start time of the tasks to be executed
Repeat – Repeat for particular days
PLC Name – Name of the PLCs to analyze
Repeat for all PLCs – Repeat the analysis for all PLCs
Workflows – This selection is used to select the functionalities available for export
Delete Icon – Delete a particular task
Copy Icon – Duplicate a particular task
The following toolbar options are available to the user

- Save all tasks that needs to be executed in a batch
- Expand all tasks
- Collapse all tasks
- Deletes all tasks

Task Scheduling
SIMATIC Project Insight uses Windows Task Scheduler to schedule automated tasks to execute
as shown below.
Figure 4-16: Task Scheduling - How it works

^^
A sample task in Windows Scheduler is shown in Figure 4-17
Figure 4-17: Task Scheduling - Sample

Task Reports
The task reports are available to user after the batch execution as shown
Figure 4-18: Batch execution
The exported JSONs and the task reports are available in export path folder as shown.
Performance
The performance of the system might get degraded during the batch execution as SIMATIC
Project Insight might use most of the system resources during batch execution.
NOTE The navigation for the "Scheduling tasks for Batch Export", you find in chapter 2.10.

4.11 Telemetry
SIMATIC Project Insight collects and process usage and non-personal, non-business-oriented
telemetry data. Users can choose not to send the telemetry data from the slider button "Help us
to improve" present in the home screen of SIMATIC Project Insight.
Figure 4-19: Choose sending telemetry
4.12 Namespaces & Units Analysis

The units feature and namespaces feature are supported by SIMATIC Project Insight for
analysis and visualization.
Representation
In "Call Structure", "UDT Dependencies", "Signal Flow", "Unit Relations View", "Sequence
Analytics" & "Dynamic Queries", the TIA V18 datapoints/blocks/UDTs are displayed or used in
the form of <Namespace>.<ObjectName>.<DatapointName>
The Units information is visualized in "Call Structure" and "Signal Flow".
The fully qualified name of the block should be used in the query of "Query Builder" application
if the block is contained within a namespace.
Eg : To get all datapoints from block "Block_1" present in the namespace "spinner"
Select * from "spinner.block_1";
Visualization
The functionalities "Call Structure", "UDT Dependencies", "Material Flow", "Unit Relations View",
"Sequence Analytics" display the fully qualified namespace in the visualization and the blocks
without namespace are displayed only with block name.
Export
The JSON export contains the namespace information of the datapoints/blocks in the format
shown below:
<Namespace>.<ObjectName>.<DatapointName>

4.13 Multi-User Projects
The "Muti-User" projects ".als17" & ".als18" are supported for analysis using SIMATIC Project
Insight.
4.14 Feedback & Crash Handling

Feedback
The user of SIMATIC Project Insight has option to provide their valuable feedback by clicking on
the link "feedback" present on the left side bottom corner.
This feedback link is available in every page of SIMATIC Project Insight.
Clicking on the link, opens the feedback form in the default browser if there is internet
connection in the machine which can be filled in by the user and submitted to Siemens for
improvement of SIMATIC Project Insight.
A QR Code opens such that the user can scan the QR code via mobile to send their feedback
incase if internet is not present in the machine where SIMATIC Project Insight is installed.
Crash Handling
In case of unforeseen circumstances where SIMATIC Project Insight crashes, an e-mail client
opens with crash report attached in the mail attachment, and the user can write his free text
feedback to inform Siemens about the crash.
4.15 Know-How Protection Blocks Analysis

The analysis of the know-how protected blocks are done by checking ON the checkbox "Include
KHP blocks for analysis".
SIMATIC Project Insight prompts user to enter the know-how protected passwords for all the
blocks as shown, the password can be replicated to all blocks by checking on the check box
"Replicate passwords for the other blocks". SIMATIC Project Insight does not store the "Know-
How Protected Blocks" passwords in any form.
Figure 4-20: Know-How Protection Blocks Analysis
4.16 Application Usage Time-Boxing

The SIMATIC Project Insight is restricted to be used till Dec 31st, 2024.

4.17 SIMATIC Profiling Tool
With SIMATIC Controller Profiling, Siemens offers a comprehensive analysis tool for your user
programs.
4.17.1 Overview
With SIMATIC Controller Profiling, you can analyze and evaluate the runtime behavior of your
user program on a SIMATIC S7-1500 controller in depth. All relevant information can be
graphically displayed and evaluated with Google Chrome.
Figure 4-21: Display in Browser (Google Chrome)

4.17.2 Mode of Operation
Profiling is integrated in the firmware of many SIMATIC S7-1500 controllers from firmware V3.1.
You can find out whether the controller supports profiling in the technical data.
The controllers record the profiling data in a ring buffer. A bin file contains a list containing the
start and end of block numbers with priorities and time stamps. The associated INF file contains
the block names for the block numbers.
When the ring buffer is full, older data will be overwritten.
The data must therefore be read from the CPU immediately after an event to be examined. If
the CPU goes into the STOP state after an error, the data is only overwritten by motion OBs.
You can read the data from the controller using the SIMATIC Profiling Tool via the Web API
interface and generate a compressed trace file in JSON format for analysis with the Chrome
browser.
Figure 4-22: Associated INF file for block numbers

4.17.3 Functionality
In the SIMATIC S7-1500 controllers from firmware V3.1 onwards, profiling is integrated into the
firmware. The controllers record the profiling data in a ring buffer.
This binary data consists of a list of building block names, timestamps, and flags that indicate
the start and end of the building block calls. If the ring buffer is full, older data will be overwritten.
The data must therefore be read from the CPU immediately after an event to be investigated. If
the CPU goes into the STOP state after an error, the data will not be overwritten. You read the
data from the controller with the profiling tool via the Web API interface and use it to generate a
compressed trace file in JSON format for analysis with the Chrome browser.
Figure 4-23: Functionality PLC Profiling and trace data to browser

Profiling for CPU 1516TF, CPU 1517F, CPU 1517TF, CPU 1517F, CPU 1518TF and
NOTE
CPU 1518 MFPs are currently not supported.
4.17.4 Components Used
This application example has been created with the following hard- and software components:
Component Number Article Number Note
STEP 7 Professional V18 1 6ES7822-1..08-.. -
STEP 7 Professional V19 1 6ES7822-1..09-.. -
SIMATIC S7-1500 Controller 1 - Firmware V3.1 or higher
Google Chrome - - -
You can purchase these components from the Siemens Industry Mall.
4.17.5 Web Server Settings
TIA Portal V18

For the profiling data from the SIMATIC S7-1500 CPU to be read via the Web API, you must
activate the CPU's web server. To do this, follow these steps:
1. In the properties of the SIMATIC S7-1500 CPU, click on "Web server".

2. Add "Activate Web server on this module" and confirm the safety notice.
3. For secure access to the web server, the default setting of a configured CPU is the radio
button "Permit access only with HTTPS" enabled by default.
Figure 4-24: Web Server Settings


TIA Portal V19 – and Firmware V3.1
In order for the profiling data from the SIMATIC S7-1500 CPU to be read via the Web API, you
must activate the CPU's web server. To do this, follow these steps:
1. In the properties of the SIMATIC S7-1500 CPU, click on "Web server".
2. Activate "Activate Web server on this module" and confirm the safety notice.
3. For secure access to the web server, the default setting of a configured CPU is the radio
button "Permit access only with HTTPS" enabled by default.
Figure 4-25: Web Server TIA Porta V19 - 1
4. Under "Security settings", open "Users and roles".

5. Open the "Roles" tab.
6. Add a new role, such as "Webserver access".
7. Under "Runtime rights", activate the "Function right" "Read process data"
8. ("Read process data").

8. Open the "Users" tab.
9. Create a user with a password
10. Assign the new role to the user, such as "Web server access".


4.17.6 Reading out recording for evaluation in Chrome
If the web server is activated on your CPU, you can use the Profiling Tool to read the profiling
data from the SIMATIC S7-1500 CPU via the Web API. To do this, follow these steps:
1. Launch the profiling tool and enter the IP address of the CPU as well as the user and
password you have for the web server.
2. Select a folder where you want to save the profiling data. The option "Write profiling data to
file" is enabled by default.
3. Click on "Download profiling data from PLC" to read the profiling data from the CPU. →The
data is stored as binary data in the selected folder.
4. Click on "Export everything to a compressed trace file" to download all the data for
evaluation in the Chrome browser.
Alternatively, you can generate only the overview, see Figure 4-30.
You can use the "Load profiling data from file" button to transfer the stored profiling data to
the Tool and generate it for evaluation in the Chrome browser.
Disabling the "Export PIP entries" options can help prevent the trace viewer from is not
NOTE
overwhelmed by many TPA events.
Disabling the "Export direct access entries" options can help ensure that the trace viewer is
not overloaded with many random-access events.
Figure 4-29: Reading out recording for evaluation in Chrome - 1

Figure 4-30: Reading out recording for evaluation in Chrome - 2

4.17.7 Evaluate Recording
Basics
Google Chrome's tracing tool offers you the opportunity to evaluate the profiling data in a
targeted manner. You can access the tool with the URL "chrome://tracing". Various functions
are available for the evaluation of recordings:
The following table provides an overview of the most important features:
Service Function
Alt + Mouse Wheel Zoom in / out
Or: w/s
A/D Swivel left/right
f Zoom to selection
m Select Current Selection
0 Reset zoom and pan
Mouse Controls
Selection mode: Select fields or area with mouse
Pan Mode: Pan Left/Right
Zoom mode: zoom in/out by dragging up/down Timing
mode: Drag or move markers
By clicking on "?" you will get an overview of all functions for operation.
NOTE Place the "Mouse Controls" as high up as possible so that they are not obstructed by moving
the window areas. If the "Mouse Controls" are hidden, they can be by scrolling with the right
scroll bar.
Loading a Recording
To load a generated recording, follow these steps:
1. Enter the URL "chrome://tracing" or "about:tracing" in the address bar.
2. Drag and drop the file generated by the profiling tool into the browser.
Alternatively, you can click on "Load" and select the file.
Figure 4-31: Evaluate Recording

4.17.8 Examples of evaluations
OB cycle with maximum processing time

To determine the minimum and maximum OB execution time in a time range, proceed as
follows:
Figure 4-32: OB cycle with maximum processing time

Load the profiling data with the profiling tool and generate the overview for the evaluation in
the Chrome Browser. Load the generated data with Chrome tracing and select the "Select
mode" option.
3. Mark the entire tracks or a specific area. → After that, you will see a list of all the marked
OBs are displayed.
4. Select the OB with the highest processing time.
(OB "Main" and OB "SimaHydTO_Main_HMI" are the same length.)
Figure 4-33: Mark the entire tracks or a specific area

5. Select the "Self Time" option. → The longest and shortest OB execution time is displayed.
Note: The difference in runtime (jitter) between the min and max values is very large.
The goal is to find out how the long runtimes come about.
6. Highlight the top bar of the graphic. → At the bottom, the cycles with the highest processing
time is displayed.
7. Click on the event with the highest processing time.
Figure 4-34: OB cycle with maximum processing time - 1

8. Click "m" and then "f" to highlight the cycle and zoom the selection.
Figure 4-35: OB cycle with maximum processing time - 2
Result
The SimaHydTO_Main_HMI [OB124] has a maximum processing time of 44.109ms in cycle
1375. There are no irregularities to be detected. The communication load is also no higher than
before and after the cycle.
→ Further evaluation of the building blocks is required.

The "cycle / jitter" measurements are only exported in the overview. Under "Cycle / jitter time",
the SimaHydTO_Main_HMI [OB124] has a maximum processing time of 48.119ms. This is
NOTE
the duration from the start of the OB to the start of the following OB, which is calculated
internally.

4.17.9 Building block with the longest processing time - (Example 1)
In chapter 4.17.7, the OB cycle with the maximum processing time was determined.
To find the block with the longest processing time in this OB cycle, follow these steps:
1. Load the profiling data using the profiling tool. In the "Export Range" tab, select the OB and
a cycle range in the range of the specific OB cycle. In chapter 4.17.7, the 1375 cycle was
designated as the longest cycle. Therefore, a range from 1370 to 1380 is chosen to have
several cycles for comparison. Generate the area for evaluation in the Chrome browser.
Figure 4-36: Building block with the longest processing time - (Example 1) - 1
2. Load the generated data with chrome tracing. The longest cycle can be seen quickly in the
following figure. However, you can also enter the number of the OB cycle you are looking
for in the search box and the cycle will then be highlighted.
Figure 4-37: Building block with the longest processing time - (Example 1) - 2

Result
The figure shows that the "Main cycle" has a duration of 48.120ms. The "Main cycle" uses the
time stamps of the CPU. The duration therefore corresponds to the actual duration of the entire
cycle.
3. Next, select the "Select mode" option.

4. Mark all the building blocks in this OB cycle.
→ After that, you will be presented with a list of all the building blocks.
5. Click on "Self time" twice.
→ The building blocks are sorted in descending order of "Self time".
Figure 4-38: Main cycle

Result
In this example, the first entries are "Interrupted" and a parent building block. "Interrupted" are
higher-priority OBs that interrupt the OB cycle. What can already be seen in the recording is the
block "SimaHydTO_AxisBasics_AnyAxis [FB33192]" the block with the longest total processing
time. By searching for the module, it is highlighted and thus the evaluation is facilitated.
A comparison of the cycles shows that the device is called three times in all OB cycles. The
second call of the block is so short in the other cycles that it can only be seen by zooming in
(see figure below).
Figure 4-39: Comparison of the cycles
Result
With the information, the programmer can analyze and optimize the one component in a targeted
manner.

4.17.10 Building block with the longest processing time - (Example 2)
To find the block with the longest total processing time in an OB cycle, follow these steps:
1. Load the generated data with Chrome tracing and select the "Select mode" option.
2. Mark all the building blocks in this OB cycle.
→ After that, you will be presented with a list of all the building blocks.
3. Click on "Self-time" twice.
→ The building blocks are sorted in descending order of "self-time".
Figure 4-40: Find block with longest processing time in OB cycle
Result
The GetSymbolPath [FC913] function is invoked 750 times in the OB cycle and has a total
processing time of 92,210ms.

Long processing times in an OB cycle can be avoided if, for example, initializations or one-time
readouts of various data are shifted to the startup OB.
4.17.11 Timing
For example, to measure the time between two OB calls, do the following:
1. Select the "Timing mode" option.
2. Click at the beginning of the OB call and move the mouse pointer to the beginning while
holding down the mouse button of the next OB call. From there, release the mouse button.
Result
1. The measured time is shown to you at the top.
Timing also allows you to measure the time between two interrupts.
NOTE
With it, you can check that the projected times are adhered to.
Figure 4-41: Measure the time between two OB calls

4.18 Specific functionality
Customer Specific Responsibilities:
• Operator is responsible for the confidentiality, integrity and availability of data exported from
SIMATIC Project Insight application and the binaries.
• Perimeter firewall configuration responsibility lies with end customer.
• The system is installed in an environment that ensures physical access is limited to
authorized maintenance personnel only. Managing unauthorized attachment of removable
devices is the responsibility of the operator.
• The platform including hardware, firmware and operating system is securely configured and
maintained by the operator.
• The operator can protect the environment from malware infection.
• Updates will be provided to customers for applications and the platform at a frequency to be
determined.
4.19 Known Issues

SIMATIC Project Insight relies on TIA Openness Framework for extraction of information from
TIA Portal. Any fault in TIA Openness Framework will result in project analysis failure in
SIMATIC Project Insight.

4.20 Restrictions
Note 1:
TIA portal projects protected by UMAC are not supported.
Note 2:
For PLC Tags, the complete symbolic name is now displayed with the members separated by a
dot, e.g.:
PLC_Tag . Member
However, the address of the PLC tags and the comments are not extracted presently. This
behavior is related to the following applications: "UDT dependencies", "Query Builder", "Signal
Flow" and "Sequence Analytics".
In "Query Builder", the address of the PLC tag members is given as the parent tag address
appended with an asterisk (*) in the query results, e.g.:
PLC_Tag.Member would be displayed as PLC_Tag_Address* in the query results.

For a PLC_Tag with address of %Q0.0, the PLC_Tag.Member address would be displayed as
%Q0.0*.
Note 3:
Due to an inherent limitation in TIA Portal Openness, datapoints corresponding to some of the
inbuilt datatypes may not be considered.
A datatype example for this limitation is DTL. This behavior affects the following applications:
"UDT Dependencies", "Signal Flow", "Sequence Analytics" and "Query Builder".
Note 4:
The individual array indices as datapoints are not considered and hence, represented in the
form of [*] in all the functions and JSON export.
Note 5:
SIMATIC Project Insight does analysis on the symbolic name/symbolic access of the variables
of the blocks. The reference/absolute/pointer access of variables are not considered for analysis
in SIMATIC Project Insight.
Note 6:
Data blocks used as datapoints in TIA portal are not considered for analysis in "Query Builder"
feature of SIMATIC Project Insight.
4.21 Alternative solutions

Limited alternatives of the functionalities of SIMATIC Project Insight are available through TIA
portal cross reference mechanism.

5 Appendix
5.1 Service and support
Industry Online Support
Do you have any questions or need assistance?
Siemens Industry Online Support offers round the clock access to our entire service and support
know-how and portfolio.
The Industry Online Support is the central address for information about our products, solutions,
and services.
Product information, manuals, downloads, FAQs, application examples and videos – all
information is accessible with just a few mouse clicks:
support.industry.siemens.com
Technical Support
The Technical Support of Siemens Industry provides you fast and competent support regarding
all technical queries with numerous tailor-made offers
– ranging from basic support to individual support contracts. Please send queries to Technical
Support via Web form:
siemens.com/SupportRequest
SITRAIN – Digital Industry Academy

We support you with our globally available training courses for industry with practical
experience, innovative learning methods and a concept that’s tailored to the customer’s specific
needs.
For more information on our offered trainings and courses, as well as their locations and dates,
refer to our web page:
siemens.com/sitrain
Service offer
Our range of services includes the following:
• Plant data services
• Spare parts services
• Repair services
• On-site and maintenance services
• Retrofitting and modernization services
• Service programs and contracts
You can find detailed information on our range of services in the service catalog web page:
support.industry.siemens.com/cs/sc
Industry Online Support app

You will receive optimum support wherever you are with the "Siemens Industry Online Support"
app. The app is available for iOS and Android:
support.industry.siemens.com/cs/ww/en/sc/2067

5.2 Industry Mall
The Siemens Industry Mall is the platform on which the entire siemens Industry product portfolio
is accessible. From the selection of products to the order and the delivery tracking, the Industry
Mall enables the complete purchasing processing – directly and independently of time and
location:
mall.industry.siemens.com
5.3 Links and literature

Table 5-1: Links and literature
Nr. Thema
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Link to this entry page of this application example

https://support.industry.siemens.com/cs/ww/en/view/109818320
\3\
5.4 Change documentation

Table 5-2: Change documentation
Version Date Modifications
V1.0.3.0 04/2024 Service Pack 3 (Added support for TIA Portal V19) and minor updates
V1.0.2.0 01/2024 Service Pack 2 (Added SIMATIC Profiling Tool)
V1.0.1.2 12/2023 Minor Updates (Application is extended till Dec 31st , 2024)
V1.0.1.1 10/2023 Minor Updates
V1.0.1.0 09/2023 Service Pack 1 (Added "Scheduling Tasks for Batch Export")
V1.0.0.1 03/2023 Minor updates
V1.0.0.0 03/2023 Draft version


SIMATIC Project Insight DEMO-V1.0.3.0 DOC EN

Uploaded by

Document Information

Original Title

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

SIMATIC Project Insight DEMO-V1.0.3.0 DOC EN

Uploaded by

Copyright:

Available Formats

SIMATIC Project Insight