1. CONNECT. TRANSFORM. AUTOMATE.
Disaster Recovery in GIS:
FME Cloud Server Saves the Day
2. What’s This All About, Then?
▪ The scope of this presentation is total loss of a
▪ The goal is to establish basic operations but a
discussion of Business Continuity is out of scope
▪ We’ll look at additional leverage provided by the
▪ Interesting presentation from Georgia Power!
3. Worst-Case Scenario
4. Don’t Panic!!!
CC BY 2.0 Alois Staudacher:
5. Cloud and/or multi-site
Both may be better!
▪ Little to maintain
▪ Scales quickly
▪ No assets
▪ Easy to include
▪ Operating space for
▪ Not Internet reliant
▪ Predictable cost
▪ Can build partnerships
▪ High bandwidth
6. FME Server: On-Site Or Cloud!
CC BY 2.0 Arsh_86:
Settle for no
7. Our Sample Use Case
● Athens-Clarke County: population 116,000
● Data will come in from and support multiple
(Planning, Assessor, Fire, PD, UGA, Traffic
Engineering, Dispatch, State and Federal
● Multi-site agency
● Agencies and partners (such as utility
organizations) should be able to submit data
● Metadata should be captured
● Technicians will analyze data
● Customers need actionable data products
8. Data Reconstruction Workflow
Amazon Cloud DB
9. Advantages of a Web interface
▪ Abstract and centralize access (S3 IAM
keys, FME Cloud API keys, web interface roles)
▪ Simplify workflows for users, who may be
▪ Spin up entire DR stack on demand
▪ Branding/Organizational Identification
▪ No resources required on-premises (which is
19. TL;DL: FME Cloud Server
Saves the Day!
▪ Up and running faster than you can move to
your backup site
▪ AWS scales to meet massive data needs
▪ Inexpensive: FME Cloud Server starts at
▪ With APIs, whole process can be automated
▪ All stakeholders can easily submit data which is
robustly served to all customers
▪ Can be part of an existing data continuity plan
▪ Provides opportunities for other business
units, providing organization-wide leverage
20. Thank You!
▪ For more information:
▪ Lou Manglass: email@example.com