There is a parameter that allows you to travel before and after the shift. If the work starts at 8:00 and travel should not start before 8:15 you could either let the shift start at 8:15 or create a 15’ loading activity fixed at 8:00. For that consider a regular CALL activity or a break. Similar at the end of the shift.

Thank you ​@Alexander Heinze,

Which parameter is it for the travel after the shift. I think we have this place as the travel does go beyond the shift time by up to 30 mins.

Is there a way of creating a regular CALL activity in PSO so it’s at the start of each shift? This would then be visible on the PSO Workbench, but from a FSM perspective it would simply show travel starts ‘x’ time into each shift.

I don’t want to go down the route of calendar exceptions either from FSM feeding into PSO. 

I think its travel_to and travel_from on the shift entity, but do check the Schema guide please. Breaks can be put into the shift templates, but activities need to come from the upstream system. I don't know FSM, so I cannot tell what's possible there.