@inproceedings{UlmerBraunChengetal.2022,
  author    = {Ulmer, Jessica and Braun, Sebastian and Cheng, Chi-Tsun and Dowey, Steve and Wollert, J{\"o}rg},
  title     = {Usage of digital twins for gamification applications in manufacturing},
  series = {Procedia CIRP},
  volume    = {107},
  booktitle = {Procedia CIRP},
  publisher = {Elsevier},
  address   = {Amsterdam},
  issn      = {2212-8271},
  doi       = {10.1016/j.procir.2022.05.044},
  pages     = {675 -- 680},
  year      = {2022},
  abstract  = {Gamification applications are on the rise in the manufacturing sector to customize working scenarios, offer user-specific feedback, and provide personalized learning offerings. Commonly, different sensors are integrated into work environments to track workers' actions. Game elements are selected according to the work task and users' preferences. However, implementing gamified workplaces remains challenging as different data sources must be established, evaluated, and connected. Developers often require information from several areas of the companies to offer meaningful gamification strategies for their employees. Moreover, work environments and the associated support systems are usually not flexible enough to adapt to personal needs. Digital twins are one primary possibility to create a uniform data approach that can provide semantic information to gamification applications. Frequently, several digital twins have to interact with each other to provide information about the workplace, the manufacturing process, and the knowledge of the employees. This research aims to create an overview of existing digital twin approaches for digital support systems and presents a concept to use digital twins for gamified support and training systems. The concept is based upon the Reference Architecture Industry 4.0 (RAMI 4.0) and includes information about the whole life cycle of the assets. It is applied to an existing gamified training system and evaluated in the Industry 4.0 model factory by an example of a handle mounting.},
  language  = {en}
}
@inproceedings{ChavezBermudezWollert2022,
  author    = {Chavez Bermudez, Victor Francisco and Wollert, J{\"o}rg},
  title     = {10BASE-T1L industry 4.0 smart switch for field devices based on IO-Link},
  series = {2022 IEEE 18th International Conference on Factory Communication Systems (WFCS)},
  booktitle = {2022 IEEE 18th International Conference on Factory Communication Systems (WFCS)},
  publisher = {IEEE},
  isbn      = {978-1-6654-1086-1},
  doi       = {10.1109/WFCS53837.2022.9779176},
  pages     = {4 Seiten},
  year      = {2022},
  abstract  = {The recent amendment to the Ethernet physical layer known as the IEEE 802.3cg specification, allows to connect devices up to a distance of one kilometer and delivers a maximum of 60 watts of power over a twisted pair of wires. This new standard, also known as 10BASE-TIL, promises to overcome the limits of current physical layers used for field devices and bring them a step closer to Ethernet-based applications. The main advantage of 10BASE- TIL is that it can deliver power and data over the same line over a long distance, where traditional solutions (e.g., CAN, IO-Link, HART) fall short and cannot match its 10 Mbps bandwidth. Due to its recentness, IOBASE- TIL is still not integrated into field devices and it has been less than two years since silicon manufacturers released the first Ethernet-PHY chips. In this paper, we present a design proposal on how field devices could be integrated into a IOBASE-TIL smart switch that allows plug-and-play connectivity for sensors and actuators and is compliant with the Industry 4.0 vision. Instead of presenting a new field-level protocol for this work, we have decided to adopt the IO-Link specification which already includes a plug-and-play approach with features such as diagnosis and device configuration. The main objective of this work is to explore how field devices could be integrated into 10BASE-TIL Ethernet, its adaption with a well-known protocol, and its integration with Industry 4.0 technologies.},
  language  = {en}
}