Jump to content

GLA Summit 2020/TestStand goes Agile: Difference between revisions

From LabVIEW Wiki
Added page
 
m Update with infobox and presentation template
 
Line 1: Line 1:
'''TestStand Goes Agile''' by Nikolaus (Niko) Naredi-Rainer
{{infobox
|category=presentation
|icon=GLASummitButton.png
|presentation-conference=GLA Summit 2020
|presentation-presenter=Nikolaus Naredi-Rainer
}}


''In this presentation  I will cover a TestStand/LabVIEW architecture in an IIoT environment. Our software, covering the classical end-of-line test of a communication device for the railway service, is used for assembly and also for the repair of broken devices. This classical approach is extended with the functionality to report all ongoing processes to a JIRA Kanban board, so that the end customer is able to see in real-time the status of all devices that are under warranty. To achieve this transparency, the original LabVIEW/TestStand architecture is complemented with REST-API calls. This allows for the End-of-Line tester to automatically create components and track issues.
{{presentation
To gain more information into the production process itself and identify steps that are most critical in the assembly of the device, the test results are additionally uploaded to a WATS database. From there, summaries like first-pass-yield or assembly times can be extracted easily.''
|presenters=Nikolaus Naredi-Rainer
|abstract=In this presentation  I will cover a TestStand/LabVIEW architecture in an IIoT environment. Our software, covering the classical end-of-line test of a communication device for the railway service, is used for assembly and also for the repair of broken devices. This classical approach is extended with the functionality to report all ongoing processes to a JIRA Kanban board, so that the end customer is able to see in real-time the status of all devices that are under warranty. To achieve this transparency, the original LabVIEW/TestStand architecture is complemented with REST-API calls. This allows for the End-of-Line tester to automatically create components and track issues.
To gain more information into the production process itself and identify steps that are most critical in the assembly of the device, the test results are additionally uploaded to a WATS database. From there, summaries like first-pass-yield or assembly times can be extracted easily.


''In summary, this architecture allows a holistic view into the assembly/repair process from an engineering point of view as well as full transparency towards the end customer.''
In summary, this architecture allows a holistic view into the assembly/repair process from an engineering point of view as well as full transparency towards the end customer.
|youtube-id=oAD2G2JukRM
}}


 
==External links==
<div style="text-align:center;"><youtube width="800" height="600">oAD2G2JukRM</youtube></div>
*[https://www.glasummit.org/presentation-list/2020 GLA Summit 2020 Presentations]
 
==Presentation Links==
* [https://youtu.be/mLdv-PRP0M4 YouTube Video Link]
 
==See Also==
{{ambox|text=Add links to internal wiki pages that would also help.}}
 
==External Links==
{{ambox|text=Add links to external resources that would also help.}}


[[Category:GLA Summit 2020]]
[[Category:GLA Summit 2020]]

Latest revision as of 06:48, 22 August 2024

TestStand goes Agile
Conference GLA Summit 2020
Presenters Nikolaus Naredi-Rainer
TestStand goes Agile by Nikolaus Naredi-Rainer

In this presentation I will cover a TestStand/LabVIEW architecture in an IIoT environment. Our software, covering the classical end-of-line test of a communication device for the railway service, is used for assembly and also for the repair of broken devices. This classical approach is extended with the functionality to report all ongoing processes to a JIRA Kanban board, so that the end customer is able to see in real-time the status of all devices that are under warranty. To achieve this transparency, the original LabVIEW/TestStand architecture is complemented with REST-API calls. This allows for the End-of-Line tester to automatically create components and track issues.

To gain more information into the production process itself and identify steps that are most critical in the assembly of the device, the test results are additionally uploaded to a WATS database. From there, summaries like first-pass-yield or assembly times can be extracted easily.

In summary, this architecture allows a holistic view into the assembly/repair process from an engineering point of view as well as full transparency towards the end customer.



External links