Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
73:custom_reference_models [2019/04/02 18:29] – emr73:custom_reference_models [2019/04/02 18:38] – emr
Line 1: Line 1:
 ====== Create Custom Reference Models ====== ====== Create Custom Reference Models ======
  
-Reference models …+===== Reference Models =====
  
-…+Reference models are very similar normal Stages process, but typically use a different metamodel to define compliance requirements. Typically, a metamodel called ''TTO-Model for Standards'' (or similar) is already installed on every server, which is equipped to model Chapters and Requirements.
  
-Scopes+The only difference between a process and a reference model is the process type that can be set in ''Management > Settings'' under Process Kind. 
 +===== Reference Model Scopes =====
  
-…+===== Cross-Reference Models =====
  
 Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly. Reference models can also be mapped onto other reference models. For example, it may make sense to map evidence tables in the appendices of some standards onto the standard requirements themselves and then trace your processes only onto the evidence tables. The Compliance Traceability report can then use the cross-reference-model-mappings to show compliance to the original standard without having to map to it directly.