5 - GATES Industry Day.pptx
PPTX presentation 3 MB Posted
- Solicitation number
- FA4452-12-R-0002
About this file
GATES PM Presentation
View the file
Other files
Show all 38
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Global Air Transportation Execution System (GATES) Architecture
Cedric Mitchell
GATES PMO
Unrivaled Global Reach for America … ALWAYS!
Headquarters Air Mobility Command
What is GATES?
Mission: DOD’s single port automation system supporting movement of personnel and cargo worldwide in direct support of war fighters Enables in-transit visibility (ITV) critical to command and control Processes and manifests cargo and passengers supporting unit deployment, sustainment, and Defense Courier operations Supports DOD's ability to bill for movement Exchanges information with multiple data sources both internal and external to the DOD 19 Aerial Port GATES, 65 RGATES (approx.), DGATES ( < 99 ) 11,500+ Users (approx..)
Aerial Port = 8985; HQ = 2537; DGATES = 350
Common Misconceptions GATES is EVERYWHERE!
GATES is not at all airfields worldwide GATES data is replicated to all sites Only Reference data is replicated to all sites Data is ONLY sent to destinations associated with the data GATES database is static GATES database is transactional (based on events) GATES Is Down!!
Distributed architecture prevents complete system outage GATES “down” for a user does not = system down Relative to user perspective…HQ / Aerial port / Water port
TACC
Users Aerial Port Users
TMO
Users
SDDC OPS
Users Surface Terminal Users
USTC/J3
Users
GATES
Functional Architecture
Integration External Systems (>50 systems)
Reports
Standard Adhoc Query Mission/Manifest Management Passenger Reservation
Process
Signup Manifest Transportation Management/In-Transit Visibility Uniques Added
BPS
functions Norfolk functions
Cargo
Cargo Processing Terminating Cargo Processing Originating
Truck Dock Air Terminal
Surface Terminal Rail Head Staging Areas Specialized Functions Customs Documentation
POV
Stevedore Services Accountability
Air & Water Interfaces
CMOS
TCAIMS II
Disk File Based
DSS
GEX
PIPELINE
FACTS
TRACKER
RF-ITV SERVER v5.0
IGC
TMDS
GATES Air Interfaces
Disk File Based
AALPS
DCAPES
LOGMOD
JAMMS
DCBS (ASIFICS)
TCAIMS II
APIS
MMHS
MEIS
MDSS II
SMS
BMC (Web Query)
Systems in Green could potentially become EDI interfaces using a version of the 858 transaction.
Systems in Blue have unique data requirement and are not good candidates for EDI.
AALPS: Automated Air Load Planning System ABDM: Automated Business Decision Model APIS: Advanced Passenger Information System ASIFICS: Airlift Services Industrial Fund Integrated Computer System CMI: Commercial Movement Interface CMOS: Cargo Movement Operations Systems DCAPES: Deliberate and Crisis Action Planning and Execution Segments DEAMS: Defense Enterprise Accounting and Management System DS2T: Deployment and Sustainment Support Tool DSS: Distribution Standard System EDQMS: Enterprise Data Quality Management System FACTS: Financial and Air Clearance Transportation System GDSS: Global Decision Support System GEX: Global Exchange (e-Business Server) GTN: Global Transportation Network ITRAM: International Traffic Management System LOGMOD: Logistics Module MMHS: Mechanized Materials Handling System Pipeline:
RF-ITV Server: Radio-Frequency Intransit Visibility Server SMS: Single Mobility System TC-ACCIS: Transportation Coordinator’s Automated Command and Control Information System TCAIMS II: Transportation Coordination’s Automated Information Management System II TMDS: Table Management Distribution System Tracker:
GATES Water Interfaces
GATES
AWRDS
MDSS II
Disk File Based
NLAC
CAB
MTMS
AAFES
FISC
ICODES
IBS **
EDCL v5.0
IRRIS
GFM
PAT
DORRA
iSDDC
TOPS-DPS
DPMS
MSC
TIPS
EDC-v5.0
Systems in Green could potentially become EDI interfaces using a version of the 858 transaction.
Systems in Blue have unique data requirement and are not good candidates for EDI.
AALPS: Automated Air Load Planning System ABDM: Automated Business Decision Model APIS: Advanced Passenger Information System ASIFICS: Airlift Services Industrial Fund Integrated Computer System CMI: Commercial Movement Interface CMOS: Cargo Movement Operations Systems DCAPES: Deliberate and Crisis Action Planning and Execution Segments DEAMS: Defense Enterprise Accounting and Management System DS2T: Deployment and Sustainment Support Tool DSS: Distribution Standard System EDQMS: Enterprise Data Quality Management System FACTS: Financial and Air Clearance Transportation System GDSS: Global Decision Support System GEX: Global Exchange (e-Business Server) GTN: Global Transportation Network ITRAM: International Traffic Management System LOGMOD: Logistics Module MMHS: Mechanized Materials Handling System Pipeline:
RF-ITV Server: Radio-Frequency Intransit Visibility Server SMS: Single Mobility System TC-ACCIS: Transportation Coordinator’s Automated Command and Control Information System TCAIMS II: Transportation Coordination’s Automated Information Management System II TMDS: Table Management Distribution System Tracker:
GATES Architectural Concept
GATES Central Site
RGATES
“Child Site” GATES Site “Parent Site”
GATES
Alt Site External Interfaces
GATES Site “Parent Site”
RGATES
“Child Site”
DGATES
RGATES
“Child Site”
RGATES
WPS Site
GATES Site “Parent Site”
RGATES
“Child Site”
DGATES
DGATES
RGATES
WPS Site
RGATES
WPS Site
Central Site Disaster recovery site Identical hardware & software at Scott & DECC Automatic failover for user functionality Core functionality can be active at either site Failover without user intervention New releases can be fielded without interruption to users
L00_C1 D00_C1
OPC
OPDW
GATES Con Analysis Server Oper/prod Database
Replication Server GATES Central Site Replication GEMS Server
RSSD
Database Sybase EP
Cluster Pair
OPREP
OPCA
OPOS
OPEA
GATES Application Server
J2EE
Apache Instance GATES History/Stage Database
Cluster Pair Cluster Pair
ALTSEC
GATES Audit Archive Server Security
RGATES Reference Server
GATES Audit Archive Server Security Database RGATES Reference Server
GATES-SEC
Scott
DECC
OPCDP
ALTCDP
GATES ID Replication Server Open Switch Server
Replication Server
RSSD
Database Open Switch Consolidate Open Switch Con_analysis Open Switch Data Pro Open Switch History Oper/Prod Database Stage Database External I/F Process Water Port ODBC Database Central Site Consolidate Server
ALTC
ALTDW
GATES Con Analysis Server Oper/prod Database
Replication Server GATES Central Site Replication GEMS Server
RSSD
Database Sybase EP
ALTREP
ALTCA
ALTOS
ALTEA
GATES Application Server
J2EE
Apache Instance GATES ID Replication Server Open Switch Server
Replication Server
RSSD
Database Open Switch Consolidate Open Switch Con_analysis Open Switch Data Pro Open Switch History
GATES Data Pro Server Oper/prod Database
J2EE
Server Apache Instance
GATES Data Pro Server Oper/prod Database
J2EE
Server Apache Instance
IQ
Server History Database trans Database Replication Server
RSSD
Database
GATES History/Stage Database
Oper/Prod Database Stage Database External I/F Process Water Port ODBC Database Central Site Consolidate Server
IQ
Server History Database trans Database Replication Server
RSSD
GATES Central Site Central Site:
At Scott AFB.
Hot backup at DECC St Louis.
Central database of all GATES traffic.
GATES interface with external interfaces.
Replicates necessary information to other GATES sites.
GATES Central Site
RGATES
“Child Site” GATES Site “Parent Site”
External Interfaces
DGATES
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment) Administrative traffic (e.g. NetIQ (system monitoring), Intruder Alert, Enterprise Security Manager)
GATES Aerial Ports
GATES (UNIX):
Major fixed aerial port.
“Parent site” for RGATES child sites.
Replicates all data to central site and necessary information to other GATES and child RGATES sites.
“Child Site” GATES Site “Parent Site”
External Interfaces
(e.g., Ramstein)
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
RGATES Aerial Ports RGATES (Windows):
Fixed or deployed aerial port.
Connected to “parent site”.
All data sent to “parent site” & sent from there to receiving site.
Typically supports a single location.
“Child Site” GATES Site “Parent Site”
External Interfaces
(e.g., Bagram, Bahrain/Incirlik)
DGATES Aerial Ports Deployed GATES (DGATES – MS Windows):
Intended to be temporary.
Connects directly to central site.
All data sent to central site and sent from there to receiving site.
Can take identity of new locations not serviced by other GATES, RGATES or DGATES sites.
“Child Site” GATES Site “Parent Site”
External Interfaces
(e.g., Tsunami Relief)
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
Typical GATES Aerial Port (19 Locations)
FIDS
Display
Wireless VPN
Hand Held Terminals
GATES VPN
AIT Server
GATES
RFID Encoder
ID Card Reader
Boarding Pass Printer
Multi-shipping Label Printer Kiosk
Hip Label Printer GATES Specialized Equip (wired)
GATES Specialized Equip (wireless)
GATES Client External Source
UNIX
Typical RGATES Port (Scalable)
FIDS
Display
Wireless VPN
Hand Held Terminals
GATES VPN
AIT Server
GATES
RFID Encoder
ID Card Reader
Boarding Pass Printer
Multi-shipping Label Printer Kiosk
Hip Label Printer GATES Specialized Equip (wired)
GATES Specialized Equip (wireless) Windows
Client External Source
RGATES Water Ports RGATES (Windows):
Fixed or deployed aerial port.
Connected to “central site”.
All data sent to “central site” & sent from there to receiving site.
Typically supports a single location.
External Interfaces
DGATES
“Carry Away” (e.g., Beaumont)
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
D/R GATES Communications Basics D/RGATES Server Client on same PC Client connected via a LAN from another PC Servers require a TCP/IP address accessing NIPRNET LAN/MAN connected to NIPRNET INMARSAT terminal Dialup modem Other satellite terminal Data replication secured by SSL Other WAN connections secured by VPN (Currently only implemented at specific sites)
Fault Tolerance
GATES architecture degrades gracefully Data entry continues during network outages From scanned barcodes, passenger counts, etc All data queued until communications are restored Outage duration causes data latency to IGC
CONUS Aerial Ports
Travis Little Rock Ft Carson Offutt Peterson March Kelly San Diego McChord
Seattle
Charleston Jacksonville
GITMO
McDill Patrick Pope Soto Cano
Hickam Christchurch Bucholz Pago Pago Wake Island Richmond Alice Springs
McGuire Ft Campbell Westover Andrews Baltimore Thule Lajes Field Dover
Louisville Ft Mead Elmendorf
Eielson Norfolk
STL / Scott Wright Patterson Central
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
CONUS Water Ports
Southport Charleston Jacksonville Beaumont Seattle Concord Ft. Eustis Cheatham Guantanamo Bay Pearl Harbor Port Hueneme
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
OCONUS Aerial Ports
Al Udeid Al Dhafra Al Sahra Bagram Baghdad Al Asad Bahrain Kandahar Eskan Village Ali Al Salem Balad Kirkuk Kabul Kuwait Sharona Tall Afar Tallil
Ramstein Djibouti Cairo Fujairah Incirlik Amman D Ben Gurion Jebel Ali Manas Moron Pristina Souda Bay Spangdahlem Thumrait Osan
Kimhae Kunsan
Yokota Fukuoka Misawa Diego Garcia Iwakuni Paya Lebar
Kadena Utapao Manila Zamboanga Bangkok Clark Field Rota
Aviano
Andersen
Naples
Mildenhall
Sigonella
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
OCONUS Water Ports
Kwajalein Bremerhaven Rotterdam Izmir Kuwait City Lajes Naples Manama Mannheim Mildenhall Piraeus Okinawa Pusan Yokohama Singapore Rota Livorno Marianas
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
How GATES Connects
GATES Site “Parent Site”
IGC
External Interfaces
GATES Site “Parent Site”
DGATES
RGATES
GATES Site “Parent Site” GATES Site “Parent Site”
RGATES
“Child Site”
RGATES
“Child Site”
RGATES
“Child Site”
DGATES
DGATES
RGATES
“Child Site”
RGATES
“Child Site”
“Child Site”
Black lines show logical network connectivity between sites for data communications Central site and all GATES sites communicate directly between each other RGATES sites communicate directly to their parent site DGATES sites communicate directly to the Central site
Other comm not shown:
Replication of security information to the Central site All Sites may initiate specific queries against the data at the Central site (e.g. track and trace a shipment)
Data Replication Between Central, GATES, RGATES, DGATES Site
Central Major
GATES
Port
RGATES
Port
DGATES
Site Type User Functionality External Systems Interface Here Yes Material Mgt Handling Sys No No Traffic Mgt. Office/ Track and Trace/ GATES Enterprise Management Services PAX/Cargo Processing/Diskette Data Replication Real Time Real Time 5-15 min (or manual) to Parent 5-15 min (or manual) to Parent Parent N/A N/A Central Major GATES Port Central
Database Content All Data Reference data, Local Port + Supported Child locations Reference data + Local Port Reference data + Local Port PAX/Cargo Processing/Diskette PAX/Cargo Processing/Diskette
Server
SUN
SUNFIRE 25K
SUN
SUNFIRE
4800/v880
Windows OS Windows OS
GATES Water Port Transaction (from Requirement to ITV/TAV) Shipper creates
ETRR
IBS
Sustainment Unit
GATES
IBS
Sustainment Unit
IBS
CSS
Skeleton Record **ETRR = Export Traffic Release Request
DSS
ATCMD
SDDC User
User may override or intervene in creation/completion of Skeletal Record
TCMD
non-MRM15
**TCMD = Transportation Control & Movement Document Updated Shipping Instruction
In-Transit Visibility Total Asset Visibility
GATES Span of Control
LAN/
MAN
LAN/
MAN
GATES Controlled
Base Controlled
NOSC Controlled
Commercial Controlled
AFNOC Controlled
Communications Challenges NIPRNET communications outages Power Configuration Infrastructure Saturation Site infrastructure outages DNS resolution (global AMC DNS name vice local DNS name)
TAKE AWAYS
Complexity 11,500 user accounts (Ports, TMOs, Embassies, etc.)
Users processing data for 129 active aerial ports Users from 180 “Traffic Management Offices” Users from 271 aerial ports and Command/Service staff user locations 35+ user security roles 1 day Tracked 1,040 mission sorties and generated manifests for 3,121 passengers, 3,738 pallets, and 2,195 pieces of loose cargo worldwide.
Hardware includes: laptops, servers, HHTs, card readers, special printers, RFID, VPNs, etc.
Rationale for architecture Gracefully degrades Central Site Failover Tolerates NIPRNET outages Low WAN bandwidth (tolerant of high latency)
TAKE AWAYS
GATES is Fielded Worldwide 19 Major Aerial Ports 65 RGATES (Remote GATES) Sites 11 DGATES (Deployed GATES) Active Sites Across Commands (AMC, ACC, ANG, ARC, AETC, USAFE, PACAF) Across Services (Air Force, Navy, Army, Marines) Diverse Functional Community Aerial Ports (A4TI) Defense Courier System (USTC/J3) Worldwide Port System (SDDC/G9)
Global Air Transportation Execution System (GATES) Architecture
Cedric Mitchell
GATES PMO
Headquarters Air Mobility Command image3.jpeg image4.jpeg image5.jpeg image6.wmf image7.jpeg image8.jpeg image9.png image15.jpeg image16.jpeg image17.jpeg image18.jpeg image19.png image20.jpeg image10.jpeg image11.jpeg image12.jpeg image13.jpeg image14.jpeg image21.jpeg image22.jpeg image23.emf image24.wmf image25.wmf oleObject3.bin
SA
SWA
image1.png image2.png
File details come from the government source that posted it. Updated .