Reporting on Sensei_Tasks and Sensei_Assignments in Altus Reports

When a user sets the 'Effort' on a Sensei_task (This is a task using the standard Altus scheduling tool inside Altus), the value entered for effort will be split evenly in the reports between all resources assigned to the task.

As an example, a Project Manager sets the effort on a Sensei_task in their task list at 100 hours and the Project Manager then assigns 4 users to the task. Each resource would be “allocated” 25 hours of the effort for this task in the reports. Assignment units have no bearing on this division of effort. As the task is progressed, it is assumed that it is progressed evenly across all assignments. So if the same task mentioned above is progressed to 50%, then each resource "assignment" in the Altus reports will have 12.5 hours of effort completed, and 12.5 hours of effort remaining.

Synthesizing Time-phased assignment data from Altus Schedule Assignments

In providing core scheduling capability, Altus schedule does not store the assignment or task-level values in a time phased way. This means that we do not have access to the per-day values for work that we might find in Project Online or other Project management tools.

In order to synthesize this data from the assignment data that we do have access to in Dataverse, a method was utilized in which a row is created for each day for an assignment using the start date and finish date. These rows are then filtered by the rows in the resource capacity table, ensuring that rows for days on which the resource is not working are not included. Finally, the number of rows (working days) for each assignment is calculated by counting the remaining rows for each assignment, and then the total effort for the assignment is divided by this number giving us the daily effort for each assignment. An example of this process is depicted in the animation below.

Please note, this method assumes that the effort is spread evenly over all working days for the assignment and results in a flat (un-contoured) assignment, as the true daily values are unavailable for reporting.

Also of note is that because generic resources do not have associated capacity, there will not be an opportunity to synthesize the time-phased resource assignments for this resource type.

External Execution Tool Assignment Effort

There is a limitation when using External Execution tool Task Sync where if tasks in an external execution tool that are assigned to multiple resources have varying values for work (effort) assigned to each resource, these specific values are not synced into Altus. For example, if a task from Project Online (external execution tool) has three resources assigned to it, with a total work value of 100 hours, is split unevenly in the following manner: 50 hours for resource 1, 25 hours for resource 2 and 25 hours for resource 3, these assignments are imported into Altus with an EVEN split on the task, and the reporting for the Altus "assignments" will indicate 33.33 hours for each resource. This is due to the nature of the Altus Schedule control, and the fact that the work/effort data is not stored at an assignment level or in a timephased manner.