Technical Document of Acdm Portal Nia 2

ACV PMO – IT Team
TECHNICAL DESCRIPTION OF ACDM PORTAL

PHASE 1
Version 5.2: 12/12/2023
Editor: Phan Truong Khoi – IT Specialist

Le Hoang Anh Thong – IT Specialist
Nguyen Phuong Duy – IT Specialist
Reviewer: Huynh Bao Quoc – IT Manager
ACDM Portal Technical Description 1

ACV PMO – IT Team
INDEX
1. SYSTEM ARCHITECTURE OF ACDM PORTAL ON PRIVATE CLOUD-
BASED................................................................................................................................ 11
1.1 General Introduction .............................................................................................. 11
1.2 System Architecture ............................................................................................... 11
1.2.1 Solution Model of ACV Private Cloud ................................................................... 11
1.2.3. Data backup for ACV Private Cloud/ACDM PORTAL ............................................... 12
1.2.2 Security System for NIA Private Cloud .................................................................. 13
1.3 Configuration of hardware infrastructure and security services of NIA Private
Cloud/ ACDM PORTAL: ...................................................................................... 14
1.4 Organization and classification of network security zones upon demand of system
operations to maintain information security. ......................................................... 15
1.5 Configuration of NIA-ACDM PORTAL servers ................................................... 17
1.6 System requirement:............................................................................................... 17
2. CONNECTIONS TO ACDM PORTAL CLOUD AT NIA ........................................... 17
3. TECHNOLOGY SOLUTION.......................................................................................... 19
3.1 Overview ................................................................................................................ 19
3.2 NIA ......................................................................................................................... 20
3.2.1 Implementation of ACDM Phase 1 at NIA ............................................................. 21
3.2.2 NIA GATEWAY: .................................................................................................... 22
3.2.3 NIA SMIS:............................................................................................................... 23
3.2.4 VMS(VIAGS) NIA, FlightUpdate(HGS), FlightView(VJ): ................................. 25
3.3 NIA ......................................................................................................................... 26
3.3.1 NIA SMIS ................................................................................................................ 26
3.4 TestZone ................................................................................................................. 27
3.4.1 NIA .......................................................................................................................... 27
3.5 API description to update flight data ..................................................................... 29
3.5.1 Token ....................................................................................................................... 29
3.5.2 Header ...................................................................................................................... 30
3.5.3 Request Body ........................................................................................................... 30
3.5.4 Example ................................................................................................................... 31
3.6 List of Data fields in ACDM PORTAL: ................................................................ 32
3.6.1 List of Data fields .................................................................................................... 32
4. FDE FIELDS FOR PHASE 1........................................................................................... 38
4.1 FDE Detail information.......................................................................................... 38
4.1.1 EXIT (Estimated Taxi-In Time) .............................................................................. 38
4.1.2 EXOT (Estimated Taxi-Out Time) .......................................................................... 38
4.1.3 APRK (Arrival Parking Location) ........................................................................... 38
ACV PMO – IT Team
4.1.4 DPRK (Departure Parking Stand) ........................................................................... 39

4.1.5 FLTST (Flight Status) ............................................................................................. 39
4.1.6 EIBT (Estimated In-Block Time) ............................................................................ 39
4.1.7 LRWY (Landing Runway) ...................................................................................... 39
4.1.8 ELDT (Estimated Landing Time)............................................................................ 39
4.1.9 ALDT (Actual Landing Time) ................................................................................ 39
4.1.10 TRWY (Take off Runway) ...................................................................................... 39
4.1.11 TSAT (Target Start-up Approval Time) .................................................................. 39
4.1.12 TTOT (Target Take-Off Time)................................................................................ 39
4.1.13 ATOT (Actual Take-Off Time) ............................................................................... 39
4.1.14 CTOT (Calculated Take-Off Time) ......................................................................... 40
4.1.15 ACREG (Aircraft Registration) ............................................................................... 40
4.1.16 IATAACSUBTYPE (IATA Aircraft Sub-Type) ..................................................... 40
4.1.17 IATACSGN (IATA Callsign) ................................................................................. 40
4.1.18 ICAOCSGN (ICAO Callsign) ................................................................................. 40
4.1.19 IATAADEP (Aerodrome of Departure IATA) ....................................................... 40
4.1.20 ICAOADEP (Aerodrome of Departure ICAO) ....................................................... 40
4.1.21 SIBT (Scheduled In-Block Time)............................................................................ 40
4.1.22 AIBT (Actual In-Block Time) ................................................................................. 40
4.1.23 MGHA (Main Ground Handling Agent) ................................................................. 40
4.1.24 ACGT (Actual Commence of Ground handling Time) ........................................... 41
4.1.25 AEGT (Actual End of Ground handling Time) ....................................................... 41
4.1.26 ASBT (Actual Start Boarding Time) ....................................................................... 41
4.1.27 ETTT (Estimated Turn-round Time) ....................................................................... 41
4.1.28 SOBT (Scheduled Off-Block Time) ........................................................................ 41
4.1.29 EOBT (Estimated Off-Block Time) ........................................................................ 41
4.1.30 TOBT (Target Off-Block Time) .............................................................................. 41
4.1.31 AOBT (Actual Off-Block Time) ............................................................................. 41
4.1.32 IATAADES (Aerodrome of Destination IATA) ..................................................... 42
4.1.33 ICAOADES (Aerodrome of Destination ICAO)..................................................... 42
4.1.34 ARDT (Actual Ready Time) ................................................................................... 42
4.1.35 Overall diagram of FDE Calculation ....................................................................... 42
4.2 Connection diagram and input method: ................................................................. 43
4.2.1 The order of priority for data sources is updated by the user .................................. 43
4.2.2 Overall diagram ....................................................................................................... 44
4.2.3 Diagram of fields directly inputted to ACDM Portal .............................................. 46
4.2.4 Diagram of fields transmitted via API from VIAGS ............................................... 46
4.2.5 Diagram of fields transmitted from Ground handlers to ACDM Portal’s Open API
................................................................................................................................. 46
4.2.6 Diagram of fields transmitted via API from NIA Gateway..................................... 47
5. TWO-WAY DATA SYNCHRONIZATION .................................................................. 47

ACV PMO – IT Team
5.1 Two-way data synchronization at NIA .................................................................. 48

6. MAIN FEATURES OF ACDM PORTAL: .................................................................... 49
6.1 Alert........................................................................................................................ 49
6.2 Features of FLTST field ......................................................................................... 51
6.2.1 List of FLTST .......................................................................................................... 51
1.1.1 Overall Diagram of FLTST .................................................................................... 53
7. OVERVIEW ACV ACDM WEBSITE............................................................................ 54
7.1 ACDM Flight ......................................................................................................... 54
7.1.1 Overview ACDM Flight page ................................................................................. 54
7.1.2 Header of ACDM Flight page ................................................................................. 54
7.1.3 Toolbar ACDM Flight Page .................................................................................... 55
7.1.4 Overview Flight Information Display ..................................................................... 63
7.1.5 Edit Flight Information: ........................................................................................... 68
7.1.6 Instructions for entering time information on the ACDM portal system ................ 70
7.1.7 Overview warning function ..................................................................................... 72
7.1.8 Overview Flight Status Information ........................................................................ 77
7.2 ACDM Flight Detail Page ...................................................................................... 78
7.2.1 Overall introduction ................................................................................................. 78
7.2.2 Basic information fields of ACDM Flight Detail .................................................... 80
7.2.3 Time information fields of ACDM Flight Detail .................................................... 81
7.2.4 Formula 16 Milestones ............................................................................................ 82
7.3 ACDM Exit Exot Table page ................................................................................. 83
7.3.2 Introduction of functionalities ................................................................................. 84
7.4 Runway Config page .............................................................................................. 87
7.4.2 Adding rule function ................................................................................................ 87
7.4.3 Introduction of edit Rule function ........................................................................... 88
7.5 ACDM Link Flight page ........................................................................................ 89
7.5.2 Introduction of flight pairing function ..................................................................... 90
7.6 TSAT Windows ..................................................................................................... 91
7.6.2 Introduction of TSAT Windows display ................................................................ 91
7.6.3 Introduction of TSAT Windows information fields ................................................ 92
7.6.4 Functionalities of TSAT Windows .......................................................................... 93
7.6.5 TSAT + X ................................................................................................................ 94
7.7 TOBT Windows ..................................................................................................... 95
7.7.1 Overview ................................................................................................................. 95
7.7.2 PIN/UNPIN, Searching ........................................................................................... 97
ACV PMO – IT Team
7.7.3 Alert ......................................................................................................................... 98

7.8 System Status page ............................................................................................... 100
7.8.1 Overall introduction ............................................................................................... 100
7.9 Alert Configuration Page ..................................................................................... 101
7.9.1 Overall introduction of Alert Config ..................................................................... 101
7.9.2 Alert Config Functionalities .................................................................................. 102
7.10 TSAT Windows for Pilot ..................................................................................... 103
7.10.1 Overview ............................................................................................................... 103
7.10.2 The TSAT Windows for Pilot feature ................................................................... 104
7.11 TwoWay Monitor ................................................................................................. 108
7.11.1 Overview ............................................................................................................... 108
7.12 Announcement ..................................................................................................... 108
7.12.1 Overview ............................................................................................................... 108
7.12.2 Config Announcement ........................................................................................... 109
7.13 AutoLink Flights .................................................................................................. 110
7.13.1 OverView............................................................................................................... 110
7.13.2 Functions ............................................................................................................... 111
7.14 Report KPI ........................................................................................................... 112
7.14.1 Overview ............................................................................................................... 112
7.15 FDE Checking ...................................................................................................... 113
7.15.1 Overview ............................................................................................................... 113
7.15.2 FDE Checking Instructions ................................................................................... 114

ACV PMO – IT Team
FIGURES
Image 1. NIA Private Cloud overall solution model ............................................................ 11
Image 2. Data backup model NIA Private Cloud ................................................................. 13
Image 3. Security model for ACDM System........................................................................ 14
Image 4. Connections to ACDM Portal at NIA .................................................................... 18
Image 5. Overview of data flow from SMIS synchronized to ACDM PORTAL ................ 21
Image 6. NIA – VATM Topology of ACDM Phase 1 ......................................................... 22
Image 7. Dataflow description from AMAN/DMAN to SMIS ............................................ 23
Image 8. Dataflow diagram of ELDT/TSAT/TTOT/TRWY/LRWY pushing ..................... 24
Image 9. Dataflow of decoding AMHS and pushing to SMIS database .............................. 25
Image 10. Data flow from VMS (VIAGS), and FlightUpdate (HGS) is synchronized to
ACDM PORTAL at NIA ....................................................................................... 26
Image 11. Overview of data flow from SMIS synchronized to ACDM PORTAL ................ 26
Image 12. Data Mapping from VJ to ACDM TestZone ......................................................... 27
Image 13. Data flow from HGS Database is synchronized to NIA TestZone Database ........ 28
Image 14. Data flow from NIA Database is synchronized to NIA TestZone Database ......... 28
Image 15. Data flow from VMS (VIAGS) TestZone is synchronized to NIA TestZone
Database. ................................................................................................................ 29
Image 16. Request Body of API ............................................................................................. 30
Image 17. Example of data transmission by API ................................................................... 32
Image 18. Overall of FDE calculations .................................................................................. 43
Image 19. Diagram of fields directly inputted to ACDM Portal by NIA’s stakeholders ....... 46
Image 20. Diagram of fields transmitted via API from VIAGS ............................................. 46
Image 21. Diagram of fields transmitted via API from HGS ................................................. 47
Image 22. Diagram of fields transmitted via API from SMIS at NIA .................................... 47
Image 23. Diagram of fields transmitted via API from NIA Gateway ................................... 47
Image 24. Two-way data synchronization at NIA .................................................................. 48
Image 25. Notification panel for alert..................................................................................... 49
Image 26. Diagram of FLTST ................................................................................................ 53
Image 27. ACDM Flight page ................................................................................................ 54
Image 28. Header of ACDM Flight page ............................................................................... 54
Image 29. Toolbar of ACDM Flight page .............................................................................. 55
Image 30. Dropdown-list on toolbar ....................................................................................... 55
Image 31. Configuration to customize display function ......................................................... 56
Image 32. Customizable configuration to display information columns ................................ 57
Image 33. Customizable Notice interface ............................................................................... 58
Image 34. Customizable configuration for searching flight information ............................... 58
Image 35. Information display to filter by date ...................................................................... 59

ACV PMO – IT Team
Image 36. Drop box to select date .......................................................................................... 60

Image 37. Information display to filter by time duration ....................................................... 60
Image 38. Drop box to select date of time filter ..................................................................... 61
Image 39. Drop box to select specific time ............................................................................ 61
Image 40. Flight information display by time filter ............................................................... 62
Image 41. Example of searching information by flight number ............................................. 62
Image 42. Example of searching for Flightno VN246 ........................................................... 63
Image 43. Example of searching by ICAO ID for HVN186 .................................................. 63
Image 44. Default display of flight information ..................................................................... 64
Image 45. Flight information display by VN time zone and ICAO standard ......................... 64
Image 46. Flight information display by UTC time and ICAO standard ............................... 65
Image 47. Display of history information fields. .................................................................... 66
Image 48. Selection display to show history information fields ............................................ 66
Image 49. ACDM Portal display interface of attention case. ................................................. 68
Image 50. “Reset Grid View” interface .................................................................................. 68
Image 51. Adjust other non-time milestones .......................................................................... 68
Image 52. Adjust LRWY information .................................................................................... 69
Image 53. Dialog box display to adjust time milestones ........................................................ 69
Image 54. Dialog box display to adjust time milestones after click “Now”........................... 70
Image 55. Dialog box display after click “+5 min” ................................................................ 70
Image 56. Cặp chuyến đi-đến có ngày bay khác nhau ........................................................... 71
Image 57. Notification when information has large deviation from SIBT/SOBT interface. . 72
Image 58. Alert display after adjust flight information .......................................................... 73
Image 59. Alert display of incorrect time information ........................................................... 73
Image 60. Illustration when user enter information of case 1 ................................................ 74
Image 61. Notice display to confirm time information of case 1 ........................................... 74
Image 68. Notice of incorrect Parking bay information ......................................................... 77
Image 69. ACDM Flight Detail default display for roud trip flights...................................... 78
Image 70. ACDM Flight Detail default display for departure flight ...................................... 79
Image 71. ACDM Flight Detail default display for arrival flight........................................... 79
Image 72. ACDM Flight Detail display to comply with ICAO for roud trip flight ............... 80
Image 73. Fundamental information of IATA code flight ..................................................... 80
Image 74. Fundamental information of ICAO code flights .................................................... 81
ACV PMO – IT Team
Image 75. ACDM EXIT EXOT TABLE interface ................................................................. 84

