Managing Security and Access Control

This chapter covers the following topics:

Managing User Roles and Access

Oracle Adaptive Intelligent Apps for Manufacturing uses the following application persona and roles in process or discrete manufacturing to access the four modules, namely Insights, Predictions, Genealogy and Trace, and Factory Command Center, as well as the Setup page:

These persona have access to the application modules, features and data relevant to their role. Based on their roles they have access to perform the following functions:

Metadata Extraction and Data Preparation

The data analyst and data scientist can perform the following functions related to extracting metadata and preparing the data:

Model Building for Predictions and Insights

The data analyst and data scientist can perform the following functions related to model building for predictions and insights:

Model Evaluation and Publication

The data analyst and data scientist can perform the following functions related to evaluation and publishing models:

Predictive Analysis

The business user, data analyst, and data scientist can perform the following functions related to predictive analysis:

Historical Data Analysis

The business user, data analyst, and data scientist can perform the following functions related to historical data analysis:

Factory Command Center

The business user and data analyst can monitor the following functions using the Factory Command Center:

Genealogy & Trace

The business user and data analyst can perform the following functions related to genealogy and trace:

Administration

The applications administrator can perform the following functions:

REST APIs

To use REST web services, a user must have access to Oracle Identity Cloud Service with either the Identity Domain Administrator or Application Administrator role. The user must first register the AIAMFG Client Application in Oracle Identity Cloud Service, then use a third-party client such as Postman to access REST web services.

Warning: REST web services do not verify a user's organization access.

User Roles and Access

The following table shows the access to the modules and pages based on user roles:

Adaptive Intelligent Apps For Manufacturing Menu Roles and Access
  Business User Data Analyst Data Scientist Application Administrator
Home Yes Yes Yes Yes
From the Home page:        
Insights Yes Yes Yes Yes
Factory Command Center Yes Yes No Yes
Genealogy & Trace Yes Yes No Yes
Predictions Yes Yes Yes Yes
Setup No No No Yes
From the Insights page:        
Quality Yes Yes Yes Yes
Yield Yes Yes Yes Yes
Serial Quality Yes Yes Yes Yes
Serial Yield Yes Yes Yes Yes
Evaluation No Yes Yes Yes
Modeling No Yes Yes Yes
Data Preparation No Yes Yes Yes
Data Ingestion No Yes Yes Yes
Configuration No Yes (but not Time Series Feature Sets) Yes Yes
From the Genealogy & Trace page:        
Timeline Viewer Yes Yes No Yes
Network Viewer Yes Yes No Yes
From the Predictions page:        
Quality Yes Yes Yes Yes
Yield Yes Yes Yes Yes
Serial Quality Yes Yes Yes Yes
Serial Yield Yes Yes Yes Yes
Confusion Matrix No Yes Yes Yes
Modeling No Yes Yes Yes
Data Preparation No Yes Yes Yes
Data Ingestion No Yes (but not Sensor Devices Data) Yes Yes
Configuration No Yes (but not Time Series Feature Sets) Yes Yes
From the Setup page:        
Organization Access No No No Yes
Key Performance Indicators No No No Yes
Time Series Feature Sets No No No Yes
From the User Name menu:        
Preferences Yes Yes Yes Yes
Background Processes No No No Yes
Profile Yes Yes Yes Yes

For complete navigation details, see: Oracle Adaptive Intelligent Apps for Manufacturing Navigation

Creating and Managing Users

AIAMFG uses Oracle Identity Cloud Service to manage users and provide access to AIAMFG. When your organization signs up for an Oracle Cloud account and then orders subscriptions to cloud services, including AIAMFG, your organization designates one person to receive an email containing a link used to activate the services ordered. See: Getting Started with Oracle Cloud

Your Oracle Cloud account includes Oracle Identity Cloud Service (IDCS) as well as AIAMFG. See: Oracle Identity Cloud Service. The person who activates the services ordered is assigned the Identity Domain Administrator role by Oracle and can create other users with various roles. See: Managing Oracle Identity Cloud Service Users. The user with the Identity Domain Administrator role can manage AIAMFG users themselves or they can create one or more users with the IDCS User Administrator role to add the AIAMFG users and with the IDCS Application Administrator role to grant the AIAMFG application and roles to users.

The newly created user receives an email with a link to activate their Oracle Cloud account. Once the new user activates their account and they have been assigned a role for an application instance, then they can log in to the system and define their user preferences. Each user must specify their preferred organization and category set, at a minimum. See Defining User Preferences.

Your Identity Domain Administrator applies default settings to the entire identity domain in the cloud. If the identity domain encompasses multiple time zones and languages, for example, you may prefer to specify personal settings. AIAMFG supports multiple languages. To select one of these languages, see Setting Up Your IDCS User Profile.

