As users navigate through the application they will come across various drop-down lists of choices. The values found in these lists are configured during the setup of the software in the ‘Keywords & labels’ setup document.
Project types
The values defined in the ‘Project types’ list, appear in the [Project description document-> categorization tab -> [Type] field].
The ‘Type’ field can be used as a filter criterion when generating reports.
Project statuses
The [Project status] field is found in the header of the ‘Project description’ document. Its value is initially selected during the creation of a new project and can be updated throughout the project’s lifecycle.
The application is setup with a list of default statuses; it is possible to add statuses or change the labels of those statuses already in the list:
Stand-by#0
In Progress#2 Completed#10 Cancelled#12 Template#01
The syntax is: StatusLabel#StatusCode where the StatusLabel may be modified without influencing the behaviour of the status.
The StatusCode is used programmatically to identify the status and therefore must not be changed.
Projects with StatusCode #0 are always considered inactive.
Projects with a StatusCode between #1 and #9 can be seen and worked on by all team members and time can be reported against project tasks
Projects with StatusCode #10 have a completed status.
Projects with a StatusCode of #11 and higher have a cancelled status. In this status modifications can no longer be made directly to the project through the 'Project' database or indirectly through timesheets.
Note: None of the default StatusCode (#0, #2, #10, #12, #01) must be deleted. The Status with these Codes have to exist. It is also not allowed to use a default label on another StatusCode (e.g. "In Progress#3" is not allowed). It is possible to give different labels to all existing and new StatusCodes (expl. "Online#2" is possible).
Document types
Geniusproject terminology refers to all project ‘records’ as documents. The application includes a series of standard Geniusproject documents that are created throughout the lifecycle of most
projects; such as a project description document, plan document, task, assignment and deliverable documents etc.
In addition to the standard Geniusproject documents, organizations can create a library of their own unique document types that they can append to their projects. The ‘document types’ section, in the ‘Keywords & labels’ setup document, is where the list of organization specific documents is defined.
Once the list of types is created and the ‘Keywords & labels’ setup document is saved, corresponding documents will be created per type, and organizations can then create templates and workflows necessary to comply with their project management processes.
Cost types
A cost is typically a non-labour related expense that is budgeted into a project, such as materials, travel, advertizing, etc.
Costs are identified in ‘Inv. & exp.’ Section of a project budget.
...as well as in project ‘Cost’ documents.
The cost types available in the drop down lists are defined in the ‘Keywords & labels’ setup document.
Activity types
Activity types are used to categorize tasks. Project leaders can group project tasks into activity types for the purposes of budgeting, invoicing and reporting.
A task’s activity type is defined in its ‘Task’ document.
To change the Typ in Gantt Plan open the General Tab from a Task:
Activity types are also used for multi-rates management. If a resource’s billable rate is dependent on the type of activities they perform on a given project, organizations can define these different rates by activity type.
A resource’s rate by activity type is found in each resource profile document on the ‘Rates’ tab.
Note: For the purposes of multi-rates management, the 'Activity types' defined here must be the same as the ones defined in the General setup document of the 'Resources' database.
Activity types can also be used to break down the labour charges within a project’s detailed budget
Origins of Issues
Throughout the course of any given project, it is expected that certain issues and problems will arise. Geniusproject’s issue management section allows project managers to keep track of all issues they encounter throughout the execution of their projects, making it easier to anticipate them in the future and incorporate the necessary mitigation plans into their upcoming projects.
The ‘Origins of issues’ section of the Keywords & Labels document is where organizations will list the different types of issues they typically encounter throughout the lifecycle of their projects. Once the list is completed, project managers and team members can create issue reports specifying the appropriate origin.
Roles
Roles are a way to assign unique responsibilities to different users on a per project basis. Once roles are created, they are applied to document revision and approval workflows where only users assigned to a specific role can execute certain actions.
To begin, an organization must first identify the list of roles they need to manage, i.e. budget approver, contract approver etc., and create them in the roles section of the keywords & labels document.
To add a new role, simply click on the icon and add the role name to the list. The next step is to add the necessary role(s) to the relevant projects.
Open your project’s project description document in edit mode Click «Create» on the action menu bar and select «Role»
In the role document that opens select the necessary role and users to assign it to
Once roles have been assigned to project team members, any project document workflow that has statuses that must be approved by a user assigned to a specific role, will automatically notify the user(s) when it is time to perform their revisions.
Note: If Roles are defined in Setup the users will ask every time on saving their Project description to fill Project Roles.
To learn about creating workflows, see the upcoming section titled ‘Workflow in Geniusproject’.
Note: Deliverable types, Deliverable formats, Reply types and Note types are no longer supported and only remains for compatibility with previous versions.