This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 16 MAR 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, 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 described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Oracle IoT Fleet Monitoring Cloud Service now provides an enhanced user interface for effective tracking and monitoring of fleets, shipments, and their associated entities.
The Design Center, Operation Center, and Configuration menus let you design your artifacts, monitor your operations, and configure the application.
The Operation Center now includes the following views for your organization: Fleet Map, Fleet Dashboard, Shipments Map, Shipments KPI Dashboard, Vehicles, Shipment Transaction Logs, Shipment Summary, Shipments: Dashboard, Facilities, Trips, Drivers, Incidents, and Alerts.
The Design Center includes the following views to help the administrator create and configure the organizational artifacts: Organization, Vehicle Types, Vehicle Summary, Trips, Drivers, Shipments, Facilities, and Geofences.
The Configuration menu lets the administrator configure users, settings such as analytic controls and maps, connectors such as the Freight Tiger connector, and file uploads such as device models. These configurations are applied globally within the cloud service instance.
Integration with Oracle Warehouse Management Cloud Service (WMS)
Integration with Oracle Warehouse Management Cloud Service is now enabled. From the Organization view in Design Center, an administrator can add a WMS instance and verify connectivity to the instance.
After configuring the WMS integration for an organization, the administrator uses the Facilities view in Design Center to import facilities from WMS, edits the automatically created default check-in geofence, defines custom geofences, uploads floor plans, and defines rules for each imported facility.
Use the Facilities and the Fleet Dashboard views from the Operation Center of an organization to obtain all the facilities and their KPIs.
If a shipment stops at a facility, you can view the facility details from the shipment's Shipment Details page.
For a shipment imported from Oracle Transportation Management Cloud Service, Oracle IoT Fleet Monitoring Cloud Service locates its corresponding load in WMS and then automatically creates or updates the default appointment for the load in WMS using the shipment's start time. Oracle IoT Fleet Monitoring Cloud Service also updates the appointment in WMS whenever the shipment ETA changes.
In addition to the form-based trip creation process, an administrator can now create a trip using an existing trip template for the organization.
The steps to create a trip template have changed. As an administrator:
-
You do not need to upload a CSV file of a trip template.
-
When you create a trip from the Trips view of Operation Center, you can select the option to save it as a trip template for the organization.
-
From the Trips view of Design Center, you can create a trip template for an organization using a form-based user interface.
You can now create and apply rules on trips.
New System-defined Alert for Rule Engine
A generic system alert, RESystemAlert is now available in addition to the existing system-defined alerts. When creating an alert based rule, you can select RESystemAlert for use cases that do not fall into the GeofenceViolation, IdlingSystemViolation, or SpeedViolation categories.
A configurable setting to enable automatic shipment completion is now available at the organization level. The setting is enabled by default, so that the shipment automatically completes after the shipment exits the last stop.