Adobe Captivate - Oracle



Slide 2 - Oracle Transportation Management Transfer of Information Oracle Transportation Mobile 1.0 Functional Overview

[pic]

Slide notes

Welcome to the Oracle Transportation Management Transfer of Information session explaining the enhancements to the Oracle Transportation Mobile 1.0 section of the OTM 6.4.1 release. This functional overview provides a high-level description of the key features added to Oracle Transportation Mobile 1.0 in the OTM 6.4.1 release.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 3 - Use of the information, documents and online training courses (collectively, “Materials”) found on this area of the Site constitutes agreement with the following terms and conditions (as well as those set forth in the Purpose and Disclaimer sections below): 1. Oracle is pleased to allow its business partner (“Partner”) to download and copy the Materials found on this area of the Site. The Materials are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create derivative works from the Materials. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties. 2. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. 3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials. Materials are provided "as is" without warranty of any kind, either express, implied or statutory, including without limitation the implied warranties of merchantability, satisfactory quality, fitness for a particular purpose, accuracy, timeliness and non-infringement of third-party rights. The information contained herein is subject to change without notice. 4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of these Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.

[pic]

Slide notes

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Purpose This document provides an overview of features and enhancements included in Oracle Transportation Mobile Release 1.0 and applicable updates. It is intended solely to help you assess the business benefits of upgrading your existing Oracle Products to this release, or implementing completely new Oracle developed products, and planning your I.T. Projects. Disclaimer This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement or other applicable contract with Oracle, with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without Oracle’s prior written consent. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is intended to outline our general product direction. It is intended for informational purposes only and solely to assist you in planning for the implementation and upgrade of the product features described. Release information contained in this document is not a firm development plan. Release information published here should not be used as the basis for customer delivery commitments, as part of marketing efforts, or during contract negotiations. This is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality, and inclusion or not thereof in the commercially available version of the Software, if any, is subject to change at any time and is always at Oracle’s sole discretion. This document is not considered part of the applicable program documentation. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

[pic]

Slide notes

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 5 - Objectives

[pic]

Slide notes

This session will prepare you to:

• Identify the new functionality in this release

• Learn how the new features address business needs

• Determine how to configure the new functionality

• Understand any dependencies or interactions

• Find additional release information and resources

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Program Agenda

[pic]

Slide notes

This presentation will cover the following topics:

• Prior Designs: In this section we will look at Oracle Transportation Management’s earlier mobile offerings to see how they evolved to today’s solution.

• Current Design: In this section we will briefly examine what the goals were for this release and describe what the capabilities are of the new Mobile app.

• Use Cases: This is the bulk of the presentation and will introduce the use cases that this app intends to solve, as well as an in-depth look at the screens that support these use cases.

• Additional Considerations: Some closing thoughts about other features the app offers, as well as how to download the app.

• Additional Resources: This section describes where to go to get additional help.

Notes

| |

| |

| |

| |

| |

| |

Slide 7 - Prior Designs

[pic]

Slide notes

First we will review prior designs of Oracle Transportation Mobile.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Prior Design

[pic]

Slide notes

OTM’s “Wireless” feature was available in the 5.5.x timeframe and offered basic mobile access to OTM. The feature at the time was not as deep as our current Mobile offering and suffered from being developed on a now-deprecated technology. The Wireless Application Protocol, or “WAP”, technology had many limitations at the time, ultimately leading to its replacement by the more common HTML-based browsers. HTML is commonly available today on modern mobile devices such as Android, Blackberry, iOS, and Windows phones. This technology change is what led to the development of OTM’s next generation mobile solution.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Prior Design

[pic]

Slide notes

• In version 6.3, OTM introduced its “Mobile Site”, based on HTML 5 browser-based technology. Access to OTM’s mobile site is gained by navigating to the standard OTM URL used by desktop users. OTM automatically detects that access is being requested by a mobile device and presents the mobile access site that is seen here.

• The 6.3 Mobile Site provides you with simple access to common carrier-centric tasks, such as:

o Viewing Tenders, Accepting/Declining Shipments, Entering Shipment Events and Viewing Statuses of Shipments.

o This solution is only supported on 6.3.x versions of OTM.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 10 - Current Design

