Flightscape eFlight Manager vs SAP Mobile Services Client

Flightscape eFlight Manager is a Flight Plan Manager add-on to expand the connected flight to the cockpit. The application automates the process of collecting all the information for your trip by ingesting flight plans from your flight planning system of choice. A comprehensive and complete package is then generated containing all the latest information required for a trip such as MET, NOTAM, Upper Wind and Temperature / Significant Weather charts and documentation. As well as being a system for delivering data for a trip, eFlight Manager has the ability to capture information from the flight crew. Information such as fuel records, actual flight times, and actual Fuel On board (FOB) are uploaded to the ground server for immediate analysis and reporting. Major features include: - ARINC 633-2 flight plan ingestion. Pre-flight Briefing: - METAR data with green, amber, red coloring based on configurable minima. - TAF for each airfield. - NOTAM for each airfield. - SNOWTAM for each airfield. - Update facility to receive the latest data for your trip. - FIR NOTAM, ASHTAM and SIGMETS. - Operational notices. - PDF Briefing Package. - Flight Recalculation - Sign Off. Trip: - Flight Summary showing weight and fuel information with offline recalculations. - Delay records. - Trip Log for capturing actual flight times, fuel on board, etc. Scratch Pad - Captures text notes. - Captures drawings. Device Sync - Allows crews to “push” or “share” the data that has been entered into eFM from their device to another device

The SAP Mobile Services Client is a native iOS application that gets its UI and business logic from JSON metadata. The metadata is defined in an SAP Business Application Studio or SAP Web IDE-based editor. It's provided to the client using the App Update service of SAP Mobile Services. The client connects to SAP Mobile Services with an endpoint URL, among other properties provided by the user. These properties are usually embedded in a custom URL that is sent to the user's email. The custom URL must start with "sapmobilesvcs://." When the client connects to Mobile Services, it receives the app metadata and connects to one or more OData services. OData can be securely stored locally so that it's available offline. The UI is implemented with the SAP Fiori framework. This app is "generic" in that no application definitions or data come with the app. It's only usable if the user connects securely to a Mobile Services instance. For full list of changes, see: https://me.sap.com/notes/3730887