Design-Operation Continuum Methods for Traffic Master

The lifecycle of lifts could last up to 30 years. As with any other electrical or mechanical component, software of lifts also requires a maintenance process. Maintenance copes with (1) hardware obsolescence and/or degradation, (2) bug fixing, (3) new functionalities, (4) requirements changes, etc. This evolution requires reliable and automatic engineering methods for developing and operating lifts. Advances in the last few years have resulted in a more efficient development process, improving modelling and simulation techniques to validate complex systems from the early phases of development. However, once the system is deployed, methods used during operation and maintenance do not have synergies with methods used during the design. The steps from the development to operation, i.e. testing, delivery and deployment, often require certain manual work to guarantee reliability. Current software development approaches are not applicable or require extension for lifts, where evolution is constant. Furthermore, learning from operational data to enhance the design is becoming a necessity in this sector. The ADEPTNESS project seeks to investigate and implement a streamlined and automatic workflow that makes methods and tools for the software development and maintenance of lifts to be seamlessly used during design phases as well as in operation. The ADEPTNESS framework uses a novel embedded microservices-based architecture for the context of lifts. The generation and reuse of test cases and oracles from initial phases of the development to the system in operation and back to the laboratory for further analysis will be investigated. This will guarantee a faster and more reliable detection of faults before a new software release is deployed into the lift installations. This deployment will be automatic and synchronised to improve the agility of the whole workflow that covers design-operation continuum. Additionally, test oracles will run both at design-time as well as at operation, permitting the continuous validation of a software release.