We are offering a solution for airlines who typically have a significant budget allocated to traditional airline messaging solutions, also known as Type B messaging, which may be orders of magnitude higher than that required to support alternative business messaging solutions. This is an area where there is a lot of scope for cost optimization, if the right approach is chosen using the appropriate tools.
The airline community initially created the standards for Type B messaging, which have been adopted by the whole community and is pervasive in the airline industry which it has supported over many decades. Initially designed to ensure reliable communications within the closed community using private networks at a time when there was no other solution, it can be considered as the ancestor of the open email systems in common use today.
Type B messaging has been relevant in the past as it was considered as the only reliable means of communication, in terms of availability and security, based on the standards at that time. However technology has made huge advances and today email systems are used by every organization. A point has been reached where the question must be asked as to whether Type B messaging has the same relevance today as it had in the past. However eliminating Type B messaging is not so obvious because, as a consequence of its widespread adoption, the Type B messaging service is most often so much embedded into the operations of an airline that it cannot easily be phased out without a major disruption. While it is not possible for an airline to eliminate the use of Type B messaging overnight, we can consider using a methodology to gradually shift traffic away from Type B, in a process transparent to the users.
Such a migration of traffic from Type B messaging to email could be facilitated by a gateway between the two systems, which is specifically designed to promote such migration. While there are existing gateways which bridge the two systems by converting traffic from one format to the other, unfortunately these gateways do not have functionalities meant to promote the migration away from Type B.
Maerobot has designed Message Bridge, a gateway which can be installed and managed by the airline on its own premises, to automate the smooth transition from Type B messaging to the airline’s email services, thereby helping the airline exercise a better control over its messaging requirements and costs.
More information about how Message Bridge, the Type B messaging solution of Maerobot, is delivered to the airline community can be found below..
Message Bridge is a locally managed gateway, between the Type B messaging ecosystem and the existing business email infrastructure of an organization, which is meant to allow a user receive both emails and Type B messages in a single email client interface, and also respond to both email and Type B addresses from the same client interface. While this user friendly functionality could be implemented by some other existing solutions, the objective of Message Bridge is to carry out a check to determine if the response can be sent over the email channel, in which case the preferred channel will be the email channel. The local routing functionalities of Message Bridge will allow the delivery path to be selected locally, thus ensuring that only Type B traffic without any alternate route is sent to the Type B service provider. In particular, email traffic is directly sent over the email infrastructure of the organization at no additional cost, rather than being sent to a Type B service provider for onward relay through an external gateway at a cost.
Organizations who implement Message Bridge still maintain their current Type B and email services, but they have the flexibility to manage and optimize their traffic to fit their operational requirements, and consequently control their messaging costs. Message Bridge will allow users to smoothly transition their traffic away from Type B to email at their own pace, by migrating users to Message Bridge in batches if this is the preferred migration path.
After the implementation of Message Bridge, the share of Type B traffic will decrease in favor of email traffic, and this trend will accelerate as your external correspondents also migrate to Message Bridge.
The application is meant to be customized for each environment, and Maerobot will work with the organization to set up Message Bridge for it to be integrated into its existing infrastructure with minimal disruption.
2. Message Bridge will restrict its communication only through the two interfaces listed above, and will only be able to send/receive Type B messages and emails through these interfaces.
3. Received Type B messages are routed to email addresses selected by the local administrator, through the configuration of Message Bridge. The type B addresses can be routed to any email account of the organization, in its domain, and this routing can be modified by the local administrator at any time, without necessarily making any changes to the Type B services or local email infrastructure.
4. Message Bridge will identify email recipients and Type B recipients in an outgoing email, and the delivery will be optimized to route responses meant for email recipients, as well as for Type B recipients if possible, over the email channel, while using the Type B channel only for recipients who have no equivalent email address.
5. When messages are sent over the Type B channel to external correspondents, the alternate email route to access the originator is advertised, to allow the correspondents to respond over that alternate route for future communications.
6. In particular if two correspondents are using Message Bridge, they will by default automatically select the email channel for their communications.
7. It is possible to force a communication over the Type B channel if required.
8. Message Bridge is designed to support specific Type B functionalities for the smooth running of your operations.
Message Bridge is meant to be used by members of the airline community who are already using Type B messaging and would like to gradually move away from this service. If you are such an organization, please contact us providing the details in the contact form and we shall be pleased to offer a presentation of Message Bridge customized for your environment. Typically an organization who decides to implement Message Bridge should be ready to work together with Maerobot in a joint implementation project, meant to install Message Bridge in several logical phases. Each phase is implemented and tested before proceeding to the next phase until the completion of the installation of Message Bridge, following which the migration of live users may be performed by the organization.