This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 12 APR 2022 | Production Monitoring | Updated document. Added new features for Production Monitoring. | |
| 12 APR 2022 | Asset Monitoring | Updated document. Added new features for Asset Monitoring. | |
| 08 APR 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
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.
Support for User-Defined Metrics in Rules
When you define conditions in rules, you can now use custom metrics in addition to system-defined metrics, attributes, alerts, and location. This feature lets you use values of both formula-based and duration-based custom metrics.
Display of Stop Geo-Fences and Route Geo-Fences in Map Views
On the Trip Map or Shipment Map view, you can optionally view system-created stop geo-fences of trips or shipments. As a result, you can effectively monitor your trips and shipments for location pings received within the stop geo-fences, which help in accurate detection of arrivals and departure events.
Unavailability of Freight Tiger Connector
The feature of using the Freight Tiger shipment connector to integrate Oracle IoT Fleet Monitoring Cloud with the Freight Tiger platform has been discontinued.
Direct Ingestion of Sensor Data
Your digital twin assets are now directly addressable over the network, using standard protocols, authentication mechanisms, and payload formats. Ingest IoT data from directly connected devices, gateways, and network servers directly into your asset and machine sensor attributes. Choose direct ingestion to eliminate the need for registering devices and device models, and for creating IoT messages.
Use standard HTTP or MQTT protocol to send sensor data in JSON or CSV format. The application supports mutual authentication using certificates in addition to basic authentication.
The application lets you download ready-to-use schema samples for your entities. If you have custom payloads, use the interpreter editor interface to create the mappings and routing.
Use Dynamic Attributes to Set and Monitor Custom Asset States
Use dynamic attributes to store custom data that changes often, such as the asset operating mode. For example, an asset may have various operating modes, such as idle, low, medium, high, and maintenance.
You can track the current and historical values for your dynamic attributes in the digital twin view, along with your sensor attributes. Use the operations center, or automatic action-based rules to update the dynamic attribute values. You can use duration metrics to track the durations spent in different asset states.
Use OCI Anomaly Detection on Externally Stored IoT Data
OCI Anomaly Detection uses an Oracle-patented multivariate time-series anomaly detection algorithm originally developed by Oracle Labs. OCI Anomaly Detection helps avoid business disruptions through the early detection of multivariate anomalies.
If you are using the OCI Anomaly Detection AI Service, you can configure anomaly detection for externally stored Asset Monitoring data. You can convert the sensor data stored in Oracle Autonomous Database into the format expected by the OCI Anomaly Detection service, and use this data to create and train the anomaly model.
New Asset and Work Order Links to Oracle Maintenance Cloud
If you have imported assets from Oracle Maintenance Cloud, you can use the Assets page to open an asset page directly in Oracle Maintenance Cloud. You can also open a maintenance work order linked to an asset incident from the Incidents page.
New External Storage Options for Incidents and Warnings
You can now externally store incidents and warnings, in addition to your IoT sensor attributes and analytics data for long-term persistence. Choose one of the external storage options, Oracle Autonomous Database or OCI Object Storage, for long-term data availability and analysis.
Use the rich querying functionality in Oracle Autonomous Database, or chart and analyze the stored data in external applications, such as Oracle Analytics Cloud. For example, you can use analyses, projects, and dashboards in Analytics Cloud to find the answers that you need from key IoT asset data displayed in graphical formats. You can use applications such as Oracle Visual Builder to create dashboards and mashups.
SMS, Email, and HTTP Notifications
SMS and email notifications are now supported for warnings and alerts in addition to incidents. When an associated rule triggers an incident, warning, or alert, a notification is sent to all configured subscribers.
SMS and email notifications eliminate the need to monitor the IoT application continuously. All subscribers are actively informed about incidents, warnings, and alerts that need their attention. They can then use the mobile app or Web interface to look at, and address, the issues.
HTTP endpoint notifications are also supported for external applications. For example, an application, such as Oracle Transportation Management (OTM) or Oracle Intelligent Track and Trace can receive alerts and incident notifications from the connected IoT application.
Direct Ingestion of Sensor Data
Your digital twin machines are now directly addressable over the network, using standard protocols, authentication mechanisms, and payload formats. Ingest IoT data from directly connected devices, gateways, and network servers directly into your machine sensor attributes. Choose direct ingestion to eliminate the need for registering devices and device models, and for creating IoT messages.
Use standard HTTP or MQTT protocol to send sensor data in JSON or CSV format. The application supports mutual authentication using certificates in addition to basic authentication.
The application lets you download ready-to-use schema samples for your entities. If you have custom payloads, use the interpreter editor interface to create the mappings and routing.
Use Dynamic Attributes to Set and Monitor Custom Machine States
Use dynamic attributes to store custom data that changes often, such as the machine operating mode or production mode. For example, a machine may have different production modes, such as Product A, Product B, and Product C.
You can track the current and historical values for your dynamic attributes in the digital twin view, along with your sensor attributes. Use the operations center to update the dynamic attribute values. You can use duration metrics to track the durations spent in different machine states.
New External Storage Options for Incidents and Warnings
You can now externally store incidents and warnings, in addition to your IoT sensor attributes and analytics data for long-term persistence. Choose one of the external storage options, Oracle Autonomous Database or OCI Object Storage, for long-term data availability and analysis.
Use the rich querying functionality in Oracle Autonomous Database, or chart and analyze the stored data in external applications, such as Oracle Analytics Cloud. For example, you can use analyses, projects, and dashboards in Analytics Cloud to find the answers that you need from key IoT machine data displayed in graphical formats. You can use applications such as Oracle Visual Builder to create dashboards and mashups.
SMS, Email, and HTTP Notifications
SMS and email notifications are now supported for warnings and alerts in addition to incidents. When an associated rule triggers an incident, warning, or alert, a notification is sent to all configured subscribers.
SMS and email notifications eliminate the need to monitor the IoT application continuously. All subscribers are actively informed about incidents, warnings, and alerts that need their attention. They can then use the mobile app or Web interface to look at, and address, the issues.
HTTP endpoint notifications are also supported for external applications. For example, an application, such as Oracle Transportation Management (OTM) or Oracle Intelligent Track and Trace can receive alerts and incident notifications from the connected IoT application.
Enhanced Integration with Oracle Manufacturing
When configuring integration with Oracle Manufacturing, you can choose to create one-to-one mappings between the manufacturing organizations and your IoT organizations. If you choose one-to-one, the IoT server creates a separate IoT organization for each manufacturing organization that you enable in Oracle Manufacturing. If you choose many-to-one, then entities from each manufacturing organization that you enable in Oracle Manufacturing are imported into the selected organization in Production Monitoring.
Oracle Manufacturing automatically synchronizes the factory entities with IoT for all manufacturing organizations that you enable in Oracle Manufacturing. Production Monitoring no longer needs to pull these entities at regular intervals. The pull settings are deprecated and may be removed in a future release. The outbound sync from Production Monitoring works as before.