Skill availability maximum duration

Hi ​@Heraghty123 

It seems skill unavailabilities are not directly supported in the PSO ARP in the same way they are in the standard PSO scheduling schema. In the standard scheduling schema, you can define a skill unavailability by creating an Availability record with the “available” flag set to “false”, then linking it to the resource's skill via the Resource_Skill_Availability entity. This explicitly "punches a hole" in a resource's skill for a specific period.

A example would be something like this, 

<Resource_Skill_Availability>
  <id>Link_01</id>
  <resource_id>RES_101</resource_id>
  <skill_id>ADVANCED_REPAIR</skill_id>
  <availability_id>Unavail_Skill_Period_01</availability_id>
</Resource_Skill_Availability>
<Availability>
  <id>Unavail_Skill_Period_01</id>
  <datetime_start>2026-05-01T08:00:00Z</datetime_start>
  <datetime_end>2026-05-01T17:00:00Z</datetime_end>
  <available>false</available>
</Availability>

However, it seems the PSO ARP is designed solely to capture the periods when a resource possesses a skill. By default, a resource is assumed to hold a skill at all times unless specific possession windows are defined. To create an unavailability in PSO ARP workspace, the workaround is to define multiple skill availability records that cover the periods surrounding the excluded window, leaving the "unavailable" period as a gap. For example, if you want to exclude May, you would define one record up to the end of April and another starting from June onwards.

This is admittedly less intuitive than a direct unavailability flag. It may be worth raising as a product enhancement request, as the underlying DSE scheduling schema already supports this concept natively and I believe it just isn't currently exposed through the ARP modelling interface.

Also you should be able to define the duration for more than 99 days, What’s the PSO version you are using?