To add a new user

Either a user with the IDCS Identity Domain Administrator role or the IDCS User Administrator role can add a new user.

  1. Navigate to Oracle Identity Cloud Service. Click your name icon, then Admin Console.

  2. In Oracle Identity Cloud Service, add a user. Refer to Creating User Accounts for the remaining steps.

  3. The user receives an email, asking them to activate their account. The user must click the link provided.

    The user still requires access to an application and an application role, as described in the next steps, before they can use the account.

To assign a user to an application

Either a user with the IDCS Identity Domain Administrator role or the IDCS Application Administrator role can assign a user to an Oracle application and application role.

  1. Navigate to Oracle Identity Cloud Service. Click your name icon, then Admin Console.

  2. In the Identity Cloud Service console, expand the Navigation Drawer, click Oracle Cloud Services, and then click your application, named AIAMFG_<Instance_Type>.

    Additional Information: Oracle Identity Cloud Service can have multiple application instance types. Examples of instance types include production (with an application name of AIAMFG_PROD) and test (with an application name of AIAMFG_TEST).

  3. Refer to Assigning Users to Oracle Applications for the remaining steps.

    Choose from the following roles:

    • Application Administrator

    • Data Analyst

    • Data Scientist

    • Business User

To assign organization access to a user

Only a user with the AIAMFG Application Administrator role can assign organization access to a user.

  1. Navigate to the Organization Access page.

    From the Home page, click Setup, then Organization Access.

  2. In the Organization Access page, use the Person Name search field to search for a user.

  3. Use the Org Code, Name search field to search for an organization.

    Tip: You can also narrow the list of organizations by selecting:

    • List all organizations

    • List organizations with user access

    • List organizations with no user access

  4. Select the check box for the organization.

    Tip: Select multiple organizations to update them all for the same user at the same time.

    the picture is described in the document text

  5. Click the plus icon to assign organization access to the user or click the X icon to remove organization access.

    A green check mark appears beside the organization name once user access is assigned. A red X appears beside the organization name to indicate no user access.

    Tip: Using the steps above, you can add or remove organization access to multiple organizations at one time for one user. Alternatively, use the Swap button (to the right of the Create Organization button) to update multiple users for one organization at the same time.

To create a data ingestion organization

As Oracle Adaptive Intelligent Apps for Manufacturing displays analysis data by organization, the data collected from various data sources using different ingestion methods belongs to a unique organization code. You must define and be assigned to a Case Record Data Ingestion organization to upload case record data files and a Business Entity Data organization to upload the business entity data files.

To create a Case Record or Business Entity data ingestion organization, see Setting Up Data Ingestion, Oracle Adaptive Intelligent Apps for Manufacturing Data Ingestion User's Guide.

Related Topics

Removing User Accounts

Assigning Groups to Oracle Applications

Removing Groups from Oracle Applications

Setting Up Your IDCS User Profile

Your IDCS domain has user profile settings that you can choose to personalize, such as a preferred language and your login password. AIAMFG supports the following languages, in addition to the default language, English (United States):

IDCS by default shows all languages, but AIAMFG supports only a subset of these languages. AIAMFG selects a language for translation of the user interface in the following order, until it finds a supported language. AIAMFG selects:

  1. The language in the My Profile Details tab of the My Profile console in IDCS, unless this language is not supported. See: Set Up or Modify Your Profile or To set up your IDCS user profile.

  2. The supported base language of a selected variant language, unless this base language is not supported. For example, if you select Dutch (Netherlands), the variant language, AIAMFG reverts to Dutch, the supported base language.

  3. The IDCS domain default language, unless this language is not supported. See: Change Default Settings.

    Tip: Use this option to set the language for a larger group of users instead of setting the preferred language for each user.

  4. English (United States), the default language.

Data Ingestion Methods and Supported Languages

Users can ingest data into AIAMFG using either CSV files for any data or using Oracle Data Pump and Oracle GoldenGate, which is only used by E-Business Suite (EBS) customers who implement AIAMFG. Users who only ingest data using CSV files can view the AIAMFG user interface (UI) and messages in a supported language, but the languages available can change for users who ingest data using a combination of CSV files and Oracle GoldenGate or only Oracle GoldenGate. Oracle GoldenGate supports any language, which may or may not be supported by AIAMFG. This intersection of supported languages determines the languages to which the UI and messages can be translated.

Important: At this time, AIAMFG only translates the UI and messages, not data. You can ingest data in any language. For example, if you ingest data in Korean, the data remains stored as Korean text for all users, regardless of a user's selected language.

