- Login
- Contacts
- Sitemap
- Imprint
- Legal notice
- Language
Movilizer for SAP |
Movilizer for SAP Track and Trace
(mTT) – A Mobile App for SAP OER, SAP EM
and SAP AII
for any steakholder involved in your Supply Chain
Introduction Movilizer for SAP Track and Trace:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 |
In order to be able to pack you normally enter the patent ID and then all the children IDs packed into the parent. With this function you are able to pack any level hierarchy (e.g. packing items into cases, or packing cases into pallets). | ||
|
|||
2 |
Should you use the Movilizer for T&T integrated with SAP OER , the new built hierarchy would contain the parent ID and the packed children. In SAP OER you can see then the packing events and the corresponding Hierarchy (in this example the case contains 2 items). | ||
|
|||
Unpack – Capturing unpacking events
Unpack – Capturing unpacking events
1 |
In order to be able to unpack, you normally enter the patent ID and then all the children IDs that are being unpacked. With this function you are able to unpack any level hierarchy (e.g. unpacking items from cases, or unpacking cases from pallets). | ||
|
|||
2 |
Should you use the Movilizer for T&T integrated with SAP OER , the changed hierarchy is visible in the SAP OER Cockpit. | ||
Ship / Receive – Capturing shipping events
Ship / Receive – Capturing shipping events
1 |
In order to be able to capture a shipping or receiving event normally you need to enter or select the reference document number against which the shipping (outbound delivery ID) or receiving (inbound delivery ID) in being done. Once the Delivery ID is entered, the user can then proceed to enter the Pallet IDs (or cases, items IDs) shipped or received with the delivery. | ||
|
|||
2 |
As soon as the delivery was completely shipped, the synchronization is started and is being sent to the SAP OER. Alternatively it is possible to get a confirmation screen with the details of the shipped Ids. In SAP OER the Product IDs (inclusive Pallets and cases can be displayed) as well as the details of the corresponding delivery can be displayed. | ||
|
|||
Decommission – Capturing decommissioning events
Decommission – Capturing decommissioning events
1 |
In order to be able to document the destruction of Product IDs, the user would use the function decommissioning. Via this function, it is possible to decommission a single ID (provided the hierarchy was unpacked before) or the entire hierarchy (e.g. a full case with its corresponding items can be fully decommissioned). | ||
|
|||
2 |
Should you use the Movilizer for T&T integrated with SAP OER , the new event "decommissioning" will be visible not only for the observed ID (e.g. the case ID in case a full case was decommissioned), but also for all Product IDs contained in the hierarchy. | ||
|
|||
Verify – Verifying Product IDs
Verify – Verifying Product IDs
1 |
This feature allows you to verify any Product ID against your SAP OER repository. For this, the user enters the Product ID to be verified and automatically the synchronization stars. SAP OER sends then the relevant information with regards to the Product ID (Event handler attributes and overall status "known" or "unknown") to the mobile device. | ||
|
|||
2 |
In SAP OER, additional information for the Product IDs is stored as event handler attributes or a status information to the event handler. | ||
|
|||
3 |
SAP OER, for each verification transaction, and event type "authenticated" is created and booked in the system containing the requestor of the verification event as well as the timestamp information when the verification event was created. Thanks to this feature audit trial is guaranteed. | ||
|
|||
2 Technical Features
The technical capabilities of the Movilizer for Track & Trace results out of a detail requirements analysis run by several large customers implementing global track & trace projects.
Feature Description |
|
It runs on any mobile device and works also offline (mobile phones, rugged PDAs, fix barcode readers, forklift terminals etc.) |
A mobile application for Track & Trace should work offline / online and should offer flexibility in the mobile device selection: it should support various different models of ruggedized PDAs but also support of fix scanners, forklift terminals, or even normal mobile phones.
The Movilizer Client is a very small piece of software (some few Kilobytes) written in different native languages (depending on the target device) capable of running in offline / on nearly any mobile phone, smart phone, PDA, Tablet PC, Netbook or Notebook. Please refer to http://www.movilizer.com/Supported_Devices/ for a complete list of supported devices.  The deployment of the Movilizer Client is done via SMS or simple file transfer and is exactly as easy as downloading a ringtone (average set up time is seconds). The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step. |
Optimized for sites with poor infrastructure (maximum data compression) |
To overcome possible network limitations in low infrastructure countries or in remote locations the mobile application for Track & Trace should minimize the required data traffic between the devices and data center (offering compression mechanism or similar). For network optimization purposes smaller but continuous data packages are generally more desirable than large packages sent in few peaks.
The Movilizer minimizes the required data traffic between the devices and the Movilizer Cloud because the mobile devices exchange binary containers with the Movilizer cloud (and not an XML format like EPCIS or PML). The binary format guarantees maximum data compression and ensures that the Movilizer client is able to run on any hardware (regardless of the hardware requirements), even on simple mobile phones. Additionally, the Movilizer facilitates the continuous sending of information (only a TCP/IP connection, via for example LAN, Wi-Fi or GPRS/3G is required for this purpose). The message packaging does not happen on the mobile client but on the Movilizer connectors. This allows the mobile devices to send data whenever a logical process is closed. A constant data transfer of smaller packages avoids network peaks and decreases the risks of broken connections. This network will reduce network provisioning costs and optimizes the usage of the available network. |
100% EPCIS compliant |
A mobile application for Track & Trace should be able to generate and send xml messages in EPCIS format to the central Track & Trace database (SAP OER). The Movilizer for SAP Track & Trace is 100% EPCIS compliant. Even though Movilizer clients send binary files to the Movilizer Cloud (and not EPCIS), binary packages are translated into XML which are then transmitted to the Movilizer connector in encrypted XML messages (optional feature) via secured web services. In the Movilizer connector those message are converted into EPCIS and send to SAP OER via the standard SAP PI EPCIS interface. If connected to SAP Auto-ID Infrastructure the translation is into PML or ALE. If connected to SAP EM no conversion takes place. A simple remote function call is done in order to be able to post the event against the event handler. |
Background integration with existing DSD, PoD mobile applications |
In many scenarios track & trace needs to integrate with standard customer delivery processes (DSD or Van Sales). In many occasions customers have already mobile applications deployed for DSD processes, and redeveloping them for Track & Trace purposes is not an option. For this reason, the mobile application for Track & Trace supports background integration with Direct Store Delivery (DSD) and Proof of Delivery (PoD) type of applications |
Background integration with exiting mobile WM applications |
In many occasions, track & trace is rolled out in warehouses where mobile Warehouse Management applications are already in use. In those cases, it needs to be ensured that the warehouse operator still only needs to scan once, even though the data is used two different purposes: for WMS and for Track & Trace. To allow this with minimal changes in the existing WMS application, the Movilizer for Track & Trace offers "out of the box" a generic interface that allows background integration with existing Warehouse Management mobile applications. |
Quick and easy installation in the mobile devices |
The Movilizer Client can be installed in any case in less than 2 minutes on any mobile device (PDA or mobile phone) it does not require any special technical skills. This will make possible that the super user sets up a device without any intervention of the helpdesk support.
Technically, the deployment of the Movilizer framework for devices not having GSM/GPRS/3G capabilities (e.g. PDAs, TabletPCs or Laptops) is triggered via transmission of an installable file (*.cab, *.jar etc.) to the device via any channels that allows a simple file transfer (e-mail, ftp, Bluetooth, active sync etc.). Once on the device a double click automatically installs the Movilizer without any user interaction. Average set up time: around 30 seconds or even less. The deployment of the Movilizer framework for cell phones is triggered by a technical SMS. Average set up time: between 30 and 180 seconds, mainly depending on the bandwidth of the wireless connection. |
Comprehensive central configuration possibilities, marginal programming |
The Movilizer for SAP Track & Trace allows you to configure different the mobile application and all its functionalities for different users and user groups. The configuration of the mobile application is done in the SPRO transaction of your SAP OER/EM or SAP AII system using the standard customizing node for Movilizer. Refer to the block "Key Differentiators for more details on the configuration possibilities. |
Barcode Scanning and RFID |
BARCODE Scanning The Movilizer supports barcode scanning in any standard format (2D Datamatrix or lineal barcodes), provided the mobile device has a built-in barcode scanner. Additionally, should your mobile device not have a built-in barcode scanner but an autofocus camera, the Movilizer offers the option to use the mobile phone camera as a barcode scanner. In this way any standard mobile phone can become a barcode scanner. (Supported Devices via mobile phone camera: any Nokia serie 60s, with exception of the Nokia E90, any BlackBerry device. On request any device can be supported. 
RFID Reading / Writing The Movilizer supports reading RFID data and writing data to RFID tags in any frequency (NFS, LF, HF or UHF), provided the mobile device has a built-in RFID reader. Additionally, should your mobile device not have a built-in RFID reader, the Movilizer offers the option to use the mobile device bluetooth to connect to external RFID readers.Companies like Microsensys supply low cost Bluetooth enabled RFID readers for different frequencies and in different formats. In this way any standard mobile phone or PDA can become an RFID enabled device.  |
Supports Printing (for Re-Packing and other reports) |
The Movilizer is able to talk to mobile or fix printers via Bluetooth in order to trigger any type of scanning. Via this feature the mobile application is able to trigger the generation of labels for new IDs (during the re-packing process) or to print any kind of in device report relevant for the operator (e.g. report containing all the Pallet IDs scanned against a delivery etc.). |
Offline field validations of any type and centrally managed |
The Movilizer for SAP Track & Trace needs to be able to validate information such as Product ID formats during data entry. The Movilizer provides a script language (called Movilizer Expression Language, "MEL") that allows running almost every validation on the mobile device. MEL Scripts (which are always linked to screens) are defined centrally and are being run on the mobile device side only (offline validations). For you as a customer, this mainly means that any type of validation in the mobile application is defined centrally (in the SAP T&T Connector, in the ABAP workbench) and not hardcoded in any of the screens. Thanks to this you will have at any time the flexibility to change at time not only any parameters being part of the validation, but the entire validation rules. New validation rules can be edited, added or remove during the runtime ("on the fly" without having to have any user interaction and of course without any downtime). "MEL" is the maximum expression of flexibility and adaptability. For example, thanks to this feature, you would able to handle completely new ID formats without having to change a single line of coding on the mobile application and without any new deployment of the mobile devices (the user would just switched on the mobile application and after the first synchronization the application would support the new ID format). In summary, with the standard feature Movilizer Expression Language (MEL), the Movilizer provides a very powerful tool for field validations. |
Supports GPS Geo-Coordinates capturing |
GPS capturing during order/notification execution The Movilizer allows you to link any process (capturing shipping event for example in case of van selling) with the background capturing of GPS coordinates. In this way you can always know who created or processed what (Movilizer user), where (Geo-coordinate) and when (Timestamp is automatically captured in background as well).For this feature a GPS or A-GPS enabled mobile device is required. 
Automatic vehicle / device tracking via GPS You can also configure the Movilizer to do automatic vehicle / device tracking. In this modus, the technician's mobile phone automatically sends GPS geo-coordinates every X minutes (time interval configurable), so that the dispatcher is able to follow the technicians route during the day. 
|
3 Key Differentiators
Key Diferrentiator |
Feature Description |
|
It is simple and very low cost: so that it can even be deployed to external employees. |
The Movilizer is the lowest cost option to "movilize" SAP Track & Trace in the market today. Because it is low cost and even "usage based" licensing is possible, you are able to even deploy the Movilizer to external employees or final customers. With the Movilizer you can even think of creating a new communication channels with you end customers for example allowing them to use their mobile phones for self service purposes: rather than having to call the service helpdesk end customers could use the Movilizer to report malfunctions (notification creation. | |
| It runs on any simple mobile phone |
A mobile application for Track & Trace should work offline / online and should offer flexibility in the mobile device selection: it should support various different models of ruggedized PDAs but also support of fix scanners, forklift terminals, or even normal mobile phones.
The Movilizer Client is a very small piece of software (some few Kilobytes) written in different native languages (depending on the target device) capable of running in offline / on nearly any mobile phone, smart phone, PDA, Tablet PC, Netbook or Notebook. Please refer to http://www.movilizer.com/Supported_Devices/ for a complete list of supported devices. The deployment of the Movilizer Client is done via SMS or simple file transfer and is exactly as easy as downloading a ringtone (average set up time is seconds). The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step. |
|
| It is deployed in seconds (device setup can be done by the end user) |
The Movilizer Client can be installed in any case in less than 1 minute on any mobile device (PDA or mobile phone) it does not require any special technical skills. This will make possible that any "super user" is able to set up a device without any intervention of the helpdesk support. The deployment of the Movilizer client for cell phones is triggered by a technical SMS. Average set up time: between 30 and 60 seconds, mainly depending on the bandwidth of the wireless connection. Technically, the deployment of the Movilizer client for devices not having GSM/GPRS/3G capabilities (e.g. PDAs, TabletPCs or Laptops) is triggered via transmission of an installable file (*.cab, *.jar etc.) to the device via any channels that allows a simple file transfer (e-mail, ftp, Bluetooth, active sync etc.). Once on the device a double click automatically installs the Movilizer without any user interaction. Average set up time: around 30 seconds or even less.The Movilizer for SAP Track & Trace is so easy and quick to set up, that any super user in the warehouse is able to set up new devices without helpdesk support. |
|
| It does not require any end user training |
The Movilizer has been designed to be used not only by internal employees but also by externals (third parties, temporary staff or even final customer); in those scenarios training and change management are just not feasible. The application itself needs to be self explaining. For this reason, the reason the Movilizer is 100% process driven, and not information driven. The Movilizer works like a wizard. This means that the process is built in the sequence of screens. All what the user needs to do is to read the information on the screen, eventually to capture data if relevant and to confirm with "OK" or to go back with "BACK". The user has never to decide between more than two options "BACK" or "OK".  |
|
| It takes weeks to implement and you can do it yourself |
The Movilizer has been designed to be used not only by internal employees but also by externals (third parties, temporary staff or even final customer); in those scenarios training and change management are just not feasible. The application itself needs to be self explaining. For this reason, the reason the Movilizer is 100% process driven, and not information driven. The Movilizer works like a wizard. This means that the process is built in the sequence of screens. All what the user needs to do is to read the information on the screen, eventually to capture data if relevant and to confirm with "OK" or to go back with "BACK". The user has never to decide between more than two options "BACK" or "OK". But more important: should the standard Movilizer for SAP PM template not meet 100% your requirements, you can change or enhance it yourself. The entire mobile app is built in ABAP/4. The Movilizer does not require any client or middleware development. The mobile app business logic is 100% under your control in your SAP system. After 5 days Movilizer training, even a Junior ABAP developer can enhance any Movilizer template or even build completely new apps. |
|
| No Upfront Licenses | You can use the Movilizer without purchasing any upfront licenses. | |
| Monthly support fees (SaaS) |
In order to use the Movilizer all you pay is a monthly support fee for each live user (The monthly fee depends on the number of users and scenario, but the range is normally between 15€ and 30€ per user per month). Third level support is included in the mentioned fee. First and Second level support can be purchased separately if wished (although this is typically something your IT department can do itself. The Movilizer offers as well the possibility to pay per executed transaction (rather than per user/month). This option is especially interesting if the purpose is to give your final customer access to the Movilizer (E.g. they can create malfunction notifications whenever an asset is not working rather than calling the service helpdesk). In this scenario the transaction based payment will probably be more competitive. |
|
| You are 100% in control of future changes and enhancements in the app. | Since the entire business logic is in the backend, you are free to change the application whenever you require it. To add new fields, remove or add screens or change the flow of the mobile application you don´t need any help from Movilitas. You can do it on your own with your own IT resources (all you need is ABAP/4 skills) without having to contact Movilitas any time you need changes in the mobile application. | |
It is the most flexible mobile app: |
The Movilizer is the most flexible mobile app for SAP Track & Trace in the market today. | |
| It is device agnostic |
A mobile application for Track & Trace should work offline / online and should offer flexibility in the mobile device selection: it should support various different models of ruggedized PDAs but also support of fix scanners, forklift terminals, or even normal mobile phones.
The Movilizer Client is a very small piece of software (some few Kilobytes) written in different native languages (depending on the target device) capable of running in offline / on nearly any mobile phone, smart phone, PDA, Tablet PC, Netbook or Notebook. Please refer to http://www.movilizer.com/Supported_Devices/ for a complete list of supported devices. The deployment of the Movilizer Client is done via SMS or simple file transfer and is exactly as easy as downloading a ringtone (average set up time is seconds). The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step. The Movilizer leaves you full flexibility in the device choice and in the type of synchronization mechanism. And this is mainly because the Movilizer is device agnostic and supports multiple synchronization mechanism: LAN, Wi-Fi, GPRS / 3G, ActiveSync etc. |
|
| Configuration instead of development (Movilizer customizing in SPRO) |
The Movilizer for SAP Track & Trace offers easy and centrally managed configuration and installation possibilities for any of the individual devices and sites. Devices and user roles can be configured centrally in order to define a range of location configuration options and parameters, which include:
1. Assignment of menus and functionalities to users, user roles and sites In the Movilizer configuration workbench (part of the certified standard Movilizer connector for SAP) it is possible to configure not only the main functions and menus but also the individual screens from the different functions. See below for example the screen for entering the delivery ID reference number. Any label, any field and subsequent action, any validation can be configured and / or enhanced centrally via the Movilizer configuration workbench. Below some of the screenshots of the Movilizer configuration workbench for user menus. Here it is possible to define and package role dependent menus. For each functions (=business step in Movilizer language) it is possible to define an icon, a sequence in the main menu, the exact name etc. Each function can be activated or deactivates depending on the particular user role. If new functions are developed (in ABAP) those can easily be added to an existing application via the Movilizer configuration workbench. Via the Movilizer configuration workbench you basically configure the following:
  2. Global Location Number (GLN) assignment to mobile devices It is possible to centrally assign mobile users to reading points, GLN locations and time zones. Changing the assignment here of a given mobile user to a different location will automatically change the parameter in the EPCIS message for all messages proceeding from that particular given mobile user.  As depicted in the screenshot above, this transaction also allows time setting and time zones assignment to mobile devices and locations. 3. Language and user settings Users can are assigned to phones numbers in the customizing. In case of PDAs without GSM capabilities a device Key replaces the Phone Number for deployment purposes.  4. Packaging and conversion settings to EPCIS and other protocols Also in the Movilizer it is possible to define the EPCIS data packaging based on types of events and also based on number of events from a given location.  5. Application monitoring Application monitoring can be done in the SAP Connector directly via the Movilizer specific monitoring transactions for aggregated monitoring, or via the standard SLG1 transaction for low level message monitoring as depicted in the two screenshots below.   |
|
| It allows changing processes on the fly | The Movilizer gives you the agility and flexibility to adapt to any changing requirements. You can add, delete or change any field or screen without any interruption to operations. The final Movilizer users will not even realise it. The Movilizer combines the advantages of pure online applications (centralised software logistics, instantaneous deployment etc.) with the charm of offline applications. | |
| You can create "mash-ups" (interfacing SAP with non-SAP) on the mobile device |
With the Movilizer you build your app like Lego. Our highly granular building blocks are called "Movelets" and allow you to interface any SAP Module (PM, MM etc.) and any non SAP application on the mobile device. For the mobile User, a single app. For your IT team, simple standardised Lego pieces easy to support and to further develop.  A mash up example in the screenshot above. Even any Excel worksheet containing a simple survey can be embedded in the application flow of the normal execution of e.g. SAP orders. The filled survey is transferred from Movilizer back to the excel Workbook. For the user one single application. Technically two totally different apps: The SAP PM app containing the work order and the excel app containing the simple survey. |
|
Integration |
||
| Multi Backend integration via the Movilizer cloud (with SAP OER, SAP AII, SAP ERP or non SAP). | The Movilizer for SAP Track & Trace can be integrated with SAP OER (via SAP PI or directly) with SAP AII or with SAP EM (for Transport Management processes for example). But the Movilizer is also able to handle | |
| "On device background integration" with DSD, PoD and WM mobile applications |
A mobile application for Track & Trace should work offline / online and should offer flexibility in the mobile device selection: it should support various different models of ruggedized PDAs but also support of fix scanners, forklift terminals, or even normal mobile phones.
The Movilizer Client is a very small piece of software (some few Kilobytes) written in different native languages (depending on the target device) capable of running in offline / on nearly any mobile phone, smart phone, PDA, Tablet PC, Netbook or Notebook. Please refer to http://www.movilizer.com/Supported_Devices/ for a complete list of supported devices. The deployment of the Movilizer Client is done via SMS or simple file transfer and is exactly as easy as downloading a ringtone (average set up time is seconds). The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step.
|
|
| Development only in backend (e.g. ABAP/4). | Since the entire business logic is 100% in the backend, you are free to change or enhance the application whenever you require it. To add new fields, remove or add screens or change the flow of the mobile application you don´t need any help from Movilitas. You can do it on your own with your own IT resources (all you need is ABAP/4 skills) without having to contact Movilitas any time you need changes in the mobile application. This guarantees your total independency from Movilitas as. | |
The Movilizer for Track & Trace
Architecture
1 The Movilizer SAP Connector
(for SAP OER, SAP EM or SAP AII)
The Movilizer Connector: the Movilizer Connector for SAP OER can be installed on SAP OER, SAP AII or in SAP PI and contains the business logic of the mobile application.
The Connector itself fulfils the following functions:
- Centralized configuration of mobile application:it allows the centralised configuration of the mobile application. Required functions, menus and user settings can be defined and managed centrally in the Movilizer connector for Track & Trace.
- Executes the EPCIS conversion:it is here where messages are converted into the EPCIS standard protocol for further processing. This allows the central configuration and assignment of devices to GLNs, reading points or even to time zones.
- EPCIS message packaging:thanks to the EPCIS connector, it is possible to package incoming messages and only run the conversion and further processing once a given number of messages are waiting in the inbound queue. Here it is also possible to group messages by location for example.
The Movilizer SAP Connector uses the web service functionality of SAP. With SAP Basis Rel 7.0 SP14, the SAP web service functionality has been improved and the Movilizer SAP Connector package relies on these adjustments. The required minimum level to implement the delivered package containing the web service proxy is therefore
→ NetWeaver 7.0 with SP 14 or later
Should your backend system not fulfill this requirement, the Movilizer SAP Connector components can be deployed in a distributed manner (one NetWeaver 7.0 system in your landscape is enough to enable the Movilizer to connect to any of your SAP older systems).
2 The Movilizer Cloud
The Movilizer Cloud: it is a secured multitenant and hosted middleware with 99,5% guaranteed availability that can connect any backend system with any mobile phone by sending and receiving encrypted business data in both directions. Because it is multitenant it allows economies of scale (single infrastructure is leveraged by many tenants). The Movilizer cloud follows the classic principles of Software as a Service (SaaS). For large implementation there is an option to build a Movilizer private cloud.
The following functions are provided out of the box by the Movilizer cloud:
- Staging area: any messages sent from the mobile devices (e.g. captured product IDs) or to the mobile devices (e.g. ERP delivery documents) are stored in the staging area waiting for delivery to the mobile devices or backend.
- Message validation: the cloud validates any incoming messages to ensure that only messages with the right structure are being further processed.
- Infrastructure management: the cloud offer compression and decompression (from XML into binary and vice-versa) and ensures that regardless of the network the messaging arrives.
- Central monitoring and Software logistics for Movilizer Clients: the Cloud offers full monitoring of the Mobile Clients. For instance which device synchronized what and when (also possible to see which device did not synchronized in a given period of time).
- Mobile Client software logistics and deployment: Which devices has which software version and which functions assigned (= Movelets); it also allows not only monitoring but its active management.
- Message Tracking: each synchronized message from the Movilizer clients to SAP OER or vice versa receive a message tracking ID and can be monitored.
- Timestamp synchronization: at the beginning of each synchronization, automatically, the Movilizer cloud always calculates the timestamp difference between the Movilizer clients and the cloud, so that the cloud can recalculate the correct time. The client is then informed and if configured accordingly the client itself can readjust the time to align with the cloud current time.
- End To End Encryption: end to end encryption is standard. This means that in the cloud the message payload is not readable (only the header information and tracking ID of the messages but not the contents). This is an optional feature which is deactivated per default.
Important remark: the Movilizer cloud itself is a technical layer which does not contain any business process logic. This makes end to end message encryption possible.
3 The Movilizer Client
It is very small software (some few Kilobytes) written in different native languages (depending on the target device) capable of running on nearly any mobile phone, smart phone, PDA, Tablet PC, Netbook or Notebook. Please refer to http://www.movilizer.com/Supported_Devices/ for a complete list of supported devices.
The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step. The Movilizer uses the native user interface of your mobile phone or PDA.
The deployment of the Movilizer Client is done via SMS and is exactly as easy as downloading a ringtone (average set up time is seconds). The Movilizer client works online—offline. This means that you don't need connectivity to be able to work with it. The synchronization can be triggered automatically in background, explicitly by the mobile user or based on a process step.
Other Movilitas Sites
(c)
Movilitas Solutions GmbH, 2011