Photo

AviNet Connector

 

  1. What is AviNet Connector?

    ARINC’s AviNet Connector is a simple, self-installable Java software application that enables a customer to easily integrate their messaging applications with the AviNet Messaging Service and thereby leverage the power of ARINC’s IATA Messaging Community to their advantage.

    AviNet Connector integrate into existing applications by reading inbound messages from a server’s file directory and writing outbound messages to a server’s file directory. ARINC’s messaging architecture can accept customer messages in many formats (SITATEX®, XML, Type-B, etc.) and transmit messages to their destination in the format required by the receiving organization.

  2. How does AviNet Connector send and receive messages?

    A simple example is two folders, IN and OUT, are created on installation; AviNet Connector then creates two queues, one for sending data an one to receive it, which will interact with these folders. Any messages placed into the OUT folder are picked up by AviNet Connector and moved to the SEND Queue over an internet or leased line connection to an ARINC MQ System (AMQS) node as shown in Fig.1 below. Any messages on the Receive Queue from AMQS are placed into the IN folder when they can then be picked up by the application..

    N.B. Multiple IN and OUT directories can be created to meet the customer’s needs.

    How AviNet Connector Sends and Receives Messages | Mission Critical Transmissions with Rockwell Collins

    Fig.1 Simple example of connector message flow

  3. How are Messages delivered into the correct format?

    AMQS Message Flows employ standard transforms that are applied to SITATEX SDK, IATA TypeB and XML flat files. Other bespoke transforms can be provided on request.

  4. Does Connector reformat the messages?

    No processing of messages takes place on the customer premises. All the transformation is completed by the AMQS, off-loading application servers.

  5. Can it replace the SITATEX SDK?

    It is a direct, lower cost replacement that provides a faster, higher quality and more robust messaging service with superior functionality which is customizable to meet customer’s business requirements.

  6. Can it replace the SITATEX LAN Gateway?

    No it is not a replacement for the LAN gateway, although we do have an Enterprise solution that is able to provide this functionality as well.

  7. Does Connector check for message format errors?

    Message format validation is carried out by the AMQS Message Flow component.

  8. What is required for the install?
    1. A static IP address a few days prior to install to allow the ARINC firewall to be configured to permit the customer IP address access.
    2. Customer network firewalls must be configured to allow access to the ARINC IP addresses.
    3. A password will be required for download of the software from ARINC’s FTP site which you receive from the ARINC Project Lead.
    4. Java 1.5 or higher.
    5. Single or multiple shared drives/partitions for both the AviNet Connector and Customer application to which both will need Read and Write access privileges.
  9. Will I be given help for the install?

    Yes as well as providing you with a very comprehensive help guide one of our engineers will walk you through the process.

  10. Can it be configured for Windows and UNIX/Linux platforms?

    Yes it can be configured on multiple platforms:

    • Windows
      • Windows 7
      • Windows Vista
      • Windows 2008 Server
      • Windows XP
      • Windows 2003 Server
    • UNIX
    • Linux
  11. Is configuration complex?

    No it is has 10 very simple steps that you are walked through by the ARINC Project Lead.

  12. Can Connector make use of low cost Internet Connections rather than leased lines?

    Yes AviNet Connector is able to make full use of the Public Internet and Fig.2 below provides a basic diagram of the functionality associated with the AviNet Connector software using the public Internet.

    AviNet Connector Uses Low Cost Internet Connections | Rockwell Collins Aviation Messaging Systems

    Fig. 2 AviNet Connector over Public Internet

  13. Does Connector work with all applications?

    No applications that are not able to create flat files would require a straight MQ solution which we can also provide.

  14. How long does it take to install?

    From the time the contract is signed we can have a standard AviNet Connector Install completed within 10 working days.

  15. Can we still use SITA applications with AviNet Connector?

    Yes AviNet Connector works with nearly all applications in the aviation industry including SITA applications.

  16. Can we use the same IATA address for AviNet Connector and AviNet Mail?

    Yes it is possible to use the same IATA address although we would advise a separate address is used for each application just for easy management.

  17. What software/system requirements are needed for AviNet Connector?

    AviNet Connector just requires Java JRE 1.5 or higher and basic memory and processing hardware capabilities:

    • At least 256 MB of RAM
    • At least 40 MB of hard drive space for running the application
    • At least 25 MB of free hard drive space for messaging directories
  18. Can we send AFTN messages through AviNet Connector?

    Yes all message types can be sent through AviNet Connector via ARINC’s AMQS.

  19. What type of files does AviNet Connector need to convert to Type B and vice versa?

    Flat files in any format can be transmitted through connector and the AMQS carries out the file conversion.

  20. If my AviNet Connector session fails then how are the messages backed up and recovered?

    All messages are stored in a queue until delivery is made. If there is a failure in the service all messages are stored in this queue until the service is restarted and they can be delivered.

  21. Can AviNet Connector be used to run multiple sessions?

    Yes AviNet Connector supports multiple sessions which are virtual tunnels between customer applications and the AMQS Node that lets AviNet Connector separate messages into discrete groups e.g. one session for Type B flight plans and another for cargo messages.

  22. Are the messages secure?

    Yes AviNet Connector uses SSL encryption.

