81 lines
3.1 KiB
YAML
81 lines
3.1 KiB
YAML
id: https://nde.nl/ontology/hc/class/BusinessCriticality
|
|
name: business_criticality_class
|
|
title: BusinessCriticality Class
|
|
description: >-
|
|
Business criticality level classification for continuity planning.
|
|
|
|
Provides structured classification for operational impact assessment:
|
|
- **CRITICAL**: Institution cannot function without (hours)
|
|
- **HIGH**: Significant impact if unavailable (days)
|
|
- **MEDIUM**: Important but workarounds exist (weeks)
|
|
- **LOW**: Minimal operational impact
|
|
|
|
Drives backup and disaster recovery priorities.
|
|
|
|
Created per slot_fixes.yaml revision for business_criticality migration (Rule 53/56/57).
|
|
|
|
version: 1.0.0
|
|
prefixes:
|
|
linkml: https://w3id.org/linkml/
|
|
hc: https://nde.nl/ontology/hc/
|
|
schema: http://schema.org/
|
|
rico: https://www.ica.org/standards/RiC/ontology#
|
|
imports:
|
|
- linkml:types
|
|
- ../slots/has_or_had_identifier
|
|
- ../slots/has_or_had_label
|
|
- ../slots/has_or_had_description
|
|
default_prefix: hc
|
|
|
|
classes:
|
|
BusinessCriticality:
|
|
class_uri: hc:BusinessCriticality
|
|
description: >-
|
|
Business criticality level for continuity planning.
|
|
|
|
Structured class replacing string-valued business_criticality slot.
|
|
Enables type classification via has_or_had_type.
|
|
slots:
|
|
- has_or_had_identifier
|
|
- has_or_had_label
|
|
- has_or_had_description
|
|
slot_usage:
|
|
has_or_had_label:
|
|
description: >-
|
|
Criticality level label (CRITICAL, HIGH, MEDIUM, LOW).
|
|
required: true
|
|
examples:
|
|
- value: CRITICAL
|
|
description: Institution cannot function without this (hours to impact)
|
|
- value: HIGH
|
|
description: Significant impact if unavailable (days to impact)
|
|
- value: MEDIUM
|
|
description: Important but workarounds exist (weeks to impact)
|
|
- value: LOW
|
|
description: Minimal operational impact
|
|
has_or_had_description:
|
|
description: >-
|
|
Explanation of criticality assessment.
|
|
required: false
|
|
examples:
|
|
- value: "Financial system required for daily operations, payroll processing"
|
|
description: Why system is CRITICAL
|
|
- value: "Historical project files, reference only, no operational dependency"
|
|
description: Why system is MEDIUM
|
|
examples:
|
|
- value:
|
|
has_or_had_label: CRITICAL
|
|
has_or_had_description: "Financial system - required for operations, payroll cannot be processed without"
|
|
description: Critical financial system
|
|
- value:
|
|
has_or_had_label: HIGH
|
|
has_or_had_description: "Director's correspondence - important for decision continuity"
|
|
description: High-priority communications
|
|
- value:
|
|
has_or_had_label: MEDIUM
|
|
has_or_had_description: "Historical project files - reference only, operational workarounds exist"
|
|
description: Medium-priority archives
|
|
- value:
|
|
has_or_had_label: LOW
|
|
has_or_had_description: "Promotional materials archive - minimal impact on operations"
|
|
description: Low-priority materials
|