Exercise 2: Internal Severity vs. Provider-Side Severity — Possible Solution
====================================================================

Why they are separate things:

An organization's own internal severity classification (Chapter 6) is
based on IMPACT TO THAT ORGANIZATION specifically -- how many of ITS
customers are affected, whether ITS revenue or SLA commitments to ITS
OWN customers are at risk, and so on. This classification is entirely
internal and determines the organization's own escalation and
communication response.

A provider's support-case severity, by contrast, is based on the
PROVIDER's own severity definitions (e.g. "production system down" vs.
"general guidance," per this chapter) and determines THEIR response-
time commitment under the support tier being used. The provider has no
direct visibility into, or obligation tied to, the requesting
organization's own internal business impact -- their severity
categories exist to govern the provider's own support operations, not
to mirror the customer's internal classification automatically.

These are simply two different organizations, each running their own
classification system for their own operational purposes -- an
organization's Sev1 internally doesn't automatically become the
provider's highest severity level; it has to be independently and
accurately represented in the case itself.

Why accurately setting the provider-side severity matters:

Per the chapter, an INFLATED severity in the case "may simply get
reclassified by the provider rather than fast-tracked" -- providers
have their own criteria for what qualifies as their top severity
level, and case severity isn't just accepted at face value regardless
of accuracy. An UNDERSTATED severity, on the other hand, produces "a
slower response than the actual situation needs" -- if a genuinely
production-down issue is filed at a lower severity, the provider's own
committed response time for that lower severity applies, which may be
considerably slower than what a correctly-classified production-down
case would receive.

Getting this right, honestly and accurately, directly determines how
fast the provider actually responds -- neither exaggerating nor
understating it serves the requesting organization's actual interest.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains that the two severity systems exist for two different
organizations' own operational purposes -- which is WHY they're
separate rather than automatically linked -- and then applies the
chapter's own stated consequences of getting the provider-side
severity wrong in either direction (inflated gets reclassified,
understated gets a slower response), rather than treating "set it
accurately" as an unexplained rule.