- About AIS
- Getting Started
- Solutions
- Resources
- About AIS
- Team
- Innovation
- Posts
- Pricing Plans
- Terms & Conditions
- Privacy Policy & Disclosures
- Why Partner with AIS?
- Service Delivery
- Project Management
- Support Structure
- Relationship Management
- Service Level Objectives
- Service Request Escalation Procedure
- Solutions
-
- AIS Labs
- Office Phone VoIP
- NMS Monitoring
- SIEM Protection
- XDR Threat Detection
- AIS Managed Firewall
-
- Managed Services
- Helpdesk Services
- Endpoint Management
- Vendor Management
- IT Administrative Services
- IT Managed Services
-
- Consulting
- IT Project Management
- IT Escalation Support
- AV Solution Design
- IT Strategy & Planning
- Network Solution Design
- Resources
- Markets
- Use Cases
- Posts
- Insights
- Pricing
- FAQs
- Account Executive
- AV Installer
- Data Cabling Technician
- Full Stack Developer
- Low Voltage Wiring Installer
- PHP Developer
- Principal Consultant
- Senior Network Engineer
- Service Desk Tier One
- Careers
ITIL - Transition
2 minute read
Contact AISService Transition: delivery of services required by a business into live/operational use, and often encompasses the project side of IT rather than business as usual (BAU).
Service Transition Processes
1. Transition planning and support
Coordinate the resources to deploy a major Release within the predicted cost, time and quality estimates
2. Change management
Ensure that standardized methods and procedures are used for efficient handling of all changes.
Aims of Change Management:
Minimal disruption of services
Reduction in back-out activities
Economic use of resources involved in the change
Types of Change Management:
Standard Change
Normal Change
Urgent/Emergency Change
3. Service asset and configuration management
Maintain information about Configuration Items required to deliver an IT service, including their relationships
Key Processes:
Identification
Planning
Change control
Change management
Maintenance
4. Release and deployment management
Plan, schedule and control the movement of releases to test and live environments. The primary goal of Release Management is to ensure that the integrity of the live environment is protected and that the correct components are released.
Goals:
Planning the rollout of software
Controlling the distribution and installation of changes to IT systems
Designing and implementing procedures for the distribution and installation of changes to IT systems
Effectively communicating and managing expectations of the customer during the planning and rollout of new releases
5. Service validation and testing
Ensures deployed releases and resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
6. Change evaluation
Assess major Changes, like the introduction of a new service or a substantial change to an existing service, before those Changes are allowed to proceed to the next phase in their life cycle.
7. Knowledge management
Gather, analyze, store and share knowledge and information within an organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge.