This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 29 SEP 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.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Custom Dashboards for Vehicle Types and Drivers
You can create a custom dashboard for vehicle types and drivers to visualize your most relevant business metrics in a single pane and use it to track their respective performances.
For example, you can create a dashboard for vehicles and then use it to track metrics such as availability status, consumed fuel cost, idling duration, and so on.
Steps to Enable
You don't need to do anything to enable this feature.
Clustering Support for Entities of the Same Type
The IoT application can automatically cluster entities based on attribute behavior. You can choose to create a clustering configuration for an asset type. This lets IoT group entities with similar attribute behavior over the specified data window.
For example, say you have a temperature sensor entity-type, but different sensors have different normal temperature ranges, depending on whether the sensor is being used to measure ambient temperature or furnace temperature. A cluster is able to separate the ambient sensor entities from the furnace sensor entities.
The Clustering tab in Operations Center shows you the details on the clusters, including sensor values and the cluster memberships that the application creates. You can also visualize the tightness of each cluster, and the distances between individual clusters.
Steps to Enable
You don't need to do anything to enable this feature.
Feedback Center for System Events
The Feedback Center notifies the administrator about system activity that may require administrator review and action.
For example, the system may need to notify you about storage capacity issues. Or the system may wish to report analytics issues, such as a metric computation being suspended, or a prediction-scoring failing two times in a row.
The administrator can review the details for an event of interest, mark the issue as acknowledged, and choose to comment against the event with updates or remarks for other administrators.
Steps to Enable
You don't need to do anything to enable this feature.
Feedback Center for System Events
The Feedback Center notifies the administrator about system activity that may require administrator review and action. For example, the system may need to notify you about storage capacity issues.
The administrator can review the details for an event of interest, mark the issue as acknowledged, and choose to comment against the event with updates or remarks for other administrators.
Steps to Enable
You don't need to do anything to enable this feature.
Support for Process Manufacturing Work Orders
Production Monitoring now supports process manufacturing work orders in addition to discrete manufacturing work orders. Use the factory production view to see the various stages and operations for a process work order. The work order view, together with associated factory and machine metrics, is now available for the primary product.
For each operation in the process work order, you can see the various serial and parallel routing tasks, together with the operator and machine resources associated with each routing task.
You can use both system and custom metrics with process work orders. System metrics, such as the number of in-process and pending work orders are available by default. You may also wish to create custom metrics that use work order data, such as batch quantity or reject/scrap data.
Steps to Enable
You don't need to do anything to enable this feature.
Production Exceptions for Machine Incidents
Production Monitoring can notify Manufacturing Cloud about machine incidents that affect the completion of a work order. The notifications can include additional details, such as the incident severity and estimated downtime.
You can configure rules to create production exceptions in Manufacturing Cloud corresponding to incidents in Production Monitoring. When you subsequently resolve or withdraw an incident in Production Monitoring, IoT automatically closes the production exception in Manufacturing Cloud.
Alternatively, if you close the production exception in Manufacturing Cloud, the incident is automatically resolved in Production Monitoring. If you also happen to have a maintenance work order for the same incident in Maintenance Cloud, then the incident status is updated to Work in Progress in Production Monitoring.
Steps to Enable
You don't need to do anything to enable this feature.
Clustering Support for Entities of the Same Type
The IoT application can automatically cluster entities based on attribute behavior. You can choose to create a clustering configuration for a machine type. This lets IoT group entities with similar attribute behavior over the specified data window.
For example, say you have a temperature sensor entity-type, but different sensors have different normal temperature ranges, depending on whether the sensor is being used to measure ambient temperature or furnace temperature. A cluster is able to separate the ambient sensor entities from the furnace sensor entities.
The Clustering tab in Operations Center shows you the details on the clusters, including sensor values and the cluster memberships that the application creates. You can also visualize the tightness of each cluster, and the distances between individual clusters.
Steps to Enable
You don't need to do anything to enable this feature.
Feedback Center for System Events
The Feedback Center notifies the administrator about system activity that may require administrator review and action.
For example, the system may need to notify you about storage capacity issues. Or the system may wish to report analytics issues, such as a metric computation being suspended, or a prediction-scoring failing two times in a row.
The administrator can review the details for an event of interest, mark the issue as acknowledged, and choose to comment against the event with updates or remarks for other administrators.
Steps to Enable
You don't need to do anything to enable this feature.