# Host lookup tables This package expects the OpenITSM host to maintain three deployment-specific lookup tables. They are NOT part of the package (the package only defines the abstract triage process); each host deployment populates them. ## Expert groups The routing DMN resolves to one of these `group_slug` values. The host MUST have a matching `expert_groups` row for each: | slug | name | |-------------------|-------------------| | `helpdesk-l1` | L1 helpdesk | | `noc-l1` | Network Ops L1 | | `noc-l2` | Network Ops L2 | | `soc-l2` | Security Ops L2 | | `facility-l2` | Facility & Power L2 | | `platform-l2` | Platform Ops L2 | | `external-handoff`| External handoff | ## Service tiers The priority DMN consumes these tier codes. Hosts MUST have a matching `service_tiers` row. | code | name | first_response | resolution | |---------------|-------------------------------|----------------|------------| | `tier_1` | Tier 1 (mission-critical) | 15 min | 240 min | | `tier_2` | Tier 2 (standard) | 60 min | 480 min | | `best_effort` | Best effort (non-SLA) | — (no SLA) | — | ## Taxonomy The closed list of taxonomy codes `ai.classify@1` can emit, mirrored in the classify_incident Algorithm Card's `io.outputs.taxonomy_code.constraints.enum` and consumed as input to the priority + routing DMN. | code | LV | EN | |-------------------------------|--------------------------|---------------------| | `network.outage.link_down` | Saites pārtraukums | Link down | | `network.degradation` | Tīkla degradācija | Network degradation | | `network.routing` | Maršrutēšana | Routing | | `network.dns` | DNS | DNS | | `security.incident` | Drošības incidents | Security incident | | `facility.power` | Elektroapgāde | Power / facility | | `storage.capacity` | Diska vieta | Storage capacity | | `service.customer_request` | Klienta pieprasījums | Customer request | | `unknown.uncategorized` | Neklasificēts | Uncategorized |