Refine
Year of publication
- 2021 (17) (remove)
Document Type
- Part of a Book (17) (remove)
Keywords
- robotic process automation (2)
- Central receiver power plant (1)
- Coefficient of ocular rigidity (1)
- Concentrated systems (1)
- Concentrating solar power (1)
- Corneo-scleral shell (1)
- Cross-platform (1)
- Customer Experience Management (1)
- Customer Journeys (1)
- Differential tonometry (1)
- Evaluation (1)
- Eyeball (1)
- Fresnel power plant (1)
- Gas turbine (1)
- Intelligentes Parken (1)
- Kommerzielle Interaktionen (1)
- Mobile web (1)
- PWA (1)
- Pressure-volume relationship (1)
- Progressive Web App (1)
Institute
- Fachbereich Elektrotechnik und Informationstechnik (9)
- Fachbereich Energietechnik (3)
- Fachbereich Medizintechnik und Technomathematik (2)
- Fachbereich Bauingenieurwesen (1)
- Fachbereich Gestaltung (1)
- Fachbereich Wirtschaftswissenschaften (1)
- IBB - Institut für Baustoffe und Baukonstruktionen (1)
- IfB - Institut für Bioengineering (1)
- Nowum-Energy (1)
- Solar-Institut Jülich (1)
This chapter describes three general strategies to master uncertainty in technical systems: robustness, flexibility and resilience. It builds on the previous chapters about methods to analyse and identify uncertainty and may rely on the availability of technologies for particular systems, such as active components. Robustness aims for the design of technical systems that are insensitive to anticipated uncertainties. Flexibility increases the ability of a system to work under different situations. Resilience extends this characteristic by requiring a given minimal functional performance, even after disturbances or failure of system components, and it may incorporate recovery. The three strategies are described and discussed in turn. Moreover, they are demonstrated on specific technical systems.
Robotic process automation (RPA) has attracted increasing attention in research and practice. This chapter positions, structures, and frames the topic as an introduction to this book. RPA is understood as a broad concept that comprises a variety of concrete solutions. From a management perspective RPA offers an innovative approach for realizing automation potentials, whereas from a technical perspective the implementation based on software products and the impact of artificial intelligence (AI) and machine learning (ML) are relevant. RPA is industry-independent and can be used, for example, in finance, telecommunications, and the public sector. With respect to RPA this chapter discusses definitions, related approaches, a structuring framework, a research framework, and an inside as well as outside architectural view. Furthermore, it provides an overview of the book combined with short summaries of each chapter.
Die Studie erörtert anhand eines Fallbeispiels aus der Mathematik für Ingenieur*innen, wie didaktische Gestaltungsprinzipien für Soziale Präsenz, Kollaboration und das Lösen von praxisnahen Problemen mit mathematischem Denken in einer Online-Umgebung aussehen können. Hierfür zieht der
Beitrag den forschungsmethodologischen Rahmen Design-Based Research (DBR) hinzu und berichtet über Zwischenergebnisse. DBR wird an dieser Stelle als eine systematische Herangehensweise an kurzfristige Lehrveränderungen und als Chance auf dem Weg zu einer neuen Hochschullehre nach der COVID-19-Pandemie dargestellt, die theoretische und empirische Erkenntnisse mit Praxisverknüpfung und -relevanz vereint.
The term ocular rigidity is widely used in clinical ophthalmology. Generally it is assumed as a resistance of the whole eyeball to mechanical deformation and relates to biomechanical properties of the eye and its tissues. Basic principles and formulas for clinical tonometry, tonography and pulsatile ocular blood flow measurements are based on the concept of ocular rigidity. There is evidence for altered ocular rigidity in aging, in several eye diseases and after eye surgery. Unfortunately, there is no consensual view on ocular rigidity: it used to make a quite different sense for different people but still the same name. Foremost there is no clear consent between biomechanical engineers and ophthalmologists on the concept. Moreover ocular rigidity is occasionally characterized using various parameters with their different physical dimensions. In contrast to engineering approach, clinical approach to ocular rigidity claims to characterize the total mechanical response of the eyeball to its deformation without any detailed considerations on eye morphology or material properties of its tissues. Further to the previous chapter this section aims to describe clinical approach to ocular rigidity from the perspective of an engineer in an attempt to straighten out this concept, to show its advantages, disadvantages and various applications.
Magnetic nanoparticle relaxation in biomedical application: focus on simulating nanoparticle heating
(2021)
Intelligent autonomous software robots replacing human activities and performing administrative processes are reality in today’s corporate world. This includes, for example, decisions about invoice payments, identification of customers for a marketing campaign, and answering customer complaints. What happens if such a software robot causes a damage? Due to the complete absence of human activities, the question is not trivial. It could even happen that no one is liable for a damage towards a third party, which could create an uncalculatable legal risk for business partners. Furthermore, the implementation and operation of those software robots involves various stakeholders, which result in the unsolvable endeavor of identifying the originator of a damage. Overall it is advisable to all involved parties to carefully consider the legal situation. This chapter discusses the liability of software robots from an interdisciplinary perspective. Based on different technical scenarios the legal aspects of liability are discussed.
The existence of several mobile operating systems, such as Android and iOS, is a challenge for developers because the individual platforms are not compatible with each other and require separate app developments. For this reason, cross-platform approaches have become popular but lack in cloning the native behavior of the different operating systems. Out of the plenty cross-platform approaches, the progressive web app (PWA) approach is perceived as promising but needs further investigation. Therefore, the paper at hand aims at investigating whether PWAs are a suitable alternative for native apps by developing a PWA clone of an existing app. Two surveys are conducted in which potential users test and evaluate the PWA prototype with regard to its usability. The survey results indicate that PWAs have great potential, but cannot be treated as a general alternative to native apps. For guiding developers when and how to use PWAs, four design guidelines for the development of PWA-based apps are derived based on the results.