Evolution (SP) – Risk Alerts – Same but Different

During the migration phase, MCM UI is going through some changes as part of evolution from a Silverlight based platform to an Angular Platform. But more it changes to make it more intuitive for our users, the more it retains the essence and soul of the functional elements that made MCM popular with the same end users.

Presenting some ‘look and feel’ changes our Users will be able to see and recognize in the Angular interface.

Risk Alert View- Country names are not colors, instead the alert category is what ‘carries’ the color which allows much better visualization of the selected alert.

Silverlight (Current Interface)

 

Angular Interface (Sneak Peak)

 

As depicted in the above pictures, it will be much easier to visually associate the alert with the selected country in the Angular Interface.

(please click on the the image to see an enlarged view of the same)

Sneak Peek 2- Asset Admin Interface

Presenting a sneak peek of our Asset Admin Interface.

Our development team has been doing some redesigning to make it even more simpler for our users to navigate the interface. Now, instead of changing tabs, our users will be able to visualize and navigate within the same page. The user mapping does not consist of 2 different tables anymore. It is one table with a checkbox column indicating if the user is part of the selected Asset Group.

(please click on the image to view the enlarged version)

Progress Update 3 – Risk Intelligence & Automessaging

In all current versions of MCM (Silverlight and WPF), our Risk Alerts and Country Summary tabs of the Map UI completely relied on having Risk intelligence data to be displayed and be usable to users. As a result, only users that had the risk intelligence modules assigned were able to see and interact with Country polygons. Risk intelligence data controlled Country/region data. Having this backward controlled correlation caused some functional limitations for users who did not subscribe to our risk intelligence module

As the MCM platform advanced, we added more and more features to the country list ( like selecting a country and then attaching an auto message to that country). This functionality allowed the platform users to send auto message to all travelers entering that country. Due to the current correlation these cool features were only available to users that also subscribed to the risk intelligence module, even when the auto message content had nothing to do with risk intelligence.

With the decision to reverse this correlation during our Angular UI design, and by having Countries control the risk data, it opens up more features for users that currently do not have risk intelligence module assigned to them (such as the aforementioned country auto messages). It will also give those users the chance to see how many travelers are in each country at any given time.

Also, now that risk intelligence is secondary, We can also see the opportunity for us to further divide those countries up into their respective regions. That way a user can always see how many travelers are in a region, even if there is no risk alert for it.

Our platform Architect and the design team are continually finding innovative ways to enhance MCM. The migration to Angular provides us an opportunity to revisit some functionality, and incorporate improvements (redesign the approach as in the case above) so as to make the UI even more intuitive for all our users going forward.

Progress Update 2 – Polygons

For the past couple of weeks, our development team has focused on migrating our Polygon functionality, and we are extremely proud to share the progress made on that front. During the first week, we were successful in  implementing the following:

  • Loading and displaying of Polygons
  • Polygon info control upon click on a polygon, including calendar
  • Change of Polygon attributes via menu
  • Polygon tool-tip
  • Creating of a new Polygon
  • And searching for a location with the bottom search box

This past week was devoted to enhancing the Polygon functionality and integrating persistent Auto Messaging and Risk Intelligence (Countries, Regions). We have successfully implemented the following this week:

  • Polygons can now be related with auto messages
  • Polygons can now also be saved, edited and deleted
  • As we move forward with integrating Risk Intelligence, we have been able to make some major enhancements to existing functionality, and have improved some functional logic to make the Angular UI even more intuitive and user-friendly.

Stay tuned for our next blog update where we will aim to provide more details around the Risk intelligence enhancements, as well as some more sneak peek of our in-development UI. We feel extreme joy in sharing these progress updates with our readers, especially since our development team is working tirelessly, and is making tremendous headway with the migration project.

Progress Update 1

The development team is moving very rapidly with additions to our Angular MCM UI, as more and more functionality is continually being added. Having already made great headway in the transformation of Itinerary view and the Flight view to Angular, we have started incorporating a lot of correlated functionality at a breakneck speed.

Some of the latest additions to the Angular UI include:

  • Basic messaging (including status feedback and responses)
  • Manual messaging
  • Messaging history
  • Display of Traveler contact information
  • Itinerary status change 
  • Map layer selector
  • Itinerary calendar and date change 
  • Visibility of the plane paths 
  • Additional options added to the layer menu

