BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.adass.org//adass2026//speaker//RT93KR
BEGIN:VTIMEZONE
TZID:AWST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=20051231T160000Z
TZNAME:AWST
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20070325T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:AWST
TZOFFSETFROM:+0900
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20071028T030000
RRULE:FREQ=YEARLY;BYDAY=4SU;BYMONTH=10;UNTIL=20081025T190000Z
TZNAME:AWDT
TZOFFSETFROM:+0800
TZOFFSETTO:+0900
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-adass2026-MUDUE9@pretalx.adass.org
DTSTART;TZID=AWST:20261102T163000
DTEND;TZID=AWST:20261102T164500
DESCRIPTION:The ESA Near-Earth Object Coordination Centre (NEOCC) is respon
 sible for the monitoring of Near-Earth Objects and the assessment of poten
 tial impact hazards. These activities rely on Aegis [1]\, a software syste
 m for asteroid orbit determination\, ephemerides generation\, uncertainty 
 propagation\, close-approach analysis\, and impact monitoring. The results
  and computational capabilities of Aegis are made available to the communi
 ty through the NEOCC web portal [2] and dedicated APIs [3]. As operational
  demands evolved\, Aegis transitioned from a standalone scientific applica
 tion to a service deployed within ESA's cloud infrastructure.\n\nThis cont
 ribution presents the architectural evolution of Aegis and the engineering
  decisions that enabled its migration to a distributed operational environ
 ment while preserving a mature and validated scientific code base. The ori
 ginal system was conceived as a largely monolithic application running on 
 a single machine. Rather than pursuing a complete redesign\, the developme
 nt strategy focused on incremental modernisation\, gradually introducing c
 ontainerisation\, automated testing and deployment workflows\, service-ori
 ented interfaces\, and distributed execution capabilities.\n\nToday\, Aegi
 s operates as a collection of Docker-based services deployed on ESA Cloud 
 using Docker Swarm orchestration. Scientific processing remains largely pe
 rformed by established Fortran components\, while Python services coordina
 te workflows\, expose REST interfaces\, and exchange information through R
 edis-based messaging queues. Although parts of the system still rely on sh
 ared file-system access\, reflecting historical design choices\, this appr
 oach has proven adequate for current operational requirements and data vol
 umes while allowing progressive migration towards more centralised data ma
 nagement solutions. The software has also been deployed on ESA High-Perfor
 mance Computing (HPC) infrastructures\, requiring targeted adaptations but
  without fundamental changes to its scientific components.\n\nModern softw
 are engineering often favours highly scalable cloud-native solutions. Howe
 ver\, scientific operational systems frequently evolve under different con
 straints\, including long-lived code bases\, limited development resources
 \, strict reliability requirements\, and moderate data volumes. The Aegis 
 experience shows that significant gains in maintainability\, deployment fl
 exibility\, and operational robustness can be achieved through incremental
  modernisation\, without the need for unnecessarily complex architectures.
 \n\n[1] https://doi.org/10.1007/s10569-024-10225-z\n[2] https://neo.ssa.es
 a.int/\n[3] https://neo.ssa.esa.int/computer-access
DTSTAMP:20261001T101725Z
LOCATION:Banquet Hall
SUMMARY:Engineering for Requirements: The Evolution of the Aegis Asteroid I
 mpact Monitoring System at ESA - Francesco Gianotto
URL:https://pretalx.adass.org/adass2026/talk/MUDUE9/
END:VEVENT
END:VCALENDAR