Scheduling Data

Scheduling data includes data fetches for tables for scheduling entities such as activities, resources, shifts, skills etc. Full details of the scheduling schema can be found in the Scheduling Schema Guide in the IFS Planning & Scheduling Optimization (PSO) documentation.

Tables & Rules mapped

Broadcast

The Broadcast attributes are either hardcoded, set in the Dataset Parameters or set in the mapping package as follows:

• Broadcast_id - Hardcoded
• active - Ignored
• broadcast_type_id - Hardcoded (we only support WEBSERVICE at present)
• cron_string - Ignored
• description - Hardcoded
• plan_type - Taken from the mapping package
• minimum_plan_quality - Dataset Parameter
• minimum_step_interval - Ignored
• only_once - Ignored
• maximum_wait - Dataset Parameter
• input_reference_id - Ignored
• maximum_frequency - Taken from the mapping package
• allocation_type - Taken from the mapping package
• expiry_datetime - Ignored
• time_filter_start - Taken from the mapping package
• time_filter_end - Taken from the mapping package
• minimum_visit_status - Taken from the mapping package
• include_abe_broadcast - Taken from the mapping package *
• include_dsp_broadcast - Taken from the mapping package *

* If these are set to true then the load input will include the additional broadcast request. This will always be for a 'CHANGE' plan and filtered to the correct allocation type (2 for ABE, 8 for DSP). In addition, if you don't explicitly set this parameter but the dataset process type is set to 'Appointment' then the ABE broadcast will automatically be added.

Broadcast Parameters

The Broadcast Parameters are taken from PSO Integration Configuration Broadcast Settings or hardcoded as follows:

• wsid - Hardcoded
• url - Taken from PSO Integration Configuration
• username - Taken from PSO Integration Configuration
• password - Taken from PSO Integration Configuration
• required_tables - Taken from the mapping package