We are indeed extremely excited with our progress so far, and will continue to share more relevant updates with our readers.

Update – Developer Quotes

As we dive deeper into Angular migration, we wanted to share some updates from our Migration team. The respective development teams are making great progress with MCM UI, MCM Admin UI and MCM Asset Admin UI. Below are some notable quotes from the respective lead migrators:

” Despite some early hurdles, we have taken great strides with our Migration of the MCM Map UI. We have developed Angular components that will enable us to control the data and action flow with the Map UI.

Using our internal library of such data and action flow components, we have transformed common functionality such as login, pop ups and data grids to Angular, as well as transfer and management of real-time data and notifications.

It is exciting to see the effort correlate with the reward, as we are tracking way ahead of our internal timelines, and continue to make tremendous progress with the MCM UI migration”

Thomas Pfeffer –  MCM UI

“Revamping the MCM Admin User Interface has begun.  While Silverlight development is taking a back seat, Angular 4 is quickly becoming the core of our client side products.  The latest Admin beta (Angular) has only a few features, however things are progressing quickly.

We look forward to sharing more regular updates with our readers”

Drew Jackson – MCM Admin UI

” About 3 weeks ago we also started the conversion from Silverlight to Angular for our Asset Administration User Interface. Most of these 3 weeks were spent establishing components that are responsible for adding, updating and deleting data.

However, this past week was mostly spent finally creating components that are going to be visual to the users, like the data grids that allow the visualization of different Asset Groups. At this point you can expect more frequent updates to the UI now that most of the data management components are in place.

It is gratifying to be part of a dynamic team which thrives on learning more about Angular each day”

Alexander La Bianca – MCM Asset Admin UI

Sneak Peek 1 (Map Control)

As promised, we are excited to provide our readers, the first sneak peek of the Angular UI.

One of the major changes in the Angular UI is going to be the Map content provider. As most of you are aware, in the current Silverlight based MCM we are using Microsoft Bing Maps as the Map content provider. However, as for the Angular MCM UI we would be using Google Maps as the primary provider for all Map related content.

Displayed below is the ‘first look’ for itinerary explorer of the Angular UI with Google Maps:

 

  • Please note that all the images provided in the blogs during our migration phase will be development based images, and can/will undergo significant changes before they are production ready.

Annual Developers Meet

We have just concluded our annual developers meeting in Florida. This week long event (Oct 2nd – Oct 6th) was led by our CIO and attended by our senior developers and our VP of Software development. Besides being a great bonding exercise, this is also a ‘think tank’ type event where various topics are discussed regarding design, innovation and product development. However, the prominent discussion theme this year was our ongoing migration to Angular.

This meeting provided our executives and our developers an open platform to discuss various aspects of Angular, and gave the Charter development team an opportunity to align on the progress of the migration.

Stay tuned, and do subscribe to our blog for instant notifications on updates . We will have more exciting things to share as we forge ahead on the projected path to success.

 

What? Why? Silverlight

What is Silverlight and why is it needed for MCM?


This is a question that is often on peoples mind when they are using MCM, so we thought about having a short non-techincal blog post to shed some light.

Silverlight is Application Frameworks by Microsoft Corp, that is used to create and run rich internet (browser-based) applications, such as MCM. These Frameworks have now been deprecated and are marked for sunset in 2020. Therefore, many internet applications that relied on Silverlight technology have been migrating to more advanced, and plugin free technology such as HTML5, Angular etc.

Silverlight is the underlying technology of the current MCM UI, which is featured in most, if not all the UI/Graphic based functionality, including the application display, login dialog, menu items etc. Silverlight, along with additional development code written in C#, allows our users to perform most of everything they do in MCM UI.

The current MCM UI would not work without Silverlight plugin as it is tightly integrated with the core functionality.  However, our Angular UI, when released, will have no reliance on Silverlight and no Silverlight plugins will be required.

Release v8.1

We have successfully deployed MCM v8.1 for most of our clients on September 15th 2017. This would be considered our final full release that relies on Silverlight technology. The latest release of MCM contains many functional enhancements, and a new feature that allows travelers to check-in while traveling or when back at home.