[pic]

Slide notes

Next we will see what drove the next generation of OTM’s mobile solution.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 11 - Goals

[pic]

Slide notes

• The main goal of OTM’s 1.0 mobile solution was to recreate the 6.3 Mobile Site on Oracle’s Mobile Application Framework (MAF) technology to provide downloadable, native iOS and Android apps. At this time the Mobile Application Framework does not support building apps on Windows Mobile, so no app is available for this operating system.

• Creating a downloadable app provides a more natural mobile experience via gestures such as swiping, scrolling, and rotating. A native app has other benefits, such as providing a local database for access when out of a carrier or Wi-Fi network.

• Finally, providing reusable APIs for custom development was also a high priority. This would allow you to build “lite” apps that leverage the same APIs that OTM’s mobile solution uses to access the OTM server.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 12 - App Store Description

[pic]

Slide notes

Here you see the description of OTM’s Mobile app as it appears in Apple’s App Store as well as in Google Play. This provides a good summary of the capabilities of this app:

The Oracle Transportation Mobile app allows OTM customers to extend the use of the industry’s most powerful Transportation Management System to their mobile work force, drivers, and service providers. Simply download the app, point it to your instance of OTM, and instantly support these and other use cases:

• View, accept, and decline shipment tenders

• Provide current shipment status information, including GPS position

• Upload photos

• Collect signatures for proof of delivery

• Mark shipments as favorites for easy look-up

• View shipment, stop, and order detail

• View shipments on a map

Note that the Oracle Transportation Mobile app is not a standalone tool and must be connected to an instance of Oracle Transportation Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Use Cases

[pic]

Slide notes

Next we will review the use cases that this app was designed to solve. We will also demonstrate each use case via screenshots of the mobile app.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Use Cases

[pic]

Slide notes

The mobile app is designed to be used by a carrier or driver to support the following use cases:

1. I want to review tenders that have been offered to me.

2. I want to accept or decline tenders.

3. I want to view and update the status of shipments that I have accepted.

We will demonstrate how each of these use cases is performed next. First we will start with login and basic navigation of the app before proceeding through each use case.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 15 - Launch and Login

[pic]

Slide notes

From the device’s desktop, locate and tap on the OTM app. In this image it is the last red icon containing a truck with a magnifying glass and the word ORACLE.

A splash screen will display while the app is loading.

An End User License Agreement is displayed next. Read through the agreement and if you agree with the terms tap Agree. You will not be able to use the app unless you have agreed to these terms.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Launch and Login

[pic]

Slide notes

Enter the URL for the OTM instance to which you want to connect and tap GET STARTED. This URL can be changed in the future from within the app if required.

The login screen will prompt you for a username and password. Aliases are not currently supported, so you must enter the full domain.user name and a corresponding password. There are options to remember the user name and to remain signed in. These options are selected by default and will save the corresponding information. The REMAIN SIGNED IN option will keep the user logged in for 8 hours before requiring a new session.

The Home screen is also called the Springboard. It provides a dashboard-like view of the shipments which have been tendered to and accepted by this user. The Tendered shipments section has two boxes summarizing the number of newly-tendered shipments as well as the total number of tenders awaiting a response. Once viewed, a shipment will no longer be considered new and will instead be counted in the ALL box. Tapping on either of these boxes will take you to that list of shipments.

Similarly, the Accepted Shipments section shows all shipments which have been accepted by this user. There are three boxes here, showing the number of exceptions, favorites and all shipments. Just as with the tendered shipment boxes, tapping on any of these boxes will take you to that list of shipments.

The circular arrow in the upper right hand corner is called the Refresh icon and will update the counts and data in this view. Counts are updated automatically whenever you navigate back to the Springboard from another view; however new data is only queried on login and when tapping the Refresh button.

The icon with the three parallel lines in the upper left hand corner will take you to the springboard menu. We’ll look at that next.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Launch and Login

[pic]

Slide notes

When you tap the Springboard Menu icon the springboard menu panel will slide out from the left side. The springboard menu provides various options:

First of all it displays the name of the user who is logged in.

• Change Server URL will allow you to change the OTM URL to which the app is connected. This could be useful when switching between test/production environments or when connecting to a different OTM customer altogether.

