| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| 73:compliance [2019/09/19 18:46] – emr | 73:compliance [2020/07/15 15:34] – emr |
|---|
| Typically a process has to comply only with specific sections of a reference model. Those sections are called [[:general:reference_model|scopes]]. The processes are then mapped against these scopes. | Typically a process has to comply only with specific sections of a reference model. Those sections are called [[:general:reference_model|scopes]]. The processes are then mapped against these scopes. |
| |
| {{ :73:compliance-assignscopes.png?direct&801x393 }} | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:compliance-assignscopes.png|{{ :73:compliance-assignscopes.png?direct&801x393 }}]] |
| |
| To define that a process needs to be compliant with to a set of reference model scopes, use the ''Management > Compliance'' menu and add them via the ''Add Reference Model'' button. | To define that a process needs to be compliant with to a set of reference model scopes, use the ''Management > Compliance'' menu and add them via the ''Add Reference Model'' button. |
| To assign process content to a specific requirement, use the context menu in ''Compliance References'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(2)**</font> . The assignment works exactly the same as in assigning process elements to each other. You can use the element comment for each assignment to record details about each mapping, e.g. which chapter of a work product covers the standard requirement. | To assign process content to a specific requirement, use the context menu in ''Compliance References'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(2)**</font> . The assignment works exactly the same as in assigning process elements to each other. You can use the element comment for each assignment to record details about each mapping, e.g. which chapter of a work product covers the standard requirement. |
| |
| {{ :73:compliance-mapping.png?direct&801x393 }} | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:compliance-mapping.png|{{ :73:compliance-mapping.png?direct&801x393 }}]] |
| |
| Finally, it can be defined how well a set of mappings covers a standard requirement. To set the coverage, use the context menu in the ''Compliance Coverage'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(3)**</font> . | Finally, it can be defined how well a set of mappings covers a standard requirement. To set the coverage, use the context menu in the ''Compliance Coverage'' box <font inherit/inherit;;#ecf0f1;;#e74c3c>**(3)**</font> . |
| |
| {{ :73:compliance-rating.png?direct&300x247 }} | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:compliance-rating.png|{{ :73:compliance-rating.png?direct&300x247 }}]] |
| |
| Defining the correct coverage is typically expert judgement, but you can use the following scheme as an orientation: | Defining the correct coverage is typically expert judgement, but you can use the following scheme as an orientation: |
| Some process participants need to understand why a certain activity or work product is required. This can be accomplished by using the ''Compliance'' perspective when viewing the process content. | Some process participants need to understand why a certain activity or work product is required. This can be accomplished by using the ''Compliance'' perspective when viewing the process content. |
| |
| {{ :73:compliance-viewmappings.png?direct&801x393 }} | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:compliance-viewmappings.png|{{ :73:compliance-viewmappings.png?direct&801x393 }}]] |
| |
| This perspective is configurable, but normally shows the description of the process element and its compliance mappings side-by-side. The users can follow the links to the respective compliance requirements, ideally by opening the link in a new browser tab or window. | This perspective is configurable, but normally shows the description of the process element and its compliance mappings side-by-side. The users can follow the links to the respective compliance requirements, ideally by opening the link in a new browser tab or window. |
| To generate the traces, select the desired reference model scopes and run the report. | To generate the traces, select the desired reference model scopes and run the report. |
| |
| {{ :73:compliance-traces.png?direct&800x444 }} | {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/73/compliancetraces_1.png?direct&800x409 }} |
| |
| To see the compliance requirements and the mapped process content, use the ''Simple'' view of the report. To see the individual mapping parameters, coverage, and notes, select the ''Detailed'' view. Both views contain direct links to the compliance requirements and the mapped process element. The links automatically open a new browser tab. | The report shows the compliance requirements and the process content that is mapped to them. It also contains the coverage, notes, and other information. There are direct links to the compliance requirements and the mapped process element. The links automatically open a new browser tab. |
| |
| In some cases, it saves a lot of time to map reference models onto each other. If you would like to also include those indirect traces, switch on ''Include Mappings across Reference Models''. | In some cases, it saves a lot of time to map reference models onto each other. If you would like to also include those indirect traces, switch on ''Include Mappings across Reference Models''. |
| ===== Show Compliance Gaps ===== | ===== Show Compliance Gaps ===== |
| |
| The same report can also be used to see the compliance gaps. Simply enable ''Include Empty Mappings'' and run the report as described above. | The same report can also be used to find the compliance gaps. Simply set ''Include Gaps'' to "Yes" or "Only Gaps" and run the report as described above. |
| |
| ===== Generate Evidence ===== | ===== Generate Evidence ===== |