HOW TO IMPLEMENT ARTICLE 110 OF THE ELECTRONIC COMMUNICATIONS CODE
GETTING IT RIGHT THE FIRST TIME
What: 1 Day Workshop
When: 16 May 2019
Where: Belgian Police Headquarters - Rue Royale 202, 1000 Brussels, Belgium
Entry fee: 260€
Based on the experience and learning from leading Australia's equivalent ("Emergency Alert") Public Warning System. This will focus on the benefits of an outcomes-driven and requirements-led approach against which to evaluate the best available technologies. We will explain how to create value for money and a greater return on investment by delivering a single architecture that provides a common platform for multiple operational requirements.
This workshop complements the PSCE White Paper "HOW TO IMPLEMENT ARTICLE 110 OF THE ELECTRONIC COMMUNICATIONS CODE - GETTING IT RIGHT THE FIRST TIME".
The purpose of the first PSCE workshop is to help national project teams with the process for design through to delivery of their Public Warning System in order to achieve full compliance with Article 110 EECC by June 2022.
Michael Hallowes will facilitate much of the workshop. He is the former Emergency Services Commissioner and National Director of Australia’s Emergency Alert Program. He will offer his hands-on experience from leading the design to delivery of Australia’s equivalent Public Warning System, known as the “Emergency Alert - Location Based Solution”, as a guide to successful implementation of Article 110 EECC.
Topics for the facilitated discussion sessions will include:
- Understanding the statutory requirements of Article 110 EECC
- Maximising value for money and return on investment from an all hazards, all agencies approach to the design
- Lessons from other countries
- *Exercising the statutory duty to warn the public in times of emergency
- *Requirements mapping against the National Risk/Threat Register (or equivalent)
- *Scenario planning to identify use cases
- *Data privacy legislation affecting public alerting
- Sequencing the project to follow best practice:
- People (community expectations and operational requirements)
- Process (when and how will to use the system), and then
- Technology (choosing the right one as the enabler).
- Automated, near real-time system assurance
- Functional requirements of the system operator
- Control Room integration
- Community education
- Operational readiness
- Principles for industry engagement.
* Indicates a topic that delegates will need to research beforehand and bring copies of relevant documents to aid the group discussions.