GARANTIS IT Solutions Ltd. takes active part in organizing the event and presenting some information/sharing experience about Polarion projects.
This Conference is a good chance for users of Polarion to share experience, find solutions, learn new ways to solve common tasks,
to find out about the future plans for Polarion ALM product.
| Time | Activity | Presenter |
| 08:30-09:00 | Check-in | Guido Lange & Siemens representative |
| 09:00-09:15 | Opening | Christian Kettl on behalf of MTU Aero Engines, München. Guido Lange on behalf of Polarion User Group |
| 09:15-09:40 |
Ziele, Arbeitsweise, Arbeitsgruppen, Veranstaltungen des Vereins | Tim Behnke, President (1. Vorsitzender), PLM Benutzergruppe e. V. |
| 09:40-10:00 | Aussprache und Abstimmung: Soll die Polarion User Group eine Arbeitsgruppe im PLM Benutzergruppe e. V. werden? | |
| 10:00-10:25 | Requirement based testing in Polarion | Lars Thordsen, Danfoss Drives, Gråsten, DK |
| 10:25-10:50 | 10 years Polarion at Sartorius – A journey to PDLC | Thomas Schink, Sartorius Lab Instruments, Göttingen |
| 10:50-11:15 | Polarion as issue tracking system: experiences, pros & cons | Guido Lange, cip alpha, Heidenheim |
| 11:15-11:40 |
Practical usage of tips & tricks in Polarion
Ideas how to improve life of Administrators
 [PDF download]