• Reset Local Database will remove all local data from the app and download fresh data. This would only be needed when directed by Support.

• Preferences opens the preferences menu. The only option here is to DISPLAY UOM AS ENTERED. By default OTM Mobile will display units of measure in the user preference set on the OTM server. This setting overrides that preference and will display values as they have been stored in the OTM database.

• About OTM will display app version and legal information.

• Full Site will open a new browser window so you can log on to the full desktop version of OTM. You will need to provide login information but the URL will be pre-populated.

• Help takes you to the app’s help files. Several help topics are provided to explain navigation, logic, and release notes.

• Finally, Logout will log the user out of the app.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 18 - Use Case 1: Review Tenders

[pic]

Slide notes

Now we will look at each of the use cases identified earlier, starting with reviewing tenders.

From the Springboard tap on the NEW box in solid blue.

We are taken to a list of tendered shipments. The tendered shipment list has two tabs, corresponding to the boxes we saw on the springboard. These tabs will take you between the NEW and ALL views of tendered shipments.

Each shipment in this view will give the shipment ID and respond by date and time. The service provider has until this deadline to accept the tender before it will be withdrawn. The blue circle to the left of the shipment ID indicates that this is a NEW shipment that has not been previously viewed by this user. Once you tap to see the details of the shipment, the circle will be removed and the NEW count will be decremented by the number of shipments viewed.

The first and last stops on the shipment are displayed next, along with the stop name and time of arrival. At this point, if you feel that you have enough information to make an acceptance decision about the shipment you can tap either the ACCEPT or DECLINE buttons below the shipment. If you need more information about the shipment you can tap anywhere on the shipment box to drill into more information. We will do this next.

The icons in the upper right hand corner of the last screen shot are the sorting icons. They allow you to control the order in which the shipments are displayed in this view.

Notes

| |

| |

| |

| |

Slide 19 - Use Case 1: Review Tenders

[pic]

Slide notes

Here we’ve decided to get more information about the shipment before deciding whether to accept or to decline. We arrived here by tapping on the shipment from the Tendered Shipments list. There are two tabs in this view: Stops and Shipment Details. The Stops view will list all stops on the shipment, total distance and time of the shipment and distance and time between each stop. Each stop will also have an icon showing the activity being performed at this stop – whether a pickup (arrow points into the truck) or a delivery (arrow pointing outward). There is a blue map icon just below the Shipment Details tab; this will plot the shipment stops on a map. We will see this view shortly. Again, if you have enough information to make a decision about this shipment you can choose to ACCEPT or DECLINE from this view.

First we want to see more information about the second stop on this shipment – Eugene, Oregon. To do this we tap on the stop.

The next screen shot is a detail of the Eugene stop. It shows information such as activities to be performed, appointments (if any), arrival time, departure time, ship unit count, and weight and volume related to this stop. There are additional drill-downs for location data and order information. In the upper right hand corner of the screen are up and down chevron icons. These allow you to navigate to the previous or next stops of the shipment.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 20 - Use Case 1: Review Tenders

[pic]

Slide notes

The first screen shot is what you see when tapping the map icon from the screen shot displayed previously. New to this view is the map view – displayed between the first and last stops of the shipment. You can interact with this map by sliding and zooming for more information. You can ACCEPT or DECLINE if desired. There’s also a Shipment List icon below the Shipment Details tab that will return you to the Tendered Shipments list.

Finally, you can tap on the Shipment Details tab to get an overview of the shipment. Equipment, total weight, total volume and shipment contact information is provided in this view. The app will invoke the device’s native text messaging, phone and email apps to immediately communicate with the person identified here when the corresponding icons are tapped.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 21 - Use Case 1: Review Tenders

[pic]

Slide notes

At this point we have completed Use Case 1: Review Tenders. Before moving on, let’s review information about the logic behind the data presented in the Review Tender screens:

The contact information provided in the previous view is pulled from the involved party on the shipment marked as the LOGSTICS contact.

Time zones are absent from the app in order to streamline the user experience. Any times unrelated to a location, such as the RESPOND BY time, are assumed to be in the device’s time zone. Any times related to a location, such as a shipment stop arrival, are displayed in THAT location’s time zone.

