Prerequisites#

Complete this preparation before starting the learning path in Workspace. Prepare the permissions for the scenario you will perform. Each scenario lists the required operational context and starting conditions.

Environment and Example Data#

• Use a Critical Manufacturing MES training environment.
• Use a working model that includes a Calendar, Factory, Area, Resource, Service, Step, Flow, ServiceContext, Product, and a Material to process. Ensure these elements are configured to support the operations in the selected scenario.
• Ensure the required object types and units are available.
• Use unique names for new objects. If an exercise name already exists, choose a different name and use it consistently.

This tutorial uses a Cookie Factory model as an example. You can use any working model with the required elements. Configuring the model itself is outside the scope of this tutorial.

Follow the Before You Start section in each scenario and use the same model consistently throughout the learning path.

Administrator Access#

Use an administrator or page designer account for configuration, then sign in as the runtime User for the scenario to verify the result.

The configuration account needs permission to:

• Create and edit Workgroups.
• Create, design, and save UI Pages, and complete their Change Set approval and effectiveness process.
• Configure Role features.
• Associate Workspaces with Roles, and assign Roles and Workgroups to users.
• Create and configure Queries, Checklists and Data Collections.

The configuration account also needs permission to prepare the scenario-specific data:

• Quality Workspace: create and configure Steps, Flows, Materials, Reasons, Step Reasons, Services, and ServiceContext records.
• Maintenance Workspace: create and configure Parameters, Data Collections, Checklists, Maintenance Plans, a User, and an associated Employee; associate a plan with a Resource, and request and release Maintenance Activity Orders.

Users and Data Access#

• Ensure each runtime User is Active, enabled, and able to sign in. Assign the MES OAuth Scope Role.
• Assign the Role for the scenario and the Security Features listed below before switching to that User.
• Grant the applicable Data Groups for the UI Pages and operational records used by the exercise, including write access where the User records data or performs operations.

Operator Workspace#

Prepare an Operator Role and an Active User, such as Baking Operator 01. Assign the following Security Features to the Role:

• Manufacturing.fabExplorer
• Material.Dispatch
• Material.DispatchAndTrackIn
• Material.Show
• Material.TrackIn
• Material.TrackOut
• Resource.ChangeState
• Resource.Show
• UIPage.Show

Quality Workspace#

Prepare a Quality Engineer Role and an Active User. Assign the following Security Features to the Role:

• Manufacturing.fabExplorer
• Material.DispatchAndTrackIn
• Material.Hold
• Material.Release
• Material.Show
• Resource.Show
• UIPage.Show

The User must also belong to the Role that will be assigned to the Hold Reason in the Quality Workspace scenario.

Maintenance Workspace#

The Maintenance Workspace scenario uses one User to access all a Workspace and complete a Maintenance Activity Order. Its Query lists Released and In Progress Maintenance Activity Orders assigned to Maintenance Technician.

Before starting the scenario, complete the following preparation:

1. Prepare the Maintenance Technician Role.

2. Assign every Security Feature in each of the following feature groups to this Role:

   • Checklist Management
   • Data Collection Management
   • Maintenance Management
   • Manufacturing
   • Material Management
   • Resource Management

3. Also assign UIPage.Show from the UI Page feature group.

4. Keep the Feature assignments listed above for the Operator and Quality Engineer Roles.

During the scenario, follow the instructions to complete the remaining setup before performing maintenance:

• Set Maintenance Technician as the Owner Role when associating a Maintenance Plan with a Resource. To accept a maintenance order, the User must belong to the Owner Role of the resulting Maintenance Plan Instance.
• Create a User named Operations Coordinator, with Maintenance Technician as its Primary Role, and assign the MES OAuth Scope, Operator, and Quality Engineer Roles. Configure its access to all three Workspaces.
• Create an Employee associated with this User. This association is required to begin a Maintenance Activity Order.

Begin your learning path by accessing Workspaces and Workgroups Scenarios.