Assets en CMDB
Applicatiegereedheid beoordelen
Submit readiness evidence · Review readiness evidence
Choose the task you want to carry out. Each procedure includes its prerequisites, steps and safeguards.
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Submit readiness evidence
Submit readiness evidence.
Who can do this: Requester, Reader, Operator, Tenant administrator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Submitting readiness evidence does not immediately change canonical users, devices, applications, ownership, or relationships; an operator review decision is required.
- Ordinary requesters report only their own usage; department-scoped people and device review requires department key-user or equivalent authorized context.
- Search the requester-safe application catalogue before submitting a missing application, and use Service Catalog instead when the user wants future access rather than reporting current use.
- A review containing only Not sure answers cannot be submitted; at least one concrete application detail is required.
- Shared review links are department-scoped, expire after 30 days, and can be revoked; revocation blocks new access but retains already submitted evidence.
- Application identity remains operator-owned. External and portal reviewers submit evidence and proposals, not direct catalogue mutations.
- Check that Application Readiness is enabled and open the view available to your role: requester, department key user, operator or tenant admin.
- For requester work, open Portal → Applications and choose the relevant track: people and devices, application catalogue/use, or action-required evidence.
- Search the visible application catalogue before reporting a missing application, then provide at least one concrete detail and submit the evidence to IT.
Expected outcome: The user has reviewed the result of submit readiness evidence in the application.
Review readiness evidence
Review readiness evidence.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Submitting readiness evidence does not immediately change canonical users, devices, applications, ownership, or relationships; an operator review decision is required.
- Shared review links are department-scoped, expire after 30 days, and can be revoked; revocation blocks new access but retains already submitted evidence.
- Application identity remains operator-owned. External and portal reviewers submit evidence and proposals, not direct catalogue mutations.
- Reopening a completed review keeps accepted relationships in place while requesting more information.
- Match suggestions are advisory. Verify aliases, department context, and semantic identity before linking or merging applications.
- Check that Application Readiness is enabled and open the view available to your role: requester, department key user, operator or tenant admin.
- For operator work, open Assets → Application Readiness and review department coverage, applications, people/devices, knowledge requirements, and the active review queue.
- Use Needs review versus Completed and the People, Catalogue, or Usage tracks to narrow the queue.
- Inspect original evidence, aliases, relationship context, match suggestions, and review history before deciding.
- Accept or reject evidence, request clarification, propose a resolution, update catalogue knowledge requirements, or merge only when the preview confirms the intended canonical result.
- For external department review, create a shared link, communicate its 30-day scope, monitor usage, and revoke it when the review round ends.
Expected outcome: The user has reviewed the result of review readiness evidence in the application.
Aanbevolen werkwijze
- Geef voorrang aan gegevens die dienstverlening, compliance en kosten beïnvloeden.
- Leg relaties vast die een concrete operationele vraag beantwoorden.
Gerelateerde handleidingen
Lees verder in Assets en CMDB
Registraties, relaties, groepen, documenten en CMDB-structuur.