There are four data ingestion scenarios:

  1. Only ingest data using CSV files; never enable Oracle GoldenGate. AIAMFG renders in any of the supported languages.

  2. Initially ingest data using CSV files, but enable Oracle GoldenGate later. Initially, AIAMFG renders in any of the supported languages. Later, if Oracle GoldenGate ingests data, it collects data from the EBS source in any language. For example, if Oracle GoldenGate ingests data in Dutch, French, German, and Polish, the AIAMFG UI and messages only render in Dutch, French, and German, which are the common languages at the intersection between the Oracle GoldenGate data from EBS and the AIMFG supported languages. If Oracle GoldenGate ingests Spanish data later, then AIAMFG renders in Spanish, in addition to Dutch, French, and German.

  3. Only ingest data using Oracle GoldenGate. Oracle GoldenGate can ingest data in any language. If any ingested languages intersect with the AIAMFG-supported languages, AIAMFG renders in those intersection languages. For example, if Oracle GoldenGate ingests data in Dutch, French, German, and Polish, AIAMFG renders in Dutch, French, and German.

  4. Initially ingest data using Oracle GoldenGate, but ingest data using CSV files later. Initially, if any ingested languages intersect with the AIAMFG-supported languages, AIAMFG renders in those intersection languages. For example, if Oracle GoldenGate ingests data in Dutch, French, German, and Polish, AIAMFG renders in Dutch, French, and German. Later, when French, German, and Spanish data is ingested using CSV files, AIAMFG only renders in French and German. If Oracle GoldenGate ingests data in Spanish later, then AIAMFG can render in Spanish, French, and German from that point on.

Action: Run the background process "Maintain Multi-lingual Tables" if you enable a supported language after transaction data already exists in other languages. The program adds the newly enabled language. When a user logs in with the new language, they will be able to view the updated data. See: Running Background Processes.

The graphic below illustrates how AIAMFG can only render in the languages at the intersection of the Oracle GoldenGate-ingested languages and the AIAMFG-supported languages. This restriction only applies when ingesting EBS data using Oracle GoldenGate.

Supported Languages Depend Upon the Data Ingestion Method Used

the picture is described in the document text

To set up or change your preferred language

You can navigate from AIAMFG to IDCS by selecting Profile from the User Name drop-down list. From the IDCS My Profile console, you can configure many of your user settings and change your password, in addition to selecting your preferred language. For information about configuring each of the user settings available from the My Profile console, see: Configure User Settings.

  1. Navigate to the My Profile console.

    From the User Name drop-down list, select Profile.

  2. In the Preferred Language field, select one of the languages supported by AIAMFG.

  3. Click Save.

  4. Sign out of AIAMFG, then sign in.

    The Home page now displays in your preferred language.

    Note: If you selected a language not supported by AIAMFG, the application renders in the default language of English (United States).

Defining User Preferences

The information in the Insights, Genealogy and Trace, Predictions, and Factory Command Center modules is shown in the context of the specific plant and department selected in the User Preferences page. You can set user preferences to specify how information is displayed in the module pages available for analyzing insights, genealogy and trace, predictions, and factory current status.

  1. Navigate to the User Preferences page.

    Click the user name, and then click Preferences.

  2. In the General region, specify values in the following fields. The Insights, Genealogy and Trace, Predictions, and Factory Command Center modules automatically display data only associated with the selected values.

    • Organization Code – Mandatory. Select a preferred organization from the list of organizations assigned to you in the Organization Access page.

    • Category Set – Mandatory.

    • Department Code – Optional, for discrete manufacturing organizations only.

  3. In the Factory Command Center: Material region, optionally specify a numerical value in the following fields:

    • Expiration Time Fence (days) – number of days prior to the expiration date that users are notified through the Item Expiring KPI.

    • Receipt Delay Tolerance (hours) – number of hours beyond the receipt due date before a receipt delay is reported.

    • WIP Return Time Fence (hours) – number of past hours to consider and display component return transactions for open work orders.

  4. In the Factory Command Center: Machine region, optionally select a value in the Alarms last N hours field to show the alarms during the last N hours. You can choose to view alarms up to a maximum of 24 hours.

  5. In the Factory Command Center: Management region, optionally select a numerical value in the following fields:

    • Pending Work Order Time Fence (days) – the interval during which a soon to be started work order displays.

    • Delay Tolerance (hours) – the number of hours beyond which a work order or operation displays a delay in starting or completing.

    • Completed Work Order Time Fence (days) – the interval during which recently completed work orders display.

  6. In the Logging region:

    • click the Enable Log button to enable logging.

    • select from the following in the Log Level field:

      • Error

      • Warning

      • Info

      • Statement.

  7. In the Background Process Tracing region:

    • click the Enable Trace button to enable background process tracing.

    • select from the following in the Trace Level field:

      • Regular Trace

      • Trace with Binds

      • Trace with Waits

      • Trace with Binds and Waits

    • select the background process to trace in the Program Name field.

  8. Click Save to save your preferences.