Set Up Connected Assets and Equipment

You can use the data from smart equipment and assets to automate tasks in Manufacturing and Maintenance, such as automatically updating production quantities and generating exceptions and maintenance work orders for faults and errors.

You need to provision and configure the SCM Core Service- Smart Operations service on your instance before you can capture and evaluate events from connected assets in Maintenance and connected equipment in Manufacturing. Once the SCM Core Service- Smart Operations service is enabled on your Oracle Public Cloud region instance, follow the implementation steps described in the following sections.

Before you start

Your IIoT environment or external system should be available and configured. You should have connected your assets and machines, and created the required attributes to identify and generate data.

Smart Operations currently support the following standard events:

Operation Execution Start: Indicates the start of a work order operation at a workstation.
Operation Execution Stop: Indicates the stopping of work order operation execution at a workstation.
Quantity Report: Reports production quantities, such as completed and rejected quantities, for a work order operation at a workstation.
Asset Fault: Indicates a fault generated by a connected equipment or asset. Faults are associated with fault codes and can be of types Diagnostic and Failure.
Asset Status: Indicates the status of the connected equipment or asset, such as Idle, In Use, or Down.

Note: See Create Operational Events in the REST API for Oracle Supply Chain Management Cloud guide for sample payload examples.

Your IIoT environment or external system should have been configured to map the relevant equipment or asset attributes to the event payload attributes specification. This includes the following:

Direct mapping for attributes that are fetched directly from the connected asset or machine:
- Fault Code (String)
- Work Order Number (String)
- Operation Sequence (Number)
- Serial Number (String)
- Quantity (Number)
Derived mapping for attributes that are transformed into Oracle-specified event attributes, including the supported List of Values (LoV).
The Status LoV supports the following: “Idle, In Use and Down”. The Quantity Report Type LoV supports “Complete and Reject”.
Additional optional mappings if required.
For example, you may need to map fault types to fault codes. Say, fault type Failure maps to fault codes E01 and E03, and fault type Diagnostic maps to fault codes E02 and E04.

You should have configured the authentication mechanism to post events from your external system or IIoT environment to Smart Operations, as follows:

The IIoT environment or external system should use OAuth Integration for authentication and authorization to be able to post data for Smart Operations.
The IIoT environment or external system should have the provision to capture Oracle Client ID, Secret (masked), Scope, Oracle AUTH Token URL, and Oracle Fusion Cloud Endpoint URL.
The IIoT environment or external system should be able to invoke the Oracle AUTH Token URL with client ID, secret, and scope to retrieve the bearer token.
The IIoT environment or external system should be able to POST events to the Oracle Fusion Cloud Endpoint URL using the retrieved bearer token.
Note: See Create Operational Events in the REST API for Oracle Supply Chain Management Cloud guide for sample payload examples.

Create an Identity Domain Application and Configure Authorization

Generate a client ID and client secret that can be used to configure OAuth integration in your IIoT environment or external system. You can create one or more identity domain applications for each integration.

Sign in to your Oracle Identity Cloud Service console as an administrator.
From the navigation menu, select Identity & Security.
Under Identity, click Domains and select the identity domain.
Click Integrated applications.
On the Integrated applications page, click Add application.
In the Add application dialog, select Confidential Application and click Launch workflow.
Provide a name for the application. For example, SMART_OPERATIONS_HTTP_CLIENT.
On the Configure OAuth step, select Configure this application as a client now under Client configuration.
Under Authorization, select Client credentials.
Under Token issuance policy select Add resources.
Under Resources, click Add scope.
Search for the scope spectra-scm-core.
Under Select scope, select Urn:opc:resource:fusion:{namespace}:scm-core/api/scm-core/operational-data and click Add.
Here {namespace} is your instance namespace.
Click Next, then Finish.
Click Activate to activate the application.
You can get the client ID and client secret under the General Information section.

Enable Security Console External Application Integration

Enable the Security Console for your connected assets and equipment, which facilitates integration with your IIoT environment or external system.

To begin, set a profile value that prepares the Security Console to work with permission groups and related objects. In the Setup and Maintenance work area:

