This document discusses options for centralizing or decentralizing different aspects of implementing a public warning system (PWS) between a state and mobile carriers. It examines centralizing or decentralizing the technical architecture, distribution of power among stakeholders, and tendering process. For each decision, the document provides factors to consider like technical prerequisites, speed of implementation, and allocation of responsibilities to help validate the best approach. The overall message is that there is no single best solution and a thorough assessment of objectives, drivers, and risks is needed to increase chances of long-term success.

1. Implementing PWS
To centralize or
not to centralize
Mathieu Lafforgue
Global tender at State level vs. Freemarket model at all levels?

2. Crisis management system
GIS
Alert aggregator
Mobile carriers' layer
Mobile App
Website
Other communication channels
1.
2.
3.
4.
5.
6.
7.

3. For each item, you'll
have to decide to
centralize, or not.
Let's take a practical approach
applied to PWS between a
State and mobile carriers.
Validate your
decision
2.
Distribution
of Power
Your
perspectives
Technical
architecture
Tendering
process

4. State
PWS
PWS
How centralized are your
stakeholders and alert issuers?
Distribution
of Power

5. New implementation?
Modernization?
Extension?
Where are you starting from, where are you going to?
Comply to regulation?
Increase effectiveness?
Rationalize?
What are your key drivers?
What are your objectives?
Your
perspectives

6. Centralized or decentralized
technical architecture?
MNOs' layer
Public authorities layer
Decentralized in public authorities layer,
delegated at mobile carrier layer
Centralized & consolidated
under a single public authority
Mobile networks
Public authority layer
Technical
architecture

7. Mobile networks
Public authority layer
Simple political/administrative context
Availability of skills
Prerequisites of this model:
Speed of implementation
Simplification of responsibilities
Risks of dependency & Long-term evolutivity
Interventionism in MNO network operations
Pros:
Cons
State bears full responsibility
Extraction of sensitive data from operators
Implications of this model:
Centralized
technical architecture...
Centralized & consolidated
under a single public authority
Technical
architecture

8. MNOs' layer
Public authorities layer
Decentralized in public authorities layer,
delegated at mobile carrier layer
Alert aggregator in a public entity
Define interface contracts
Prerequisites of this model:
Scalable and resilient architecture
Empower all involved parties
Longer upstream phases
Complex program management
Pros:
Cons
Balanced sharing of responsibilities
Implications of this model:
...or decentralized
technical architecture?
Technical
architecture

9. Tendering process:
centralize, or decentralize?
Centralized/consolidated purchase process: Tender(s) at public authority level:
Tenders at MNO level:
Fast bidding process
Upfront optimization
Open, standard, agile and ecosystem
Search for the optimum for each block
Autonomy of decision of MNOs
Tendering
process

10. 1. Is it mandated?
2. Does it bring
significant value?
3. Are the risks low?
One YES ↦ Centralize
Three NOs ↦ Don't
*McKinsey methodology
How to
validate
your
decisions
Quick tip

11. There is no one-
size-fits-all solution.
By going through a
detailed assessment,
you increase your
chances of success in
the long-run.

12. Mathieu Lafforgue
Product Marketing Manager
mathieu.lafforgue@intersec.com
Phone: +33 6 38 85 61 39
Thank you!