Glossary:Pages Edited
From USM Wiki
Page | Modification Date |
---|---|
Request catalog | 2025-05-26 19:22:35 |
Acceptance environment | 2025-04-12 12:37:46 |
Workflow | 2025-06-10 06:15:56 |
Repair time | 2024-08-30 13:11:59 |
Agree | 2024-08-30 13:18:57 |
Residual risk | 2025-06-14 15:48:51 |
Requester | 2025-06-04 07:02:08 |
Response time | 2025-06-08 08:07:41 |
Resource | 2024-11-03 13:04:36 |
Risk | 2025-06-09 08:12:19 |
Risk coordinator | 2025-04-23 11:55:50 |
Risk database | 2025-05-26 19:27:04 |
Risk inventory plan | 2025-05-26 19:33:25 |
Risk manager | 2024-08-30 14:19:20 |
Risk matrix | 2025-06-09 18:42:05 |
Risk profile | 2025-05-26 19:36:48 |
Risk scan | 2024-08-30 14:23:29 |
Role | 2025-06-07 05:35:59 |
Root cause analysis | 2025-05-27 11:43:37 |
MIR model | 2025-06-24 16:35:08 |
RUF model | 2024-08-30 15:05:01 |
Routine | 2025-08-28 02:00:06 |
Routing | 2025-06-14 15:54:19 |
Support | 2024-09-15 10:35:34 |
User | 2025-06-07 15:05:26 |
Entity | 2025-09-18 02:00:10 |
Action | 2025-09-18 02:00:10 |
Object | 2024-10-07 14:14:20 |
Domain | 2024-09-13 13:58:39 |
System test | 2024-09-13 14:27:38 |
System | 2025-06-09 19:30:22 |
System driven | 2024-10-19 10:56:54 |
Task | 2025-07-02 17:21:42 |
Team | 2024-11-03 15:36:00 |
Team-based organization | 2025-05-26 19:52:55 |
Team report | 2025-07-02 17:18:57 |
Technical catalog | 2024-09-29 17:20:45 |
Team coordinator | 2024-11-02 12:37:51 |
Technical design | 2024-09-09 20:28:11 |
Technology driven | 2025-04-13 09:57:42 |
Technology management | 2025-06-10 05:38:07 |
Technology resource | 2025-07-02 17:14:48 |
Test | 2024-09-02 13:18:08 |
Test environment | 2025-06-10 05:49:11 |
Text strategy | 2024-09-02 13:22:31 |
Threat | 2024-09-02 13:24:37 |
Throughput | 2025-06-08 12:35:12 |
Tool | 2025-05-31 14:51:29 |
Trigger | 2025-05-10 04:33:11 |
Agreement | 2025-06-10 06:02:03 |
Architecture | 2025-06-08 08:15:12 |
Organizational resource | 2024-09-20 16:05:13 |
Activity | 2024-11-02 13:26:20 |
Process | 2025-09-10 02:00:09 |
Process step | 2024-09-14 12:22:43 |
Underpinning contract | 2024-10-20 14:02:05 |
Unified | 2024-09-09 20:13:32 |
Unskilled service desk | 2025-05-27 11:52:10 |
Upgrade | 2024-09-03 13:28:24 |
Uptime | 2025-06-08 08:22:24 |
Urgent change | 2024-09-03 13:30:46 |
USM panel | 2025-01-04 10:24:09 |
User acceptance test | 2024-09-03 13:42:54 |
USM process model | 2025-08-26 02:00:16 |
Value | 2025-08-28 02:00:18 |
Value stream | 2025-08-28 02:00:13 |
Version | 2025-06-10 06:08:08 |
Vertical escalation | 2024-09-09 20:11:53 |
Vision | 2025-08-28 02:00:20 |
Weekly plan | 2024-09-04 08:56:53 |
Window | 2025-07-02 18:34:16 |
Wish | 2025-06-15 19:01:01 |
Work | 2024-09-04 19:10:57 |
Work instruction | 2025-08-28 02:00:09 |
Accountability | 2025-06-08 07:57:45 |
Administrator | 2024-09-04 13:23:53 |
Service delivery | 2024-09-13 14:11:20 |
Business | 2025-06-13 05:09:35 |
Practice | 2025-09-10 02:00:06 |
Release | 2025-06-09 18:26:46 |
Alert | 2025-06-08 08:05:11 |
Threshold | 2024-09-07 05:41:20 |
Request | 2025-05-27 08:04:15 |
Application | 2025-05-23 11:23:46 |
Component | 2024-09-07 05:59:35 |
Asset register | 2024-09-07 13:32:48 |
Class | 2024-09-07 13:36:04 |
Audit | 2024-09-10 12:34:36 |
Separation of duties | 2025-05-23 11:49:08 |
Impact table | 2025-06-08 08:19:42 |
Manage | 2025-06-13 10:13:34 |
Coordinate | 2024-11-03 13:07:40 |
Coordinator | 2024-11-03 14:58:51 |
Operator | 2025-06-01 13:16:48 |
Execute | 2025-06-15 05:26:29 |
Operate | 2025-08-26 02:00:12 |
Manager | 2024-09-17 09:51:21 |
Incident coordinator | 2025-05-27 11:50:38 |
Process coordinator | 2024-10-08 15:00:50 |
Line coordinator | 2025-05-26 09:11:46 |
Change coordinator | 2025-05-26 09:19:40 |
Process manager | 2025-05-27 11:48:10 |
Incident manager | 2024-09-12 12:09:52 |
Complaint | 2025-06-09 18:25:55 |
Call | 2025-07-01 09:23:06 |
Request for change | 2025-05-27 11:38:02 |
Asset | 2024-09-09 19:17:46 |
Change | 2025-06-10 13:12:59 |
Recovery time | 2024-09-09 20:10:34 |
Improve | 2024-09-09 20:17:11 |
Team coordination | 2025-07-02 18:33:11 |
Control | 2024-09-11 11:39:59 |
Classify | 2025-06-09 11:12:55 |
Availability | 2025-08-23 02:00:09 |
Configuration | 2024-09-11 10:46:37 |
Benchmark | 2024-09-11 10:48:41 |
Best effort | 2024-09-11 10:49:41 |
Relate | 2024-09-11 10:50:44 |
BPM tool | 2025-06-08 11:52:53 |
Management | 2025-07-02 17:27:57 |
Charging | 2025-05-26 09:21:44 |
Building information model | 2025-05-23 11:53:43 |
Business relationship manager | 2024-09-11 11:14:16 |
Change Management | 2025-06-09 11:00:26 |
Change calendar | 2025-07-02 17:29:54 |
Continuity | 2025-08-23 02:00:08 |
Contract Management | 2025-06-07 05:42:17 |
Customer journey | 2025-05-31 15:09:59 |
Output | 2025-06-08 12:36:23 |
Contract manager | 2024-11-02 16:29:04 |
Daily plan | 2025-07-02 18:27:56 |
Operations Management | 2024-09-19 09:20:21 |
Demand | 2025-09-10 02:00:09 |
Diagnosis | 2025-06-09 06:42:56 |
Recovery | 2025-05-23 11:37:01 |
Incident lifecycle | 2025-05-26 09:13:41 |
Disaster | 2025-07-01 09:51:38 |
DTAP street | 2025-06-10 09:24:12 |
Development environment | 2024-09-12 06:20:08 |
Detection time | 2024-09-12 06:20:51 |
Event | 2025-04-13 07:46:27 |
Escalate | 2024-09-12 06:23:37 |
Facility management | 2024-09-13 19:01:26 |
Facility manager | 2024-09-12 12:00:39 |
Fix | 2024-09-12 12:02:12 |
Building management | 2024-09-12 12:02:46 |
Business driven | 2025-06-09 07:43:52 |
Horizontal escalation | 2024-09-12 12:05:39 |
Human resource management | 2024-09-13 18:56:02 |
Incident call | 2025-05-26 09:10:07 |
Inside-out | 2024-09-12 12:13:15 |
Insourcing | 2025-06-09 11:06:37 |
Internal customer | 2024-09-12 12:14:54 |
Capacity | 2025-08-23 02:00:07 |
Customer | 2025-05-21 09:20:51 |
Line management | 2025-07-02 18:30:19 |
Configuration item | 2024-09-13 19:21:43 |
Management system | 2025-06-09 13:25:32 |
Non-functional characteristic | 2025-06-10 13:15:48 |
Operations coordinator | 2025-04-23 12:03:53 |
OPS calendar | 2025-04-03 08:03:49 |
Outside-in | 2024-09-13 18:38:01 |
Customer excellence | 2025-06-08 12:37:56 |
Portability | 2025-08-23 02:00:08 |
Portfolio | 2025-06-10 08:24:28 |
Priority | 2025-05-10 04:15:51 |
Production environment | 2024-09-13 06:06:45 |
Procedure | 2024-11-23 16:47:41 |
Process management | 2024-09-29 17:04:54 |
Realize | 2024-09-13 14:00:29 |
Repair | 2025-05-26 09:53:41 |
Reporting | 2025-05-26 09:51:40 |
Risk Management | 2025-06-09 11:03:55 |
Shadow service | 2025-06-10 12:34:39 |
Service excellence | 2024-09-13 14:13:41 |
Service catalog | 2025-05-26 19:24:15 |
Service lifecycle | 2025-04-23 11:56:30 |
Service manager | 2024-09-13 14:17:52 |
Service request | 2025-06-14 16:09:55 |
Skilled service desk | 2024-09-13 14:21:44 |
Solution team | 2025-05-26 19:58:37 |
Shift left | 2025-09-10 02:00:07 |
Supply chain | 2024-09-13 14:25:43 |
Availability management | 2025-06-10 07:30:54 |
Service driven | 2025-04-13 10:05:41 |
Provider | 2025-06-09 15:20:14 |
Employee | 2024-09-13 18:39:36 |
Performance | 2025-06-09 15:10:29 |
Customer driven | 2025-04-13 09:50:50 |
Incident | 2025-06-09 08:09:43 |
Function | 2025-03-24 06:13:09 |
Document | 2024-09-13 19:04:15 |
Configuration management database | 2024-09-13 19:18:49 |
Capacity manager | 2024-09-13 19:24:29 |
Availability manager | 2025-06-10 12:30:00 |
Facility | 2025-06-07 05:32:43 |
Supplier | 2024-10-20 14:01:09 |
Service provider | 2024-10-19 10:17:52 |
Service | 2024-11-05 14:36:05 |
Goods | 2025-06-09 07:45:03 |
Functioning | 2025-06-30 08:54:55 |
Functionality | 2024-09-29 17:13:19 |
Profile | 2025-05-21 09:19:09 |
Responsibility | 2025-08-26 02:00:16 |
Authority | 2025-09-18 02:00:09 |
Capacity management | 2024-09-19 09:13:08 |
Process-based organization | 2024-09-19 09:14:16 |
DevOps | 2024-09-19 09:15:16 |
Relationship management | 2024-09-19 09:18:12 |
Business process model and notation | 2024-11-02 15:42:14 |
Human resource | 2024-11-03 15:30:22 |
Management architecture | 2025-06-09 13:23:56 |
Antecedent | 2025-06-10 13:21:19 |
Architecture pattern | 2024-09-21 14:50:49 |
Problem | 2024-10-09 07:23:54 |
Attribute | 2024-11-05 14:56:16 |
Stakeholder | 2024-09-20 19:18:12 |
Call management | 2025-05-26 19:50:37 |
Change manager | 2024-10-09 07:40:59 |
Service management architecture | 2025-05-26 19:43:55 |
Process owner | 2024-09-29 17:06:07 |
Input | 2024-10-09 07:08:41 |
Outcome | 2025-06-09 06:57:59 |
Product | 2025-06-09 15:16:12 |
Service offering | 2025-05-26 19:45:10 |
Deployment | 2024-09-29 17:18:49 |
RACI table | 2024-09-29 17:22:23 |
Conformance | 2025-08-23 02:00:09 |
Acceptance | 2025-05-26 19:48:26 |
Coordinating organization | 2024-10-13 18:01:31 |
Sourcing cycle | 2024-10-09 07:04:55 |
Compliance | 2025-06-01 14:44:02 |
Chapter | 2025-06-09 11:11:25 |
Supplier manager | 2024-10-09 07:09:58 |
Service level | 2024-10-09 07:12:07 |
Skill | 2024-10-09 07:13:26 |
Service delivery coordination tool | 2024-10-19 11:03:34 |
Service-tree | 2024-10-09 07:15:42 |
Configuration manager | 2025-04-23 12:22:09 |
Configuration management | 2024-12-13 06:39:37 |
Agreed opening time | 2025-06-10 06:00:35 |
Critical success factor | 2025-07-02 17:17:04 |
Service agreement | 2024-10-19 10:51:07 |
Operational excellence | 2024-10-19 11:00:54 |
Organization | 2024-11-05 14:46:58 |
Contract coordinator | 2024-11-02 16:31:07 |
Culture | 2024-11-03 15:08:41 |
Party | 2024-11-08 15:23:24 |
Application form | 2024-11-06 09:17:18 |
Categorize | 2024-11-11 15:45:47 |
Goal | 2025-07-07 12:13:31 |
Objective | 2025-06-10 06:17:32 |
Staff | 2025-05-26 19:54:47 |
Likelihood | 2025-04-17 00:05:58 |
Urgency table | 2025-06-10 12:31:50 |
Priority table | 2025-06-09 15:14:58 |
Priority value table | 2025-05-10 04:30:04 |
Failure | 2025-06-10 05:56:05 |
Primary task | 2025-05-26 09:16:06 |
Line | 2025-04-23 11:54:05 |
Operations manager | 2025-06-07 05:23:40 |
Line manager | 2025-05-10 03:59:22 |
Recover | 2025-05-26 09:48:57 |
Economy of scale | 2025-06-10 12:33:29 |
Job matrix | 2025-05-26 09:23:39 |
Mitigate | 2025-06-09 13:32:42 |
Performance indicator | 2025-06-13 15:48:39 |
Prioritize | 2025-05-26 09:38:22 |
Program | 2025-07-02 18:28:48 |
Risk appetite | 2025-06-14 15:46:21 |
Secondary task | 2025-07-02 17:30:29 |
Service integrator | 2025-05-26 19:42:38 |
Acceptance criteria | 2025-05-26 19:51:57 |
Interaction | 2025-09-18 02:00:07 |
Functionality management | 2025-07-08 04:43:33 |
Building block | 2025-05-29 18:14:59 |
Likelihood table | 2025-09-10 02:00:06 |
Detection | 2025-06-09 06:44:30 |
Impact | 2025-06-05 14:42:35 |
Operational level agreement | 2025-06-05 15:00:11 |
Customer satisfaction | 2025-06-09 11:18:00 |
Key performance indicator | 2025-06-05 15:18:42 |
Quality | 2025-06-05 15:48:44 |
Matrix organization | 2025-06-05 16:08:24 |
Back office | 2025-06-08 11:47:22 |
Baseline | 2025-06-08 11:49:04 |
Budget control | 2025-06-08 11:53:45 |
Delivery | 2025-06-09 06:40:14 |
Downtime | 2025-06-09 06:45:51 |
End user | 2025-06-25 13:05:18 |
Framework | 2025-06-09 07:33:38 |
Customer intimacy | 2025-06-09 11:17:27 |
Solution time | 2025-06-09 11:20:26 |
Managed infrastructure | 2025-06-09 13:21:36 |
Management method | 2025-06-09 13:25:01 |
Monitoring | 2025-06-09 13:33:23 |
Reaction time | 2025-06-09 18:24:02 |
Centralized support | 2025-09-10 02:00:05 |
Process database | 2025-06-10 07:28:06 |
Matching | 2025-06-13 14:52:39 |
Service desk | 2025-06-14 16:02:17 |
Urgency | 2025-06-15 18:51:16 |
TAR | 2025-07-05 11:21:47 |
Method | 2025-06-24 20:34:45 |
Economy of scope | 2025-06-25 12:54:11 |
Monthly plan | 2025-07-02 17:24:37 |
Disaster recovery plan | 2025-07-02 17:33:02 |
Facility management information system | 2025-07-02 18:25:51 |
Process coordination | 2025-07-02 18:37:20 |
Reliability | 2025-08-23 02:00:10 |
Scalability | 2025-08-23 02:00:11 |
Capability | 2025-08-23 02:00:11 |
Strategy | 2025-09-18 10:40:40 |