Click the Tasks panel, and click Search.
Search for the string Manage Administrator Profile Values.
Click the Manage Administrator Profile Values task in the search results.
In the Search: Profile Option section, enter ORA_ASE_SAS_INTEGRATION_ENABLED in the Profile Option Code field and click Search.

A record of the ORA_ASE_SAS_INTEGRATION_ENABLED profile option code appears.
In the row for the Site profile level, select Yes in the Profile Value field.
Click Save and Close.

Enable Permission Groups

You can enable permission groups for the predefined job role. Alternatively, if you are using your own custom job role for data ingestion, you can enable permission groups and add the appropriate duty role for operational data ingestion to the role hierarchy.

Use the following steps to enable permission groups for the predefined job role:

Click Roles in the security console.
To access the security console, click Navigator > Tools > Security Console.
Search for the ORA_SCM_SMO_SMART_OPERATIONS_SERVICE_AGENT_JOB role.
Select the Edit Role option from the search result section.
Click Enable Permission Groups to enable permission groups for the role. Confirm your choice.
Click the Summary step and click Save and Close. You can also navigate to the Summary step by clicking Next until you reach the final step.

Use the following steps to use a custom job role:

Click Roles in the security console.
To access the security console, click Navigator > Tools > Security Console.
Search for the ORA_SCM_SMO_SMART_OPERATIONS_SERVICE_AGENT_JOB role.
Select the Copy Role option from the search result section.
Select Copy top role and inherited roles in the Copy Options dialog and click Copy Role.
Optionally edit the name and code for the custom role.
Click Enable Permission Groups to enable permission groups for the role. Confirm your choice.
Click the Role Hierarchy step. You can also click Next until you reach the Role Hierarchy step.
Click the Roles and Permission Groups tab and click Add Role.
Search and add the duty role ORA_DR_SMO_INGEST_OPERATIONAL_DATA_DUTY.
Click the Summary step and click Save and Close. You can also navigate to the Summary step by clicking Next until you reach the final step.

Assign Job Role to the Client ID

Associate the Smart Operations Service Agent job role (ORA_SCM_SMO_SMART_OPERATIONS_SERVICE_AGENT_JOB) or the custom job role with the confidential application Client ID. This ensures that the Client ID generated for OAuth integration in the IIoT environment or external system is authorized to post events to Smart Operations.

Customers currently need to create an SR and provide the following information to Oracle Support for Manufacturing:

Select Product Module - Oracle Fusion Manufacturing Cloud Service.
Select Category - Work Execution.
Select Subcategory - Manage Work Orders.
Select Component: Installation Issue (INSTALL).
Copy and paste this text into description area of the SR: Assign the job role {Job Role Code} to the {Client ID}.
Replace {Job Role Code} and {Client ID} with the values from your environment.

Use the following SR information for Maintenance:

Select Product Module - Oracle Maintenance Cloud Service.
Select Category - Maintenance Work Orders.
Select Subcategory - Maintenance Work Orders.
Select Component: Installation Issue (INSTALL).
Copy and paste this text into description area of the SR: Assign the job role {Job Role Code} to the {Client ID}.
Replace {Job Role Code} and {Client ID} with the values from your environment.

Verify Event Payload Transmission

Invoke the Oracle AUTH Token URL with client ID, secret, and scope to retrieve the bearer token. Post events to the Oracle Fusion Cloud Endpoint URL using the bearer token.

Note:

Your external system or IIoT environment should be able to get a SUCCESS response on event POST. If the response is not received, the system should be able to retry to POST the event. Additionally, your external system or IIoT environment should be able to capture the logs of both successful and failed POST events.

What to do next

Smart Operations let users create operational rules for asset faults and asset status events. These operational rules evaluate the incoming events and execute automated workflow actions if the rule conditions are met. To create operational rules using Smart Operations, refer to the 25A What's New material for Manufacturing and Maintenance:

Smart Operations maintain a record of operational events, such as operation execution start or stop, quantity report events, and asset status events. You can view the operational event records and also view operational events that failed to process. To learn more about viewing operational events, refer to the 25A What's New material for Manufacturing:

Complete Work Order Operations Automatically Using Equipment Signals at Workstations