When Covid hit, government agencies scrambled to solve the problem of connecting employees and contracts to their internal networks. This story tells a tale of how one group in an agency built an ecosystem in AWS to allow remote users the ability to continue their day-to-day data processing. FME played a crucial role in how this ecosystem functions and allowed users to continue on with their work 3 years later and it is still going strong.

1. Remotely Possible
Thinking outside the Polygon
The challenges, lessons and benefits in distributed
work patterns from the COVID pandemic.

2. Presenters
The
Peak
of
Data
Integration
20
23
Brett
Madsen
Data Integration Specialist
Defence Mapping
Geoscience Australia
Daniel
McIlroy
Data Integration Lead
Defence Mapping
Geoscience Australia

3. The
Peak
of
Data
Integration
20
23
The Problem

4. The
Peak
of
Data
Integration
20
23
Cloud Logic
• Enterprise GIS team provided five of each
licence type for our prototype
• Managed Simple Windows Directory
Service (AWS)
• Archive data to S3 storage (AWS)
• EC2 Virtual Machines (AWS) running FME
(Safe), ArcGIS Desktop, ArcGIS Pro, QGIS

5. The
Peak
of
Data
Integration
20
23
Benefits
✔ Minimises latency issues between data and
storage
✔ Reduce reliance on physical hardware
✔ Consistent software versioning for project staff
✔ Expands recruitment to outside of ACT
✔ Rapidly onboard spare capacity from external
collaborators
✔ Scalable to meet the needs of the project
Virtual Desktop
Environment

6. The
Peak
of
Data
Integration
20
23
Architecture

7. The
Peak
of
Data
Integration
20
23
Challenges

8. The
Peak
of
Data
Integration
20
23
Challenges
Software licencing
•FME for data amalgamation
requires ArcGIS integration for Geodatabase work
•ArcGIS Pro required for future generalisation work
•Need to use a Licence Server
Cloud engineering
•Using the right type of file storage infrastructure to
balance cost and functionality
•Directory Service needed to govern access to the
system, adding complexity to environment
administration
Security
•IT security requirements add an extra layer of
complexity and reporting
Staffing
•Staffing has been unstable throughout the life of the
project

9. The
Peak
of
Data
Integration
20
23
Conclusion

10. Outcomes
• Directory Service governs access to both FSx and the
EC2 virtual machines. This limits the number of people
that are given access to the AWS console.
• Architecture reviewed by GA's AWS Solutions Architect
and Data Architect (circa early 2021)
• Adhere to government security standards
• Scalable services across the architecture
• Others want to replicate

11. The
Peak
of
Data
Integration
20
23
Conclusion
● The Virtual Environment is delivering what it was
expected to and is essential to the success of that
project.
● Cautious of scope creep.
● Managing internal relationships is key.
● Cattle, Pets and Endangered Species.
● Sitting in the shade, not hiding in the shadows.

12. The
Peak
of
Data
Integration
20
23
From a small idea.
A great many tasks have been
achieved.

13. ThankYou!
brett.madsen@ga.gov.au