In Business Aviation (BizAv), a part of general aviation (GA), processes and their optimization are still receiving insufficient attention - even today. Digitization and possible automation are slow due to the large number of different solutions and complex structures. In many places, the coordination of flights, orders and customer and supplier management are effected manually or are only slightly information-based (e-mail, Excel, paper) using a multitude of incompatible systems containing nonintegrated structures. In order to close the resulting gaps in communication and information management, intermediaries are employed. On further consideration, however, this need in itself is only a symptom and the causes are more deeply hidden. The effects are usually high costs associated with a large overhead of up to 35% of the actual costs of relevant services or operating material. The causes are hidden in the systemic. First and foremost, there are delays in communication as well as inhomogeneous data or low-transparency processes. The effects thereof are noticeable for the customer through the price on the one hand and the lack of adequate performance on the other hand. Orders are therefore subject to considerable uncertainties in their realization1 . The quality of business aviation suffers. A future, already designed as a fully autonomous system hardware requires a different general environment. It requires a setting without manual intervention and without delays in its operation. It requires the availability of an integrated, freely accessible and decentralized database and exchange layer for the complete representation of all relevant information and payment flows in the system2 . In view of the overall digitization and automation efforts and the resulting, ever-increasing speed of implementation worldwide, organizations should strive to reduce their overhead in order to continue to persists on the market. For BizAv organizations, with reduced or completely eliminated overhead, there are opportunities to enter new markets and completely new customer segments. Many potential customers would not (yet) use a business jet or air taxi due to excessive prices, to date it is still a privilege. In order to resolve these fundamental problems, eliminate causes and make BizAv fit for the future, AVINOC was created.
The Aviation Network Operation Centers, which have been in existence since 2008, is an enterprise resource planning (ERP) software and business cloud application for BizAv, which has been further developed to this day. Inspired by the wide range of possibilities offered by Blockchain technology today, the development team decided in 2017 to transform existing knowledge from the ERP solution into a completely new system, the Aviation Network Operation Chain.
AVINOC as a Blockchain solution provides a transparent, integrated, permissionless and decentralized base data layer for the exchange of relevant information for the GA. The main focus here is on BizAv. The aim of AVINOC is flight coordination, order management and infrastructural issues of the GA worldwide and, with the help of the integrated transaction and payment system, achievement of an optimal use of resources and a high level of cost reduction on the market. The primary goal is to strengthen the BizAv market with focus on reducing the time span of the information and payment flow to zero, thus creating an optimal supply chain. This will allow the entire global market to be strengthened and made sustainable for the future. It will furthermore result in positive effects on all other economic sectors of a country with well-defined BizAv. It will also enable future technologies, such as autonomous or semi-autonomous flying, to be effectively and efficiently deployed in organizations.
AVINOC是一个适用于合同管理的区块链，P2PSC。它是具有自给自足节点的网状网络区块链混合体。参与者仅在其数据上定义权限，并且仅在P2PSC系统中定义权限。 AVINOC中的区块链本身仍然是无权的，透明的和分散的 - 对于发明者和急性的意图是真实的。
$30 509 510
$1 175 523
The team is rather big, but is what to aim still at. Vision of the project interesting and useful to many, but the idea not new. I dont see protype MVP therefore for a product I put 2 so far