The FAILSAFE workshop will provide a forum to discuss tools and techniques to address the difficulties and challenges of deploying Embedded Wireless Sensor Systems (EWSS) in the wild, and aim to produce reliable, robust systems. We seek papers of up to 8 pages about any tools, methods, techniques, or approaches to engineer robust and resilient EWSS. This includes robustness and resilience faults and failures from the environment, human error, or malicious activities. Examples include novel simulation frameworks, the use of formal methods like model checking, design methodologies, languages that explicitly handle faults and failures, forms of unit, integration, or run time testing, models to test performance during faults and failures, and anything else relevant to this discussion.
Papers describing and presenting data of problems and failures of experimental efforts, practical experiences, and industrial and commercial developments in all aspects of sensor networks, mobile devices, and wireless communication are also solicited and encouraged. We seek work that discusses real Deployments and ways to engineer them, Security of EWSS, both ways to engineer security at design time, and approaches to run time security, and Application resilience including designed resilience for control systems. We encourage submissions of the above topics of interest that cover, but are not limited to:
Deployments and how to design them
- Testing frameworks, models, simulators, formal methods that deal with sensor system deployment failures, and can be used to prevent similar failures of wireless sensor systems. This includes failure of the sensor systems themselves, or the affect that their failure would have on the application that uses their data.
- Monitoring tools, control systems, or code update systems for use in sensor system deployments to detect and diagnose node or system performance issues, failures, or malicious activity.
- Any account of a real ENSS deployment with an emphasis on any design tools or methodologies used, and an assessment of the benefit that they provided.
- Examples of a deployment that was tested, and failed due to unexpected circumstances. The testing methodology must be presented and discussed, as well as how it failed to account for the phenomenon that caused the failure, and a potential solution described.
- Failure and the diagnosis of an actual deployment of mobile apps, networks and systems. Must include some data and analysis of what caused the failure.
Secure Design and Operation of EWSS
- Approaches to address faults and failures caused by malicious activity aimed at the disruption of the EWSS or the application that uses it.
- Formal models of security attacks.
- Secure by design approaches to EWSS.
- Runtime security or intrusion detection systems for EWSS.
- Any documented example of a real EWSS deployment that either was attacked by malicious agents, or that deployed security mechanisms, with a description of what was done.
Resilient and Robust Applications and Control
- Design methods to create applications or controllers that are resilient and robust to the loss, delay, or corruption of data from an EWSS.
- Applications of formal methods to design and/or verify resilient and robust sensor networks.
- Examples or methods to engineer coupled communication and control systems that are resilient and robust.
- Examples of real deployment using wireless sensors for a controller with instances of failure or any design methodology used, or any security considerations taken.
Submission Deadline, 17th of August 2018
Notification, 10th of September 2018
Final Version Due, 20th of September 2018
Workshop, 4th of November 2018
The organisers of FAILSAFE recognise that some information from deployments may have a sensitive nature or be under a non-disclosure agreement. In these cases, it is acceptable to anonymise any information as long as it does not inhibit the point or issues being presented in the work. If you have any queries about this at all, please contact the general program chair Michael Breza (firstname.lastname@example.org) for further advise and clarification.