Smart Hangar Management System Solution
I System Topology Diagram
II System Composition
The system topology is shown in the figure above, which mainly realizes the audio/video command & dispatch of 34 hangars by the command center, as well as the monitoring of the operating status of each hangar subsystem.
The command center is deployed with an IDM unified command & dispatch host, a command server, an IDM MCC-T intelligent dispatch console, a management host, a video surveillance server, 2 sets of IDM IOTMP 2.5G IoT integrated service optical transmission equipment, and 2 sets of 48-port Ethernet switches.
At the remote end, 34 hangars share one intelligent control system weak-current integrated cabinet for every 2 hangars, with 1 set of IDM IOT3500 2.5G IoT integrated service optical transmission equipment deployed.
The command center and each intelligent control system weak-current integrated cabinet are interconnected via optical fiber. The remote IDM IOT3500 2.5G IoT integrated service optical transmission equipment aggregates and accesses the command center IDM IOTMP 2.5G IoT integrated service optical transmission equipment through a 2.5G optical line, realizing the upload of hangar audio/video signals, flight parameter business data, dispatch telephones, and status data of each hangar operating subsystem, as well as the transmission of downlink commands.
2.1 Command Center System Functions
2.1.1 IDM MCC-T Intelligent Dispatch Console
(1). Supports the center end to select any hangar for broadcasting;
(2). Supports the center end to group multiple hangars into one intercom group for simultaneous broadcasting;
(3). Supports the center end to monitor any hangar. Also supports programmed patrol monitoring;
(4). Supports hangars to call the center end via buttons and conduct intercom;
(5). Supports triggered broadcasting associated with hangar IoT detection events; after a hangar is triggered, broadcasting can be played to both the hangar and the center end simultaneously;
(6). Supports scheduled playback file lists for all terminals;
(7). Supports real-time inserted voice with priority higher than file broadcasting;
(8). Through the center end's telephone gateway, supports intercommunication between hangar broadcasting and the telephone system;
(9). Supports audio gateway access, capable of playing CD, analog microphone, and analog mixer audio;
(10). Automatic broadcasting modes include scheduled trigger, event trigger, loop trigger, etc.
2.1.2 IDM MCC Unified Command & Dispatch Host
The IDM unified command & dispatch host is a multi-functional unified communication platform integrating multiple system function modules such as IP broadcasting system, audio/video intercom, IP telephone system, and program-controlled switching.
The IDM unified communication platform can perform unified centralized configuration management and audio/video communication service support for local or remote network audio devices.
All functions are realized through PC professional client software, APP terminal application software, and other products, including voice, video, data, command, and plan dispatch functions. It can also achieve seamless integration with different communication systems through professional gateway service modules, providing interconnection and interworking of data/image/voice for various terminals and communication command platforms. Specific functions are as follows:
l Voice Dispatch
l Video Dispatch
l Video Surveillance
l Intercom
l Voice/Video Conference
l Voice/File Broadcasting
l Message Command Dispatch
l Plan Dispatch
l GIS Dispatch
l Call Record Management
l Multimedia Record Management
l User Resource Management
l Trunk/Routing Management
l Unified Terminal Parameter Management
l System Permission Management
2.1.3 Architecture Description
(1). Unified Communication System
Installed on the local server or service end, completing functions such as terminal device configuration, registration, grouping, and management;
(2). Unified Communication Platform
A graphical interface operation platform, installable on Windows and Linux operating platforms. Through real-time communication with the unified communication system, hangar administrators/operators use this platform to view device status and perform functions such as single-point or area calling, broadcasting, conferencing, and video linkage;
(3). Broadcast/Intercom APP
A graphical interface operation platform supporting Android installation. Provides convenient functions for mobile personnel such as calling, broadcasting, and viewing device status through this APP;
(4). Access Terminals
Analog telephones, SIP phones, SIP network speakers, SIP wall-mounted speakers, SIP sound columns, network voice intercom, network video intercom, broadcast gateways, mobile APPs, network cameras, etc.
2.1.4 System Functions
(1). Supports the center end to select any hangar for broadcasting;
(2). Supports the center end to group multiple hangars into one intercom group for simultaneous broadcasting;
(3). Supports the center end to monitor any hangar. Also supports programmed patrol monitoring;
(4). Supports hangars to call the center end via buttons and conduct intercom;
(5). Supports triggered broadcasting associated with hangar IoT detection events; after a hangar is triggered, broadcasting can be played to both the hangar and the center end simultaneously;
(6). Supports scheduled playback file lists for all terminals;
(7). Supports real-time inserted voice with priority higher than file broadcasting;
(8). Through the center end's telephone gateway, supports intercommunication between hangar broadcasting and the telephone system;
(9). Supports audio gateway access, capable of playing CD, analog microphone, and analog mixer audio;
(10). Automatic broadcasting modes include scheduled trigger, event trigger, loop trigger, etc.
2.2 IoT Dispatch Platform
2.2.1 Command Server
This server mainly completes the issuance and service functions of remote control commands from the command center to hangars (indicator lights, doors, main power supply, light switches, etc.).
2.2.2 Composition and Solution
The IoT-based hangar data collection service platform realizes functions such as data collection, protocol conversion, data processing, and visualized display of network devices, sensor perception devices, and various control devices within the hangar. It achieves the goals of full digitalization, virtualization, intensification, and intellectualization of hangar facility and equipment management, automatic collection of key operating data (power supply devices, fueling devices, equipment switches, electricity consumption, water consumption), remote real-time monitoring, and intelligent early warning, strengthening real-time supervision of hangar operation status: through analysis and data mining of various operating data at the hangar site, it provides functions such as real-time operation monitoring, process control, operation simulation, operation anomaly early warning, optimized operation decision-making, and risk analysis for hangar operation management.
Establish a perception layer system. The perception layer devices mainly include power supply devices, fueling devices, main power supply, oil pumps, oil tanks, fans, online instrumentation, automatic control systems, and temperature/humidity environment monitoring sensors, which form the foundation of the IoT technology architecture. Through devices such as intelligent IoT gateways, data protocol conversion is realized, performing conversion of multiple communication interfaces and communication protocols, realizing automatic collection of operating data from various PLCs and drivers, and establishing data communication with various PLCs and drivers through IoT protocols, ultimately forming a complete perception layer system.
The perception layer provides a large amount of operating data from equipment, facilities, and IoT sensors. Only by deeply mining the relationships among various data and reasonably utilizing these data can the establishment of the IoT system be meaningful, i.e., the IoT dispatch platform. Firstly, through preliminary processing and display of various data from the perception layer, it realizes over-limit alarming of real-time hangar operating data; secondly, through summary calculation of production operation data, it realizes various charts for daily hangar operation management, facilitating management personnel in summarizing and analyzing daily operation conditions; through in-depth analysis and mining of hangar operating data, it realizes various anomaly warnings, optimized dispatch analysis, and comprehensive decision-making guiding hangar operation management, as well as equipment analysis, cost analysis, and risk analysis guiding airport comprehensive operation decision-making. The IoT dispatch platform can perform flexible programmed control of data collection devices and controls within the hangar.
2.2.3 System Functions
Remote operations can be performed at the center end, and local operations can also be performed through touchscreen control consoles provided in the hangar; for all collectors, location, name, IP address, range, unit, collection rate, etc. can be set, and current data and historical data can be viewed; for all controllers, manual control, automatic control, and switching rules between manual and automatic can be set; control parameters can be subscribed, and control rules can be compiled; it has big data processing functions for hangar parameter collection and operation, such as big data early warning, data statistics, and hangar situation display.
Remote surveillance management realizes automatic real-time collection and remote real-time transmission of operating data and equipment operation status data in automatic control systems such as hangar fueling and power supply, incorporating early warning and alarm functions, displaying over-limit alarms of various data intuitively through flashing, sound, pop-up message boxes, SMS, etc. At the same time, alarm handling plans and historical similar alarm prompts are integrated into alarm handling, making alarm handling intelligent and improving handling efficiency, realizing comparative analysis of real-time collected data, intuitively displaying data fluctuation through curves, and allowing viewing of historical data at any time.
Equipment asset management revolves around business management contents such as archives ledgers, maintenance, repair, overhaul and technical renovation approval, and spare parts inventory in daily equipment management, forming an informatized equipment management system. At the same time, various operating data of equipment can be summarized and statistically processed, forming various analysis and prediction management.
Decision analysis management invokes various operating data stored in the system to realize analysis and monitoring of equipment, energy consumption, cost, etc. Through various charts such as tables, flip boards, line charts, bar charts, scatter plots, pie charts, funnel charts, radar charts, Sankey diagrams, parallel coordinate plots, maps, word clouds, waterfall charts, embedded web pages, rich text, and dual Y-axis charts, analysis of hangar data monitoring items can be performed.
The IDM IoT dispatch platform can perform flexible programmed control of data collection devices and controls within the hangar.
(1) Remote operations can be performed at the center end, and local operations can also be performed through touchscreen control consoles provided in the hangar;
(2) An operation button is assigned to each collector and controller on the dispatch console;
(3) For all collectors, location, name, IP address, range, unit, collection rate, etc. can be set, and current data and historical data can be viewed;
(4) For all controllers, manual control, automatic control, and switching rules between manual and automatic can be set; control parameters can be subscribed, and control rules can be compiled;
(5) It has big data processing functions for hangar parameter collection and operation, such as big data early warning, data statistics, and hangar situation display.
Hangar control contents include:
(1) Hangar lighting control, supporting remote or local control, with detection and alarm based on current or illuminance. Supports linkage control with personnel entry and indoor illuminance;
(2) Signal light control for aircraft entering and exiting the hangar, supporting remote or local control, with detection and alarm based on current or illuminance. Supports local and center-end control;
(3) Monitoring and control of the hangar main power supply, supporting current detection and voltage detection methods. Can be remotely or locally controlled;
(4) Parameter monitoring of linear power supply devices;
(5) Parameter monitoring of linear fueling devices;
(6) Reserved flight parameter upload interface; (using Gigabit Ethernet or USB interface, software only performs security confirmation)
(7) Integrated integration of video surveillance system; supports PTZ operation of cameras, as well as recording, query, etc.;
(8) For common functions and operations, menu-based prompts are provided; screen refresh time shall not exceed 2 seconds;
(9) When a single fault occurs, the alarm response time of the fault screen shall not exceed 5 seconds;
(10) After a control command is issued, the response time for on-site equipment to begin executing the action shall be less than 2 seconds;
(11) Provides help and operation guidance functions, enabling users to complete various operations through this feature;
(12) Provides information on pre-programmed time-based or event-driven automatic control application software, including: programming content, programmer name, programming time, modifier name, modification time, and modification content;
(13) Records system operations, confirmation times of various alarm messages, and names of confirming personnel;
(14) Shall provide detailed descriptions of the system software architecture and working principles, such as central control software and controller control software; the software shall adopt a modular component design that allows flexible assembly; the design principles and structure of the system real-time database shall be described in detail.
(15) The software shall adopt a layered, user-oriented, open, standardized, and modular architecture to facilitate system function expansion and upgrades, with strong fault tolerance and short response times.
(16) The application software shall include at least the following functions: graphical operation, alarm management, programming, historical data recording and management, report generation, trend chart analysis, and system management.
The graphical operation function shall display engineering floor plans, equipment distribution diagrams, monitored system diagrams, and other related graphics in color. The legends shall be simulated representations of actual equipment, with real-time dynamic data of the system or equipment displayed adjacent to the legends. Equipment statuses such as on/off, manual/automatic, and fault conditions, as well as parameters including temperature, humidity, and power consumption, shall be presented through graphics, animations, reports, and other means. All equipment shall be controllable and monitorable online using only a keyboard or mouse, without interrupting normal system operation. An integrated voice prompt platform shall provide timely prompts for various operations and alarms in standard Mandarin.
2.3 IoT Data Collection Services
2.3.1 System Functions
This system is primarily based on IoT technology and is structured into four layers: the on-site infrastructure layer, the basic support layer, the business management layer, and the business application layer.
The infrastructure layer comprises multiple types of monitoring equipment, including environmental monitoring, fire protection monitoring, and water/electricity/gas monitoring devices. It utilizes the Raytrans IDM IOT3500 2.5G IoT integrated service optical transmission equipment to collect and forward data from various sensing devices in real time. This layer also includes the network communication sub-layer, which is responsible for data transmission over IP networks based on the MQTT IoT protocol, including LoRa networks, Wi-Fi networks, Ethernet LANs, etc., enabling network access and transmission.
The business management layer primarily consists of the IoT data collection service platform. The basic database is responsible for real-time storage and query of massive data, with extremely high storage and query performance. The IoT data collection service platform is responsible for real-time data display, event alarms, data monitoring, emergency response, and system integration. Various management application systems can be developed on this platform, such as environmental monitoring systems, remote intelligent water/electricity/gas monitoring and management systems, and fire protection monitoring and early warning systems, with integration of GIS systems, information publishing platforms, etc.
The business application layer mainly involves specific applications, such as online monitoring systems for power supply/fuel supply devices, environmental monitoring systems, remote intelligent water/electricity/gas monitoring and management systems, fire protection monitoring and early warning systems, and GIS visualization big data centers.
Through the organic integration of the above four layers, automatic sampling and online monitoring of the hangar sensing layer can be achieved; hangar IoT monitoring data is collected and automatically transmitted to the system platform layer; the platform layer performs data aggregation, organization, and comprehensive analysis; monitoring information is transmitted to the management application layer; the management application layer provides visualized data monitoring display and data analysis functions.
The system mainly provides capabilities including device access, device management, and rule engine.
2.3.1.1 Device Access
The IoT data collection service software supports massive device connections to the cloud, enabling stable and reliable two-way communication between devices and the IoT data collection service software.
| Function | Description |
|---|---|
| Device Access | Provides cross-platform porting guidance, supports device access across multiple platforms, and provides device-side SDKs, drivers, etc., to facilitate easy access for different devices and gateways. |
| Message Communication | Provides product and device message communication, facilitating management of device-to-server communication and simplifying authorization operations. |
| MQTT Protocol Support | Provides device-side SDKs for multiple protocols, meeting both the real-time requirements of long connections and the low-power requirements of short connections. |
| Cloud-to-Cloud Integration | Provides cloud-to-cloud integration SDKs to rapidly build bridging services, establishing two-way data channels between devices and the IoT data collection service software. |
2.3.1.2 Message Communication
The IoT data collection service software supports the configuration of rules through the following functions to achieve synchronization, transformation, filtering, and storage of communication messages among devices, servers, and the IoT data collection service software.
| Function | Description |
|---|---|
| Server-side Subscription | Subscribes to one or more types of messages from all devices under a product. The server can obtain subscribed messages through AMQP clients or Message Service (MNS) clients. |
| Data Flow | The IoT data collection service software forwards specified fields of specified messages to destinations according to configured data flow rules for storage and computing processing. |
| Scenario Linkage | By configuring simple rules, device data can be seamlessly forwarded to other devices, enabling device linkage. |
| RRPC Communication | Provides both RRPC and PUB/SUB communication modes to meet requirements in different scenarios. Among them, PUB/SUB is message routing based on Topics. |
| Broadcast Communication | Supports broadcast communication, i.e., sending messages to all devices under a specified product (devices do not need to subscribe to the broadcast Topic), or to all devices subscribed to a specified Topic. Online devices can receive broadcast messages sent by the server. |
2.3.1.3 Device Management
| Function | Description |
|---|---|
| Thing Model | Provides device thing models to simplify device application development. |
| Digital Twin | Dynamically presents business models of the physical world in digital form, performing real-time collection, computation analysis, monitoring, and statistics of physical entity information. |
| Data Parsing | Supports transparent transmission of data in binary format to the user's own server without storing device data, thereby ensuring data security and controllability. |
| Tags | Enables custom labeling of products, devices, or groups for flexible management; supports geographic location tags to mark device locations and set GeoLocation attribute values for devices. |
Implementing device classification and cross-product device management.
|
|
|
|
|
Quickly search for devices that meet specified conditions using SQL-like statements.
|
|
|
Simultaneously initiate property settings, asynchronous service invocations, and custom tasks to multiple devices.
|
|
|
Provides a device shadow caching mechanism that decouples devices from applications, addressing the pain point of unreliable communication over unstable wireless networks.
|
|
|
Provides the capability to store, download, and delete device files.
|
|
|
Solves the problem of resource-constrained embedded devices being unable to obtain server time in real time.
|
|
|
Implements management of sub-devices and the topological relationships between sub-devices and gateways, as well as monitoring and O&M of sub-devices.
|
|
|
Implements cross-region, cross-instance, and cross-account device distribution, reducing device onboarding costs.
|
|
Time Series Data Storage Management
|
Provides in-instance data storage capabilities, facilitating storage and real-time access to massive device data for users.
|
2.3.1.4 Monitoring and O&M
|
Feature
|
Description
|
| --- | --- |
|
|
Performs real-time monitoring and Cloud Monitor alerting on metrics related to devices, messages, thing models, and rule engines.
|
|
|
Displays a geographic heat map distribution of devices, allowing you to intuitively and quickly understand the status of all devices.
|
|
|
Directly sends commands from the IoT data acquisition service software console to devices to debug device-side functions.
|
|
|
Simulates real devices establishing connections with the IoT data acquisition service software, uses simulated data to test the communication functions between the IoT data acquisition service software and the device side, and locates issues.
|
|
|
Displays server-side operation logs and device local logs to help you locate issues and perform fault analysis.
|
|
|
Empowers remote device upgrade capabilities.
|
|
|
Remotely updates device configuration information such as system parameters and network parameters online.
|
|
|
Processes alert information triggered by scenario linkage rules in the rule engine.
|
|
|
Enables remote connection to IoT data acquisition service software devices behind firewalls by establishing a WebSocket channel between the access end and the device end.
|
2.3.1.5 Data Governance
Provides a metadata-driven one-stop data governance platform, realizing unified management of全域数据 (all-domain data), intelligent extraction of data standards, full lifecycle management of data from collection and ingestion to application and request, dynamic tracking of data lineage, precise control of data security, and circulation and management of data assets. This helps hangar management develop, manage, share, and use data in a comprehensive, automated, and intelligent manner.
2.3.1.6 Big Data Visualization
(1). Multi-Type Data Source Configuration
Supports data modeling for offline computing; supports directly pulling data from data warehouses and data storage; uses SQL for offline data computation, with data automatically imported into intermediate tables.
(2). Data Exploration
Allows users to directly connect to their own data sources; supports multiple database types such as Generic SQL, Palo, ElasticSearch, and InfluxDB; uses interactive Notebooks to explore data.
(3). Rich Chart Presentation
Supports basic charts as well as multiple chart types such as funnel charts, Sankey diagrams, box plots, pivot tables, and maps; flexible chart style configuration; time window linkage with a unified time region control that automatically pulls the latest data for display every day.
2.3.2 Hangar IoT Monitoring System Basic Database
Performs digital transformation of basic elements such as hangar sensing terminals, access terminals, IoT gateways, and monitoring points, establishing a hangar IoT monitoring basic big database to achieve standardized and unified hangar management data.
The hangar IoT monitoring basic big database is the data foundation for smart hangar management, including comprehensive data on the hangar environment, automatic control equipment, security, access control, refueling, and power supply. Basic data can be classified by data source into automatically collected data, manually entered data, and data obtained through integration with other systems. Automatically collected data refers to data obtained by the IoT data acquisition service platform through network connections with various IoT terminals, intelligent sensing systems, sensors, video surveillance systems, and other systems. The basic database is not static but is continuously developed and updated. Manual input into the basic database is performed by hangar staff through the platform, mobile APP, and other means for real-time maintenance and updates to ensure data accuracy.
(1) Personnel information: including basic information and extended information, hangar management and staff details (name, ID document type and number, organization name and address, location, position (including family members), political affiliation, etc.);
(2) Location: establishment of a 2D, 2.5D, or 3D geographic information system map of the completed hangar;
(3) Events: referring to events related to hangar management, including infrastructure maintenance, emergency response incidents, personnel and vehicle dispatch events, etc.;
(4) Objects: various constituent components of the hangar, including equipment, facilities, supplies, vehicles, etc.;
(5) Organization: referring to the hangar management organizational structure, teams, etc.
The hangar basic database transforms disordered and complex data into organized, highly summarized data. Based on the analysis models and prediction models established for the hangar, the IoT data collection service platform implements functions such as collection, update, processing, analysis, prediction, and decision-making for the hangar basic database.