C2 (3 points)
https://knobit.org/id/task/dg-operating-model/C2
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dg-operating-model/C2 |
| rdfs:label | C2 (3 points) en |
| schema:hasPart | dg-operating-model C2: DC-004 has two deciders and sits in two mandates |
| schema:hasPart | dg-operating-model C2: DC-005 has no decider |
| schema:hasPart | dg-operating-model C2: DC-002 has no escalation and DC-006 escalates down |
| schema:identifier | C2 |
| schema:position | 2 |
| schema:text | Every decision has exactly one decider and an upward escalation path, 1 each. (a) DC-004 Settle a cross-domain definition dispute has two deciders (GB-001 and GB-003) and sits in both bodies' decides lists: one decider, or the decision type split into business definitions (GB-001) and risk data aggregation and reporting controls (GB-003), with the decides lists matching. (b) DC-005 has no decider: a decider is proposed - the domain owner of the data element is the natural one, with the CDO consulted - or the gap raised as an open question. (c) Escalation, 0.5 each: DC-002 has escalates_to null although its decider is a domain owner, so it gets GB-001; DC-006 is decided by the council and escalates down to the domain working groups, so it escalates to the Management Board instead. en |