Image 76. Add Parking Bay dialog box.................................................................................. 85
Image 77. List of RunWay...................................................................................................... 85
Image 78. Edit dialog display ................................................................................................. 85
Image 79. Delete Parking Bay notification............................................................................. 86
Image 80. Searching display by Parking Bay. ........................................................................ 87
Image 81. Configuration display ............................................................................................ 87
Image 82. Dialog box to add Config ...................................................................................... 88
Image 83. Dialog box of Edit function ................................................................................... 89
Image 84. ACDM Flight Link page ........................................................................................ 90
Image 85. Select flights to pair ............................................................................................... 91
Image 86. Select flights to pair ............................................................................................... 91
Image 87. Main display of TSAT Windows .......................................................................... 92
Image 88. Searching Flight to Pin in TSAT Windows +/-5 ................................................... 93
Image 89. Dropdown list of flights ......................................................................................... 94
Image 90. BAV240 is remakred. ............................................................................................ 94
Image 91. TSAT + X .............................................................................................................. 95
Image 92. TOBT Windows +/-30 minutes interface .............................................................. 96
Image 93. TOBT Windows Other FLTs Within +/-90” interface ......................................... 96
Image 94. History of flight in TOBT Windows.. ................................................................... 97
Image 95. Searching flight in TOBT Windows +/-30 ............................................................ 97
Image 96. DropDown List Flights .......................................................................................... 98
Image 97. HVN245 is PINNED. ............................................................................................ 98
Image 98. Alert TOBT is inputted by GH’s system. .............................................................. 99
Image 99. Alert TOBT is inputted manual by user ................................................................ 99
Image 100. Alert New TOBT is updated from 0 minutes to -5 minutes from the
current time ............................................................................................................ 99
Image 101. Alert New TOBT is updated from 5 minutes to 10 minutes from the
current time ............................................................................................................ 99
Image 102. Alert when flight has ARDT time ....................................................................... 100
Image 103. System Status interface in Nội Bài ...................................................................... 101
Image 104. Alert Config interface .......................................................................................... 102
Image 105. Interface of configuration “Alert when EOBT and SOBTdiscrepancy
+/- 0 mins” ........................................................................................................... 102
Image 106. Config Level column in “warning when EOBT is different with SOBT time” .. 103
Image 107. After config Level column in “warning when EOBT is different with
SOBT time” ......................................................................................................... 103
Image 108. NIA TSAT Windows for Pilot interface .............................................................. 104
Image 109. Converting UTC time to Local time toggle button interface ............................... 104
ACV PMO – IT Team
Image 110. Flights drop-down list interface ........................................................................... 105

Image 111. Countdown Timer turn organe............................................................................. 106
Image 112. Countdown Timer turn green............................................................................... 106
Image 113. Countdown Timer turn red .................................................................................. 107
Image 114. TSAT Windows for Pilot interface after selected flight ...................................... 107
Image 115. Update TSAT to 1435 interface ........................................................................... 108
Image 116. TwoWay Monitor interface ................................................................................. 108
Image 117. Main Page Announcement ................................................................................... 109
Image 118. Flight Manage Announcement ............................................................................ 109
Image 119. System Announcement button ............................................................................. 109
Image 120. Announcement Dialog ......................................................................................... 110
Image 121. Auto Link Flight interface ................................................................................... 111
Image 122. Add flight. ............................................................................................................ 112
Image 123. Edit Flight. ........................................................................................................... 112
Image 124. Delete flight. ........................................................................................................ 112
Image 125. Report KPI page interface ................................................................................... 113
Image 126. Select Range of time interface. ............................................................................ 113
Image 127. FDE Checking interface. ..................................................................................... 114
Image 128. FDE Checking Instructions.................................................................................. 114
Image 129. FDE Checking Result.. ........................................................................................ 115

ACV PMO – IT Team
TABLES
Table 1. Configuration detail of hardware infrastructure .................................................... 15
Table 2. Configuration of Servers for NIA-ACDM ............................................................ 17
Table 3. Token Information ................................................................................................. 29
Table 4. Header information of API .................................................................................... 30
Table 5. Request Body of API ............................................................................................. 31
Table 6. Description of Information fields for API ............................................................. 38
Table 7. Statistical table for alerts ....................................................................................... 51
Table 8. Statistical table for the established states of FLTST ............................................. 52
Table 9. DropDown List Flights .......................................................................................... 98

ACV PMO – IT Team
1. System Architecture of ACDM PORTAL on Private Cloud-Based

1.1 General Introduction
The ACV Private Cloud infrastructure is designed to meet the growth of ACV over next 5
years, including the rapid growth situation (horizontal expansion -Scale out) with a huge number
of resources.
ACV Private Cloud is in a Rated 3 - TIA 942 standard data center, for diverse demands of
data computing, storage, security, data backup.
1.2 System Architecture
1.2.1 Solution Model of ACV Private Cloud
ACV Private Cloud infrastructure with individual resources, storage and connection lines,
using Software Define Data Center (SDDC) architecture and VMware's HCI solution.
ACV Private Cloud comprehensively meets ACV deployment demand of large and
individual infrastructure resources for specific applications such as ERP, E-commerce..., which
has strictly requirements of information security standards, include ISO 27001, 27017, PCI
DSS.
Image 1. NIA Private Cloud overall solution model

ACV PMO – IT Team
1.2.2. IP Planning for ACDM HCI

Server , NAS, SAN
STT Devices Hostname IP Purpose VLAN Domain
1 ESXi 1 Esxi1-ACDM 172.16.88.101/24 Manager 141 NIA.local
172.16.88.111/24 ILO 141
2 ESXi 2 Esxi2-ACDM 172.16.88.102/24 Manager 141 NIA.local
172.16.88.112/24 ILO 141
3 Mgmt Server Mgmt-ACDM 172.16.88.103/24 Manager 141 NIA.local
10.10.10.2/30 iSCSi
172.16.88.113/24 ILO 141 NIA.local
4 vCenter vCenterACDM 172.16.88.100/24 141 NIA.local
5 NAS NAS-ACDM 172.16.88.120/24 NAS mgmt 141 NIA.local
10.10.10.1/30 iSCSi
6 SAN SAN-ACDM 172.16.88.121/24 SAN mgmt 141 NIA.local
172.16.88.122/24
Virtual Server
STT VS Hostname IP Status VLAN Domain
1 Database Server SQL-ACDM 172.16.156.11/24 156 NIA.local
2 DC Server PDC-ACDM 172.16.156.10/24 156 NIA.local
3 Web Server WEB-ACDM 172.16.157.11/24 157 NIA.local
4 AMAN/DMAN ADMAN-ACDM 172.16.156.22/24 156 NIA.local
5 AMHS AMHS-ACDM 172.16.156.12/24 156 NIA.local
Network
1 Manager Manager 172.16.88.0/24 Mgmt 141
10.10.10.0/30 iSCSi
2 Server Farm Farm 172.16.156.0/24 156
3 DMZ DMZ 172.16.157.0/24 157
4 C9300X-01 C9300-ACDM 172.16.6.140/13 102
5 C9300X-02
1.2.3. Data backup for ACV Private Cloud/ACDM PORTAL
(FR: [GEN]-[REC]-[010] to [GEN]-[REC]-[210])
• Veeam solution
• Scheduling on portal
• Data Compression
• Record multiple versions
• Fully backup, saving after changes

ACV PMO – IT Team
• Backup speed does not depend on bandwidth of virtualization

• Centralized administration
• Recovery: overwrite on target VM or create new VM
• Able to recover entire or specific data in VM
Image 2. Data backup model NIA Private Cloud

1.2.2 Security System for NIA Private Cloud
Virtual servers will be separated by Firewall Checkpoint 5600-HA operating at layer 7
implementing Virtual System Extension (VSX) n along with security policies for each service
to ensure security and data safety, minimizing the possibility of being exploited. Exploitation,
attack, unauthorized intrusion with real-time thread prevention, web security, application layer
security, etc. The option of using the existing Checkpoint 5600 firewall system to act as an
Internal Firewall for the ACDM Portal System helps take advantage of the equipment
infrastructure that has been invested, minimizing costs and human resources to operate the
system. Firewall Checkpoint acts as an Internal Firewall connected to External Firewall
FortiGate (supporting Fortinet SD-WAN) to connect to ACV Private Cloud and increase
system performance and security.

ACV PMO – IT Team
Image 3. Security model for ACDM System

1.3 Configuration of hardware infrastructure and security services of NIA Private
Cloud/ ACDM PORTAL:
(FR: [GEN]-[SYS]-[020], [GEN]-[SYS]-[040], [GEN]-[SYS]-[050], [GEN]-[SYS]-[080],
[GEN]-[SEC]-[010] to [GEN]-[SEC]-[080])
Configuration of HCI for NIA Private Cloud/ACDM

PORTAL
Dedicated Private Cloud – DPC
Virtualization technology VMware
CPU 48

ACV PMO – IT Team
RAM (GB) 256
Storage HDD SAS after RAID (GB) 4000
Domestic Bandwidth (Mbps) 250
International Bandwidth (Mbps) 5
Flow data Unlimited
Internal LAN connection 10Gbps
IPs 3
Backup License 10
Backup Storage (GB) 40000
The information security service uses new generation multi-layer firewall, redundancy
configuration to separate independent zones.
External layer: 2 NGFW devices, internal layer: 2 NGFW devices.
Protection services include anti-DDoS L4/L7, WAF for website
Connection services
The connection service is able to provide 10 gbps among virtual servers cluster and
also outside of the cluster.
Table 1. Configuration detail of hardware infrastructure

1.4 Organization and classification of network security zones upon demand of system
operations to maintain information security.
(FR: [AOD]-[DAT]-[120], [SER]-[COM]-[060], [SER]-[COM]-[070], [SER]-[WAR]-
[010], [SER]-[WAR]-[020])

ACV PMO – IT Team

ACV PMO – IT Team
1.5 Configuration of NIA-ACDM PORTAL servers

No Server Configuration Functionalities
name
1 DB01 24 CPUs, 64 Gb RAM, 02 TB HDD SAS Database Storage, include:
OS: Windows Server 2022 Standard Database of NB
Database of Test Zone
2 DB02 12 CPUs, 32 Gb RAM, 01 TB HDD SAS (backup for DB01)
OS: Windows Server 2022 Standard
3 API 8 CPUs, 16 Gb Ram, 01 TB HDD SAS Public OPEN API, interface
with other systems of
Stakeholders
4 ACV- 8 CPUs, 16 Gb Ram, 01 TB HDD SAS IIS host Web Application
Web ACDM PORTAL
Table 2. Configuration of Servers for NIA-ACDM

1.6 System requirement:
Browser: Chrome version 90.0.4430 or above.
2. Connections to ACDM PORTAL Cloud at NIA

ACV PMO – IT Team
Image 4. Connections to ACDM Portal at NIA

ACV PMO – IT Team
Servers function:
• Web server
Web server gets necessary information, then display to website UI for end users to
operate.
• API Server
API server has these functions:
- Connect to smtp.office365.com to identify users.
- Connect and exchange data between Stakeholders.
- Connect to database server to update and get latest data.
• Database server
- Contain databases.
- Connect and exchange data with API server to update the latest data.
• AMQP
- Synchronize two-way data between Stakeholders (HGS, VJGS, VIAGS and NIA
Gateway) and ACV.
IT ACV use VPN to connect to MGT-App to develop and fix bug ACDM Website.
End User can access via the website acdm.noibaiairport.vn.
3. Technology solution
(FR: [OPS]-[PRO]-[010], [OPS]-[PRO]-[090], [GEN]-[SYS]-[070], [GEN]-[SYS]-[190],
[GEN]-[DEG]-[010])
3.1 Overview
(FR: [OPS]-[PRO]-[050] , [OPS]-[PRO]-[070], [AOD]-[DAT]-[050] to [AOD]-[DAT]-
[070])
- The ACDM PORTAL system uses the latest technologies in developing real-time update
systems such as SQL Dependency, SignalR allowing optimization of Resources,
Performance, and Response Time.
- The database system uses MS SQL Server running on Viettel's Private Cloud platform is
partitioned to store data separately to ensure security of ACV critical data such as: flight
information, Passenger volume…

