Good day We have received the PSO 6.13.0.15 software for installation, but no release notes. I have tried looking on the Community, but the latest PSO release notes I can find is for PSO 6.13.0.9. Where can I find the PSO 6.13.0.15 release notes? Regards
Good day I am having an issue with my Passive Preventative Maintenance task time commitments. When tasks are created from a contract they have two time commitments: one for now, and a second for a future time commitment. The task should be scheduled for the future time commitment, not for the “Now” time commitment. When removing the “Now” commitment, it also removes the tasks from PSO (which show all tasks, but as unallocated). Is there a way to remove the time commitment that is scheduled for the “Now” time, and only keep the time commitment for future time, when generating tasks from a contract?
Good day Is there a way to make the PSO Dataset drop-down display alphabetically on the All Workspaces > Resources screen (the Gantt)? This is from the Admin User that can view all datasets. Below a screenshot of our current dataset drop-down:
Good day We have a situation where leave (Unavailability) was captured for a Resource on PSO under Resource Planner. The time period for the leave was 19 July 2023 12AM to 24 July 2023 7AM. The issue is that PSO assigned a task to this Resource on leave at 19:26 PM on 23 July 2023. As far as I understood, this is supposed to be impossible. Please advise of any solutions and/or causes to this issue, and where I might investigate, as there seems to be no problem with how the commit rules were set up.
Good day According to the documentation, the On/Off Shift parameters should influence PSO’s behavior, and along with changed to the Commit Rules in PSO, it should be possible to Un-commit a task if it has net been Accepted at the end of a shift.Currently, it seems that the On/Off Shift parameter on the Person records does not do anything, and does not push to PSO at all. How do I go about setting this up? Is there a setting or a business rule that needs to be updated?Regards,Hannes
Good day We started using PSO to schedule tasks yesterday. Everything was working correctly with tasks committing according to the commit rules, and newer tasks coming in and sitting the queue with “Allocated” status. A day later, and a lot of tasks that were allocated became unallocated, even though their SLA is still active, with plenty of room on the schedule to commit these tasks. The Current Allocation Value also changed to zero, where it should not be zero, but have an allocation value in accordance with the SLA. Please see the screenshot below:Previously Allocated task now Unallocated while SLA is still activeAny help with this issue would be appreciated, or any ideas for where to start investigating.
Hi Community When recreating commit rules in PSO after an upgrade was performed to version 6.9.0.12, I am seeing some new parameters added to the Commit Rule. Where can I find more info on how these parameters work and what impact they will have on task commitments?Parameters in question:Shifts in future Rule Window Start Rule Window End Day Pattern Time zone Regards,Hannes
Good day When adding a resource from FSM Smart Client to PSO, all information gets pushed correctly. When a resource needs to change locations (e.g. between different regions due to moving etc.) the new assigned locations do not update in PSO, even when changed in FSM and the dataset initialized. Skill updates immediately when changed in FSM and reflects in PSO. Is there a way to have the location data update dynamically where necessary, the same as the skills? Regards,Hannes
Good day Creation and management of rosters will move from FSM to PSO in my situation. Creating exclusions on a resource on the roster in PSO reflects on the PSO schedule board. As the FSM schedule board will still be used to manage some tasks, is there a way to have the exclusions created in PSO display on FSM schedule board? Regards,Hannes
Good day PSO was set up with a few different datasets. All necessary sections were setup under theses datasets (rules, resources, rotas, scheduling templates etc.). Suddenly, all scheduling datasets have changed to “Expired” status for no reason that I can see. Normally I would be able to change an Expired dataset back to active, but in this case cannot change anything. Any idea how to address this issue, before the expired datasets get removed by PSO for being inactive?
Good dayPlease see the above pictures for the resource duplication. During team setup, the team member’s Resource ID was changed. The user was not deleted in either FSM or PSO when the Resource ID was changed. Now the user shows up in PSO with both the old and the new Resource ID. Tasks does not get scheduled to the old Resource ID, but they both show in the Resource planner and the PSO Schedule board. Is there a way to prevent this duplication, or will it be a manual process of removing the old resource from the Team in FSM, as well as removing the old resource from PSO and the resource planner?
Good dayI am having the following issue.I have teams setup in FSM with team members and scheduling resources, all connected to certain datasets. I have created corresponding datasets in PSO, and after setup is complete everything works as it should (team members/resources added in FSM displays immediately in PSO, tasks get scheduled correctly according to commit rules etc.).The problem I have is that after tasks are scheduled, making changes to the rota or resource planner, it will move all tasks around. For instance, if the scheduling period for the rota is 1May to 1June, and any changes are made, PSO will move my committed tasks to the end of the rota period. Committed tasks will now be scheduled and committed for 1June, and allocated tasks will stay on the current day, but can’t become committed when tasks are completed, as committed tasks are now on the wrong day.What can I do to fix this?Regards,Hannes
Good dayI am having the following issue.I have teams setup in FSM with team members and scheduling resources, all connected to certain datasets. I have created corresponding datasets in PSO, and after setup is complete everything works as it should (team members/resources added in FSM displays immediately in PSO, tasks get scheduled correctly according to commit rules etc.).My problem is, everything works perfectly for a while, before the connection between datasets in PSO and FSM fails. Updating any data in FSM does not pull through to PSO.I have tested this by creating new testing datasets, scheduling app params (exports) etc. and connecting all necessary data to them, but they still fail after a while. Deleting everything and recreating all data will have it working again, until it fails again.What could be causing this failure? Could it be due to a system upgrade? If it is caused by upgrades, is there a way to preserve the connections so I don’t have to recreate everything to make
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
