Marcelo Zambrana

Cloud Solution Architect, Microsoft

Marcelo Zambrana is a cloud solution architect at Microsoft focused on infrastructure automation and application development. He has been helping federal, state, and private industry customers for multiple years, including banking and healthcare. Marcelo specializes in enterprise hybrid architecture, cloud migration, cloud service models (PaaS, IaaS, and SaaS), automation, infrastructure and compliance as a code, and configuration management. In short: big DevOps fun with a little bit of an OCD problem on the details.

Past sessions

Summit 2020 Automating Federal Aviation Administration’s (FAA) System Wide Information Management (SWIM) Data Ingestion and Analysis

June 23, 2020 05:00 PM PT

The System Wide Information Management (SWIM) Program is a National Airspace System (NAS)-wide information system that supports Next Generation Air Transportation System (NextGen) goals. SWIM facilitates the data-sharing requirements for NextGen, providing the digital data-sharing backbone of NextGen. The SWIM Cloud Distribution Service (SCDS) is a Federal Aviation Administration (FAA) cloud-based service that provides publicly available FAA SWIM content to FAA approved consumers via Solace JMS messaging. In this session we are going to show case the work we did at USDOT-BTS on Automating the required Infrastructure, Configuration, Ingestion and Analysis of the following public SWIM Data Sets:

  • SWIM Terminal Data Distribution System (STDDS)
  • Traffic Flow Management (TFMS)
  • Time Based Flow Management (TBFM)

SWIM provides a lot of information which with proper validation and analysis you can discover interesting insights like:

  • Number of flights
  • Number of delayed flights
  • Number of passengers affected by those delays

It could also be extended to analyze and predict multiple scenarios related to flights, airport and passenger behavior. Our initial solution leverages Azure Databricks, Apache Kafka and Spark-XML among others, but it is a flexible environment that could be extended to analyze more SWIM or similar streamed data sources, and since we are using Infrastructure as a code and Configuration Managements tools, it could be deployed and/or extended anywhere.