Scenarios

ARINC has a large customer base and below are examples of the generic types of customers that have been successfully switched to AviNet Connector and are very happy with the transition in regards to performance and cost.

Scenario 1
Type of Company - Airline Short and Medium haul
Size of Company - 59 Aircraft
Location/Country - UK based
How long they have used AviNet Connector - Approx. 1.5 yrs
Do they have multiple instances of Connector - One
Was it used as a replacement for SITA SDK or LAN Gateway. Yes – SDK and SITATEX LAN Gatway
Applications they use it for - AIMS, FWS, Lynx and FAX. Also developed an auto re-start facility for resilience.

Scenario 2
Type of Company - Airline Flag Carrier Short and Long haul
Size of Company - 25 Aircraft
Location/Country - Kazakhstan
How long they have used AviNet Connector - 2years
Do they have multiple instances of Connector - One Connector - 2 channels
Was it used as a replacement for SITA SDK or LAN Gateway.- Yes SDK and Lan Gateway
Applications they use it for. - AIMS, (ASM or MVT or LDM) CRIS

Scenario 3
Type of Company - AVIATION SOFTWARE SOLUTIONS
Size of Company - Small
Location/Country - Switzerland
How long they have used AviNet Connector - 2.5 years
Do they have multiple instances of Connector - No
Was it used as a replacement for SITA SDK or LAN Gateway.- Yes
Applications they use it for. - In-House software

Scenario 4
Type of Company - AVIATION SOFTWARE SOLUTIONS
Size of Company - Medium
Location/Country - Hamburg, Germany
How long they have used AviNet Connector - 2.5yrs
Do they have multiple instances of Connector - No
Was it used as a replacement for SITA SDK or LAN Gateway.- No
Applications they use it for. - In-house software with AviNet eXchange

Scenario 5
Type of Company - Cargo Carrier
Size of Company - Large Corporate Group
Location/Country - Russia
How long they have used AviNet Connector - One month
Do they have multiple instances of Connector - No
Was it used as a replacement for SITA SDK or LAN Gateway.- Yes
Applications they use it for. - AIRCOM – ACARS

Scenario 6
Type of Company - Handling Agent
Size of Company - Large Global
Location/Country - Global
How long they have used AviNet Connector - 2 years
Do they have multiple instances of Connector - Yes
Was it used as a replacement for SITA SDK or LAN Gateway- Yes
Applications they use it for. - DCS, FIDS and GHS

Scenario 7
Type of Company - AVIATION SOFTWARE SOLUTIONS
Size of Company - Small
Location/Country - UK
How long they have used Connector - 2.5yrs
Do they have multiple instances of AviNet Connector - Yes
Was it used as a replacement for SITA SDK or LAN Gateway.- Yes but also for new installs
Applications they use it for. - In-house DCS and various customer applications.

Scenario 8
Type of organisation – Community and Common Market
Size of organisation – 15 island nations
Location/Country – Regional
How long they have used Connector – 6 years
Do they have multiple instances of AviNet Connector - No
Was it used as a replacement for SITA SDK or LAN Gateway.- No
Applications they use it for. – Advance Passenger Information associated with border management

Scenario 9
Type of Company – Air Cargo Handling Systems
Size of Company - Small
Location/Country - Global
How long they have used Connector – 8 Years
Do they have multiple instances of AviNet Connector - No
Was it used as a replacement for SITA SDK or LAN Gateway.- Yes but also for new installs
Applications they use it for. – Air Cargo Handling System for Airports, Airlines and Ground Handlers exchanging very high volumes of Cargo messages.

Contact Rockwell Collins' ARINC AviNet Today | Seamless, Cost-Efficient Type B Aviation Message Handling