ACV PMO – IT Team
- By using computers or mobile devices with internet connection, end users can access and use
the system on web browsers, which developed on Microsoft's latest Blazor .NET Core 7.0
platform.
- ACDM PORTAL solution will be synchronized in real time with SMIS, VMS, FlightView,
FlightUpdate systems according to existing data fields such as: FlightNo, Codeshare, Reg,
Type, Route, Status... The FDE information field for Phase 1 will also be developed and
synchronized to the ACDM PORTAL (details of each field are mentioned in section 3).
• Using micro services to monitor data changes (real-time update in flight information
retrieved from SMIS, API of Stakeholders, or information input directly on the Portal…).
The ACDM PORTAL system will update to other users in real time through Microsoft's
latest technology, SignalR Core, which is capable to support a huge number of users
concurrently accessing. Based on 16Gb Ram in the Server, it allows more than 50,000
users can concurrently access in real time (https://docs.microsoft.com/en-
us/aspnet/core/blazor/host-and- deploy/server?view=aspnetcore-6.0)
• Delay of ACDM PORTAL mostly due to the network speed of the devices connected to
the system. The delay can be happened when stakeholders update and send information
to the server, then it is processed and sent back to end user within 1500 to 1800ms.
Network delay will be included to the displayed time.
• Realtime feature of flight is only available in 3 days (current day, the next current day,
the current day before) to reduce workload of server
- In terms of operation procedures, end users still use SMIS, VMS, FlightUpdate to input data
and manage seasonal flight, daily flight schedules.
3.2 NIA
The below diagram described data synchronization between SMIS database managed by
NIA and ACDM Portal.

ACV PMO – IT Team
Image 5. Overview of data flow from SMIS synchronized to ACDM PORTAL

• At NIA airport, a computer is installed monitoring tool that uses replicate SQL technology
to synchronize SMIS Database
• Change monitoring tool for SMIS is also programmed and developed to run as a Service
deployed on this Server, which is responsible to monitor and update data in real time via API of
ACV's Web server on Cloud, then data will be updated to Database Server of ACDM.
• Another version of the Change Monitoring tool of ACDM is also programmed to be
deployed on Private Cloud infrastructure to monitor this ACDM Database, when there is any
change on the ACDM Database, based on SQL Dependency technology, the program will
recognize, and notify immediately to all clients who are using ACDM PORTAL through
SignalR technology.
• ACDM PORTAL’s data will be compared with Database of stakeholders to measure
changes and update to ACDM PORTAL in case the synchronous machine fails and the
synchronization program must be re-run.
• The data is monitored internally in Ground Handler’s systems to reduce delay of
connection to the ACDM PORTAL, only updated information fields are provided to the ACDM
PORTAL to reduce system resource and network bandwidth.
3.2.1 Implementation of ACDM Phase 1 at NIA

ACV PMO – IT Team
Image 6. NIA – VATM Topology of ACDM Phase 1

The implementation includes the below actions:
• NIA-NORATS Gateway collects 05 FDEs (ELDT, TSAT, TTOT, LRWY, TRWY) from
logfile of AMAN/DMAN system, and then automatically push on SMIS system.
• 03 FDEs (ALDT, ATOT, EOBT) are decoded from AMHS, 01 FDE (CTOT) is going to
be decoded from AMHS in near future.
• Synchronize flight information from SMIS to ACDM Portal.
3.2.2 NIA GATEWAY:
(FR: [ASP]-[AD]-[010] to [ASP]-[AD]-[060])

ACV PMO – IT Team
Image 7. Dataflow description from AMAN/DMAN to SMIS

NORATS installed a FTP Server for sending automatically text files containing flight data
elements (ELDT, TSAT, DRWY, ARWY, TTOT).
Similarly, NIA also implemented a FTP Client to receive that files, then push automatically
flight data elements to SMIS database.
Because AMAN/DMAN is an isolated system that could only share its log files, 02 gateways
VATM1 and VATM2 were implemented to collect the log files. VATM1 sends log files to
VATM2 by serial protocol, then VATM2 converts log files to text files and pushes through FTP
server. At NIA side, there is installed a FTP client that receives text files, then decodes all files
and pushes useful data to SMIS database.
Gateway NIA receives ELDT, TSAT, TTOT, LRWY, TRWY from log file of NORATS
AMAN/DMAN system by server GATEWAY VATM. GateWay VATM 1 will send file log
which has ELDT, TSAT, EXOT through Serial port. And GATEWAY VATM 2 – another
server – runs software that receives log file from Serial port and transfers that log file to text
format, then send it to NIA through FTP Server. A computer from NIA – GATEWAY NIA –
will have to run FPT Client to receive text file which has ELDT, TSAT, TTOT, LRWY, TRWY
and auto update times to ACDM PORTAL by API.
3.2.3 NIA SMIS:
(FR: [OPS]-[PRO]-[030], [GEN]-[SYS]-[170])

ACV PMO – IT Team
Decoding text files from VATM2 gateway.

Tool will spot ELDT or TSAT, then automatically convert to local time. Moreover, flight ID
(Primary key in Flight table of SMIS database) and date of flight are get from the file. If flight
ID from text file is the same as one in SMIS database, tool will push the file’s data to Flight
table SMIS database. If not, tool will push to Flight Not Found table.
Image 8. Dataflow diagram of ELDT/TSAT/TTOT/TRWY/LRWY pushing

Decoding AMHS message.
AMHS message client is attached a software that decodes all AMHS messages. The AMHS
message list decoded by the software include: FPL, DEP, ARR, DELAY, CANCEL… Output
is flight data elements that is pushed to SMIS database:
- Dataflow:
+ Input source: AMHS messages
+ Ouput: flight data elements (Flight number, ATOT, ALDT, Aircraft registration number
…)
- Integration SMIS implementation

ACV PMO – IT Team
Image 9. Dataflow of decoding AMHS and pushing to SMIS database

AMHS client address at NIA is VVNBYDYX. After receiving messages, the software will
decode and take useful data (ALDT, ATOT, EOBT, ACREG, ACTYPE) to push to SMIS
database.
3.2.4 VMS(VIAGS) NIA, FlightUpdate(HGS), FlightView(VJ):
(FR: [OPS]-[PRO]-[030], [GEN]-[SYS]-[170])
- A similar system will be deployed to synchronize data from VMS (VIAGS), FlightView (VJ)
and FlightUpdate (HGS) to ACV Database ACDM. This implementation plan is applied in
order to minimize the impact on the operation of NIA, TIA and Ground Handler’s systems.

ACV PMO – IT Team
Image 10. Data flow from VMS (VIAGS), and FlightUpdate (HGS) is synchronized to ACDM
PORTAL at NIA
3.3 NIA
3.3.1 NIA SMIS
- Specification of data transmission model from SMIS at NIA to ACV's Database system and
display to end users according to following description:
Image 11. Overview of data flow from SMIS synchronized to ACDM PORTAL
ACV PMO – IT Team
• Change monitoring tool for SMIS is programmed and developed to run as a Service
deployed on NIA Gateway, which is responsible to monitor and update data in real time
via API of NIA's Web server on-Premises, then data will be updated to Database Server
of ACDM.
• Another version of the Change Monitoring tool of ACDM is also programmed to be
deployed on Private Cloud infrastructure to monitor this ACDM Database, when there is
any change on the ACDM Database, based on SQL Dependency technology, the
program will recognize, and notify immediately to all clients who are using ACDM
PORTAL through SignalR technology.
• ACDM PORTAL’s data will be compared with Database of stakeholders to measure
changes and update to ACDM PORTAL in case the synchronous machine fails and the
synchronization program must be re-run.
• The data is monitored internally in Ground Handler’s systems to reduce delay of
connection to the ACDM PORTAL, only updated information fields are provided to the
ACDM PORTAL to reduce system resource and network bandwidth.
3.4 TestZone
3.4.1 NIA
VJ
VJ creates a Test table and VJ will scan real data and transmit the data to TestZone Database
of ACDM Portal. The data transmitted from VJ is shown in the following table:
Image 12. Data Mapping from VJ to ACDM TestZone

HGS

ACV PMO – IT Team
Both HGS and NIA can create their own Test Database, and the data from this Database will
be transmitted to the NIA TestZone Database of ACDM Portal.
Image 13. Data flow from HGS Database is synchronized to NIA TestZone Database
NIA
Image 14. Data flow from NIA Database is synchronized to NIA TestZone Database
ACV PMO – IT Team
VIAGS
Similar with SMIS TestZone, described in following diagram
Image 15. Data flow from VMS (VIAGS) TestZone is synchronized to NIA TestZone Database.
3.5 API description to update flight data
(FR: [COE]-[GEN]-[010], [COE]-[GEN]-[020], [GEN]-[SYS]-[090], [GEN]-[SYS]-[100], [GEN]-[SYS]-
[200], [GEN]-[SYS]-[210], [GEN]-[SYS]-[220], [GEN]-[SYS]-[230], [GEN]-[SYS]-[240], [GEN]-[SYS]-
[250], [GEN]-[SYS]-[260], [GEN]-[SYS]-[280], [SER]-[COM]-[010] to [SER]-[COM]-[050])
URL: https://apiflight.vietnamairport.vn
3.5.1 Token
Base Token Remarks
Hà Nội (HAN) According to each stakeholder For departure/arrival flights of HAN
Test Zone (ACV) According to each stakeholder For testing purposes of Developers
Test Zone (NIA) According to each stakeholder For departure/arrival flights of NIA
Table 3. Token Information

Since the Databases are divided into separate ZONEs corresponding to the relevant airports,
the Tokens are used to determine where the flight data will be stored; then determine whether it
is departure or arrival flight. Flight such as SGN-HAN using HAN tokens will be considered as
ACV PMO – IT Team
arrival flights to store at HAN database, while using SGN tokens will be understood as departure
and data stored at SGN database. In terms of differences between flights, so the data will be
communicated in accordance with the definitions of the FDEs in Phase 1.
POST {URI}/UpdateListFlight
3.5.2 Header
Name Type Description
authorization String Token provide to server
Table 4. Header information of API

3.5.3 Request Body
[
{
"flightNo": "<string>",
"flightDate": "<date>",
"route": "<string>",
"FlightData":[
{
"fieldName": "<string>",
"fieldValue": "<string>"
}
]
}
]
Image 16. Request Body of API
Name Type Description
FlightNo String Fight ID: VN123
FlightDate Date (yyyy-mm-dd) Flight date, example: 2022-02-22
Route String Flight route: HAN-SGN

ACV PMO – IT Team
FieldName string Information fields need to be updated,

including flight milestones and passenger
traffic data.
(Details in 3.2)
Table 5. Request Body of API

3.5.4 Example
### Key Test ACV
POST https://apiflight.vietnamairport.vn/UpdateListFlight
Authorization: Bearer
eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy93cy8yM
DA1LzA1L2lkZW50aXR5L2NsYWltcy9uYW1lIjoiNWE1MmVmODItZjA2ZC00ZmI0LWEwZjItNjMwZ
mZjNTIyOTJjIiwiRnVsbE5hbWUiOiIiLCJCYXNlIjoiQUNWIiwiU291cmNlIjoiTklBIiwiRGV2aWNlSWQi
OiIxYjQwZTg0OS1jYmY1LTQzOTEtYWU3YS1mNDg4YjA0ZmY0YTAiLCJleHAiOjI1OTUzNzUxNzIs
ImlzcyI6IkFDVkFQSS5TZXJ2ZXIiLCJhdWQiOiJBQ1ZBUEkuQ2xpZW50In0.kkf95VbLOJbELjb8IFhYE
WXfgZgfZYB3NFy6jwIRRk4qULVKqkJ5ROYN0YcKUZlAN6JY_CADLMTc_ehc39a0yw
content-type: application/json
[
{
"FlightNo": "FX6001",
"FlightDate": "2022-03-03",
"Route": "HAN-KIX",
"FlightData": [
{
"FieldName": "SIBT",
"FieldValue": "0825"
},
{
"FieldName": "ELDT",
"FieldValue": ""
},
{
"FieldName": "ALDT",
"FieldValue": ""
}
]
},
{
"FlightNo": "VJ180",
"FlightDate": "2022-03-03",

ACV PMO – IT Team
"Route": "SGN-HAN",
"FlightData": [
{
"FieldName": "ArrDep",
"FieldValue": "A"
},
{
"FieldName": "ACRegNo",
"FieldValue": "VNA662"
},
{
"FieldName": "ACType",
"FieldValue": "A320"
}
]
}
]
###
Image 17. Example of data transmission by API

3.6 List of Data fields in ACDM PORTAL:
(FR: [COE]-[GEN]-[010], [COE]-[GEN]-[030], [GEN]-[SYS]-[150])
Attention:
- All time fields are all 4-digit string type in 24h format.
Example: 1705 = 17h05
• We may have “+” sign: for the next day; and “-” sign: the day before the scheduled flight
date at the end of this 4-digit string.
For example: 1105+: on the next day; 1155-: On the previous day.
- Those information fields have column "Provide when flight schedule creation (Y/N)" whereas
Y will be sent at flight schedule creation and synchronization between ground service systems
(SMIS, VMS, FlightView, FlightUpdate). ...) and ACDM PORTAL.
- Column “Push condition” describes time to push information of that field, blank lines are not
needed to push in case of change.
- Fields of EIBT, FLTST, EXIT, ICAO CALL SIGN, IATA DEP, ICAO DEP, IATA DES,
ICAO DES, automatically calculated and processed on ACDM PORTAL so no data
transmission is required.
3.6.1 List of Data fields

ACV PMO – IT Team
(FR: [GEN]-[SYS]-[160])
No Fileds Data Description Data Source Provide Push

Type when condition
flight
schedule
creation
(Y/N))
Both arrival and departure flights
1 Status String Flight status (3 letters) (3-characters SMIS, VIAGS Y Push in
code of flight status code): VMS, VJ case of
- CNX: Canceled FlightView, HGS change
- DLY: Delayed FlightUpdate →
- CLS: Closed ACDM PORTAL
- OPN: Open
- XXX: Deleted
Source:
SMIS: Status
VMS: Status
2 ArrDep String- A: Arrival Flight SMIS, VIAGS Y
- D: Departure VMS, VJ
- Source: FlightView, HGS
- SMIS: ArrDep FlightUpdate →
ACDM PORTAL
3 ACRegNo String Aircraft registration number. SMIS, VIAGS Y Push in
Ex: VNA324 VMS, VJ case of
Source: FlightView, HGS change
SMIS: ACRegNo FlightUpdate →
VMS: REGISTERNO ACDM PORTAL
4 ACType String Aircraft type. Ex: A321 SMIS, VIAGS Y Push in
Source: VMS, VJ case of
SMIS: ACType FlightView, HGS change
VMS: AIRCRAFT FlightUpdate →
ACDM PORTAL
5 FlightType String Flight type: SMIS, VIAGS Y
- PAX VMS, VJ
- CGO FlightView, HGS
- FER

