Projects contain all the work, routines, assets, and users needed to deliver a specific project. In other words, Projects are a self-contained unit in Aphex that are set up and run their own way.
Project Roles
Project Roles are unique to a single Aphex Planner Project and users can have different roles on different projects. There are three Project Roles that exist in Aphex:
Project Admins | Project Admins are your project's super user, typically members of the Planning Team who are responsible for overseeing the planning process and publishing the project's plans. Admins have the ability to: |
Contributors | Contributors are typically Engineers on a project who have the ability to Own and edit work, and can be assigned permissions on other User's work. Contributors have the ability to: |
Field Reporters | Field Reporters are typically Site Engineers or Foremen on a project who have the ability to communicate and record performance against the work they have been Assigned to. Field Reporters can be assigned to Tasks and Packages giving them limited Task Permissions or Packages Permissions. |
Project Permissions
Permissions at a Project level are controlled by a User's Project role and impact a User's ability to edit data within an Aphex Planner project.
Project Admin | Contributor | Field Reporter (If Standard Member) | |
View Project | Yes | Yes | Yes |
Add Task | Yes | Yes | No |
Add Package | Yes | Yes | No |
Add User | Yes | Of type Contributor or Field Reporter | Of type Field Reporter only |
Update User Permissions | Yes | Of type Contributor or Field Reporter | No |
Ready and Unready Plans | Yes | If Owner of work | No |
Share Live Plan | Yes | Yes | No |
Publish Plan | Yes | No | No |
Promise Plan | Yes | No | No |
Update Published Versions | Yes | No | No |
View Published Versions | Yes | Yes | Yes |
Share Published Versions | Yes | Yes | Yes |
Imports | Create and Edit | Read Only | Read Only |
Project Data | Edit | Backlog Only | Read Only |
Publications | Edit | Read Only | Read Only |
Project Assets | |||
WBS | Edit | Read Only | Read Only |
Packages | Edit | Edit | Read Only |
Subcontractor | Edit | Read Only | Read Only |
Labour | Edit | Read Only | Read Only |
Plant | Edit | Read Only | Read Only |
Materials | Edit | Read Only | Read Only |
Users | Edit | Of type Contributor or Field Reporter | Read Only |
Teams | Edit | Read Only | Read Only |
Locations | Edit | Read Only | Read Only |
Calendars | Edit | Read Only | Read Only |
Delay Reasons | Edit | Read Only | Read Only |
Project Settings | |||
Project Details | Edit | Read Only | Read Only |
Import Frequency | Edit | Read Only | Read Only |
Publication Frequency | Edit | Read Only | Read Only |
Lookahead Period | Edit | Read Only | Read Only |
Publication Requirements | Edit | Read Only | Read Only |
Power BI Data (beta) | Edit | Read Only | Read Only |
Archive Project | Edit | Read Only | Read Only |
User Settings | |||
Profile Details | Edit | Edit | Read Only |
Authentication | Edit | Edit | Read Only |
Projects | Edit | Read Only | Read Only |
💡 Tip: In addition to Project Permissions, permissions can also exist at the level of Package and Task |
Project Assets
In Aphex, Assets are the fundamental building blocks of data on Projects. Teams add detail to Tasks in the form of Task Properties. Some Task Properties are populated with data that's controlled for consistency across a Project, and across Projects within an Organisation.
Project Assets are controlled by Project Admins, who have the ability to create and edit assets on an Aphex Planner project.
WBS (Work Breakdown Structure) | The consistent, project-wide reporting structure used to view and communicate work across the entire project |
Packages | A flexible way of grouping and structuring tasks in the plan that is in the control of owners of work, separate from a project's WBS |
Subcontractors | Contractors responsible for delivering the project, accountable for performance of work in the plan |
Labour | Wo(man)power resources required to deliver the Project |
Plant | Equipment and machinery required to deliver the Project |
Materials | Material resources required to deliver the Project |
Users | The collection of individuals who are responsible for taking ownership of building and communicating the plan in Aphex |
Teams | Collections of users on a project that work together and value visibility of each other's work |
Locations | A way to visually delineate the project into Location images that power Clash Detection and determine visual outputs of the plan on Maps |
Calendars | A collection of controls for working and non-working days |
Delay Reasons | A collection of root-causes for slippage used to understand project performance |
Project Routine
Projects are always changing, moving at a fast pace and proving a challenge to stay on top of when it comes to managing work and tracking progress. Teams deal with this and stay in sync through the use of a planning routine.
Aphex helps Projects maintain their routines by matching up with specific parts of this process helping to ease the burden of making sure the project always stays on course.
Publication Frequency | Projects can align their submission deadlines to working in Aphex by setting the project's Publication Frequency. This allows the Project to set a clear, consistent target to operate against by choosing the date and frequency of a plan's Publication. |
Lookahead Period | Setting the Lookahead period for a Project, allows Aphex to guide those that are Contributors towards the parts of the plan that need attention, such as Tasks that are missing key data. |
Publication Requirements | In order to gain consistency of data within a plans details across, Projects can select the information that all Contributors are required to assign to their work. Aphex then assists these users in ensuring that this information standard is met. |