The rese­arch depart­ment of the IT hos­pi­tal.

We remain in our hos­pi­tal image:

One pati­ent was remo­ved from the Recep­ti­on (1st level) and recor­ded by the Spe­cia­lists (2nd level) exami­ned. But even the spe­cia­lists can­not find the cau­se of the mys­te­rious dise­a­se. It is a com­ple­te­ly new or extre­me­ly rare phe­no­me­non.

In this case, the spe­cia­lists cont­act the 3rd level sup­port. This is the high­ly spe­cia­li­zed rese­arch depart­ment of the uni­ver­si­ty or the phar­maceu­ti­cal com­pa­ny that deve­lo­ped the ori­gi­nal drug. This is whe­re the lumi­na­ries, the deve­lo­pers, the archi­tects of the sys­tem are based. They have access to the “blue­print” (the source code) and can find and cor­rect fun­da­men­tal errors in the sub­s­tance.

When does the 3rd level come into play?

• Bugs” (errors) in the source code of the soft­ware.
• For com­plex pro­blems in the sys­tem archi­tec­tu­re.
• When all known 1st and 2nd level solu­ti­ons have been exhaus­ted.

The 3rd level sup­port often deve­lo­ps new solu­ti­ons (patches, updates), which are then made available to the 2nd and 1st level in order to sol­ve the pro­blem more quick­ly in the future.

Effec­ti­ve 3rd level sup­port is cru­cial for the long-term sta­bi­li­ty and secu­ri­ty of com­plex IT sys­tems.