ACV PMO – IT Team
Source: FlightUpdate →
SMIS: FlightType ACDM PORTAL
VMS: CARRY
6 CodeShare String CodeShare SMIS, VIAGS Y Push in
Source: VMS, VJ case of
SMIS: CodeShare FlightView, HGS change
FlightUpdate →
ACDM PORTAL
7 Nature Of String Nature Of Flight: SMIS, VIAGS Y
Flight - --- Normal flight VMS, VJ
- AMY Army FlightView, HGS
- CIC Cargo in Cabin FlightUpdate →
- DIV Divert ACDM PORTAL
- FER Ferry
- MED Medical
- TEC Technical
- TRN Training
Source:
SMIS: NatureOfFlight
VMS: CARRY
8 ACGT String Actual Commence of Ground SMIS, VIAGS Push in
handling Time: when ground VMS, VJ case of
handler starts serving the airlines. FlightView, HGS change
String 4-5 digits. Ex: 1105 FlightUpdate →
ACGT=AIBT=C.ON: Pair flights ACDM PORTAL
Source:
VMS: ACGT
AEGT String Actual End of Ground handling SMIS, VIAGS Push in
Time: when ground handler end VMS, VJ case of
serving the airlines. FlightView, HGS change
String 4-5 digits. Ex: 1105 FlightUpdate →
ACDM PORTAL
9 MGHA String Main Ground Handling Agent: Code SMIS, VIAGS Y
of Ground handler for flights. VMS, VJ
Ex: SAGS. FlightView, HGS
Source: FlightUpdate →
VMS: GH ACDM PORTAL
Arrival Flight
ACV PMO – IT Team
10 LRWY String Assigned Landing Runway: AMAN → NIA Push in

String: Ex: 07L Gateway → case of
ACDM change
PORTAL;
11 APRK String Arrival Parking Location: String. SMIS, VIAGS Push in

Ex: 02 VMS case of
Source: → ACDM change
SMIS: ParkingBay PORTAL
12 ELDT String Estimated Landing Time: String 4-5 AMAN → NIA Push in
digits. Ex: 1105 Gateway → case of
Source: ACDM change
SMIS: InOutBoundTime PORTAL;
13 ALDT String Actual Landing Time: String 4-5 AMHS Push in

digits. Ex: 1105 (VVNBYDYX) case of
Source: → SMIS → change
SMIS: AcutalTime ACDM PORTAL
14 SIBT String Scheduled In-Block Time: SMIS, VIAGS Y Push in

String 4-5 digits. Ex: 1105 VMS, VJ case of
SMIS: STA FlightUpdate →
VMS: STA ACDM PORTAL

ACV PMO – IT Team
SIBT cannot contain “+” or “-“

sign
15 AIBT String Actual In-Block Time: SMIS, VIAGS Push in

SMIS: C.ON FlightUpdate →
VMS: AonBT ACDM PORTAL
Departure Flight
16 TRWY String Take-off Runway: String 3-4 digits: DMAN → NIA Push in
Ex: 07L Gateway → case of
ACDM PORTAL change
17 DPRK String Departure Parking Stand: String. SMIS, VIAGS Push in

Ex: 02 VMS case of
Source: → ACDM change
SMIS: ParkingBay PORTAL
18 SOBT String Scheduled Off-Block Time: SMIS, VIAGS Y Push in
VMS: STD FlightUpdate →
SOBT cannot contain “+” or “-“ ACDM PORTAL
sign
19 ASBT String Actual Start Boarding Time: SMIS, VIAGS Push in
VMS: PREBTD/BDT FlightUpdate →
ACDM PORTAL
20 ETTT Int Estimated Turn-round Time: Integer SMIS, VIAGS Y Push in
in minutes. Ex: 60 VMS, VJ case of
VMS: ETTT FlightUpdate →
ACDM PORTAL

ACV PMO – IT Team
21 TSAT String Target Start-up Approval Time: DMAN → NIA Push in

String 4-5 digits. Ex: 1105 Gateway case of
→SMIS→ change
ACDM PORTAL
22 TTOT String Target Take-Off Time: DMAN → NIA Push in

String 4-5 digits. Ex: 1105 Gateway → case of
ACDM PORTAL change
23 ATOT String Actual Take-Off Time: AMHS Push in

String 4-5 digits. Ex: 1105 (VVNBYDYX) case of
Source: → SMIS → change
SMIS: ActualTime ACDM PORTAL
24 CTOT String Calculated Take-Off Time: Manual Push in

String 4-5 digits. Ex: 1105 case of
change
25 ARDT String Actual Ready Time: (moving) SMIS, VIAGS Push in

String 4-5 digits. Ex: 1105. VMS, VJ case of
SMIS: C.OFF FlightUpdate →
VMS: NIA: AOBT ACDM PORTAL
26 EOBT String Estimated Off-Block Time: SMIS Push in

String 4-5 digits. Ex: 1105 → ACDM case of
Source: PORTAL change
VMS: ETD
27 AOBT String Actual Off-Block Time: SMIS, VIAGS Push in
SMIS: PBT FlightUpdate →
VMS: AOBT ACDM PORTAL

ACV PMO – IT Team
28 TOBT String Target Off-Block Time: Manual

String 4-5 digits. Ex: 1105
Automatic calculate in ACDM
PORTAL, Manual Input if
necessary.
• Initial setting TOBT = EOBT
• 1st calculation: TOBT = ELDT +
EXIT + ETTT = EIBT + ETTT
• 2nd calculation: TOBT =
AIBT(ACGT) + ETTT
• If TOBT < EOBT then
TOBT=EOBT (this formulation will
continuous update when TOBT
changes)
• Source:
VMS: TOBT
Table 6. Description of Information fields for API
4. FDE fields for Phase 1
4.1 FDE Detail information
(FR: [OPS]-[PRO]-[040], [GEN]-[SYS]-[110], [GEN]-[SYS]-[120], [GEN]-[SYS]-[130],
[AOD]-[DAT]-[010], [AOD]-[DAT]-[020], [ASP]-[UID]-[050], [ASP]-[UID]-[060],
[ASP]-[OPS]-[010] to [ASP]-[OPS]-[030], [ASP]-[OPS]-[050], [ASP]-[VTT]-[010] )
AOC PROVIDE:
4.1.1 EXIT (Estimated Taxi-In Time)
(FR: [COE]-[GEN]-[010], [COE]-[GEN]-[040])
Time data summary will be declared on database of ACDM PORTAL, the default values for
inbound flights are based on LRWY and APRK. If the actual taxi-in time is different to the
default value, AOC/ATC is responsible to manually input to ACDM PORTAL.
4.1.2 EXOT (Estimated Taxi-Out Time)
(FR: [COE]-[GEN]-[010], [COE]-[GEN]-[040])
At NIA, DMAN calculates automatically and transmit to ACDM PORTAL

4.1.3 APRK (Arrival Parking Location)

ACV PMO – IT Team
At NIA, AOC manually input APRK on ACDM PORTAL.

4.1.4 DPRK (Departure Parking Stand)
At NIA, AOC manually input DPRK on ACDM PORTAL.
4.1.5 FLTST (Flight Status)
ACDM PORTAL automatically determine FDE FLSTS to display flight status
corresponding to milestones follow ACDM in Phase 1 (more detail information at 5.2)
4.1.6 EIBT (Estimated In-Block Time)
(FR: [ASP]-[GEN]-[150])
Automatic calculation for EIBT = ELDT + EXIT (calculating according to the change of
ELDT. EXIT is fixed value)
Automatically calculating the 2nd for EIBT: EIBT = ALDT + EXIT (update EIBT when
ALDT is set)
VATM provide:
4.1.7 LRWY (Landing Runway)
At NIA, receiving LRWY from AMAN via Gateway at NIA.
4.1.8 ELDT (Estimated Landing Time)
At NIA, receiving ELDT from AMAN via Gateway at NIA.
4.1.9 ALDT (Actual Landing Time)
At NIA, receiving ALDT directly via ARR telegram of ARO/AIS at NIA’s AFTN/AMHS
address: VVNBYDYX. NIA get this FDE via ground radar system with AMHS address.
4.1.10 TRWY (Take off Runway)
At NIA, receiving TWRY from DMAN via Gateway at NIA.
4.1.11 TSAT (Target Start-up Approval Time)
At NIA, receiving TSAT from DMAN via Gateway at NIA.
4.1.12 TTOT (Target Take-Off Time)
At NIA, receiving TTOT from DMAN via Gateway at NIA.
4.1.13 ATOT (Actual Take-Off Time)

ACV PMO – IT Team
At NIA, receiving ATOT directly via ARR telegram of ARO/AIS at NIA’s AFTN/AMHS
address: VVNBYDYX. NIA get this FDE via ground radar system with as ALDT.
4.1.14 CTOT (Calculated Take-Off Time)
At NIA, ATC manually inputs this FDE directly on ACDM Portal or share via ATFMC
system. This FDE will be input for all flights.
GHA provide:
4.1.15 ACREG (Aircraft Registration)
(FR: [AOD]-[DAT]-[130] )
Take ACREG automatically via SMIS and VMS from daily flight schedule.
4.1.16 IATAACSUBTYPE (IATA Aircraft Sub-Type)
Take IATAACSUBTYPE automatically via SMIS and VMS from daily flight schedule.
4.1.17 IATACSGN (IATA Callsign)
Take IATACSGN (follow IATA code) automatically via SMIS and VMS from daily flight
schedule.
4.1.18 ICAOCSGN (ICAO Callsign)
Based on IATA-coded flight number, ACDM Portal will convert from IATA to ICAOCSGN
4.1.19 IATAADEP (Aerodrome of Departure IATA)
ACDM Portal can analyze flight route from departure airport information (follow IATA
code) automatically from SMIS and VMS based on flight plan for inbound flight to get
IATAADES information.
4.1.20 ICAOADEP (Aerodrome of Departure ICAO)
Take departure airport information follow IATA code automatically from SMIS and VMS
based on flight plan for inbound flight. ACDM Portal can analyze flight route to get IATAADES
information, then convert from IATAADEP to ICAOADEP
4.1.21 SIBT (Scheduled In-Block Time)
ACDM Portal get STA from daily flight schedule of SMIS/VMS.
4.1.22 AIBT (Actual In-Block Time)
ACDM Portal get information from C.ON of SMIS and AonBT of VMS
4.1.23 MGHA (Main Ground Handling Agent)
ACV PMO – IT Team
GH will provide information for airlines, based on the declaration system for ground
handling contract.
4.1.24 ACGT (Actual Commence of Ground handling Time)
Providing time information when ground handling for airlines started.
GH will add ACGT on SMIS/VMS for each flight and transfer to ACDM Portal.
4.1.25 AEGT (Actual End of Ground handling Time)
Providing time information when ground handling for airlines ended. ACDM Portal get
information from ACDOORCLOSE from SMIS
4.1.26 ASBT (Actual Start Boarding Time)
Time when boarding is started. This FDE will be transmit automatically from SMIS/VMS to
ACDM Portal. ASBT = boarding call (SMIS)/Preboarding (VMS)
4.1.27 ETTT (Estimated Turn-round Time)
GH establish turn-around for each airline and each aircraft types to transmit to ACDM Portal.
GH will update the information according to real situation.
4.1.28 SOBT (Scheduled Off-Block Time)
Estimated time when aircraft leave its stand, information will be taken from STD of
SMIS/VMS from daily flight schedule.
4.1.29 EOBT (Estimated Off-Block Time)
Take estimated departure time from SMIS and VMS respectively to ETD from daily flight
schedule.
4.1.30 TOBT (Target Off-Block Time)
1/ Initial value TOBT = EOBT
2/ First calculation: TOBT = ELDT + EXIT + ETTT = EIBT + ETTT
3/ Second calculation: TOBT = AIBT(ACGT) + ETTT
4/ If TOBT < EOBT then TOBT=EOBT
In order to get TOBT, ETTT will be modified based on flight number and date. For the flights
do not have AIBT, TOBT = ACGT + ETTT will be applied for one-way flights and overnight
parking.
4.1.31 AOBT (Actual Off-Block Time)
ACV PMO – IT Team
Receive actual departure time from SMIS and VMS respectively to time column (PBT in
SMIS), that means time when aircrafts leave stands.
4.1.32 IATAADES (Aerodrome of Destination IATA)
Take destination airport information follow IATA code automatically from SMIS and VMS
based on flight plan for outbound flight. ACDM Portal can analyze flight route to get
IATAADES information.
4.1.33 ICAOADES (Aerodrome of Destination ICAO)
Take destination airport information follow IATA code automatically from SMIS and VMS
based on flight plan for outbound flight. ACDM Portal can analyze flight route to get
IATAADES information, then convert from IATAADES to ICAOADES.
4.1.34 ARDT (Actual Ready Time)
ACDM Portal receive information from C.OFF of SMIS and VMS
4.1.35 Overall diagram of FDE Calculation

ACV PMO – IT Team
Image 18. Overall of FDE calculations

4.2 Connection diagram and input method:
(FR: [ASP]-[INF]-[110])
4.2.1 The order of priority for data sources is updated by the user
The order of priority for data sources is set from 1 (the lowest priority) to 5 (the highest
priority)
1. System
2. SMIS
3. API

