M3 Cloud

Prerequisites

• You must have the IFS role M3SWB_PLANNER, M3SWB_VIEWER, or Infor-SystemAdmin.
• You must setup ION API for M3 Scheduling Workbench. See Setting up ION API.
• You must setup M3 BE for M3 Scheduling Workbench. See Setting up M3 BE.

Starting M3 Scheduling Workbench

See Setting up AppStream for more information.

Schedule Versions

See Schedule Versions in AppStream for more information.

Modifying Panel Files

To modify the panel files, select System > System Information > Panel Files.

The list of all panel files are displayed.

You can do these actions on each panel files:

• View original
  • You must have a Planner or Viewer role.
  • Open the original or unchanged panel file using an editor in which you cannot change the panel file.
    Note: If there is no custom file, all users will use this file.
• Edit custom
  • You must have a Planner role.
  • Copy the original file to the custom directory and edit the file using an editor.
    Note: All users will use this file.
• Delete custom
  • You must have a Planner role.
  • Delete the custom file located in the custom directory
• Toggle activate
  • You must have a Planner role.
  • Activate or deactivate the use of the custom file.
• Import custom files
  • You must have a Planner role.
  • Import backup of custom files from the Temp directory.
• Export custom files
  • You must have a Planner role.
  • Export backup of custom files to the Temp directory.

Modifying Control Files

To modify the control files, select System > System Information > Control Files.

The list of all control files are displayed.

You can do these actions on each control files:

• View original
  • You must have a Planner or Viewer role.
  • Open the original or unchanged panel file using an editor in which you cannot change the panel file.
    Note: If there is no custom file, all users will use this file.
• Edit custom
  • You must have a Planner role.
  • Copy the original file to the custom directory and edit the file using an editor.
    Note: All users will use this file.
• Delete custom
  • You must have a Planner role.
  • Delete the custom file located in the custom directory
• Toggle activate
  • You must have a Planner role.
  • Activate or deactivate the use of the custom file.
• Import custom files
  • You must have a Planner role.
  • Import backup of custom files from the Temp directory.
• Export custom files
  • You must have a Planner role.
  • Export backup of custom files to the Temp directory.

Backing up or restoring Custom Files and Data Zip Files when changing environment

When changing from test to production environment, it is useful to backup custom files and some shared data from the test environment and restore these in production environment.

Backing up in the test environment

1. Select System > Schedule Versions, then export one or more schedule versions to the Temp directory.
2. Select System > System Information > Panel Files, then export all custom panel files in the given language to the Temp directory.
3. Select System > System Information > Control Files, then export all custom control files to the Temp directory.
4. Copy the files from the temp folder to the server or computer where you can save the files.

Restoring in the production environment

1. Select System > Schedule Versions, then import one or more schedule versions from the Temp directory.
2. Select System > System Information > Panel Files, then import all custom panel files in the given language from the Temp directory.
3. Select System > System Information > Control Files, then import all custom control files from the Temp directory.

Closing the application

Click System > Exit then close M3 Cloud to exit M3 Scheduling Workbench.

Data volume

M3 Cloud has a 900 MB limit on data volume.

You can identify the free data capacity and used data capacity in System > System Information > Status.

If the data capacity usage exceeds 80%, a warning is displayed in Messages.

In case a zipped schedule version is imported that exceeds the data limit, then M3 Scheduling Workbench displays an error message that there is not enough disk space.

The M3 Scheduling Workbench data volume is primarily in these four data types:

1. Orders (Headers, Operations, and Materials)
2. Item register
3. External supplies (Purchase orders)
4. External demands (Customer orders and forecast)

These are some examples of the base data volume planned on normal resources.

• 4000 orders with 99 operations are equal to 400.000 headers and operations, which uses about 800 MB.
• 100.000 item or warehouse in item register uses about 140 MB.
• 100.000 External Supplies (Purchase order lines) uses about 50 MB.
• 100.000 External Requirements (Customer order lines) uses about 50 MB.

Migrating to M3 Scheduling Workbench Cloud