Body
Congratulations on becoming a Service Owner! This guide explains what this role means, why it is critical to the university, and the tangible steps you will take to launch, monitor, and improve your service.
Service Management ensures the delivery of reliable and efficient services (both IT and non-IT) to our user community. At UD, TeamDynamix helps to automate, track, and report on repeatable processes that enable support teams to streamline service delivery. Service Management works best when each service has clear ownership, defined support processes, and measurable outcomes.
Contents
As a Service Owner, you play a central role in ensuring that your services support the university's mission. You are the primary point of accountability for your service’s performance and its value to students, faculty, and staff. You provide direction, prioritization, and oversight across the service lifecycle. Ownership clarity enables effective decision-making, strengthens alignment with institutional goals, and ensures that services are continuously improved to meet the evolving needs of the university community.
Your involvement as a service owner is important for several key reasons:
- Customer needs and expectations are consistently prioritized and reflected in both service design and delivery.
- Cross-functional collaboration is strengthened to reduce silos and enable a more seamless and integrated experience.
- Reliability, observability, and supportability are embedded throughout the service lifecycle, leading to improved operational performance.
- Institutional investments in Services translate into measurable value for students, faculty, and staff.
Contents
To be successful, you should familiarize yourself with these foundational ITSM (IT Service Management) concepts:
- Service: is a means of enabling value by facilitating outcomes that requestors want to achieve, without the requestor having to manage specific costs and risks.
- The Core Components of a Service:
- Value: The ultimate goal of the service. Value is co-created through an active relationship between the service provider and the service requestor.
- Outcome: The result the requestor wants to achieve (e.g., increased productivity, secure data).
- Costs & Risks: The provider, rather than the requestor, absorbs the management of infrastructure, personnel, and potential failures.
- Client Portal (TDClient): The customer-facing workspace within TeamDynamix designed for end-users, stakeholders, and executives. It is the interface to access Services, Knowledge Articles, and Project/Workspaces. All UD users can view this interface and the Client Portal can be accessed via this URL: https://services.udel.edu/
- Configuration Management Database (CMDB): A centralized repository used to store and manage Configuration Items (CIs) and assets, such as laptops, servers, software, and other technology components. It provides a structured inventory that enables these items to be organized, tracked, and referenced throughout their lifecycle.
- IT Service Management Team (ITSM): This team facilitates the creation and implementation of services, maintains the entire Service Catalog, and provides guidance to improve services and workflows. The ITSM Team also is the escalation point for the Service Owner and Service Manager.
- Operational Readiness: The state of being fully prepared to support and maintain a service throughout its lifecycle. This extends beyond technical configuration in TDX to include communicating changes (i.e. Change Log), user training/documentation, and strategic communication plans to ensure the service is sustainable and well understood by its audience.
- Service Catalog: A central repository that provides information about the services available to users and the organization. It serves as the authoritative source for service descriptions, request options, support details, and ownership information.
- Service Design Package: A comprehensive collection of documentation and procedures produced during the design phase to guide a service through its entire lifecycle.
- Service Page: A description webpage within TDX that lists information about your service and allows a customer to request the Service.
- Service Form: A customizable form in TDX used to collect information from customers when requesting a service. Forms can be tailored to meet specific business needs and may include dropdowns, radio buttons, text fields, date and people pickers, file attachments, and instructional text.
- Service Lifecycle: Every service moves through five phases: Strategy (alignment), Design (specifications), Transition (testing/deployment), Operation (maintenance), and Improvement (optimization).
- Service Manager: The operational leader responsible for the daily execution and delivery of a service to its users. This role focuses on managing technical teams, coordinating incidents and changes (first point of escalation), and maintaining service stability to ensure consistent performance and operational excellence.
- Service Owner: The strategic leader who is accountable for the overall success, value, and performance of a Service throughout its entire lifecycle. This role acts as the primary decision-maker, ensuring the service remains aligned with institutional goals while providing high-level direction on roadmaps, risk management, and major incidents.
- TeamDynamix (TDX): The university’s comprehensive IT Service Management (ITSM) platform used to automate and streamline service delivery. TDX serves as the central hub for the Service Catalog, request forms, and backend workflows, providing the necessary infrastructure for ticketing, reporting, and tracking service performance.
- TeamDynamix Production Environment: This is the live instance of TDX where all active work, ticket management, and client portal interactions occur. This is the primary environment for day-to-day operations.
- TeamDynamix Sandbox Environment: This is a separate, non-production copy of the TDX system used for testing and development. This environment allows technicians and administrators to build out new services, knowledge articles, and reports without affecting live data or visibility to end-users.
- TD Work Management (formerly TDNext): The technician-facing user interface within the TeamDynamix platform used to manage and fulfill service requests, manage projects, and create/run reports. Additional permissions are needed to access TD Work Management, which can be found via this URL: https://services.udel.edu/TDWorkManagement#. For more information, review the Using TeamDynamix articles.
- RACI: Responsibility assignment framework used in service management to clearly define who is involved in a task or decision.
- R: Responsible - The person who performs the work and completes the task.
- A: Accountable - The person who ultimately owns the outcome and has final approval authority.
- C: Consulted - Experts whose input is sought before decisions are made.
- I: Informed - People who need to be kept updated on progress or outcomes but are not directly involved in the work.
Contents
The Service Owner provides strategic direction and accountability for the service. The Service Manager typically focuses on daily execution, incident coordination, and operational stability. In short, the Service Owner focuses on the service’s purpose, value, priorities, and outcomes; the Service Manager focuses on how the service is delivered day to day.
Key Responsibilities: Design, Transition, Operation & Improvement
- You are the primary decision-maker and are accountable for the service’s overall success, value, performance, and improvement.
- You oversee the service’s budget, security, and compliance, ensuring it remains sustainable.
- You serve as a key contact for major incidents and outages.
Service Owner / Service Manager RACI
Activity
|
Service Owner
|
Service Manager
|
| Define Vision |
Accountable |
Consulted |
| Performance Monitoring |
Accountable |
Responsible |
| Day to Day Operations |
Informed |
Responsible |
| Budget |
Accountable |
Consulted |
| Continual Improvement |
Accountable |
Responsible |
Contents
Moving a service from an idea to a Production state typically takes 3-5 weeks. You will be expected to provide the following:
- Existing or proposed workflow (define what approvals, notifications, decisions, etc. should be included)
- Provide a link to your current workflow diagram or examples.
- Required and optional fields to be included on the form.
- Details to be included on the TDX Service Page (See the Student Laptop Loaner Request as an example of what to include):
- Who can use it?
- What is it?
- Where to get it?
- How to use it?
- What are the charges, options & fees?
- Related TDX KBs/KB drafts to link to the service
- Attachments that can used as supplementary resources
- Approvals that are needed to fulfill this service (if any)
- Details to include in the CMDB:
- Service Owner
- Service Manager
- Cross team dependencies that are needed (if any)
- Any applications used to fulfill the service
- Details you would like to be able to report on/track
- You will be provided basic reporting against your service
- Tasks assigned to me / Tasks assigned to my groups
- Open tickets assigned to my groups
- Open unassigned tickets
- Tickets requiring my approval
- Open tickets assigned to me
- Open tickets assigned to me that are “on hold”
- Open tickets assigned to my groups that are “on hold”
After you provide and discuss these details with the ITSM team, the team will develop the service in the TDX “Sandbox” instance. This non-Production version of TDX will allow you to review and test the service before it goes live. Your Sandbox signoff will be required before the service is pushed to production in TDX client portal.
Contents
Helpful Articles
Contents