| 3 workspaces | details |
|---|---|
| COMPANY | Company is the workspace for mapping companies or departments in a structured way and for managing company-related information and data. |
| PROJECT | Project is the workspace for managing projects centrally and automatically distributing project information and tasks. |
| PERSONAL | The personal space is, so to speak, the personal workplace of the user. In this personally accessible area, each user receives a summary of their tasks, information, etc. from all projects in a clear overview. |
| features: participants | details |
|---|---|
| participant management | You can search for (name or email), invite and manage participants from all your workspaces. |
| quick invite | The Quick Invite feature allows license owners to invite multiple users, to multiple projects, and assign them to different roles at the same time. |
| distribution lists | Define your project-specific distribution lists, which can be accessed by all participants in order to send messages in a time-saving manner. |
| participant history | At any time there is a complete and unchangeable overview of who has invited or uninvited which participants on the platform and when. |
| deputy management | Comprehensive deputy regulations. |
| Google Maps integration | Locate your project team members by clicking on the “Maps” icon. In another tab Google Maps opens with the address of the user. |
| system and default roles | Predefined system and default roles are automatically provided to you when you are activated on the platform to enable quick use of the platform. |
| individual roles | Users can define any number of individual roles in addition to the various system and standard roles. The permissions are freely configurable by means of a check box. |
| simple authorization management | Authorizations can be defined individually at different levels (module and object level). This enables a fine-grained authorization configuration. Authorizations can be assigned on the basis of roles or persons. Existing authorization structures can be adapted during operation. An export of the authorization structure for administrators is possible at any time. |
| features: documents | details |
|---|---|
| flexibly configurable filing structures | You can use a template from our extensive template center or define your filing structure yourself. Existing folder structures from other systems can be easily adopted (e.g. using a ZIP upload). In addition, existing folder structures can be adopted in project templates for future projects. |
| document templates | Project-specific document templates can be stored in a structured manner in one place in the “Document templates” folder. For example, company templates can be stored here to ensure uniform documents. Each user also has the option of entering and managing their personal project-specific templates in the “My document templates” folder. You can also manage your document templates across projects via your personal area. The personal folder area can also be used for document transfer between project spaces to conveniently copy documents between projects using drag and drop. |
| automatic versioning and complete history | The system allows managing all versions of a document – from creation to archiving. A complete record enables information to be obtained at any time about who changed what in which version, who viewed a document, which messages were sent, etc. The history cannot be changed and is therefore audit-proof. |
| check-in / check-out mechanism | Automatic version management is enabled via an intelligent “check in / check out” mechanism. This offers the advantage that a document that is currently being edited is locked for other users (reading is still possible). After editing, the document is made available again for everyone in the new version. |
| quick check in | Our “Quick Check In” feature allows you to conveniently drag and drop a new file over an older version. You will be notified if the document is currently being edited by another user. If a new version has been created by another user since your last download, you will also receive a corresponding notice. |
| drag and drop function | Document templates, existing documents, folders or even folder structures can be easily moved around the platform or imported using the drag and drop function. |
| tagging | Tagging is the project-specific assignment of terms that describe a document in more detail. Add tags to documents to make them easier to find later. The created tags are visible and selectable for all project participants. |
| keywording | With the keywording function you can clearly define which documents should be stored in a specific folder. Multi-level keywording is possible. The keywording is integrated into the search function. |
| document Properties | Basic information about documents such as author, format, size, date, version, etc. is automatically captured. Additional information such as the processing status, descriptions, comments can be added at any time. |
| full-text search | The full-text search is the perfect help to find all documents – even across projects – for specific content and information quickly and easily. Through a variety of search parameters, sorting and display options, the search result is reduced to the individual requirements and displayed within seconds, even with a large number of files. |
| bookmark function | With a bookmark, a document can be displayed in different folders, although this document has been stored only once in the project. The purpose of this bookmark is that in this way project participants receive information from folders to which they do not have access (e.g. technical as-built documentation for the further operation of the building). In addition, this function is intended to avoid redundant storage of documents and to ensure uniform versioning. |
| online processing of documents | Online editing of documents is possible via WebDAV and supports all common MS Office documents. These can be edited online, without local caching, and automatically saved on the platform. Offline edits to the document are also automatically updated the next time the user logs in. Online editing is fully integrated in the version management and thus ensures a traceable change history for the documents. |
| document coding | Our customizable, automatic document coding (optional) supports uniform document naming in the project. Based on the file name, an automatic document name can be generated according to individually defined specifications. This greatly simplifies your search and classification of documents. |
| flexibly configurable permissions | Permissions can be set down to object level, e.g. folder or document. Folders can be additionally restricted to prevent unwanted renaming or moving. However, users can still store documents or other configurations. Existing authorization structures can be adapted during operation. |
| access check | A transparent access check allows each user to see who has access to folders or documents. |
| favorite view | To restrict the view to frequently used folders and documents, the Favorites view is available. |
| image preview | Switch the view from list view to image preview at the touch of a button. Reduce image search times by using the image preview feature. When moving the mouse pointer over a document or image, but also in the folder view, a preview image with image preview is displayed. Image previews are of course also visible in the filing structure and printable in reports. |
| hide empty folders | Besides the favorites view function, you can click “Hide empty folders” to reduce the view to those folders that contain documents. |
| notifications | Notifications can be used to inform you about events concerning a folder or a document. These can be predefined by an administrator or each user has the option to configure them themselves. Notifications can be set person-related as well as role-related. Notifications can be sent by e-mail at a time interval defined by you (immediately, daily, weekly, monthly) and can be configured for all projects. |
| cross-folder document sending | When sending messages, it is possible to attach several files that are stored in different folders. |
| document sharing using temporary links | Temporary links allow you to securely and quickly share files with unregistered platform participants while still maintaining full visibility and control over your data. The link is valid only for a predefined period of time. |
| discussions | Discussions, e.g. related to specific documents, enable a collected and clear exchange of information. |
| document workflows | Send documents through workflows to seamlessly document their processes. |
| ZIP import | Import of any file types and file sizes is supported. Documents can be uploaded simply by drag & drop. For larger files and filing structures from other systems, a bulk upload via ZIP file is available. |
| ZIP export | You can download your project filing structure (folders, documents and table of contents) as a ZIP file at any time. |
| interfaces (API) | On request, extensive interfaces are available to connect other systems (e.g.: BIM platforms, archiving systems, etc.) to projectnetworld. |
| duplicate check | During the document upload, the system checks whether the document has already been filed. |
| features: forms | details |
|---|---|
| form designer: extensive field types | This feature offers the user the possibility to build own input masks for forms with the form designer. Various field types such as drop-down menu, date, event, calculation field, links, etc. are available to you when designing your forms. |
| form designer: dependencies | Dependencies between the fields can be easily defined. |
| form designer: complex calculations | The designer makes it possible to specify complex calculations. |
| form designer: required fields | It is possible to define mandatory fields. |
| form designer: automated filling via workflows | This feature offers the user the possibility to build his own input masks for forms using the form designer. Automated filling via workflows can be set. |
| form designer: reports and evaluation lists | Create individual evaluation lists online. Individual reports, adapted to your corporate design, can be stored in a wide variety of formats (PDF, PPTX, CSV, etc.). |
| form designer: form templates | Copy forms from other projects or make use of our extensive template center. |
| form designer: field-level notifications | You can define events at field level to trigger specific notifications (changing a status, assigning people, etc.) |
| versioning of form entries | Changes in form entries are automatically saved as a new version. All old versions can be viewed at any time. The changes are documented down to field level. It is therefore always possible to trace which field was changed when and by whom. |
| form history | An audit-proof log of all accesses to all form entries is available to you at any time. This creates a transparent and secure record of who edited or viewed which form entry, and when. |
| standard print views | Various standard print views are available. Links to form entries (e.g. images, etc.) can be printed as well. |
| evaluation lists and views | Extensive filter and sorting options are available for individual evaluation lists and views. |
| form workflows | The forms module is fully interconnected with the workflow module, so form entries can be sent through workflows as desired. |
| audit history in reports | If form entries run through a workflow, the check/release history can also be printed with the form reports. |
| discussions | Discussions at the form level allow you to exchange additional information. |
| dashboard channel | The overview page of each work area (dashboard) contains the following content for the forms module: Forms changed within the last week. A discussion module can be started for each form data record. |
| features: digital plan management | details |
|---|---|
| Workflow-based plan runs | Plan runs can be defined individually per project, copied from other projects or taken over from project space templates. The definition is done graphically based on the international workflow standard BPMN 2.0 (Business Process Model and Notation). Any number of check runs can be configured with the planned run designer if different check logics are required in the project. |
| plan run versioning | Plan runs can be adapted during test operation via a version management system, thus ensuring maximum flexibility. In addition, configurations can be used to flexibly adapt the platform behavior (locking plan versions in the course of inspection tasks, etc.). |
| plan run status | The status of the plan run is displayed by means of a colored symbol logic in the plan directory to provide a quick and easy overview of the progress. If deadlines are not met during a plan run, this is marked accordingly. |
| plan code | An individual plan code can be stored in each project. This ensures that only correctly named plan documents can be sent through the test run. The value lists of the coding can be flexibly extended during the test run. In addition, the plan coding includes automatic plan versioning, which can also be adapted as required. Inspection points can be set up in such a way that they can be flexibly switched on and off per plan via checkboxes in the plan delivery catalog. |
| plan directory | The plans to be delivered are uploaded to the plan directory. All plans are displayed with their last revision number and the status of the corresponding plan run. If the plan code corresponds to an entry in the plan delivery catalog when uploading and at least one inspector has been selected, the stored plan run is started automatically.
Current plan revisions can be viewed in the plan directory at any time. Several plans can also be downloaded as a compressed ZIP file. |
| plan delivery catalogue | The plan delivery catalog can be created easily and quickly, and can also be imported via Excel upload if desired. A template is available for the import as a download. The view can be configured individually. The individual inspectors can be conveniently customized via checkboxes. Thus it is possible to define the inspectors individually per plan. The plan delivery catalog can be output in the form of a CSV or PDF file. |
| definition of test points | Test points can be set up in such a way that they can be quickly switched on and off per plan via checkboxes in the plan delivery catalog. |
| plan tasks | If a user receives a task from a plan run, he is informed about it in different ways.
If a user opens a task, he basically sees three areas: If the user has made all the necessary entries and confirmed them, the next plan run step is initiated automatically. |
| direct filing of objects in planning tasks | A direct filing of several form reports, documents and plans in a workflow or plan management task is possible. |
| plan comparison | The plan comparison function automatically recognizes plan changes and highlights them in color. Thus, differences in two plan versions (old / new) are immediately apparent. |
| multitasking function | In the course of the inspection of plans, there is the possibility, in the sense of good usability, that any number of plan run tasks can be carried out “in one step”. This prevents each task from having to be opened and completed individually. |
| plan lockable during review | If a plan is currently being processed by a person responsible in the test run, the plan can be locked during the test. |
| verification by signature stamp | The verification of plans takes place after a successful check by printing a signature stamp (names of the examiners with date) on the PDF plan. |
| plan header print | The positions of the plan header fields (e.g. plan code, revision number, release status, etc.) are specified in advance. Current information about the plan run, e.g. signature stamp after successful inspection, can be printed automatically on the PDF plan. |
| QR code function to check validity of a version | Even users who are not registered on the pnw platform can use a simple QR code scanner to scan the QR code printed on the plan and see at a glance whether they have the current version of the map in front of them. Both on the construction site and in the office. |
| reports | Smart and easy-to-generate report lists on, for example, missing or existing plans or lead times facilitate schedule control. |
| automatic filing of objects after completion of the plan run | Workflows and plan runs can be configured in such a way that after completion of the workflows, form reports are automatically created and automatically filed in a defined folder in the documents module. This function is available for standard and individual reports. In addition, documents and plans can be automatically filed in a defined folder in the documents module. |
| ZIP export | A mass export via ZIP download is possible. |
| features: workflows | details |
|---|---|
| drag abd drop design of workflows with standard elements | projectnetworld offers extensive functions for the flexible design of workflows according to the international BPMN 2.0 standard. A workflow is individually created by PNW in coordination with the users and stored in the workflow module. For example, you can digitize and automate your approval processes for projects, documents or forms. |
| individual roles (functions) | All internal and external process participants can be represented in workflows (pool). Individual participants are represented in a workflow by means of a user / user role (lane). Any users and roles can be included in a workflow. The administration of roles and rights is easy to manage. |
| serial and parallel tasks | It is possible to map serial and parallel tasks in workflows. For detailed information regarding workflow modeling according to the BPMN2.0 standard, we refer to our knowledge base. |
| single and multiple tasks | It is possible to map single and multiple tasks in workflows. For detailed information regarding workflow modeling according to the BPMN2.0 standard, we refer to our knowledge base. |
| loops | It is possible to map loops in workflows. For detailed information regarding workflow modeling according to the BPMN2.0 standard, we refer to our knowledge base. |
| individual script tasks | Script tasks are specially programmed functions that are executed by the system in the background, e.g. locking the editing of extended project properties. Script tasks are currently available for locking and unlocking documents. This can be used, for example, to prevent a document version from being created while an approval workflow is running. |
| individual color design | The individual elements in a workflow can be individually colored. For detailed information regarding workflow modeling according to the BPMN2.0 standard, we refer to our knowledge base. |
| settings for deadlines | Deadlines for test steps, for example, can be easily set and monitored. |
| settings for reminders | Reminders for e.g. due test steps can be set. The responsible person is informed on the platform by means of notifications. |
| several objects (documents, forms, etc.) can be assigned to a workflow | A workflow can be started for objects such as workspace, document and form. Since different workflow settings are to be made for these objects, different workflow types are also provided for each object type (workspace, document, form). Only one workflow instance can be started per object, but several objects (e.g. documents) can be contained in one workflow instance. |
| direct filing of documents in workflow tasks | Direct filing of multiple form reports, documents and plans in a workflow or plan management task is possible. |
| workflow object lockable during review | If a workflow object (e.g. document or form) is currently being edited by a responsible user, the object can be locked while it is being edited. |
| comment function for workflows | The comment function for workflows enables comprehensible and structured documentation of process progress. Central and individual notifications always keep the project team informed about changes in the process. |
| multitasking function for workflows | Various tasks are supported by a multitask function. For example, inspectors have the possibility to open several inspection tasks at the same time in order to complete them more efficiently. |
| Versioning workflows | Flexible adjustments, such as removing a role or task, are also possible during operation through versioning of workflows. |
| workflow history | In the workflow history, all steps that have already been performed (step name, who, time of assignment of the step, completion of the step, deadlines defined if applicable, status of the step, actions performed, and comment) are documented and references to the underlying object(s) (e.g., documents) are also stored. |
| central and individual notifications | You can use notifications to be informed about workflow events. These can be specified by an administrator or each user has the option of configuring them himself.
Notifications can be set person-related and role-related, e.g. all planners in the project receive this notification. |
| automatic filing of objects after completion of the workflow | Workflows and plan runs can be configured in such a way that, after the workflow has been completed, form reports are automatically created and automatically stored in a defined folder in the documents module. This feature is available for standard and custom reports. In addition, documents and plans can be automatically stored in a defined folder in the documents module. |
| dashboard channel | The overview page of each workspace (dashboard) contains the following content for the workflows module: New tasks and tasks – In progress, late or starting in the next week. In addition, active workflows are displayed on the project overview page. |
| features: claim management | details |
|---|---|
| creation / import of orders | Purchase orders can either be imported via an interface to an ERP system or entered manually. The following order master data can be displayed, for example: Name of the order, order number, company, type of order, description, etc. |
| claim registration (also ÖNORM compliant) | The claim filing consists of two successive sections: Submission according to the reason and submission according to the amount. A standard-compliant (ÖNORM) processing is possible.
The areas “Submission according to reason” or “Submission according to amount” can be saved as a draft. The visibility of the fields depends on the assigned role for the project participant. Any files can be uploaded as attachments in each field. Automatic notifications are sent by the system to the project participants according to their role depending on the possible actions. |
| multiple deadlines | Various deadlines can be set for the claim application: Deadline until submission according to the reason / Deadline for submission according to the amount / Deadline for examination according to the reason / Deadline for examination according to the amout / Deadline until commissioning. |
| attachment of documents | Any file can be uploaded as an attachment in any area of the claim submission or processing. |
| workflow-supported | Claims can be sent easily through individually defined workflows including deadlines. The projectnetworld Workflow Designer makes it possible to map even the most complex processes and adapt them during operation. Alternatively, you can use a template from our extensive pool. In both cases, you can configure your claims with just a few clicks and adapt them to your requirements. Or use our turnkey addendum management module. |
| history | The unchangeable history makes it possible to trace at any time who processed which tasks and what decisions were made. |
| multi-level claim audit (examination of the reason and the amount) | A level-based claim check has been systematically deposited: first on the reason and then on the amount. |
| private and public review comments | Private and public review comments create the basis for a joint handling of claims on the platform.
The dynamic display of the latest public review comments in various overviews provides a quick overview of the latest negotiation results. |
| claim processing using to-dos | Individually required persons in the course of the claim check (e.g. experts,…) can be easily integrated into the decision-making process using to-dos. |
| automatic notifications | Automatic notifications are sent by the system to the project participants according to their role, depending on the possible actions. |
| evaluations of claims | Comparison and evaluation of service changes (submitted vs. checked) can be created via convenient check masks. |
| claim-specific rolls | By activating the Claim Management module, standard roles are automatically enabled. The authorizations of these roles can be individually adapted to the project requirements. Other roles that already exist in the project can also be configured for the Claim Management module. The permissions of the module are controlled down to the field level. The visibility of the fields during supplement registration and processing depends on the role assigned to the project participant. |
| features: phases and processes | details |
|---|---|
| hierarchical work breakdown structure | projectnetworld supports the structuring of a project in phases, processes, milestones, deadlines and to-dos and can be easily adapted to company-specific requirements and standards. |
| WBS code | The WBS code (work breakdown structure code) shows the levels of the project structure. |
| logical links (dependencies and constraints) | Processes can be assigned to phases. Milestones, in turn, represent significant interim goals in processes. (Scheduling) dependencies and constraints in the links can be taken into account and individually configured. |
| phase, process and milestone planning | The following planning results are possible, for example: phases for the presentation of the rough overview, processes for a detailed sequence planning, milestones in a milestone plan, to-dos for the participant-related processing of tasks. These different elements can each be used alone or combined with each other as desired. |
| resource planning | In the personal workspace of the project member, all tasks that have been assigned to him/her are clearly displayed. The possibility of feedback on the status provides an up-to-date picture of the degree of completion or progress of individual tasks. |
| resource utilization | By assigning project members to individual tasks, a resource-specific work calendar is created that shows the current workload of individual project members. |
| effort planning | The option ” Effort planning enabled ” allows to enter the planned hourly effort for each resource of an operation. (What is the planned hourly workload of this resource until the completion of the process?) |
| progress calculation | Progress calculation can be done manually or based on a schedule. |
| automatic vs. manual planning | There are two ways of planning process: automatic planning or manual planning. |
| penalties | Define deadlines (penalties) for time-critical process or test steps (milestones). A reminder function supports you in meeting and easily tracking deadlines as well as due test steps. |
| link to to-dos | To-dos can be assigned to a process or created independently of the schedule. |
| list and GANTT view | Switch between list or graphical view at the push of a button. Entries can be changed e.g. more easily via grid edit in list view, the changes are immediately applied in the graphical view. Usability is also a top priority here and functions such as drag & drop have been integrated. |
| critical path indicator | Various sorting and filter options enable a user-specific perspective on different project situations (e.g. delayed processes). Colors and symbols support the display of certain criteria (e.g. critical path). Reports also provide an up-to-date overview of the status of the project. |
| drag and drop | Extensive drag and drop as well as direct editing options significantly increase usability for users. |
| quick edit of process lists | Process lists can be quickly adjusted with the quick edit function. |
| localization (time zones) | Our localization function is particularly useful for global project teams – you get your appointments localized by location and thus automatically adjusted to your time zone. |
| standard reports | Generate status reports and automatic task lists at any time that can be exported as PDF or Excel files. The following standard reports have already been stored systemically: Late Tasks, Due Tasks, Resource Utilization, Overloaded Resources, Scheduled Tasks. |
| import from other systems | We are open to other systems – Import of any file types and file sizes is supported. Documents can be uploaded simply by drag and drop. For larger files, project structures from alternative systems or multi-document uploads, we recommend bulk import via ZIP upload or we offer upload as a service. Note: MS Project and XML import are supported. |
| extended filter options | Numerous freely configurable filter options enable processes to be found or sorted quickly. In this way you keep track of your projects and you can set, for example, only tasks in a certain phase, only tasks assigned to certain people or only all delayed tasks to be displayed. |
| features: to-dos | details |
|---|---|
| easy task creation | Tasks can be created manually (e.g. in the To-dos module) or fully automatically (e.g. via the Workflows module). |
| private to-dos | To manage a confidential task, select the “Private to-do” checkbox when creating the to-do. Private to-dos are visible only to the creator and the executor. |
| task types linkages | To-dos can be assigned to a task or created independently of the schedule. In order to better control a complex process, the responsible person can create to-dos within the process, define responsible persons and end dates. The process can be broken down into subtasks with to-dos, so to speak. |
| tasks with integrated document filing | Any number of documents can be stored for each to-do – either uploaded directly or linked from document management. You can create a new document and a link to the new document directly from a specific to-do. Likewise, it is possible to check in a new version of an existing document. |
| central to-do lists | In the to-do list you can group to-dos by task, by status, by creator and by the user responsible for performing them. You can manage the status of assigned tasks in real time at any time. |
| private to-do lists | With projectnetworld, each project participant is assigned their tasks with a description and due date. |
| notifications | Central and individual notifications always keep the project team informed about changes in the process. Everyone involved (creator, executor) in a to-do automatically receives an email notification when a to-do is created or changed. |
| comment function tasks | Feedback, questions or results on the tasks are handled securely, comprehensibly and in compliance with data protection regulations via the platform. This structured communication significantly reduces the control effort in the project team. |
| reports | Specific project information, e.g. task workloads or due tasks, can be evaluated online or with reports at any time. Because all tasks and completion notes, from assignment to completion, is fully and automatically documented. |
| features: mailbox | details |
|---|---|
| projectnetworld mailbox | The integrated mailing function enables an efficient and traceable flow of information. The mailbox doesn’t require a separate specific project mail address but uses your e-mail address stored on the platform. It contains all messages sent by you via the platform and all messages sent to you via the platform. It is possible to search, group, filter, sort or export messages. You can switch between a project-specific or cross-project view at any time. |
| search function | The smart search function allows you to find messages quickly. The following fields can be searched: from, subject, message, to internal subscribers, to external subscribers, link. |
| grouping function | Messages can be grouped into the following categories: module, from, to internal participants, to external participants. |
| distribution lists | Messages related to documents or folders can be sent to persons, roles or distribution lists. Project-specific distribution lists – these are available to everyone in the project – or personal distribution lists can be defined. Sending to non-registered platform participants via download links is also possible. |
| complete history | Once sent, all messages cannot be changed and are therefore audit-proof. |
| features: Discussions | details |
|---|---|
| discussion forum | The Discussions module can be found in the project and company workspaces. Depending on which project or company you are in, you have access to the individually created discussion groups there or to the respective discussion contributions.
The discussion module enables a structured, comprehensible exchange of opinions between project participants. The structuring of topics into discussion groups facilitates the organization, offers transparency and secures the existing as well as acquired knowledge of the project group. Any project-related problems that arise are recorded in the system and are retained. The user can receive e-mail notifications about new entries in specific discussion groups. |
| module related discussions | Decoupled from the central discussion forum, module-related – e.g. for each document and form – discussions can be held. |
| search function | The search function makes it possible to find discussion content quickly. |
| archiving function | Posts or even discussion groups can be archived at the push of a button. Archived discussions are only displayed if the corresponding setting is set “Show archived”. |
| moving posts between discussion groups | Any post can be moved to another discussion group e.g. from the discussion group “Error found” to “Error fixed”. The entire post (including all replies) is always moved. |
| flag new posts | In the overview you can see all discussion groups in the project including information about the number of posts and a short description. If there are new, unread posts in discussion groups, they are displayed in a separate column. |
| dashboard channel | The overview page of each workspace (dashboard) contains the following content about the Workflows module: Discussion groups. |
| features: News | details |
|---|---|
| central news channel | Within a project, news and suggestions can be displayed to all project participants via the news area – similar to a bulletin board. Each participant can receive notifications about new entries via e-mail. |
| creation of news articles | During the creation you can assign a topic for your news and create a news text. Additionally, a link to another object (document, a to-do, a meeting, etc.) can be added. After confirming the entries, your news article is created and added to the list. Existing news articles cannot be edited afterwards. |
| features: reports | details |
|---|---|
| report templates | projectnetworld offers an extensive report module with report templates that can be stored project-specifically. Systematically recorded data can thus be easily brought into a graphical interface with the help of our report templates. For example, the master data of participants in meetings can be easily exported from the platform and used as the basis for a list of participants (template). |
| extensive status and project reports | Create portfolio reports, project status reports, daily reports, inspections, checklists and much more at the push of a button. With pnw you can create all necessary reports, checklists and daily logs on the spot. In principle, an export can be made from all systemically recorded data into your desired file format. |
| customization: corporate design | Reports and reports can be customized and designed in your corporate design. |
| filing of reports | Reports can be not only downloaded, but also stored directly in the Documents module. |
| features: project portfolio | details |
|---|---|
| project portfolio overview | The overview page allows categorizing projects and subprojects, creating lists and views over all projects, creating structured list views for subprojects, numerous detailed information or even managing related subprojects in a clear tree view. |
| extensive portfolio reports | Extensive portfolio reports can be generated at the push of a button. |
| customize views | Views can be configured and saved individually. |
| managing views | View configurations can be defaulted to other workspaces. |
| sharing views | Preset views can be shared. |
| subcompanies | Subcompanies or departments are displayed clearly and structured in the list view. |
| subprojects | All projects can be broken down into partial or sub-projects. |
| features: templates | details |
|---|---|
| create workspace templates | Individual workspace templates can be configured at any time. |
| create workspace templates from existing projects | Existing projects can be saved as a template in order to be able to use the proven existing project structure in new projects. |
| view management | Specify whether only folders with access rights are to be displayed in the template or whether all folders are to be displayed. However, folders without access permission cannot be opened. |
| management | details |
|---|---|
| project information management | Here you can manage your project information (e.g. status, dates, etc.). |
| company information management | Here you can change the company information (name, type, description, logo, subcompany, etc.). |
| template management | Here you can create a new template from this workspace. Users can create their own project space templates or save an existing project as a template to be able to use the proven existing project structure in new projects. In the personal area you can view or change your personal templates. |
| notification management | Here you can manage notifications on news, discussion groups, tasks, forms, documents and folders. Notifications are automatically sent by e-mail at a time interval defined by you (immediately, daily, weekly, monthly). You can change the settings for notifications at any time, both across projects and on a project-specific basis. |
| personal settings management | Here you can change your personal settings (e.g. address, telephone number, password, etc.). |
| distribution lists management | You can create or edit personal distribution lists. |
| add-ons | details |
|---|---|
| standardized interfaces (APIs) | On request, various API interfaces can also be offered by projectnetworld. |
| Single Sign On | Users can access the platform after a one-time authentication without having to additionally log in each time. |
| enterprise installation | projectnetworld is available as a cloud service or as an on-premises installation. |