ACV PMO – IT Team
4. User Input.
If the data is empty, the order of priority is reset.
4.2.2 Overall diagram
(FR: [OPS]-[PRO]-[020], [GEN]-[SYS]-[010]))
The following diagram shows an overview of the input method and responsibility of
stakeholders at NIA airport for the input of FDE fields.

ACV PMO – IT Team
Example 1: Users from AOC at NIA airport will directly input EXIT, EXOT to ACDM Portal
Overall diagram of data exchange between ACDM Portal and the system of Stakeholders at NIA airport.

ACV PMO – IT Team
4.2.3 Diagram of fields directly inputted to ACDM Portal

(FR: [GEN]-[SYS]-[060])
At NIA, stakeholder directly input these fields to ACDM Portal shown as below:
Image 19. Diagram of fields directly inputted to ACDM Portal by NIA’s stakeholders
4.2.4 Diagram of fields transmitted via API from VIAGS
VIAGS transmitted to API Portal these following fields:
ACREG, SIBT, AIBT, MGHA, ACGT, ASBT, ETTT, SOBT, EOBT, AOBT, ARDT
Image 20. Diagram of fields transmitted via API from VIAGS

4.2.5 Diagram of fields transmitted from Ground handlers to ACDM Portal’s Open API
At NIA, HGS transmitted to API Portal these following fields: ACREG, SIBT, AIBT,
MGHA, ACGT, ASBT, ETTT, SOBT, EOBT, AOBT, ARDT.

ACV PMO – IT Team
Image 21. Diagram of fields transmitted via API from HGS

At NIA, SMIS transmitted to API Portal these following fields: ACREG, SIBT, AIBT,
MGHA, ACGT, ASBT, ETTT, SOBT, EOBT, AOBT, ARDT, APRK, DPRK, ALDT, ATOT
Image 22. Diagram of fields transmitted via API from SMIS at NIA
4.2.6 Diagram of fields transmitted via API from NIA Gateway
At NIA, NIA Gateway transmitted to API Portal these following fields: LRWY, ELDT,
TRWY, TSAT, TTOT, EXOT
Image 23. Diagram of fields transmitted via API from NIA Gateway
5. Two-way data synchronization

ACV PMO – IT Team
5.1 Two-way data synchronization at NIA

Two-way data synchronization server is located at Cloud Viettel. At the two-way data
synchronization server, the following technologies will be used:
• Open API: Stakeholders use Open API technology to push data to the two-way data
synchronization server
• RapidMQ: Two-way data synchronization server using RapidMQ technology to push
data back to StakeHolders.
• Webservice: ACDM Portal uses Webservice technology to get data from StakeHolders
to Database ACDM Portal manually.
• Signal R: test the connection between the StakeHolders server and the two-way data
synchronization server.
Image 24. Two-way data synchronization at NIA

At NIA, stakeholders such as HGS, VIAGS, NIA, VJC will use Open API technology to
push their own data to the data synchronization server and the data synchronization server to
push the data to the ACDM Portal
ACDM Portal will push data back to data synchronization server, data synchronization server
will use RabidMQ technology to return data to stakeholders.

ACV PMO – IT Team
The data synchronization server will use SignalR technology to monitor the connection status
to the stakeholders through the System Monitor page.
In some objective cases where the data of the stakeholders pushed to the ACDM Portal is
not informative, the ACDM Portal can use the webservice to actively retrieve data from the
stakeholders.
ACDM Portal will push data back to data synchronization server, data synchronization server
will use RabidMQ technology to return data to stakeholders.
6. Main features of ACDM Portal:
(FR: [OPS]-[PRO]-[100], [ASP]-[GEN]-[010] to [ASP]-[GEN]-[060], [SER]-[TRA]-[010]
to [SER]-[TRA]-[040] )
Find out more in the following link: User Guide.
6.1 Alert
(FR: [OPS]-[ALR]-[010], [OPS]-[ALR]-[020], [GEN]-[SYS]-[140], [ASP]-[GEN]-[080] )
When other users or the ACDM Portal itself re-calculate, update or edit real-time information
of any flight, which currently display on screen, there will be two types of alert:
1. The modified information will blink for 15 seconds
2. ACDM Portal will pop up a notification on bottom right of the screen, which contains: the
user modified the information, which information is modified, date and time and flight
Image 25. Notification panel for alert

ACV PMO – IT Team
Moreover, ACDM Portal also have other alert features as table below. Users can config the
parameters through the Alert Config page.
No Alert Detail
1 Alert when EIBT is out of SIBT +/- 15 mins
2 Alert when AIBT is greater than EIBT + 0 mins
3 Alert when EOBT and SOBT discrepancy +/- 0 mins

4 Alert when no ALDT, when ELDT + 5 mins
5 Alert when No ASAT at TSAT + 5 mins
6 Alert when Aircraft Type discrepancy
7 Alert when Aircraft Registration discrepancy
8 Alert System Network. (Not In Phase 1)
9 Alert when EIBT + ETTT discrepancy with TOBT
10 EOBT Compliance Alert. (Not In Phase 1)
11 Alert when Boarding Not Started (Not In Phase 1)
12 Alert when TOBT Rejected or Deleted. (Not In Phase 1)
13 Alert when Flight not compliant with TOBT
14 Alert when Flight not compliant with TSAT
15 Alert when TSAT Not Respected by ATC (Not In Phase 1)
16 No ATC Flight Plan Available (Not In Phase 1)
17 Automatic TOBT Generation not possible
Alert when TOBT (calculated due to ACGT) is greater 5 minutes than the
18
previous TOBT
19 Alert when Change TRWY in use
20 Alert when Change LRWY in use
21 Alert when TSAT vs previous TSAT discrepancy
22 Alert when AO/GH update EOBT
23 Alert when AO/GH update TOBT
24 Alert when the flight status is RTG

ACV PMO – IT Team
25 Alert when the flight status is DIV

26 Alert when the flight status is CNL
27 Alert when the flight status is DLA
28 Aircraft Parking discrepancy
29 Aircraft Parking discrepancy
30 Arrival Parking Confliction (Not In Phase 1)
31 Departure Parking Confliction (Not In Phase 1)
32 Arrival Parking - No Airport Slot available (Not In Phase 1)
33 Departure Parking - No Airport Slot available (Not In Phase 1)
Table 7. Statistical table for alerts
6.2 Features of FLTST field
6.2.1 List of FLTST
# Status Notes
1 Set flight status to SCH
Each inbound and outbound flights

have own FLTST, so 2-way flight
will have 2 fields AFLSTS and
Set flight status to INI
DFLTST.
2 - 150 minutes before EOBT for domestic flights
FLTST is set following the rule:
- 210 minutes before EOBT for international flights
- If current time >= EIBT or AIBT is
set, FLTST will be AFLSTS
- Otherwise, it will be DFLSTS
Set flight status to AIR when receive ATOT from departure
3
airport
4 Set flight status to FIR when for the 1st time receive ELDT
ATFMC can change flight status to DIV (Divert) for flight
5
diversion procedure
6 Set flight status to FNL 10 minutes before ELDT
7 Set flight status to LND when receive ALDT
In case the aircraft perform missed approach procedure, When user updates ELDT, the
8
ACDM Portal will automatically change flight status to FNL system will set status to FNL
9 Set flight status to IBK when receive AIBT
10 Set flight status to BRD when receive ASBT
11 Set flight status to RDY when receive ARDT
GH can change flight status (from RDY to BRD) on ACDM
12
Portal when incident occurs after the flight is ready
13 Set flight status to OBK when receive AOBT

ACV PMO – IT Team
# Status Notes
14 Set flight status to DEP when receive ATOT

15 Can change flight status to RTG when flight is returned
Can change flight status to CNL when flight plan is
16
cancelled.
17 Can change flight status to DLA when delay
Flight status can be changed to DIV when redirecting
18
landing
Table 8. Statistical table for the established states of FLTST

ACV PMO – IT Team
1.1.1 Overall Diagram of FLTST
Image 26. Diagram of FLTST

ACV PMO – IT Team
7. Overview ACV ACDM Website

7.1 ACDM Flight
7.1.1 Overview ACDM Flight page
(FR: [ASP]-[UID]-[010] to [ASP]-[UID]-[040], [ASP]-[DIS]-[010] to [ASP]-[DIS]-[070])
The ACDM Flight page is the main flight information display page. This page will display
different information base on user's authorization.
Image 27. ACDM Flight page

7.1.2 Header of ACDM Flight page
Image 28. Header of ACDM Flight page

Item 1: ACV Logo, click it to back to main ACV ACDM
Item 2: Page title
Item 3:
• Display current time.

ACV PMO – IT Team
• Switch button for switching local and utc: Display flight information according to
GMT+7 time or UTC time
• Switch button for switching IATA and ICAO Display flight information according to
IATA code or ICAO code.
Item 4: Display username. Click it to navigate to profile user page.
7.1.3 Toolbar ACDM Flight Page
Image 29. Toolbar of ACDM Flight page

• Item 1: Dropdown button, move and click this button will show dropdown-list options:
o TSAT Planning: Click to navigate to TSAT Planning ( TIA Only)
o TSAT Window: Click to navigate to TSAT Window
o TOBT Window: Click to navigate to TOBT Window
o Exit Exot: Click to navigate to EXIT EXOT TABLE.
o AutoLink Flights: Click to navigate to AutoLink Flights .
o Runway Config: Click to navigate to Runway Config.
o Link Flight: Click to navigate to LinkFlight.
o Alert Config: Click to navigate to Alert Config.
o System Status: Click to navigate to System Status.
o Twoway Monitor: Click to navigate to Twoway Monitor.
Image 30. Dropdown-list on toolbar

- Item 2, 3, 4 have function to filter arrival flights or departure flights
• Item 2: Select all flight (include two-way flights and one-way flights)
• Item 3: Select arrival flights only (one-way flights only)
• Item 4: Select departure flights only (one-way flights only)
- Item 5, 6, 7 have function to filter domestic flights or international flights
ACV PMO – IT Team
• Item 5: Select all flights including domestic flights and international flights
• Item 6: Select international flights
• Item 7: Select domestic flights
• Item 8: refresh data
• Item 9: Customize to config columns view, config notification, config searching.
Image 31. Configuration to customize display function

Column View Config: Columns view custom configuration. The config view dialog box
will show after clicked, Click on box to enable column to view ( ) or click on again to disable
( ). Click on to select all column or click
to deselect all

ACV PMO – IT Team
Image 32. Customizable configuration to display information columns

Notification Config: Notification custom configuration. The notification config dialog box
will show after clicked. Click on box to enable field changed notifications ( ) or click on again
to disable ( ). Click on to select all column or click
to deselect all

ACV PMO – IT Team
Image 33. Customizable Notice interface

Search Config: Customize searching configuration The search config dialog box will show
after clicked. Click on box to enable searching field ( ) or click on again to disable ( ).
Click on to select all column or click
to deselect all
Image 34. Customizable configuration for searching flight information

Download Current Data: download the information of the ACDM Portal system being
displayed to the user as a “csv”file.

ACV PMO – IT Team
Reset Grid View: Since the ACDM Portal system caches the operating information on the
ACDM Portal system, if the user clicks this button, the ACDM Portal system will refresh the
display of flight data information by default.
Item 10: Only for Admin Users. Synchronize TwoWay Data between Stakeholder and
ACDM Portal
- Item number 11, 12, 13 combine to make different filters
• Item 10: Select the date and time to start filter. The default value is 2 hours ahead of current
time.
• Item 11: Select the date and time to end filter. The default value 3 hours from now.
• Item 12: Options below:
o Hide deleted, canceled flights: Enable/Disable view the canceled or deleted flights.
o View only turn-around flights: Enable/Disable view only turn around flights.
o Search by date time: Enable/Disable the filter of date only.
o Hide finished flights: Enable/Disable display finished flights (chuyến bay có giờ ATOT).
o View flights by MGHA: Enable/Disable display flights based on MGHA.
Only Admin can view all MGHA’s flights.
Attention: “View flights by MGHA” only display on NOI BAI, NOI BAI Test Zone Base.
- Note when use the filter (item 11, 12):
Filter by date:
If “search by datetime” is disabled, This filter will show and filter flights by date.
Filter by date and time: When “search by datetime” is enable.
Image 35. Information display to filter by date

ACV PMO – IT Team
In date box filter, input date information to filter or click icon to show the date to select.
Then select the date to filter or click Today button to select the current date.
Image 36. Drop box to select date

Filter by time:
This filter will be shown when the “Search by date time” box is selected. This filter will filter
all flight from the start date-time to end date-time
(FR: [AOD]-[DAT]-[100] )
Image 37. Information display to filter by time duration

ACV PMO – IT Team
Users can type text directly date and time information to filter into 2 filters box or click on
the button containing the icon next to show the date and time to choose. Then select the
date to filter or press the Today button to automatically select the current date.
Image 38. Drop box to select date of time filter

After selected the date, the system will automatically switch to the time column to select the
time. Select the time to filter or click “NOW” to let the system choose the current time.
Image 39. Drop box to select specific time

ACV PMO – IT Team
After selecting the time, click the Set button to finish. Click the Cancel button to cancel.
Image 40. Flight information display by time filter

• Item 14: Search/ Filter the flights.
Example:
- Input in search box airlines name which can separated by a comma “,”. Either IATA or
ICAO codes can be used. For example: Input "vn,vj,qh" or "hvn,vjc,bav", the system
will return the results of 3 airlines flights VietNam Airlines, VietJet, Bamboo Airways
Image 41. Example of searching information by flight number

- Search for flights with FlightNo of VN246
ACV PMO – IT Team
Image 42. Example of searching for Flightno VN246

