---
type: concept
title: Resource Management
tags: ["administration", "it-resources", "lifecycle", "ums", "it-administration", "resources"]
related: ["ums", "universitatsrechenzentrum-urz", "ressourcen-beantragen", "ressource-genehmigen", "ressource-beantragen", "ressource-loeschen", "ressource-verlaengern", "fremddomain", "ressourcen-verantwortlichkeit-aendern"]
created: 2026-06-30
updated: 2026-06-30
sources: ["output/rz_uni_greifswald_de_dienste_allgemein_ressourcen.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_ressource_beantragen.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_ressource_genehmigen.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_ressource_loeschen.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_ressource_verlaengern.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_spezialfall_fremddomain.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_verantwortlichkeit_aendern.md"]
---

# Resource Management

**Resource Management** (Ressourcenverwaltung / [[ressourcenverwaltung]]) at the Universität Greifswald is the electronic process of requesting, approving, and maintaining technical IT assets provided by the [[universitatsrechenzentrum-urz]]. Examples of these assets include **IP addresses**, **web space**, and **domains**.

## Administration via UMS
The [[ums]] (Account Management System) serves as the central interface and administration tool for all technical resources, ensuring that resource allocation is tracked and managed electronically. It is the primary interface for users and administrators to manage their technical assets.

## Resource Lifecycle
The electronic workflow in the [[ums]] covers the entire lifecycle of a resource. Because different source versions describe the stages differently, all perspectives are preserved below:

### Detailed Lifecycle (Existing Version)
- **Request / Application**: The initial application for a resource, specifically via the [[ressourcen-beantragen]] process.
- **Approval**: The authorization of the requested resource.
- **Maintenance**:
    - **Extension**: Renewing a resource before or shortly after expiration to prevent it from expiring.
    - **Responsibility Change / Transfer**: Transferring the management or changing the person responsible for a resource to another party.
- **Deletion / Termination**: The removal of resources that are no longer in use or required.

### Process Stages (Newly Generated Version - Source 1)
- **Request**: Initiating a request for a new resource via [[ressource-beantragen]].
- **Approval**: The review and acceptance of the request via [[ressource-genehmigen]] (specifically via the UMS "Genehmigung" menu).
- **Provisioning**: The [[universitatsrechenzentrum-urz]] provides the resource upon approval.
- **Maintenance**: Resources may be extended or modified (extending the validity of the resource is noted as being analogous to the deletion workflow).
- **Deletion**: The permanent removal of the resource via [[ressource-loeschen]].

### Simplified Lifecycle (from `ressource_verlaengern.md`)
1. **Request**: Initiated via [[ressource-beantragen]].
2. **Approval**: Reviewed and accepted via [[ressource-genehmigen]].
3. **Maintenance/Extension**: Validity is maintained or renewed via [[ressource-verlaengern]]. This is possible even for resources that have already expired.
4. **Deletion**: Resources are removed via [[ressource-loeschen]] when no longer required.

### Lifecycle Summary (Newly Generated Version - Source 2)
- **Requesting:** Initiating a request for a resource via [[ressource-beantragen]].
- **Approval:** Review and acceptance of the request via [[ressource-genehmigen]].
- **Maintenance:** Extending the validity of a resource or modifying its responsible parties via [[ressource-verlaengern]] and [[ressourcen-verantwortlichkeit-aendern]].
- **Deletion:** Removing a resource via [[ressource-loeschen]].

### Summary of Key Actions (from Newly Generated Version - Source 1)
- [[ressource-beantragen]]: The initial application for a resource.
- [[ressource-genehmigen]]: The review and approval process by a designated authority.
- [[ressource-verlaengern]]: Extending the validity of an existing or expired resource.
- [[ressource-loeschen]]: Removing a resource no longer in use.

## Management of Responsibility
A critical aspect of resource management is the ability to transfer or relinquish responsibility to ensure that IT resources are always associated with a valid university contact. Detailed steps for this can be found in [[ressourcen-verantwortlichkeit-aendern]].

## Resource Grace Period
To prevent accidental data loss or service interruption, the URZ implements a grace period. When a resource expires, it remains available for **12 weeks**. Users must use this window to request an extension if the resource is still required.

## Standard vs. Special Cases
While most resources follow a standard approval path, certain requests are classified as special cases:

- **External Domains ([[fremddomain]])**: 
    - Requests for domains other than `uni-greifswald.de` require higher-level approval from the Rectorate or a Dean's office.
    - These cases have specific technical restrictions, such as the prohibition of umlauts.
    - Detailed technical workflows for these cases are managed in separate documentation.

## Support
For problems related to resource management or other Campus-IT central services, users can contact the [[universitatsrechenzentrum-urz]] via:
- The [[groupware]] ticket system.
- The URZ hotline (extension 1420).