Working with SWB Schedule Versions

Consultants can prepare an SWB Schedule Version for customers and store the Schedule Version in S3 bucket.

For companies with multiple warehouse groups that use different configurations, consultants may create a separate Schedule Version for each warehouse group. Each Schedule Version file should be clearly named to identify the warehouse group it belongs to.

Alternatively, a single Schedule Version can be created and used across all warehouse groups. In this case, additional environment variables (System > Parameters > Environment Variables) can be configured to control data imports. Display filters (Navigator > Settings) can then be used to determine which folders and reports are visible in the workflow for each warehouse group.

Consultants can alternatively prepare a SWB Schedule Version for customers on their own SWB and export the Schedule Version as a zipped data file. The zipped data file is then sent to the SWB user which imports the zipped data file.

On Appstream, select My Files > Temporary Files.
On Temporary Files, drag and drop the Schedule Version zip file.
On Scheduling Workbench, click System > Schedule Versions.
Click Import.
On Source, select Temp folder.
Select the zip file and click Open.

Note: Your current SWB data will be overwritten. To retain the existing SWB data, export the current Schedule Version before importing a Schedule Version.

Exporting an SWB Schedule Version to an S3 bucket

You can save and share an SWB Schedule Version through S3 an bucket.

Select System > Schedule Versions.
Select Export.
Select Shared data folder.
A Schedule Version is always saved with this information:
- File name: Unique ID of the Schedule Version
- Exported by: User ID
- User full name
- Warehouse group
- Export date
To always save the latest plan for a warehouse group, use only the warehouse group name as the file name. When accepting the plan in SWB and exporting it to BE, use the automatic function Export version to the shared data folder. With this setup, each time you accept a plan in SWB, the Schedule Version in the shared data folder is automatically updated.
With this function, in cases where there is a temporary planner replacement, the substitute planner can easily locate and import the latest Schedule Version for the warehouse group. SWB view users can select automatic import Schedule Version, to ensure that the most recent Schedule Version is automatically imported.
Use a unique file name when you want to keep historical versions, for example:
- To save a version every month for analysis of older plans
- To keep a backup version that includes the SWB configuration
If the Current date is included in the file name, a new file is generated each time the Schedule Version is exported to the S3 bucket. In this case, we recommended that you actively manage Schedule Versions to prevent an excessive accumulation of saved files. You must delete the Schedule Versions that are no longer required.

Importing SWB Schedule Versions from S3 bucket

Select System > Schedule Versions.
Select Import.
Select Shared data folder.
Select which Schedule Version to import.
It is possible to filter and sort Schedule Versions that are displayed in list. For example, you can only show certain warehouse groups.
Note: Your current SWB data will be overwritten. To retain the existing SWB data, export the current Schedule Version before importing a new Schedule Version.

Managing Schedule Versions in S3 bucket

Set a default Schedule Version in Manage Schedule Version. When a new user launches SWB for the first time, the default Schedule Version is automatically imported.

Select System > Schedule Versions.
Select Manage.
Select the Schedule Version and select Toggle set default.
Delete obsolete Schedule Versions to avoid excessive accumulation.

View user setting up which Schedule Version to view

Select System > Schedule Versions.
Select Manage.
Select the Schedule Version and select Toggle set automatic import.

The automatic import Schedule Version is indicated next to the selected version.

The next time the View User starts SWB, the system will automatically import the selected Schedule Version from the S3 bucket, provided that the version in the S3 bucket has been updated based on the export date.

Importing a standard SWB Schedule Version

M3 Scheduling Workbench starts with a standard Schedule Version for Food. This also includes Fashion, Manufacturing, Equipment, and Theory of Constraints (TOC).

Select System > Schedule Versions.
Select Import.
Select Base data folder.
Select the zipped Schedule Version for the relevant industry.
Select Open.
Zipped Schedule Version files without “GT” in the file name are prepared for importing live customer data.
Zipped Schedule Version files with “GT” in the file name contain demo data for the M3 Scheduling Workbench Guided Tour. These versions are not intended for importing live customer data.
Note: Your current SWB data will be overwritten. To retain the existing SWB data, export the current Schedule Version before importing a new Schedule Version.

Consultant creates and prepares SWB Schedule Version for user or role

Consultants can prepare a PWB Schedule Version for customers and store the Schedule Version in S3 bucket.

For companies with multiple warehouse groups that use different configurations, consultants may create a separate Schedule Versions for each warehouse group. Each Schedule Version file should be clearly named to identify the warehouse group it belongs to.

Alternatively, a single Schedule Version can be created and used across all warehouse groups. In this case, additional environment variables (System > Parameters > Environment Variables) can be configured to control data imports. Display filters (Navigator > Settings) can then be used to determine which folders and reports are visible in the workflow for each warehouse group.

Consultants can alternatively prepare a PWB Schedule Version for customers on their own PWB and export the Schedule Version as a zipped data file. The zipped data file is then sent to the PWB user which imports the zipped data file.

On Appstream, select My Files > Temporary Files.
On Temporary Files, drag and drop the Schedule Version zip file.
On Planning Workbench, select System > Schedule Versions.
Click Import.
On Source, select Temp folder.
Select the zip file and click Open.

Note: Your current SWB data will be overwritten. To retain the existing SWB data, export the current Schedule Version before importing a new Schedule Version.

Creating a local backup of SWB Schedule Version

Select System > Schedule Versions.
Click Export.
Select Temp folder.
Select the file name.
These are the relevant information that you choose from:
- Warehouse group
- M3BE user
- Current date
Keep directory as Temp folder.
Click Save.

Note: You must download the zipped Schedule Version file from AppStream to a computer or server, as the Temporary Files folder in AppStream are not permanent.

Ensure that the zipped Schedule Version file is saved to a secure location on a computer or server for future use.

On Appstream, select My Files > Temporary Files.
Download the Schedule Version zip file to your computer or server.

Note: When reporting an incident in ServiceNow, it is often helpful attach the zipped local Schedule Version file. This enables the support team to analyze the SWB data, especially when the issue description, screenshots, and zipped data are based on the same dataset.