{"id":1452,"date":"2020-01-30T18:17:10","date_gmt":"2020-01-30T17:17:10","guid":{"rendered":"http:\/\/www.ev-i.at\/cdes\/?page_id=1452"},"modified":"2025-05-14T14:42:04","modified_gmt":"2025-05-14T12:42:04","slug":"planpruefprozess","status":"publish","type":"page","link":"https:\/\/www.cdes.at\/en\/planpruefprozess\/","title":{"rendered":"Plan review process"},"content":{"rendered":"\n
\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n

Plan review process<\/h2>\n\n\n\n

The plan review cycle is the central element in c.des<\/em><\/strong>.<\/p>\n\n\n\n

It is used to control all processes, dependencies and branches in order to guide each plan safely and traceably from its provision by the planner to its release for execution.<\/p>\n\n\n\n

Continuously developed since 2003, we can now cover almost any review situation. A fact that sets c.des<\/em><\/strong> apart from most competitors in this field.<\/p>\n\n\n\n


<\/p>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n

\n
\n

Modular Design<\/h2>\n\n\n\n

A review cycle can be composed of any number of the following modular parts:
1. One or more review phases <\/strong>(e.g. Status E<\/em>) that are linked by freely definable rules.
2. Review phases consist of one or more nodes<\/strong> (z.B. Planpr\u00fcfung<\/em>, Planfreigabe<\/em>)

Types of review nodes:
\u2022 Simple serial <\/strong>or serial node with parallel review positions <\/strong>(test matrix)
\u2022 Review options <\/strong>(decision options and their effects) freely configurable for each node.
<\/p>\n\n\n\n

Further possibilities to model a review cycle …<\/summary>
\n

Random reviews<\/strong>
Node-free reviews that can be carried out at any time for the current version of a plan\/document, regardless of the current status of the review controlled by the review cycle (example: \u00a740 review in the railway sector).<\/p>\n\n\n\n

Wave through tasks<\/strong>
Perform multiple tasks simultaneously with a given review option<\/p>\n\n\n\n

Optional reviewers by planners<\/strong> During the plan upload, additional reviewers may be involved at the planner\u2019s discretion<\/p>\n\n\n\n

Statement by planner<\/strong>
Binding statement on the plan upload (e.g. regarding deviations from previous project phases)<\/p>\n\n\n\n

Comment on reviews<\/strong>
Possible for each previous node. Events <\/em>configurable for each node upon node entry or exit<\/p>\n<\/div><\/details><\/div>\n<\/div><\/div>\n\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n
\n
\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div><\/div>\n\n\n\n
\n

Review Duration<\/h2>\n\n\n\n

The review duration <\/strong>can be defined separately for each review node. It is entered in working days <\/strong>(except Saturday). Weekends, public holidays and freely definable project holidays are taken into account when calculating the deadline automatically by c.des.<\/p>\n\n\n\n

The duration of the review and the responsibility for reviews and releases are determined by the project administrator at the beginning in the review sheet<\/strong>.<\/p>\n\n\n\n

Together with the planned delivery dates of the planned delivery catalogue, a comparison of the target and actual status is determined and visualized for the tasks and the review status<\/strong>.<\/p>\n\n\n\n

<\/p>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n

\n
\n


<\/p>\n\n\n\n

Initiation Review Cycle<\/h2>\n\n\n\n

The review cycle is initiated automatically by uploading the plan.<\/p>\n\n\n\n

The planner is supported by the intelligent plan upload<\/strong>, where<\/p>\n\n\n\n