Skip to content

Service Scheduling Integration

Service scheduling integration is based on the Scheduling optimization configuration, read more about Scheduling Optimization Configuration. When the necessary IFS components and Planning and Scheduling Optimization (PSO) components are installed, this guide describes how to configure the two system to work together.

Contents

  • Step 1: Configure default parameters
  • Step 2: Define the configuration in scheduling optimization configuration page using Add New Configuration Assistant
  • Step 3: Go to scheduling dataset page and create your dataset with the configuration id you create in Scheduling Optimization Configuration page
  • Step 4: Activate the dataset and send full load
  • Step 5: Deactivate the dataset
  • Synchronous Appointment Booking Process

Step 1: Configure default parameters

Configure Default Parameters for the PSO Integration

Please refer to the section BDR for PSO in IFS Cloud Online Documentation. The activity to be used is Define Scheduling Configuration.

Note: Please note that you have to set up the basic data requirements for this activity.

Step 2: Define the configuration in scheduling optimization configuration page using Add New Configuration Assistant. Please follow the guideline IFS Optimization Framework Configuration Assistant.

Please follow this guideline Scheduling Optimization Configuration.

Step 3: Go to scheduling dataset page and create your dataset with the configuration id you create in Scheduling Optimization Configuration page.

Please refer to the section BDR for PSO in IFS Cloud Online Documentation. The activity to be used is Define Dataset.

With Dataset segmentation changes in 24R1, Maintenance Organization Site to Dataset connection is now made on "Maintenance Organization Site - Dataset Connection". To make sure the scheduling data of a particular site is planned through only one Dataset this only allows connecting a Maintenance Organization Site only to one Scheduling Dataset. In an earlier release, this was verified by allowing only to have one active Dataset for a specific Site. Therefore, in order to fulfill this, the customers who upgrade from previous releases to 24R1 need to make sure a particular site is connected to only one Scheduling Dataset as a prerequisite for running the script POST_Svcsch_UpgradeDatasetConnections, as having multiple site record data will disregard that record upgrade. Failure to do so, will not inherit the Dataset to the Work Task level as well as the Maintenance Resource Shift Level when running the post-upgrade scripts POST_Wo_Upgrade_Jt_Task_Dataset.sql and POST_Genres_ResourceDatasetUpgrade.sql respectively resulting to enter Dataset ID manually on all Tasks and Resource Shifts in order to make them available for scheduling.

Step 4: Activate the dataset and send full load.

Step 5: Deactivate the dataset.

It is possible to deactivate the datasets using the scheduled task "Deactivate Scheduling". This needs to be set up and enabled manually. This task would be responsible for deactivating datasets that are no longer in use, helping to prevent unnecessary buildup. Please ensure that execution frequency aligns with the scheduled task "Disable Active Datasets" if they exist.

Parameters:

  1. Dataset ID - The Dataset ID's to disable. Accepts wildcards. The default value is '%' (all datasets).

  2. Deactivate Dataset - Enter 'TRUE' to deactivate the datasets. The default value is 'TRUE'.

Synchronous Appointment Booking Process

In the 24R2 release, the appointment booking request and slot acceptance process have been updated to operate synchronously. As a result, the 'ABE' broadcast from the Load XML has been removed.

Due to this change, output messages from PSO related to appointment bookings will no longer appear in the 'Scheduling Optimization Output Data' window. Instead, both input and output messages will be available in the Application Messages window.

The XML data can be found as follows:

  • Input Message Data (MESSAGE_REQUESTS.xml): Contains the XML from IFS to PSO.
  • Output Message Data (MESSAGE_RESPONSE.xml): Contains the XML from PSO to IFS.