The date that is selected to display follows the same hardcoded logic that is used by OTM’s Shipment Visibility screen. OTM will display the actual date/time if it is available, otherwise it will display the estimated date/time if available, otherwise it will display the planned date/time.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 22 - Use Case 2: Accept/Decline Tenders

[pic]

Slide notes

In the second use case we will either accept or decline the shipment.

At this point we have reviewed all the information we need to ACCEPT or DECLINE the shipment. In each option there is a confirmation message displayed before committing the response. In the case of a DECLINE, you will also select a reason from the drop-down box and optionally enter a comment.

The action chosen here will be communicated back to the OTM server and the shipment will disappear from the Tendered Shipments view. If you have decided to accept the shipment, the shipment will be moved to those views.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 23 - Use Case 3: Update Status

[pic]

Slide notes

In this final use case we will submit a status against an accepted shipment.

We begin at the Springboard and drill into all accepted shipments by tapping the ALL box under Accepted Shipments.

You are presented with a list of Accepted Shipments and four tabs across the top of the page. These tabs correspond to the boxes we saw on the Springboard: Exceptions, Favorites, ALL and a new tab called Search. The Search tab allows you to quickly navigate to a shipment in the list by searching by shipment ID. This list also has sort options, accessed by the sort icon in the upper right hand corner.

The first shipment in the list has a yellow star to the left of the shipment ID. This indicates that the shipment has been marked as a favorite. Favorite shipments are marked by tapping the star and are unmarked by tapping the star a second time. All favorites are summarized under the FAVORITES tab for quick access. Favorites can be helpful to quickly identify high-priority shipments, shipments being executed, and for other user-defined purposes.

Each shipment in the list will also have a status describing its current state, such as On Time, Not Started or Delayed. It will also display the last event submitted against the shipment, along with the stop where the event was recorded. There is also a dialog box icon with a plus sign to indicate that a new event can be added against the shipment.

More information about the shipment can be viewed by tapping anywhere on the shipment.

In this last screenshot we see shipment and stop details similar to those presented on the Tendered Shipment detail. New to this view are the introduction of an Event Count as well as a table showing either estimated or actual time versus planned time for each stop. A status for each stop is also displayed. The event count is presented for each stop as well as for times between the stops. This allows you to enter events such as delays or breakdowns in between stops.

At the bottom of the screen there is an Add Event button. You tap this button to add a new shipment-level event. We will see this action next.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 24 - Use Case 3: Update Status

[pic]

Slide notes

Let’s review the logic behind the data presented in the Accepted Tender screens:

Shipments are automatically added and removed from the Accepted Shipments list depending on the status of those shipments. Once accepted, a shipment is added to this list. The shipment is removed when the status becomes ENROUTE_COMPLETED. The ENROUTE_COMPLETED status is driven by automation agents defined on the OTM server using events submitted against the shipment.

Favorites, as mentioned previously, are managed by tapping the star next to the shipment ID. Favorites are device-specific, meaning they do not carry across devices. Favorites are retained in the accepted shipments list even after the status of that shipment becomes ENROUTE_COMPLETED. This allows a user to continue to have visibility to that shipment.

The exceptions box on the accepted shipments list follows logic also used by OTM’s Shipment Visibility screen. If a shipment or any of its stops are delayed by more than 30 minutes the shipment will appear as an exception.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 25 - Use Case 3: Update Status

[pic]

Slide notes

From the shipment detail view we can drill into the stop details by tapping on one of the stops. Here we’ve tapped on the Denver, CO stop. As with the Tendered Shipments detail view, we can see relevant details about the stop, including events already submitted against the shipment stop. The second screen shot is a continuation of the first screen shot, showing the order detail drill-down option. If the shipment stop had multiple orders, multiple order lines would appear here.

If you choose to see more information about the location you can tap the location drill-down. The next view is the drill-down. An interactive, embedded map is provided by the underlying MAF architecture. When you tap the OPEN MAP button you will be taken to the device’s native map application. For iOS this would be the Map app; for Android this would be the Google Map app. From there you could navigate to that stop.

The contact information displayed here refers to the primary contact at the location.