- Search for flights with ICAO code of HVN186
Image 43. Example of searching by ICAO ID for HVN186
7.1.4 Overview Flight Information Display

(FR: [ASP]-[GEN]-[110] to [ASP]-[GEN]-[140], [ASP]-[INF]-[010], [ASP]-[INF]-[150])
The display of flight information depends on the user-assigned authorization and options
which introduced in 3.2.2 and 3.2.3.
By default, the system will display flight information -2/+3h from the current time. If
“Search by date time” is not selected, the system will display flight information at current day.
At this time, when new flight information is added or updated, the system will update automatic
and display on it. The system will auto update real time all flights with any time field within the
current date.
The system will not automatically update flight information when the date in filter box older
than current date., or when the datetime filter is used but the start and the end datetime are not
in range -12h/+12 from current datetime. At this time, when new flight informational is add or
update, the system will not update automatic. Therefore, user need to click on refresh button
(item 8 – section 3.2.3) to refresh and display new flight information.
If FlightTime between arrival flight and departure flight is more than 5 hours, two flight
cannot link automatically.

ACV PMO – IT Team
Image 44. Default display of flight information
Image 45. Flight information display by VN time zone and ICAO standard

ACV PMO – IT Team
Image 46. Flight information display by UTC time and ICAO standard
Overview columns
First column: Show the total number of flights and the order number of the flights
Second column: Icons represent: two-way flights, arrival flights, departure flights.
Represent two-way flight.
Represent departure flight.
Represent arrival flight.

Third column: Display FlightNo of flights. Click left mouse to view history of inputted field.
The numbers next to the flight icon represent the number of flight's warning.
Ex: the number 2 next to flight THY164 symbol means flight THY164 has 2 warnings.

ACV PMO – IT Team
Image 47. Display of history information fields.

There are 2 methods to look up history input data:
Method 1: Click to drop down the list of information fields, then select the information field
user want to look up.
Method 2: Enter the field name in the box circled in red on the upper right
Image 48. Selection display to show history information fields

ACV PMO – IT Team
From the fourth column, there will be difference based on ICAO code or IATA code
IATA Code (Picture 9): will display FlightNo, Date, Route, ACREGNO (Aircraft
registration number), ATYPE(ACType), FLTST(Flight-Status).
ICAO Code (Picture 10 and picture 11): will display FlightNo, Date, DEP (Depature
Code), DES(Destination Code), ATYPE(ACType), FLTST(Flight-Status).:.
After the FLTST column, there will be a change based on the authorization assigned to the
user.
Default the view of field for user and stakeholder units are as follows:
AOC:
- View-only field: All
- Editable Field:
APRK, DPRK, FLTST, BELT, AGATE, DGATE.
GHA: Sags, Hgs, Viags, Vj gha, Bl gha (User airline can only edit their own airline
flights)
- Editable field:
ETTT, TOBT, AIBT, ARDT, FLTST, ACGT, AEGT, ASBT, AOBT
ATC:
- Editable field:
LRWY, TRWY, ELDT, ALDT, TSAT, CTOT, ATOT, FLTST, ASAT, ASRT.
AO: VN, VJ, QH, VU (User airline can only edit their own airline flights)
Attention: ACDM Portal will cache the entire display interface including: flight filter
time, flight search, order of columns, width of columns... \
Example: The user is selecting to view the flight of 13-12-2023 and is searching for flight
VN190. When the user presses F5 to reload the page or when a problem of sudden loss of
Internet connection occurs, when the user reopens the page, the interface is displayed before
pressing F5 or the problem occurs.

ACV PMO – IT Team
Image 49. ACDM Portal display interface of attention case.

If you want to display the default, press the cog button and select “Reset Grid View”.
Image 50. “Reset Grid View” interface

7.1.5 Edit Flight Information:
(FR: [AOD]-[DAT]-[110], [ASP]-[INF]-[060] to [ASP]-[INF]-[090] )
While in the editing state of a flight, the system will temporarily not update the
information in real time until the flight editing is completed and exits the edit state.
For non-timeline columns:
Left-click to edit cell. At this time, the row which has edited cell will change to yellow. Then
input the data and press Enter to confirm, press ESC to cancel.
Image 51. Adjust other non-time milestones

For only LRWY and TRWY columns, when clicked, the system will show a dropdown-list
of runways to select, click one to confirm, click outside the dropdown-list to Cancel.
Attention: Click on the middle part of the selection bar, clicking on the arrow will close
the selection list.

ACV PMO – IT Team
Image 52. Adjust LRWY information

For timeline columns:
When user selects the Local time display mode, user must enter the local time (GMT
+7).
Similar to UTC time, when selecting UTC time display mode, user must enter UTC
time.
There are two ways to edit.
1: Left click then input the data. Input “.” then hit Enter for inputting current time.
2: Right Click and the edited dialog box below will show after clicked.
Image 53. Dialog box display to adjust time milestones

Input the time or click Now to get the current time (depend on UTC or Local Time whichever
is selected). Click +5min to plus 5min or -5min to minus 5min from inputed time. Click OK to
confirm or Cancel to.

ACV PMO – IT Team
Image 54. Dialog box display to adjust time milestones after click “Now”
Image 55. Dialog box display after click “+5 min”

7.1.6 Instructions for entering time information on the ACDM portal system
Entering flight time must be according to the scheduled flight date of that flight (FlightDate),
FlightDate can be in LOCAL or UTC time zone depending on user preference.
If the time information belongs to the arrival (ELDT, ALDT, SIBT, EIBT, AIBT) then the
flight date is taken according to the arrival flight.
If the time information belongs to the depature (ACGT, AEGT, SOBT, EOBT, TOBT,
ASBT, ARDT, AOBT, CTOT, TTOT, ATOT), the flight date is taken according to the depature
flights.
Note: Flights on ACDM Portal are displayed as a pair of arrival - departure, so the flight
date of the depature and the arrival may be different.
ACV PMO – IT Team
Example:
Image 56. Cặp chuyến đi-đến có ngày bay khác nhau

