The Project module is used for project management and gathers all project-related information in one place. This includes key project details such as the project manager, dates, status, and contract information, as well as linked data from other modules in the system. Commonly used modules in connection with projects include tasks, documents, checklists, and non-conformances. However, it is also possible to make use of modules such as risk, protocols, JSA, competence, products, equipment, and finance. Registrations can be linked to a project either by opening the project and creating a new entry from there, or by going directly to the module and selecting the project within the form.
The project module offers several options and methods for working with projects in Landax. In some cases, projects are standardised and predefined, with set activities and required documentation. In others, the projects are more open, with content that is not defined in advance. For projects with predefined content, templates can be created to include elements such as activities, documentation, and participants. It is possible to set up multiple templates, allowing you to reflect the different types of projects used within your organisation. When a project is created from a template, all predefined content is copied into the project, providing a structured starting point.
Projects can include sub-projects. These may represent different phases of a project, such as sales and marketing, planning, execution, and completion, or they may represent different areas within a project.
The project module includes a tree structure consisting of main projects, sub-projects, and tasks. Using sub-projects and tasks is optional. Data added to a sub-project or task is also displayed in the main project dashboard, and data added to a task within a sub-project is displayed in both the sub-project and the main project. This provides a complete overview of all project data in one place.
Projects can be drawn as flowcharts in the process module and imported as projects. The projects follow the same structure as the processes and sub-processes, where the top-level process becomes the main project and the sub-processes become sub-projects. The boxes in the flowchart represent tasks. It is possible to select which boxes in the flowchart should be imported as tasks in the project.
Sections are used to display the content of a project. The content is presented in a dashboard. Both sections and dashboards can be edited and customised to suit your company’s preferences.
Project templates commonly consist of tasks, document requests, and participant requests, although they can also include data from other modules. When setting up a project template, it is useful to begin by identifying which activities the project includes, what documentation is required, and which roles will be needed throughout the project.
Activities in a project are registered as tasks. Tasks can include information such as the person responsible, the person performing the task, planned start and done dates, due date, status, and notes. Additional configuration options are available; to access these, activate configuration mode while viewing a task form.
Documentation may consist of documents and checklists. These can be uploaded continuously during the project or added through document requests. Documents and checklists can also be linked to a project template without being defined as document requests. A document request is a predefined request for documentation. The advantage of using document requests is that you do not need to assess the documentation needs for each individual project—once defined in the template, the requests are duplicated automatically. This makes it easy to track which documentation is required, what has been submitted, and what is missing.
Document requests can be linked to either the project or individual tasks. In some cases, they are assigned to tasks in order to define responsibility and deadlines for when the documentation must be uploaded.
Participants in a project may include employees, suppliers, customers, and contact persons. They can be added directly or through participant requests. Suppliers, customers, and contact persons cannot be given access to the project unless they are registered as users in the coworker module and granted the appropriate permissions.
Participant requests are predefined roles within a project, used to provide an overview of which roles are needed. When a project is created from a template, the requests are filled in with the individuals who will hold the respective roles in the project. Participants can also be used to manage permissions and grant access within the project.
Tasks can be automatically assigned to employees added to a project with a specific role. For this to work, participant requests must be used, along with the 'Responsible' or 'Performed by' role on the tasks.