| Konstantin Klioutchinski, Garantis IT Solutions, Berlin |
| 11:40-12:05 | Making the move from Wiki & Velocity to AM-TOOL | Roland Nguyen, cip alpha, Heidenheim |
| 12:05-12:45 | Guided tour through MTU Museum | |
| 12:45-13:45 | Lunch | |
| 13:45-15:00 | Collection of and discussion on questions and problems when using Polarion ALM | |
| 15:00-15:15 | Coffee Break | |
| 15:15-16:15 |
Roadmap for Polarion ALM 18 and 19
- strategic feature portfolio of Polarion ALM (next production year and partially also beyond)
- strategy and plans regarding Polarion ALM features and tailoring for dedicated industries like automotive, medical etc.
- recent enhancements and further plans for LiveReport Pages/Widgets
- performance and scalability enhancements and plans
| Radek Krotil, Siemens Industry Software, Prague, CZ |
| 16:15-16:30 | New test execution interface (early access feature) | Katerina Cernikova, Siemens Industry Software, Prague, CZ |
| 16:30-17:00 | Polarion integrations to other Siemens products | Derek Piette, Siemens Industry Software, Pleno, Texas, USA |
| 17:00-17:15 | Feadback, Good Bye |
|
The Conference started on time, at around 9:00.
The meeting room was located in the MTU Aero Engines building. There were many Air Engines on the way to the building.
There was a good skype connection and some people listened and watched the presentations via skype.
The scheduled presentations finished at 17:15 and some people left. However the open discussion
continued untill 18:00. During the conference we had a good chance to ask questions about functionality, problems and plans related to Polarion ALM
and get some more info about Teamcenter integration.
- Benefits of PLM Benutzgruppe are described: official organization, has budget to organize events, has many memebers (mainly from PLM, not ALM, area)
- Main language is German. For Polarion User Group the language will be English - to attract users from around Europe (and around the World)
- Paid membership. Around 390 euros per Company, which allows 2 users to participate in events organized by PLM Benutzgruppe".
Link to regisrtation page http://www.plm-benutzergruppe.de/index.php?id=12
- New Special Interest Group will be created for Polarion ALM
- "PLM Benutzgruppe" has the following SPECIAL INTEREST GROUP'S (SIG´s):
- Teamcenter Unified
- NX CAD
- CAE
- Systemmanagement
- NX Manufacturing
- Lehre und Forschung
- Datenaustausch
- Tecnomatix Product Line
- Solid Edge
- Automotiv
- Medizintechnik
- DECISION: in 2018 PUG can for free participate in PLM Benutzgruppe event on 19.+20.Juni 2018, at Lufthansa Training & Conference Center
in Seeheim- Jugenheim in Germany
Talk #2 - "Danfoss Drives Quality Assurance" - by Lars Thorsden (Danfoss)
- Test Planning right from the start
- Requirements are used as Test Basis for test planning
- The following Funamental Test Process is used:
- Planning
- Analysis & Design. Design Test Cases
- Implementation & Execution
- Evaluation - is the "exit criteria" met?
- Test Closure
- The following Test Plans are used:
- Master test plan.
- Verification level test plan
- Validation level test plan
- Field level test plan
- Using "Variants"
- Polarion Platform project
- inherit: Polarion project X project, with own/local "Test Plan" and "Test Run"
- inherit: Polarion project Y project, with own/local "Test Plan" and "Test Run"
- inherit: Polarion project Z project, with own/local "Test Plan" and "Test Run"
- Benefits:
- Reuse of requirements and Test Cases across platform products
- Easy overview of requirement coverage and actual test results
- Easy impact assessment acreoss platform products
- Visibility into other products/variants affected by a problem in a single product
Talk #3 - "10 years Polarion at Sartorius. A journey to PDLC (Product Development Life Cycle)" - by Thomas Schink (Sartorius Lab Instruments GmbH & Co KG)
- Area of business: Bioprocess and Laboratory Technologies Provider. Bioprocess Solutions. Lab Products and Services.
- From 2007 initial Polarion installation (30-40 users) - to 2018 Polarion as ALM tool for product development (700 users)
- Reuse selected objects easily (for example Requirements, User Stories, etc) - to derive new workitems, to copy/paste workitems => 2017-sr2
- version 18.0 - KanBan Drag & Drop, interactive Agile board.
- Cross project Variant Management [18.0]
- On Demand Loading for Large LiveDoc
- Active Load Balancer
- Single SignOn based on Kerberos. Teamcenter Security Services - for single Sign On
- Integration with Hudson/Jenkins
- Better handling of Attachments. Preview of Attachments
- Resource Traceabilty - for linked resources
- New Button in Administration - to trigger Thread Dump for Polarion GUI (instead of installing special software)
It can be used to investigate problematic Long-Running queries/transactions/queries
- Export Control:
- restrictions on WHO can export WHAT.
- support image-based watermarks in exported files
- support embedding info into the document to show WHEN and WHO exported the Document.
- New Agile Software Polarion Template
- no ClassicWiki is used, instead LiveWiki is used
- new E-library project
- Other speed improvements:
- startup of tomcat
- on demand loading of Derived Linked Revisions
- improvement in hangling Big Data => there shall be White Paper releases
Talk #2 - "Polarion Release News 17/17.1" - by Radek Krotil (Siemens PLM Software)
- Test Resource Management
- ISO26262 - Validation and Verification Toolkit - will be available as extension for template in Polarion 2017-SR1
- Reuse selected objects easily (for example Requirements, User Stories, etc) - to derive new workitems, to copy/paste workitems => 2017-sr2
- version 18.0 - KanBan Drag & Drop, interactive Agile board.
- Cross project Variant Management [18.0]
- On Demand Loading for Large LiveDoc
- Active Load Balancer
- Single SignOn based on Kerberos. Teamcenter Security Services - for single Sign On
- Integration with Hudson/Jenkins
- Better handling of Attachments. Preview of Attachments
- Resource Traceabilty - for linked resources
- New Button in Administration - to trigger Thread Dump for Polarion GUI (instead of installing special software)
It can be used to investigate problematic Long-Running queries/transactions/queries
- Export Control:
- restrictions on WHO can export WHAT.
- support image-based watermarks in exported files
- support embedding info into the document to show WHEN and WHO exported the Document.
- New Agile Software Polarion Template
- no ClassicWiki is used, instead LiveWiki is used
- new E-library project
- Other speed improvements:
- startup of tomcat
- on demand loading of Derived Linked Revisions
- improvement in hangling Big Data => there shall be White Paper releases
Talk #3 - "Polarion Customization at Vorwerk - looking 1 year back, current status and future plans. " - by Konstantin Klioutchinski (GARANTIS IT Solutions Ltd.)
Picture. From one polarion project to many projects for many products.
Next step: integration Polarion ALM + Teamcenter.
- This is a Case Study about Customization of Polarion. It started as specific technical solutions for Feature Driven Development customization
and now it continues as Multy-Project / Multy-Product strategy.
Also we touched topics common for all projects: * How to convince management that customization is needed? * How to administer multiple projects and propagate changes effectively? * What do you need to customize? * How to inform team about customizations?
- CUSTOMER STORY:The company wants to use Polarion ALM and Teamcenter for Design, Development and Testing of all parts of the product,
i.e. SYSTEM, Software, Mechanics, Electronics.
Polarion TEMPLATES are defined for each sub-project. Based on these templates many Polarion projects are created.
In 2016:
- We had 1 project
- We used about 60% of Polarion features
- We assumed it was COMPLEX
In 2017:
- We have many projects for many products
- We use about 90% of Polarion features
- Maybe it is COMPLEX … but we want to GO FORWARD to the Digital Factory concept
GROWTH of projects:
- From single „Software Project“ we moved to:
- multiple „System“ + „Software“ + „Mechanics“ + „Electronics“ projects
NEXT step:
- ALM + PLM
- Polarion + Teamcenter
|
|
Talk #4 - "Variant Management" - by Daniel Höllisch (AGCO Corporation)
- BOM/EBOM in Polarion. BOM - Bill of Materials, EBOM - Engineering Bill of Materials. Defined/stored/managed in Polarion.
Exported to another tool to be used in Product Configuration.
- VC Group - used to select groups and parts. For example, which parts are needed if user wants to have Diesel Engine
- BOM is always linked to CAD model, i.e. in CAD you can see the "place" of the item. In polarion there is no CAD model, i.e. no"place".
- The data in Polarion can be used to allow user to Configure their own "Tractor" - the needed items will be selected together as a group of needed items/materials for each chosen by user config option.
Picture. BOM and EBOM is defined and stored in Polarion
From presentation of Daniel Höllisch, AGCO Corporation.
Talk #5 - "HIL Test Roundtrip" - by Roland Nguyen (CipAlpha)
- AM-Pack - Automotive & Mechatronics Package
- create Test Run from TCS (from Live Doc)
- export External Test Initialization File from Test Run
- import Test Results into Test Run
Talk #6 - "Integration ALM/PLM. Questions from real projects.What are we looking for?"
- by Konstantin Klioutchinski (GARANTIS IT Solutions Ltd.) & Andreas Deuter (OWL Hochschule, University of Applied Sciences)
- BEST INTEGRATION TODAY is
Connector v1.3.0 = Polarion ALM 17 + Active Workspace 3.3 + Siemens Teamcenter 11.3
- Integration Teamcenter + Polarion - EXISTS ! ..and it is getting BETTER with every release.
- WHER STORE WHAT? - that is the Question!
Requirements, Change Requests, Defects - is their place in Teamcenter or in Polarion?
- Live Demo: PLM + ALM
Picture. WHER STORE WHAT? - that is the Question!
Requirements, Change Requests, Defects - is their place in Teamcenter or in Polarion?
Talk #7 "Live Demo of Polarion+Teamcenter integration" by Prof. Andreas Deuter (OWL University of Applied Sciences)
- This is a presentation about Teamcenter+Connector+Polarion integration. SmartFactory OWL has this connection installed and configured. If you are looking for similar connection - ask SmartFactory OWL!
- The “PLM/ALM for Smart Products” research project in the SmartFactory OWL aims to explore intelligent development processes for smart products with regard to Industrie 4.0. In this context, Siemens Teamcenter and Polarion ALM are used to create detailed use cases for the consistent management of product data to be tested regarding applicability in specific product developments.
- This presentation shows specific PLM/ALM use cases that are realized in der SmartFactory OWL with the use of Siemens Teamcenter and Polarion ALM, discussing the advantages of the current PLM/ALM integration from the user’s point of view and providing recommendations for improvements.
- OWL Hochscule developed an example project "Smart Light", which consists of (a) elements of IoT, (b) Electronics, (c) Mechanics
- During Demo:
* in Polarion can see Active Workspace
* Teamcenter contains some Design which is linked to Polarion
- You can make links (technichally) in 2 ways:
- using workflow in Teamcenter: start (preconfigured) workflow in Teamcenter and then the link will be created
- manually create link
- BOM - Teamcenter has strength to handle BOM - therefore in this example BOM is stored in Teamcenter. Electric part element in Teamcenter contains binary attachment, which is the BUILD (firmware) - produced by the "build" function in Polarion.
- Builds - can compile for Android, can be compiled in Polarion - and then can be stored in Teamcenter as an attachment. Technically is done using small proxy. => advantage : always to have latest Binary in BOM.
Polarion ALM and Teamcenter Integration - our notes
Some notes from our experience and other users, from exhibitions and conferences.
Why Polarion+Teamcenter?
- modern product include "hardware" product + "software" product. Software is everywhere.
- not conencted PLM and ALM tools can cause errors in fucntioning of "software" + "hardware".These failures have affected both the consumers and the vendors, in some cases with dramatic effects.
- In most of these situations the cause is the disconnection between PLM and ALM.
- SOLUTION: better connections betwee PLM+ALM. Better connection between Teamcenter and Polarion. Better product "Teamcenter-Polarion Connector"
Polarion vs Teamcenter? What is the Future?
There was the same information comming from different sources during the conference: Polarion and Teamcenter will co-exist in parallel.
They will be gradually connected better and better.
There is no need to switch from Teamcenter to Polarion or from Polarion to Teamcenter.
Each product has own advantages, and together they allow to solve Product Development tasks : Teamcenter can be PLM tool, and Polarion - ALM tool.
For example, for Software Development it is better to use Polarion. But for hardware parts and mechatronics - Teamcenter.
A lot of work is going on to integrate Teamcenter and Polarion. There are already examples of this integration working.
Next steps are to make it "smoother" , "more natural", to provide more functions and satisfy requests from customers.
Why Polarion ALM is good and needed? - (*) Polarion is for a system-driven product development,
(*) it is a complex tool, but user experience is made as easy as possible, (*) roll-out of Polarion is "just days", not weeks or months.
DIFFERENCE between ALM and PLM:
As Jiri Walek said: "there is only one letter difference "A" and "P" - between ALM and PLM".
ALM = is "more than Requirements" => "down to the software line of code".
PLM => down to the Bill Of Materials (BOM) and simulation of the product.
ALM and PLM have a lot of common, but obviously there is a difference: what is managed, who works with each tool, how users expect to see information,
what functionality and behaviour they expect from the tools in Product and in Application Lifecycle Management.
Additional Info
Product lifecycle management (PLM) is an information management system that can integrate data, processes, business systems and, ultimately,
people in an extended enterprise. PLM software allows you to manage this information throughout the entire lifecycle of a product efficiently and cost-effectively,
from ideation, design and manufacture, through service and disposal.
Source: Siemens PLM site
Polarion offers a complete Application Lifecycle Management (ALM) suite to offer greater visibility into the software development process.
Polarion is a unified solution for Requirements, Quality, and Application Lifecycle Management.
Polarion Software was acquired by Siemens PLM Software in January 2016, expanding their support for the growing ALM market.
Digital Factory concept
"Digitalization is everywhere and is changing all industries". Siemens, after recent purchases, is in good shape to be in a leading position for complete PLM.
There is a lot going on about Digital Factories, Smart Factories.
The main idea of Digital Factory: to have complete continious chain from Product Concept to Product Design, and then "feeding" the design documents to robots in Digital Factory, allowing them to make the product (or parts) autonomously.
Even though Polarion does not have direct link to Digital Factory concept, it becomes part of the PLM/ALM solution and consequently is used together with Teamcenter to describe Specifications and Design, or to manage Requirements, Defects, Change Requests etc.
Technically Teamcenter has (will have) programming interface to the machinery in the Factory and can control manufacturing processes. A good example is a company "Local Motors", who 3D printed a complete car.
See you at PLM Europe - 2017 ?
Come and meet GARANTIS IT Solutions at PLM Europe 2017 in Berlin.
We will be pleased to share and demonstrate our knowledge in Polarion ALM.
Share Expert Knowledge - Meet us at the Conference
GARANTIS will be available to discuss your strategic requirements for ALM Solutions:
- Which ALM solution is good for you?
- Choosing Polarion as ALM solutions
- Initial Setup of Polarion
- Customizations & Maintenance
- Process definition and Implementation of Processes in Polarion
- Integrations (Jenkins, Polarion, GIT, etc)
- Tricks & Tips
We are involved every day in short-term and long-term contracts during all stages of the software development projects.
To share our knowledge with you will be a pleasure for us.
|
|
|
Meet us after the Conference
We are always available to support our clients and to give free advise:
E-mail: info@garantis.co.uk
Direct Phone: +44 (0) 118 343 1584
