|
US$429.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
MHT5103-2020: (Technical specification for information integration system of civil transportation airport)
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| MH/T 5103-2020 | English | 429 |
Add to Cart
|
4 days [Need to translate]
|
(Technical specification for information integration system of civil transportation airport)
| Valid |
MH/T 5103-2020
|
PDF similar to MHT5103-2020
Standard similar to MHT5103-2020 GB/T 23420 Basic data | Standard ID | MH/T 5103-2020 (MH/T5103-2020) | | Description (Translated English) | (Technical specification for information integration system of civil transportation airport) | | Sector / Industry | Civil Aviation Industry Standard (Recommended) | | Classification of Chinese Standard | V50 | | Classification of International Standard | 03.220.50 | | Word Count Estimation | 17,121 | | Date of Issue | 2020-07-20 | | Date of Implementation | 2020-10-01 | | Older Standard (superseded by this standard) | MH/T 5103-2004 | | Issuing agency(ies) | Civil Aviation Administration of China | MHT5103-2020: (Technical specification for information integration system of civil transportation airport)
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Technical specification for civil transport airport information integration system
ICS 03.220.50
V 50
MH
Civil Aviation Industry Standard of the People's Republic of China
Replace MH/T 5103-2004
Technical specification for information integration system of civil transportation airport
2020-07 -20 released
2020-10 -01 Implementation
Issued by Civil Aviation Administration of China
Table of contents
Foreword...II
1 Scope...1
2 Normative references...1
3 Terms and definitions...1
4 Abbreviations...3
5 Basic regulations...3
6 System Function...4
7 System Configuration Management...7
8 Data Exchange...8
9 System Security...12
10 System performance...13
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
This standard replaces MH/T 5103-2004 "Civil Airport Information Integration System Technical Specifications". Compared with MH/T 5103-2004, the main internal
The content changes are as follows.
--The name of the standard was revised from "Civil Airport Information Integration System Technical Specifications" to "Civil Transportation Airport Information Integration System Technical Specifications";
- Change to normative reference to CB/T 22239 (see Chapter 2);
-Modified the definition of terms (see Chapter 3, Chapter 3 of the.2004 edition);
-Modify the definition of abbreviations (see Chapter 4, Chapter 4 of the.2004 edition);
-Modified the basic regulations for the construction of civil transportation airport information integration system (see Chapter 5, Chapter 5 of the.2004 edition);
--Added the technical requirements for the airport operation database (see 6.1);
--Added the technical requirements of the enterprise service bus (see 6.2);
--Modified the functional requirements of the application software (see Chapter 6.3, Chapter 9 of the.2004 edition);
--Modified network technical requirements (see Chapter 7.1,.2004 edition);
- Modified the technical requirements of the server (see Chapter 7.2,.2004 edition);
-Modified database technical requirements (see Chapter 7.3, Chapter 8 of the.2004 edition);
-Modified the requirements of the data interface (see 8.1, Chapter 10 of the.2004 edition);
--Added the requirement of external interface (see 8.2);
- Added technical requirements for information security (see 9.1);
--- Added technical requirements for operational safety (see 9.2);
- Added technical requirements for data security (see 9.3);
--- Added technical requirements for network security (see 9.4);
- Increased the technical requirements for system performance (see Chapter 10);
This standard was proposed and interpreted by the Airport Department of the Civil Aviation Administration of China.
This standard is under the jurisdiction of the China Academy of Civil Aviation Science and Technology.
Drafting organizations of this standard. China Civil Aviation Information Network Co., Ltd., Guangzhou Baiyun International Airport Construction and Development Co., Ltd., Guangzhou Baiyun
Cloud International Airport Co., Ltd.
The main drafters of this standard. Wang Xin, Chen Xiao, Li Xuehui, Zhan Jiaxin, Liu Qing, Li Kun, Yang Hanchao, Xue Lingxiang, Li Zhi, Zhang Xin
Hua, Chen Fenghua.
Technical specification for information integration system of civil transportation airport
1 Scope
This standard specifies the composition and requirements of the information integration system for civil transportation airports (including the civil part of the military-civilian airport).
This standard is applicable to the technical design and construction of the information integration system for civil transportation airports (including the civil part of a military-civilian airport).
2 Normative references
The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article
Pieces. For undated references, the latest version (including all amendments) applies to this document.
GB/T 22239 Information Security Technology Network Security Level Protection Basic Requirements
3 Terms and definitions
The following terms and definitions apply to this document.
3.1
Primary system
The current business system that provides services to the outside world supports the business operation within the system and satisfies the uninterrupted operation throughout the day.
3.2
Backup system
When the main operating system is down, switch to replace the main operating system.
3.3
Test system
Complete single system test, interface test and joint debugging test before the system goes online; meet other test requirements after going online.
3.4
Disaster recovery system
The operation data backup or the operation system backup of the airport construction in a different place.
3.5
Information integration system
An information system that provides an information sharing environment for civil transportation airports so that various information weak current systems operate automatically under unified flight information control
System. The system supports the dispatching management of the airport’s production and operation departments under unified coordination and command, and provides assistance to airports, passengers, and airlines.
Information services related to flight operations.
3.6
Public address system
The broadcasting system involved in this specification refers specifically to business broadcasting, that is, audio broadcasting for daily operations in the terminal, including flight information.
Information announcement, boarding announcement, boarding urge announcement, final boarding announcement, etc.
3.7
Flight schedule information
Flight plans issued regularly by civil aviation authorities, including flight numbers, entry and exit signs, flight tasks, attributes, aircraft types, departure
Stations, stops, destination stations, take-off and landing time of each station, execution time and other information.
3.8
Aviation information message
The aeronautical information telegrams related to flights sent, transmitted, and received through the air traffic control aeronautical telegram network, including the flight movement in AFTN
Status messages and plan messages.
3.9
F1ight information
General term for flight plan information, flight status information and flight history information, including execution date, flight mission, flight number, aircraft type,
Aircraft number, affiliated airline, attributes, departure station, stopover station, destination station, alternate station, take-off and landing time of each station, terminal number, customer class
Information such as flight status and flight status.
3.10
F1ight state
Carry out the current normal or abnormal operating status of the flight. The normal status includes check-in, check-in deadline, over-station boarding, boarding at this station,
Encourage boarding, the end of boarding, take-off, arrival at the next station, take-off and arrival ahead, abnormal conditions include delay, cancellation, alternate landing, and return
3.11
Transportation resource
Resources to provide services to passengers, including terminal buildings, VIP lounges, check-in counters, security check channels, waiting halls, boarding gates, baggage carousels, etc.
3.12
Apron resource
The resources to provide support services for aircraft, including aircraft seats, bridges, special vehicles, inspection and maintenance equipment, etc.
3.13
Flight plan
Flight plans generally include schedule plans, historical plans, next-day plans and temporary plans.
3.14
Constraint condition
The use of flight resources depends on the conditions of related variables. The value range of variables has various restrictions, such as the position of the boarding gate and the bridge.
Should wait. Each restriction is called a restriction.
3.15
Allocation rules
Based on the contract and the actual situation of the airport, formulate resource allocation rules and realize the informatization of resource allocation rules.
3.16
Contract
The guarantee contract signed between the airport and the airline includes agreements on flight and aircraft progress guarantee, resource scheduling, and profit calculation.
4 Abbreviations
The following abbreviations apply to this document.
AFTN. Aeronautical Fixed Telecommunication Network (Aeronautical Fixed Telecommunication Network)
AODB. Airport Operation Database (Airport Operation Database)
NTP. Network Time Protocol (Network Time Protocol)
API. Application Programming Interface (Application Programming Interface)
VIP. Very Important Person (Very Important Person)
5 Basic rules
5.1 System classification
The system combines the annual passenger throughput of the airport's construction target year, and combines the categories of the information integration system in Table 1 for overall design and construction.
Meet the needs of airports of different sizes. The system should be based on the overall information planning of the airport, clarify the scope of use, fully share data, and improve the airport
operation efficiency.
The configuration of the airport information integration system usually includes the main operation system, backup operation system, test operation system and disaster recovery operation system. among them
The main operating system is the standby system. Each airport can be configured according to actual conditions.
6 System function
6.1 Airport Operation Database
Airport Operation Database (AODB) is the core component of the system, used to store and manage flight operation data, and define the association of operation data
Relationship and processing rules.
Operational data includes flight information, resource information and basic information.
Note. Resource information includes check-in counters, seats, boarding gates, baggage loading and unloading carousels, and baggage claiming and loading plates.
AODB should store flight operation data for at least one year.
6.2 Enterprise Service Bus
Enterprise service bus is the core of realizing airport data exchange. The system should support data exchange with other related information weak current systems, and also
Support data exchange between other related information weak current systems and data exchange within the system.
Data exchange services can be implemented in various ways such as message middleware or service APIs.
Data exchange services should include service registration, authentication, configuration, routing and monitoring.
6.3 Application system functions
6.3.1 General rules of system functions
The functions of the information integration system should be determined according to the airport's operating mode and business requirements, including.
a) Functions to be prepared, including.
1) Flight information management;
2) Aviation message analysis management;
3) Basic information management;
4) Operational resource management;
5) Operation audit;
6) System integration and interface API;
7) Statistical analysis;
b) Optional features, including.
1) Meteorological information management;
2) Operational guarantee management;
3) Mobile security application;
4) Mobile phone mobile application;
5) Operation guarantee monitoring;
6) Flight zone operation monitoring and management;
7) VIP management;
8) Settlement and revenue management.
Note 1.Optional functions for Category A airports can include operation guarantee management, mobile guarantee, guarantee operation monitoring, mobile phone applications, and flight zone operation monitoring management.
Note 2.Optional functions for Category B airports can include operation guarantee management, mobile guarantee, guarantee operation monitoring, mobile phone applications, and flight zone operation monitoring management.
Note 3.Optional functions for Category C airports can include mobile security management, security operation monitoring, settlement and revenue management.
6.3.2 Flight information management
The flight information management function should realize flight plan information management, flight dynamic information management and flight history information management.
Flight plan information management shall be based on the operation authority setting, and provide legal users with inquiries and additions to flight plan information within the authority.
Add, delete, modify, and print operations; comprehensively generate flight plan information according to plan messages and flight schedule information;
The take-off and landing time of this station is based on the provisions of the civil aviation administrative department and the service guarantee standards of the airport and airline contracts.
The guarantee plan of the class, including guarantee items, guarantee standard time, and corresponding operation resource plan opening and closing time.
Flight status information management shall provide legal users with inquiries and additions to flight status information within the scope of the operating authority.
Add, delete, modify, and print operations; it should be able to publish flight information changes and flight status changes to the outside in real time;
Special pictures and other display forms.
The system can provide the advance flight schedule, execution progress and abnormal information of the inbound flight.
The flight history information management should be able to provide legal users with inquiries, flight history information within the scope of authorization, and
Print operation.
6.3.3 Aviation message analysis management
The system should be able to receive, process, and identify aviation information messages transmitted by the AFTN network. It can also directly receive and process aviation information
Flight information in data format sent by the company.
Real-time release of flight dynamic information, including flight departure and landing time changes, flight number changes, flight reservations, flight arrivals, flight departures, flight
Shift to the next stop, flight delay, flight cancellation, flight diversion, flight return, etc.
It should include the function of automatically calculating the estimated time of arrival of the flight based on the actual departure time and the knowledge base.
It should include the function of querying and printing the original text of historical aviation information messages of the air traffic control department and airlines.
6.3.4 Basic information management
The system should provide legal users with access to airport business resources, aviation data resources, permissions, contract information, etc.
Maintenance and management functions of basic information required by the system.
Airport business resources should include transportation resources, field resources, allocation of human resources, and the relationship among various resources.
Aviation data resources should include airlines, airports, crew requirements, aircraft types, reasons for flight exceptions, schedules, guarantee links, service
The content of the service level.
The authority shall include the content of users, roles, departments, functions, authority and authority configuration.
6.3.5 Operation resource management
The system should provide legal users to realize the planning management, pre-allocation, and dynamic allocation of airport operating resources in accordance with the operating authority settings.
The system should provide a Gantt chart or a plan view. The system automatically checks the legitimacy of the flight parking space according to the set rules,
Deploy aircraft position use conflict warning; it should include resource forecasting and early warning and post-efficiency analysis functions, optimizing rule settings; in accordance with airport management requirements
Statistics on the usage of various resources.
Airport operation resources include aircraft seats, check-in counters, boarding gates, passenger boarding bridges, baggage carousels, etc. Resource planning management includes resources
Constraints, allocation rules, priority management of source correspondence.
6.3.6 Operation audit
The system shall have the functions of recording, querying and exporting various operation audit information, and should have the printing function.
Operation audit information includes function category, content of data changes (including adding, deleting, and modifying operations), time, operator, and IP
address. The function category should include the description of the business operation type and the login and logout operations of users (including mobile terminals).
6.3.7 Statistical analysis
The system should provide legal users with statistical analysis of airport flight operation data, including querying, exporting, and printing.
Printing operation. The statistical analysis should include flight resource statistics, flight normal/abnormal statistics; it may include flight guarantee normal/abnormal statistics.
6.3.8 System Integration and Interface API
The system should provide message service or bus service API to realize connection with external systems.
6.3.9 Meteorological information management
The system can support the display of the weather information of the airport’s runway and the weather information of the departure flight destination terminal, and can realize the reception of weather information,
Analysis and display.
6.3.10 Operation assurance management
The system can automatically generate a guarantee item for the flight based on the flight mission, regional attributes, resource allocation, combined with contracts and guarantee standards.
The guarantee personnel and guarantee duration of the guarantee items can be automatically set according to the contract, model, and number of available seats.
It can support the scheduling of batch dispatch of support personnel in advance, and adjust the support personnel according to flight dynamics.
Supports hierarchical reminders of guarantee tasks; guarantee personnel can report guarantee progress and abnormal conditions in real time.
6.3.11 Mobile Security Application
The system can support the security personnel to view the schedule, status information, and weather information in real time through the handheld terminal, and receive the security task assignment,
Remind information, etc.; support automatic voice broadcast to remind task information; and real-time report guarantee progress, abnormal conditions, etc.
Mobile security applications have unified version control, user management, and permission control functions. Different users can share a set of mobile security applications,
Realize access control to content through user authority management.
6.3.12 Mobile application
The system can provide managers with the overall operation guarantee progress of the airport and realize the query of key indicators of airport operation. Support for each aviation
The details of the security progress of the class, the use of resources, early warning information and weather information are displayed.
Note. Key indicators can include in/out inquiries, flight regularity inquiries, flight guarantee inquiries, and flight resources inquiries.
6.3.13 Operation assurance monitoring
The system can monitor all flight guarantee links, guarantee resource usage and flight check-in/boarding numbers in real time, and should be able to monitor the progress of the guarantee
The situation is subject to hierarchical supervision and support to ensure the entry and release of abnormal information.
6.3.14 Flight zone operation monitoring and management
The system can realize integrated monitoring of the operation of the flight area, including real-time monitoring of aircraft and vehicles, and trajectory playback;
In case of cross-border, speeding, etc., provide alarm prompts and export statistical reports; at the same time, it can display the current aircraft and vehicle status in cooperation with the progress of the guarantee
Guarantee mission.
6.3.15 VIP management
The system should provide legal users with the management of important passenger information and travel records in accordance with the operating authority settings, and provide printing functions;
It can realize automatic association of important passengers' flights and add special marks. Among them, important passenger information management should include inquiries, additions, deletions
Delete and modify operations.
6.3.16 Settlement and revenue management
The system should convert the production data according to the format of the airport financial software, calculate various expenses according to the charging standards, and generate a statement
According to data, realize the maintenance and management of arrears and charges. Support querying and printing related documents (documents should include settlement statements, bills, and lists).
7 System Configuration Management
7.1 Technical specifications for network configuration
The computer network required by the system should propose topology, routing planning and security according to the equipment deployment and application requirements of the information integration system
Standard technical requirements.
The computer network needs should meet the business development and use needs of the airport construction target year.
The network should meet the network security requirements of the local airport.
Network technical specifications should comply with relevant national and local standards.
7.2 Technical Specifications for Server Configuration
Server selection should follow the principles of safety, reliability, advanced technology, and easy maintenance. The industry’s best performance, complete functions, and technical
Mainstream and mature products with advanced technology.
Server performance and functions need to be combined with the product life cycle to meet the annual passenger throughput of the airport’s recent construction target year and the future
Business growth.
A and B system database server should adopt minicomputer server, and C system database server can adopt minicomputer server.
The server equipment shall be redundantly configured, and the redundant configuration ratio shall be formulated in accordance with the actual situation of each airport.
Type A, Type B, and Type C server systems should adopt dual-machine hot backup or load balancing.
The information integration system based on the cloud computing architecture, the server can adopt the virtual server, the resources are uniformly allocated by the resource pool on demand, and the virtual server
The performance and function of the server should not be lower than the physical server of the same configuration.
The server should be equipped with power supply and fan redundancy, the power supply should be equipped with no less than 2 redundant hot-swappable power supplies, and the fan should be equipped with N 1 redundancy.
7.3 Technical specifications for database configuration
Database selection should follow the principles of safety, reliability, advanced technology, and easy maintenance, and current mainstream commercial products should be preferred.
Support relational databases and encourage innovative applications of non-relational databases.
It should be open, and should support mainstream hardware and operating system platforms, heterogeneous databases and data interconnection and mutual access, and multi-layer architecture.
It should support multiple standard languages to develop stored procedures.
It should have reliability and availability, and should include fault tolerance and error recovery, recording, and early warning capabilities.
It should be safe, and should include C2 level safety standards and multi-level safety control.
Abundant application development tools and environments should be provided, suitable for system applications, and should have online and offline backups, automatic backups, and log management
Features.
8 Data exchange
8.1 General description
The data exchange between the information integration system and each weak electronic system should avoid direct access to the core database of the other’s system, and should be calculated
Computer network adopts data service bus or interface mode to realize data exchange. In the process of data exchange, middleware or handshake protocol can be used to ensure that
Reliability.
The data service bus can include unified service methods, data standards, service protocols, and routing and forwarding functions.
The content of data exchange should meet the actual operational requirements of the airport and can be divided into two types. internal exchange and external exchange.
The internal data exchange objects are mainly related business systems within the airport.
The external data exch...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of MHT5103-2020_English be delivered?Answer: Upon your order, we will start to translate MHT5103-2020_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of MHT5103-2020_English with my colleagues?Answer: Yes. The purchased PDF of MHT5103-2020_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|