Tasks are the basic unit of work in Aphex. Tasks hold all the information about the unit of work.
Task Properties
Tasks properties are the details and data that can be assigned to Tasks.
Property | Description |
Name | Name given to the Task |
Start | Start date |
End | End date |
Duration | Duration in working days |
Calendar | Working and non-working days |
Shift | Shift pattern indicating a Task's working hours |
Owner | User responsible for the Task |
Assigned To | Users who can status and comment on the Task |
Subcontractor | Subcontractor responsible for delivering the Task |
Labour | Human resources required to deliver the Task |
Plant | Equipment and machinery required to deliver the Task |
Materials | Material resources required to deliver the Task |
Location | Visual map of an on-site location of the Task, or description of the off-site location |
Work Area | Physical location of a Task on-site, marked-up on a location image |
WBS Code | Structure used to group and structure Tasks in the plan |
External ID | A unique identifier used to connect a task to an external plan, this commonly represents an Activity ID in a master schedule |
Package | Custom way of grouping related Tasks in the plan |
Parent | Parent Task of a Subtask |
Notes | Additional notes that can be attached to Tasks |
Comments | Thread of communication on the Task |
Documents | Documents that can be uploaded and attached to Tasks |
Related Documents | Documents that have been uploaded and attached to the Parent Task or Package |
Related Tasks | Connected Tasks. Relationships can exist between Tasks in the form of Logic Links |
Activity ID | Unique identifier automatically assigned to every Task in the plan |
Key Task | Milestone Tasks can be configured to visually highlight them in the plan, also activating the Critical Path Overlay |
Status | Detailed performance records against Tasks that have become committed or "locked-down" |
Task Permissions
Each Task has a single Owner who is responsible for detailing, updating and making the Task ready.
Tasks can also be interacted with by other team members depending on their Project Role and whether they have been Assigned To the Task.
| Owner/ Project Admin | Assigned To | No Task Role |
Delete Task | ✔️ | - | - |
Breakdown Task | ✔️ | - | - |
Update Task Links | ✔️ | - | - |
Update Task Dates, Duration, Calendar and Shift | ✔️ | Only if Contributor | - |
Update Task Subcontractor, Labour, Plant and Materials | ✔️ | Only if Contributor | - |
Update Task Location and Work Area | ✔️ | Only if Contributor | - |
Update Task Parent, Package, WBS, External ID | ✔️ | Only if Contributor | - |
Request Non-Conflicting Clash Resolution | ✔️ | - | - |
Mark as Key Task | ✔️ | - | - |
Update Task Owner | ✔️ | - | - |
Update Task Assignees | ✔️ | ✔️ | - |
Add Task Comment | ✔️ | ✔️ | ✔️ |
Update Task Notes | ✔️ | ✔️ | - |
Update Task Documents | ✔️ | ✔️ | - |
Status Task | ✔️ | ✔️ | - |
Update Resource Actuals | ✔️ | ✔️ | - |
Task Types
Tasks can be broken-down into a collection of Subtasks within a Parent Task.
Parent Tasks
After a Task is broken down into a Parent Task, it becomes a summary of all its Subtasks.
Some properties are controlled by the Parent Task that all Subtasks will inherit:
Parent Task Properties |
|
Subtasks
Aside from the inherited properties, Subtasks can have their own individual properties:
Subtask Properties |
|
Activity Log
The Activity Log contains a record of all changes made to a Task, including the updated properties, the user that made the change, and the exact time the change was made.