Arrival: VN405, FlightDate: 15 Mar, SIBT: 2110
Depature: VN422, FlightDate: 16 Mar, SOBT: 0030
Enter time information on ACDM Portal in 5-character string format:
- From "0000" to "2359" can have "+" or "-" character at the end of the information
string according to the following regulations:
+ The "+" character means the time information is more than 1 day from the flightdate
(Flight's Scheduled Date)
+ The "-" character means the time information is 1 day before the flightdate (Flight's
Scheduled Date)
Specify the “+” and “-” characters should be based on the scheduled flight date of the flight.
Example: “+”: SGN – DAD FlightDate: 19 Feb, SOBT: 2340
Then, when entering the time information located on February 19, do not add the "+"
character. For example: AOBT: 2355.
Enter the time information located 1 day later (February 20), then add a "+" character.
Example: TOBT: 0030+
Example: “-”: DAD-SGN FlightDate: 19 Feb, SIBT: 0015
Then when entering the time information located on February 19, do not add the "-"
character. Example: AIBT: 0030.
Enter the time information located 1 day before (February 18), then add a "-" character.
Example: ELDT: 2350-
7.1.6.1 Check data during time information input ACDM Portal
The ACDM Portal system automatically checks the validity of the data by comparing it with
the flight's SIBT/SOBT time. If there is too large a deviation between the received time

ACV PMO – IT Team
information and the flight's SIBT/SOBT (greater than +/-15h), the system will handle the
following warning:
Image 57. Notification when information has large deviation from SIBT/SOBT interface.
The system will send an alert to the user, the user can choose 1 of 4 options as follows:
• “Confirm”: Confirmation, ACDM Portal will accept the value user just
entered.
• “Change”: Change the value user just entered.
• “Change to ….”: Change the input value to the new value suggested by
the ACDM Portal.
• “Cancel”: Delete the value user just entered.
Ex: Flight VN204 on March 21, 2023, SIBT: 0030.
Input Value: ELDT = 0015+
 The ACDM Portal sends an alarm as shown in Figure 39, with the request to
change the ELDT to the value 0015.
This instruction will apply ACDM Portal only, not for others software like VMS
or SMIS…
7.1.7 Overview warning function
7.1.7.1 Flight information edit warning

ACV PMO – IT Team
When the system, other user updates or edits any flight information field, if the system is in
a state of automatic real-time updating as mentioned in section 3.2.4 then the system will fire
two warnings. One is that the system will blink for 15s the cells that have been edited. Second,
the system generates a dialog box on the bottom right corner of the screen, which contains
information such as: who edited, what information was edited, modified date and time, modified
flight information.
Image 58. Alert display after adjust flight information

7.1.7.2 Incorrect time syntax warning
At timeline columns, the system will fire the warning if user input wrong time syntax.
Ex: 2548, 2457r…
Image 59. Alert display of incorrect time information

• Change: Click to input another time.
• Cancel: Click to cancel
7.1.7.3 Inputed time confirm warning.
ACV PMO – IT Team
Case 1:
For flights 1 day after the current date and the user is entering the time from 0000 to 0959,
the system will fire a warning reminding the user to enter the 5-digit time (with + sign).
Ex: 1000+.
Image 60. Illustration when user enter information of case 1
Image 61. Notice display to confirm time information of case 1

• Change value to 1000+: Click to change from 1000 to 1000+
• Change: Click to input another time
• Confirm: Click to confirm the inputted time (0455).
• Cancel: Click to cancel.
Case 2:
For flights 1 day before the current date and the user is entering the time from 2000 to 2359,
the system will fire a warning reminding the user to enter the 5-digit time (with - sign).
Ex: 2113-.
ACV PMO – IT Team

• Change value to 2113-: Click to change from 2113 to 2133-
• Change: Click to input another time
• Confirm: Click to confirm the inputted time ( 2113 )
• Cancel: Click to cancel
Case 3:
For flights at current date, if user input time from 1000+ to 2359+, system will pop up a
notice to confirm about entered time information

ACV PMO – IT Team

• Change value to 1054: click to change entered time from 1054+ to 1054
• Change: click to re-enter departure time
• Confirm: click to accept entered time information ( 1054+ )
• Cancel: click to cancel
Case 4:
For flights at current date, if user input time from 0000+ to 1959+, system will pop up a
notice to confirm about entered time information

ACV PMO – IT Team

• Change value to 0854: click to change entered time from 0854- to 0854
• Change: click to re-enter departure time
• Confirm: click to accept entered time information ( 0854- )
• Cancel: click to cancel
Alert of incorrect Parking Bay information

When user enter incorrect parking bay information, the system will pop up a Dialog box to
notify user:
Image 68. Notice of incorrect Parking bay information

• Confirm: to confirm correct information
• Cancel: to cancel
• Change: to adjust information
7.1.8 Overview Flight Status Information
In FLTST Column, the flight status will be shown
ACV PMO – IT Team
7.2 ACDM Flight Detail Page

7.2.1 Overall introduction
When user double-click on the first column to the ATYPE column of a specific flight, the
website will switch to the ACDM Flight Detail page. This page displays the details of flight
information (1 or 2 way) and Milestone which is happening in 16 Milestones. The formula of
16 Milestones will be explained in 5.2.4. Depending on the round trip flight, departure or arrival
flight, the ACDM Flight Detail page will display a different interface to distinguish.
There are 3 interfaces:
• Interface of ACDM Flight Detail for round trip flight.
• Interface of ACDM Flight Detail for departure flight.
• Interface of ACDM Flight Detail for arrival flight.
Image 69. ACDM Flight Detail default display for roud trip flights
In Figure 69, the flight received ATOT, so the flight is at 16th Milestone step and is in the
Take-off phase. Therefore, the number 16 will be displayed in red and the Take-off phase will
be displayed in green. From 1st to 15th step, because these steps were passed, so these steps will
be displayed in green. Figure 70 and 71 are similar.

ACV PMO – IT Team
Image 70. ACDM Flight Detail default display for departure flight
Image 71. ACDM Flight Detail default display for arrival flight
Similar to the ACDM Flight page, ACDM Flight Detail can display information to comply
with IATA or ICAO standards, in Vietnam timezone or UTC.

ACV PMO – IT Team
Image 72. ACDM Flight Detail display to comply with ICAO for roud trip flight
7.2.2 Basic information fields of ACDM Flight Detail
For IATA code
Image 73. Fundamental information of IATA code flight

Arrival table: contain information:
- ACType (B777F)
- ACRegNo (A7BFD)
- FlightNo IATA (QR8968)
- SIBT (0400)
Flight route table (middle table): contain information
- ARouteICAO and DRouteICAO (DOH-SGN-DOH)
- APRK: (Arr Park 24)
- DPRK (Dept Park 24)
ACV PMO – IT Team
Departure table: contain information:

- ACType (B777F)
- ACRegNo (A7BFD)
- FlightNo IATA (QR8968)
- SOBT (0545)
For ICAO code
Image 74. Fundamental information of ICAO code flights

Arrival table: contain information
- ACType (B777F)
- ACRegNo (A7BFD)
- FlightNoICAO (QTR8968-8969)
- SIBT (0400)
Flight route table (middle table): contain information
- ARouteICAO and DRouteICAO (DOH-SGN-DOH)
- APRK: (Arr Park 24)
- DPRK (Dept Park 24)
Departure table: contain information
- ACType (B777F)
- ACRegNo (A7BFD)
- FlightNoICAO (QTR8968-8969)
- SOBT (0545)
7.2.3 Time information fields of ACDM Flight Detail
Landing column: contain information
- LRWY
- ELDT
- ALDT
Taxi In column: contain information
- AXIT = AIBT – ALDT
- EXIT in EXIT EXOT Table
Inblock column: contain information
ACV PMO – IT Team
- EIBT
- AIBT
Onblock column: contain information
- AGATE:
- ACGT
- AEGT
Ready column: contain information
- ARDT
- TSAT
- ASAT
Taxi In column: contain information
- AXOT = ATOT – AOBT
- EXOT in EXIT EXOT table
Off-block column: contain information
- TRWY
- DGATE
- EOBT
- TOBT
- AOBT
Take-off column: contain information
- CTOT
- ETOT
- TTOT
- ATOT
7.2.4 Formula 16 Milestones
• Milestone 1 EOBT -3 hours: The current time before EOBT 180 minutes or lower
• Milestone 2 EOBT -2 hour: The current time before EOBT 120 minutes or lower.
• Milestone 3 Take-off outstation: this Milestone does not have formula because
ACDM Portal does not have Take-off outstation information
• Milestone 4 Local Radar Update: ACDM Portal had ELDT time and the current
time is earlier than ELDT Time
• Milestone 5 Final Approach: ACDM Portal had ELDT time
• Milestone 6 Landing: ACDM Portal had ALDT time
• Milestone 7 In Block: ACDM Portal had AIBT time

ACV PMO – IT Team
• Milestone 8 Ground Handling Starts: ACDM Portal had ACGT time

• Milestone 9 Update TOBT Prior to TSAT: The current time is between 30 and 40
minutes earlier than TOBT.
• Milestone 10 TSAT Issue: The current time is 30 minutes earlier than TOBT and has
had TSAT.
• Milestone 11 Boarding Starts: ACDM Portal has had ASBT time.
• Milestone 12 Aircraft Ready: ACDM Portal had ARDT time.
• Milestone 13 Start-up request: ACDM Portal had ASRT time.
• Milestone 14 Start-up Approved: ACDM Portal had ASAT time.
• Milestone 15 Off-block: ACDM Portal had AOBT time.
• Milestone 16 Take-off: ACDM Portal had ATOT time.
7.3 ACDM Exit Exot Table page
ACDM EXIT EXOT TABLE page is only available for user in ATC and AOC
ACDM EXIT EXOT TABLE has following functions:
• Add new Parking Bay.
• Add/Remove/Edit Exit, Exot.
• Seraching by name of Parking Bay.
• Marking Exit, Exot which haven’t inputted or input 0 value (marking by green color)
Currently ACDM EXIT EXOT page doesn’t have the function to delete Parking Bay and
RunWay. If users want to delete, the person in charge can contact to ACV to edit.

ACV PMO – IT Team
Image 75. ACDM EXIT EXOT TABLE interface

7.3.2 Introduction of functionalities
Adding new Parking Bay
Click on the New ParkingBay button, it will display the Add ParkingBay dialog box and
users must enter the parameters as shown in Figure 17. Then click OK button.

ACV PMO – IT Team
Image 76. Add Parking Bay dialog box

Parking Bay: enter name of Parking Bay to create
RunWay: Select Runway in the list
Image 77. List of RunWay

Edit Exit, Exots
Double-click on the cell that needs to be edited, the Edit dialog box will appear and user can
enter the necessary information as shown in Figure 19. Then click the OK button.
Image 78. Edit dialog display

ACV PMO – IT Team
Delete Parking Bay

Right Click to Parking Bay need to delete, ACDM Portal will show confirm dialog. Click
“OK” to confirm and “Cancel” to cancel delete.
Image 79. Delete Parking Bay notification
Searching by Parking Bay

Enter information of Parking Bay into searching box

ACV PMO – IT Team
Image 80. Searching display by Parking Bay.
7.4 Runway Config page

The Runway Config page is only available for VATM users. The Runway Config page has
a facility to automatically assign Runway values to arrival or departure flights over a period of
time. Example: It will automatically give Runway 07R for arrivals between 11:52am and
12:45pm. The user can add, remove, edit or switch that condition to be on or off.
Image 81. Configuration display

7.4.2 Adding rule function

ACV PMO – IT Team
(FR: [AOD]-[DAT]-[030])
Click “+ADD” button on the top right corner. After click, a dialog box will appear. All
required parameters must be filled in, otherwise the system will ask you to re-enter. The
parameters are as follows:
- Runway: Select the taxiway.
- ArrDep: Choose departure flight or arrival flight.
- FromTime: Select the start time to activate this rule
- ToTime: Select the end time to activate the rule.
- Active: Enable/disable this rule.
After input all the information, click Update button to finish.
Image 82. Dialog box to add Config

7.4.3 Introduction of edit Rule function
Click Edit button at the Rule line you want to edit. All required parameters must be filled in,
otherwise the system will ask to re-enter them

ACV PMO – IT Team
Image 83. Dialog box of Edit function

7.5 ACDM Link Flight page
By default setting, the system will automatically link a pair of arrival and departure flights
which are the same ACREGNO within maximum 300 minutes. The ACDM Flight Link page
has flight pairing manual function in case the system fails to match the flights, or to edit the
existing pairs of flight.
Pay attention to the following cases, it will cancel the flight pairing and find another suitable
flight to re-pair:
A. Change ACReg
B. Change Status of arrival and departure flights (From XXX, CNX to Open, Close and vice
versa)
C. Change SIBT, ALDT, SOBT, EOBT, ATOT.
Example:
In case of changing ACReg: Suppose there is a flight pair VN222-VN333
Arrival Flight: VN222 (ACReg: VNA4321 – SIBT: 1300)
Departure Flight: VN333 (ACReg: VNA4321 -SOBT: 1400)

ACV PMO – IT Team
When arrival flight VN222 changes ACReg from VNA4321 to VNA4567, then that pair of
flights will cancel pairing and both VN222 and VN333 will become a single flight. Two single
flights VN222 and VN333 will find another suitable single flight to pair up. Specifically:
- Flight VN222 will find another SINGLE flight which has the same ACReg and EARLIEST
time IN 300 MINUTES before FLIGHT VN 222. For example, the suitable flight is departure
flight VN 888 has ACReg: VNA4567 and SOBT: 1405. At this time, the flight pair is: VN222-
VN888.
- Flight VN333 will find another SINGLE flight which has the same ACReg and EARLIEST
time IN 300 MINUTES before FLIGHT VN 333. For example, the arrival flight VN111 has
ACReg: VNA4321 and SIBT: 1255. At this time, the flight pair is VN111-VN333.
The other cases are similar.
Image 84. ACDM Flight Link page

• Item 1: select date to display flight information accordingly
• Item 2: list of arrival flight
• Item 3: searching flight information in arrival flight list
• Item 4: list of departure flight
• Item 5: searching flight information in departure flight list
7.5.2 Introduction of flight pairing function
After select date to display the paired flight, at the list of arrival flights, click on the icon
to select the arrival flight. The system will display some basic information of that flight. Click
Clear to cancel the selection

ACV PMO – IT Team
Image 85. Select flights to pair

Next, select departure flight and click the icon to pair. If you agree to pair these flights,
click Link flight, or click clear to cancel
Image 86. Select flights to pair

7.6 TSAT Windows
(FR: [ASP]-[PDS]-[020] to [ASP]-[PDS]-[040], [ASP]-[PDS]-[090] , [ASP]-[PDS]-[100],
[ASP]-[PDS]-[120], [ASP]-[PDS]-[140] to [ASP]-[PDS]-[160])
TSAT Windows page has a function to support ATC in tracking and monitoring the take-off
process of flights.
7.6.2 Introduction of TSAT Windows display
TSAT Windows page has 2 following tables:

ACV PMO – IT Team
Image 87. Main display of TSAT Windows

Table 1 shows flight information with tsat +5/-5 minutes from current time and necessary
milestones.
Table 2 shows flight information when TSAT from +/-30 minutes compared with current
time and necessary milestones.
In the TSAT Windows +/- 5, flights with TSATs earlier/later than the current time +/- 5
minutes will be displayed. For flights that have ASAT time will not be displayed in this window
(except when the “SUG ON” button is selected)
The Other FLTs Within +/-30 will display flights with TSAT earlier/later than the current
time +/-30 minutes and does not include flights in the Windows TSAT +/-5. For flights having
ASAT time will not be displayed (except when the “SUG ON” button is selected).
7.6.3 Introduction of TSAT Windows information fields
• AType: Aircraft Type
• Callsign: FlightNo according to ICAO code
• Date: Date base on Local Time or UTC Time
• Des: Destination
• FLTST: Flight Status
• S/E/TOBT: SOBT, EOBT, TOBT. Order from lower to higher: SOBT → TOBT.

ACV PMO – IT Team
• SOBT time will be white, EOBT time will be yellow, TOBT time will be orange.
• DPARK: Depature Park. Parking lots in zone 1 will be green, parking lots in zone 2 will
be yellow. Parking lots that do not belong to the above two zones will be white.
• ARDT, ASRT, TSAT, ASAT, CTOT, TTOT: Flight’s Time
• Remarks: Flight Remark. Can be entered any character. However, when the flight is
Pinned, the word "PINNED" will appear in the Remarks box and will override the
previous remark of the PIN flight.
• SID: Mark flights with ASAT times.
In addition, when clicking on the "+" sign to the left of the Atype box, detailed flight
information will be displayed. This information includes:
• ACReg: ACRegNo of flight
• TRWY: Take-off Runway.
• Link Flight: Link of flights
• SOBT: SOBT
• EOBT: EOBT
• TSAT: TSAT.
• Last TSAT Time: Last TSAT Time.
Right-clicking on the “Call Sign” box will display the flight history table.
7.6.4 Functionalities of TSAT Windows
In the “Choose Flight To Pin” box, select the flight according to CALLSIGN that needs
to be marked.
Note: You can select flights in the All Flights section below to PIN/UNPIN.
Image 88. Searching Flight to Pin in TSAT Windows +/-5

Click on “Sug On” button to show/not show flights with ASAT time.

ACV PMO – IT Team
Image 89. Dropdown list of flights

Suppose we choose flight BAV240, the Remark box will display the word PINNED to mark.
Flight BAV240 will be displayed first for recognition. When Remark PINNED, the flight will
not disappear even after +/-5 time has passed. Therefore, you have to take one more step and
click on the (x) in the flight search box to uncheck it.
Image 90. BAV240 is remakred.

For Other FLTs Within +/-30 Windows will display flights whose TSAT is +/-30 minutes
earlier/later than the current time. Enter the flight you want to search for in the search box.
Search by callsign will display the flight you want to search for.
7.6.5 TSAT + X
This is a function for SORATS only. SORATS will enter the X value as needed to calculate
the new TSAT value when the TOBT field is changed by manual input or from GH's system.
Detailed as follows:
• If TOBT_OLD - Now > 25p: TSAT = Max(TOBT_NEW, Now+25)
• If TOBT_OLD - Now <= 25p: TSAT = Max(TOBT_NEW, Now+X)
Note: Now is the same as the current time that TOBT is changed
Ex: Now = 1030
Case 1: TOBT_Old – Now > 25p

ACV PMO – IT Team
Current TOBT: 1100, X: 40, TOBT will be changed: 1110 → TOBT_Old = 1100, X = 40,
TOBT_New: 1110.
Because TOBT_Old – Now → 1100 – 1030 = 30 and 30 > 25 therefore:
Max(TOBT_NEW, Now+25) = Max(1110, 1030 + 25) = Max(1110, 1055) = 1110
So TSAT = 1110.
Case 2: TOBT_Old – Now <= 25p
If X is 4040, Current TOBT: 1045, TOBT will be changed: 1050 → TOBT_Old = 1045,
X = 40, TOBT_New = 1050
Because TOBT_Old – Now → 1045 – 1030 = 15 and 15 < 25 therefore:
Max(TOBT_NEW, Now+X) = Max(1050, 1030 + 40) = Max(1050, 1110) = 1110
So TSAT = 1110.
If X is 10, Current TOBT: 1045, TOBT will be changed: 1050 → TOBT_Old = 1045,
X = 10, TOBT_New = 1050
Because TOBT_Old – Now → 1045 – 1030 = 15 and 15 < 25 therefore:
Max(TOBT_NEW, Now+X) = Max(1050, 1030 + 10) = Max(1050, 1040) = 1050
So TSAT = 1050.
SORAT will manual input X value ( X is integer and from 0 to 60) which X is shown in the
image below:
Image 91. TSAT + X

7.7 TOBT Windows
The TOBT Windows page helps NORATS users in tracking flight milestones.
7.7.1 Overview
In the TOBT Windows +/-30 flights with TOBT’s earlier/later than the current time +/- 30
minutes will be displayed.

ACV PMO – IT Team
Image 92. TOBT Windows +/-30 minutes interface

In the Other FLTs Within +/-90 Windows flights with TOBT earlier/later than the current
time +/- 90 minutes will be displayed.
Image 93. TOBT Windows Other FLTs Within +/-90” interface

TOBT columns:
• AType: Aircraft Type
• Callsign: FlightNo according to ICAO code or IATA code
• Des: Destination
• FLTST: Flight Status
• DRWY: Depature Runway
• S/E/OBT: SOBT, EOBT, TOBT. Order from lower to higher: SOBT → TOBT
• TOBT: TOBT
• TOBT Time: Last time that TOBT was changed .
• DPARK: Depature Park
• ARDT, TSAT, CTOT, TTOT: Flight’s Time
• Remarks: Flight Remark.
ACV PMO – IT Team
In addition, when clicking on the "+" sign to the left of the Atype box, detailed flight
information will be displayed. This information includes:
• DRWY: Depature Runway.
• Link Flight: Link Flights
• SOBT: SOBT
• FlightDate: Date base on Local Time or UTC Time)
• Last TOBT Time: Last TOBT Time.
• Last TOBT By: Last TOBT By.
• Last TSAT Time: Last TSAT Time.
• Last TSAT By: Last TSAT By.
Right-clicking on the “Call Sign” box will display the flight history table.
Image 94. History of flight in TOBT Windows..

7.7.2 PIN/UNPIN, Searching
In the “Choose Flight To Pin” box, select the flight according to CALLSIGN that needs to
be PINNED.
Image 95. Searching flight in TOBT Windows +/-30