The final screen shot here is the order detail, found by tapping on the order listed on the shipment stop. Order ID, weight, volume, ship unit count, and reference numbers are provided.

When you are ready to submit a new event you can tap the ADD EVENT button or icon present on most of the screens.

Notes

| |

| |

| |

| |

| |

| |

Slide 26 - Use Case 3: Update Status

[pic]

Slide notes

The Add Event screen comes pre-populated with some information from the device. The date/time and current location values are already present. You would select an event describing the type of event taking place, such as an arrival, departure or delay, and optionally add a photo, signature or remark.

The location can be changed by using the Location drop-down. When ADD EVENT is selected from a shipment stop, that stop is pre-populated in this field. The CURRENT LOCATION is only available when ADD EVENT is selected from one of the shipment views. This option sends the latitude and longitude of the device along with the event.

If you wish to add a photo – in order to capture a document, cargo damage, or otherwise document the shipment – you would tap the camera icon. From there you can either take a new photo or select an existing photo from your device’s photo library. You can also return to this view to manage photos already selected.

Next we’ll take a look at how to capture a signature.

Notes

| |

| |

| |

| |

| |

| |

| |

Slide 27 - Use Case 3: Update Status

[pic]

Slide notes

When you tap the signature icon you will see the first screen here. It will summarize the event selected in the previous screen (arrival, departure, etc.) and will allow you to type in the name of the person providing the signature. Tapping the “tap here to sign” text will bring up the signature capture screen.

The device supports both portrait and landscape orientations, both controlled by physically rotating the device. Landscape orientation will provide the signer with more real estate to sign against.

When satisfied, tap Done to save the signature.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 28 - Use Case 3: Update Status

[pic]

Slide notes

After tapping DONE on the signature screen, a thumbnail of the signature is added to the add event screen. You can also see that the photo count has been set to 1 to indicate that one photo has been selected. You can add a remark if desired.

When the SUBMIT button is tapped, the event is submitted to the OTM server and a confirmation message appears.

Events are saved to the OTM server; photos and signatures are saved as documents on the shipment and follow the capabilities offered by the document feature in OTM.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 29 - Additional Considerations

[pic]

Slide notes

Next we’ll review additional considerations about the Mobile app.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 30 - Downloading the App

[pic]

Slide notes

The app is available as a free download from the following sources:

• Android app via Google Play and

• iOS app via Apple’s App Store

The app is supported on all devices and versions certified by MAF 2.2

• The app has been optimized for smart phones but it is also compatible with tablets

• Please see Oracle Mobile Application Framework documentation for support details. Documentation is available on the Oracle Technology Network.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 31 - Customization Options

[pic]

Slide notes

While there are no customization options built into the apps themselves, you have the ability to make changes to suit your specific requirements. A Mobile Archive of the app is available with OTM 6.4.1. Customers who have separately licensed Oracle’s Mobile Application Framework can import this archive into their MAF project and make changes such as branding, translations, and label updates. A deployable app can then be built and distributed by the customer to their end users.

Customers wishing more control over their mobile experience can instead build apps from scratch leveraging the same Rest APIs that OTM Mobile uses to connect to the backend OTM server. These APIs are documented in OTM’s Integration Guide.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 32 - Offline Support

[pic]

Slide notes

As mentioned earlier, an added benefit of this mobile app is its ability to provide access to data while out of a carrier or Wi-Fi network. The app has a local encrypted database which stores shipments and related details when you log on to the app. This data is read-only while offline, as updates cannot be submitted while in this state. An error will be returned if you attempt to accept or decline shipments or submit shipment events while offline. These actions can be resumed once the connection to the network has been restored.

Note: OTM Mobile only detects an inability to connect to a network. It does not detect an inability to connect to the OTM server.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 33 - Additional Resources

[pic]

Slide notes

And finally, let's review additional resources.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 34 - Additional Resources

[pic]

Slide notes

Here are links for additional resources.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 35 - OTM Specific Resources

[pic]

Slide notes

OTM Transfer of Information Sessions are available for the releases shown here.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 36 - OTM Specific Resources

[pic]

Slide notes

Here you see information on accessing Oracle University classes for OTM.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download