| 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. |
| cross-sectional features – digital plan management | details |
|---|---|
| various sorting and filter functions | The view in the plan management module can be customized using the standard “Sort” and “Filter” functions or subdivided according to any criteria using the “Group” function. By setting a filter, you can, even with a large number of plans, for example, the overdue plan runs in a clear form. |
| standard export | The following file types are currently supported: ZIP, PDF, CSV, PPT, XLS, DOCS, XML. In addition, various API interfaces are offered by projectnetworld. |