ACV PMO – IT Team
Image 96. DropDown List Flights

Suppose we choose flight HVN245, the Remark box will display the word PINNED to mark.
Flight HVN245 will be displayed first for recognition. When Remark is PINNED, the flight will
not disappear even after +/-30 time has passed. Therefore, click on the (x) in the flight search
box to uncheck it.
Image 97. HVN245 is PINNED.

7.7.3 Alert
“TOBT Windows +/-30”
Case 1: If the TOBT of a flight is provided by the ground service unit's system (not
automatically calculated by the ACDM Portal system), TOBT will be turned to gray-yellow.

ACV PMO – IT Team
Image 98. Alert TOBT is inputted by GH’s system.

Case 2: If the TOBT is inputted manual by the user on the ACDM Portal system, TOBT will
be turned to red.
Image 99. Alert TOBT is inputted manual by user

Case 3: If the updated TOBT time is 5 minutes earlier than the current time, the ACDM
system will display red in the TOBT Time cell.
Image 100. Alert New TOBT is updated from 0 minutes to -5 minutes from the current time
Case 4: If the TOBT time is updated from 5 minutes to 10 minutes compared to the current
time, the ACDM system will display yellow-white in the TOBT Time cell.
Image 101. Alert New TOBT is updated from 5 minutes to 10 minutes from the current time
“Other FLTs Within +/-90”
If the flight has an ARDT time, the TSAT will turn to red.

ACV PMO – IT Team
Image 102. Alert when flight has ARDT time

7.8 System Status page
The FlightStatus page has function of tracking the last update of the Stakeholder’s systems
to the ACDM Portal. The Website will display a warning message (exclamation mark) if one of
StackHolder's systems fails to transmit data within 15 minutes. The Website will highlight to
notify if any system cannot transmit data within 15 minutes. This will help users (who are
delicated to monitor the system) understand and promptly fix system connection errors.
Noi Bai can monitor following systems: HGS, NIA, SMIS, VIAGS. As shown below, the
Website displays the warning message and highlighted in yellow for 2 systems of HGS and NIA.
This proves that the two systems HGS and NIA have not transmitted data to ACDM Portal in
15 minutes.

ACV PMO – IT Team
Image 103. System Status interface in Nội Bài

7.9 Alert Configuration Page
7.9.1 Overall introduction of Alert Config
Alert Configuration page has function to configure optional alarm times. Currently, it only
allows user to adjust configuration in case Alert Status is True. Editable fields: Parameter, Level,
Status. Only users have Administrator privilege can edit, others have view permission
Alert Configuration page interface as shown below:

ACV PMO – IT Team
Image 104. Alert Config interface

7.9.2 Alert Config Functionalities
Alert Config page has function to configure optional warning times and warning levels.
Configuration of alarm time:
In parameter column, click on and select time to adjust
Image 105. Interface of configuration “Alert when EOBT and SOBTdiscrepancy +/- 0 mins”
Configuration of Warning Level:
In the Color column, the warning level is divided into 3 categories based on the Level
column. As follows:
• Yellow and white (Color Code: ffffe0): normal (Level 1)
• Dark yellow (Color Code: c7c791): attention (Level 2)

ACV PMO – IT Team
• Red (Color Code: ff584c): urgent (Level 3)

Currently, the Color column is updated according to the Level column, so the Color column
cannot be customized, only be able to adjust in the Level column. For example, configure the
Level column in case "warning when EOBT time is different with SOBT", as shown below:
Image 106. Config Level column in “warning when EOBT is different with SOBT time”
Image 107. After config Level column in “warning when EOBT is different with SOBT time”
7.10 TSAT Windows for Pilot
7.10.1 Overview
The TSAT Windows for Pilot page is a page dedicated to pilots for the purpose of viewing
the necessary parameters by hand-held electronic devices such as Tables, phones. The TSAT
Windows for Pilot page has a feature to view pilot-specific data fields. These fields are
synchronized in real time. These fields include: TOBT, TSAT, ASRT, ARDT, ASAT, Depth
Park.
The default interface of the NIA TSAT Windows for Pilot page will be shown in the
following figure.

ACV PMO – IT Team
Image 108. NIA TSAT Windows for Pilot interface

7.10.2 The TSAT Windows for Pilot feature
Image 109. Converting UTC time to Local time toggle button interface
Item 1: The real-time clock that defaults to Local. If you want to change to UTC time, click
the convert toggle button next to it.

ACV PMO – IT Team
Item 2: The Flight Dropdown list. Pilot will click on the “Please Select Flight” box which
will display a drop-down list of flights. After that, pilot will drag the list to search for a flight or
enter flight information in the flight search box. After selecting the flight, the system will display
the FDE of the selected flight.
Attention: These flights are scheduled between -2 hours and +3 hours from the current time.
Image 110. Flights drop-down list interface

Item 3: The Countdown Timer. After the Pilot select flight, it will have two case.
Case 1: If the selected flight has TSAT, the countdown will active. The countdown will stop
when the selected flight updated AOBT.
When TSAT time later than current time larger than 5 min ( Example: TSAT: 0748, Current
Time: 0736), the countdown timer indicate orange.

ACV PMO – IT Team
Image 111. Countdown Timer turn organe

The countdown timer will turn to green when TSAT time from -5 min to +5 min compare
with Current Time (Example: Current Time: 0742, the countdown timer will turn to yellow when
TSAT from 0737 to 0747).
Image 112. Countdown Timer turn green

The countdown timer will turn to red when TSAT time sooner than current time larger than
5 min (Example: TSAT: 0730, Current Time: 0740)

ACV PMO – IT Team
Image 113. Countdown Timer turn red

Case 2: If the selected flight does not have TSAT or the select flight has AOBT, the
countdown timer set to “00:00:00”.
Image 114. TSAT Windows for Pilot interface after selected flight
Pilots can change the flight number and flight segment according to the IATA code by
clicking the toggle button on the right next to UTC switch button.
When a FDE of a flight data field is updated, the system will blink to indicate that the field
has been updated.
Example: Update TSAT to 1435 according to UTC time.

ACV PMO – IT Team
Image 115. Update TSAT to 1435 interface

7.11 TwoWay Monitor
7.11.1 Overview
TwoWay Monitor page is used to track the two-way data synchronization of Stakeholders.
The TwoWay Monitor page has function of tracking the last update of the Stakeholder’s systems
to the ACDM Portal. The Website will display a warning message (exclamation mark) if one of
StackHolder's systems fails to transmit data within 15 minutes. The Website will highlight to
notify if any system cannot transmit data within 15 minutes. This will help users (who are
dedicated to monitor the system) understand and promptly fix system connection errors
Image 116. TwoWay Monitor interface

7.12 Announcement
7.12.1 Overview
Only for Administrators.
Pages that view announcements are: Main Page, ACDM Flight Manage, TOBT Windows,
TSAT Windows and ACDM for Pilot.

ACV PMO – IT Team
The Images below illustrate the display of the announcement of the homepage and ACDM
Flight
Image 117. Main Page Announcement
Image 118. Flight Manage Announcement

7.12.2 Config Announcement
To Config Announcement, Access Main Page and click “System Announcement”.
s
Image 119. System Announcement button
ACV PMO – IT Team
The Dialog will appear. Choose or input information below:

• Base to announce.
• Type of announcement.
• Detail of announcement.
• Active / Disable this Announcement.
The Click “OK” to Confirm or “Cancel”
Image 120. Announcement Dialog

7.13 AutoLink Flights
7.13.1 OverView
The AutoLink Flights page is used for: automatically connecting two flights have flight
number, route, SIBT time, SOBT that had declared.
Ex: The ACDM Portal will link two flights TH230 – TH9314 (SIBT:1045 and SOBT: 1155)
automatically when ACDM Portal received information of them.
The interface of the page is as shown below::

ACV PMO – IT Team
Image 121. Auto Link Flight interface

7.13.2 Functions
(1) Add
Click “Add flight” then input information of flight. After input information, press Enter to
confirm Information or press ESC to Cancel.
Fields of information:
• ARR F.NO: Arrival Flight No
• DEP F.NO: Departure Flight No.
• ARR Route: Arrival Route.
• DEP Route: Departure Route.
• SIBT: Scheduled Inbound Time.
• SOBT: Scheduled Outbound Time.
• Active: Status

ACV PMO – IT Team
Image 122. Add flight.

(2) Edit
To Edit flight, left click to “Edit” then input information that needs to be edit. Press Enter
the confirmation or ESC to cancel.
Image 123. Edit Flight.

(3) Delete
To Delete flight, left click to “Delete” then press Enter the confirmation or ESC to cancel
Image 124. Delete flight.

7.14 Report KPI
7.14.1 Overview
This page supports user in synthesizing KPI reports according to each Airport own formula.
Go to Main Page → Report KPI

ACV PMO – IT Team
Image 125. Report KPI page interface

After entering the Report KPI page, user will select the time of the flights to compile the
report. Then click OK for the system to automatically synthesize.
Image 126. Select Range of time interface.

7.15 FDE Checking
7.15.1 Overview
The FDE Checking page is used to check the data information that StakeHolders send to
ACDM Portal and the results returned from ACDM Portal to StakeHolder.

ACV PMO – IT Team
For example, SMIS sends data TSAT 1736 and TSAT 1738 of VJ147 on DEC 11, 2023 to
ACDM Portal. However, ACDM Portal returns the result “OK” for TSAT 1738 data and the
result “Failed Network Issue”.
Note: The FDE page only checks data received from StackHolder at +/-24 hours from
the flight date.
Image 127. FDE Checking interface.

7.15.2 FDE Checking Instructions
• First, select the date at “Choose Date” so that the system can show flights on the selected
day.
• Next, select the flight you want to look up at “Choose Flight”. The system will synthesize
arrival or departure information fields depending on the selected flight.
• Next, select the information field to look up at “Select FDE”.
• Next, select the information source to send to ACDM Portal at “Select InputSource”. If
all sources are selected, leave it blank.
• Finally click “FIND” to look up. The system will return results as shown in Figure 119.
Image 128. FDE Checking Instructions

ACV PMO – IT Team
Image 129. FDE Checking Result..

The results returned are as follows:
InputSource: Data source received from StakeHolder. For example: SMIS, ADSB...
Pack Data: What values does the data received from StakeHolder have?
Pack Response: Data returned to StakeHolder after receiving data. For example: “OK!” if
the ACDM Portal system receives the data, “Failed Network Issue” is due to a network error,
“Reject Reason: TOBT rejected because TOBT earlier than EOBT” is the system refuses to
receive the data TOBT being earlier than EOBT…
Date Create: Date and time of data sent from StakeHolder to ACDM Portal.

Technical Document of Acdm Portal Nia 2

Uploaded by

Copyright:

Available Formats

Technical Document of Acdm Portal Nia 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical Document of Acdm Portal Nia 2

Uploaded by

Copyright:

Available Formats

ACV PMO – IT Team

TECHNICAL DESCRIPTION OF ACDM PORTAL

Editor: Phan Truong Khoi – IT Specialist

ACDM Portal Technical Description 1

4.1.4 DPRK (Departure Parking Stand) ........................................................................... 39

ACDM Portal Technical Description 3

5.1 Two-way data synchronization at NIA .................................................................. 48

7.7.3 Alert ......................................................................................................................... 98

ACDM Portal Technical Description 5

ACDM Portal Technical Description 6

Image 36. Drop box to select date .......................................................................................... 60

Image 75. ACDM EXIT EXOT TABLE interface ................................................................. 84

Image 110. Flights drop-down list interface ........................................................................... 105

ACDM Portal Technical Description 9

ACDM Portal Technical Description 10

1. System Architecture of ACDM PORTAL on Private Cloud-Based

Image 1. NIA Private Cloud overall solution model

1.2.2. IP Planning for ACDM HCI

ACDM Portal Technical Description 12

• Backup speed does not depend on bandwidth of virtualization

Image 2. Data backup model NIA Private Cloud

ACDM Portal Technical Description 13

Image 3. Security model for ACDM System

Configuration of HCI for NIA Private Cloud/ACDM

Dedicated Private Cloud – DPC

Virtualization technology VMware

ACDM Portal Technical Description 14

RAM (GB) 256

Storage HDD SAS after RAID (GB) 4000

Domestic Bandwidth (Mbps) 250

International Bandwidth (Mbps) 5

Flow data Unlimited

Internal LAN connection 10Gbps

Backup Storage (GB) 40000

Table 1. Configuration detail of hardware infrastructure

ACDM Portal Technical Description 15

ACDM Portal Technical Description 16

1.5 Configuration of NIA-ACDM PORTAL servers

Table 2. Configuration of Servers for NIA-ACDM

ACDM Portal Technical Description 17

Image 4. Connections to ACDM Portal at NIA

ACDM Portal Technical Description 18

ACDM Portal Technical Description 19

ACDM Portal Technical Description 20

Image 5. Overview of data flow from SMIS synchronized to ACDM PORTAL

ACDM Portal Technical Description 21

Image 6. NIA – VATM Topology of ACDM Phase 1

ACDM Portal Technical Description 22

Image 7. Dataflow description from AMAN/DMAN to SMIS

ACDM Portal Technical Description 23

Decoding text files from VATM2 gateway.

Image 8. Dataflow diagram of ELDT/TSAT/TTOT/TRWY/LRWY pushing

ACDM Portal Technical Description 24

Image 9. Dataflow of decoding AMHS and pushing to SMIS database

ACDM Portal Technical Description 25

Image 12. Data Mapping from VJ to ACDM TestZone

ACDM Portal Technical Description 27

Hà Nội (HAN) According to each stakeholder For departure/arrival flights of HAN

Table 3. Token Information

Name Type Description