Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: Zache6495
New Today: 1
New Yesterday: 161
Overall: 131060

People Online:
Visitors: 57
Members: 5
Total: 62 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Service Acceptance Criteria
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Service Acceptance Criteria

 
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Service Delivery
View previous topic :: View next topic  
Author Message
Andy_S
Newbie
Newbie


Joined: Jul 20, 2006
Posts: 7
Location: East Midlands, UK

PostPosted: Fri Mar 27, 2009 10:38 pm    Post subject: Service Acceptance Criteria Reply with quote

I have just started a new job and have been asked to produce a Service Accetance Criteria for a new Service that the Service Management team need to take on and manage as Business as Usual (BAU). I guess we will need to make sure that all Monitoring is robust, Config items registered, Continuity plans in place etc, but just wondered if anyone had any experience of this type of document? I have done various ITIL related stuff but never actually had to produce an Acceptance Criteria, so any help would be gratefully received!
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3256
Location: London, UK

PostPosted: Fri Mar 27, 2009 10:51 pm    Post subject: Reply with quote

Andy

You nailed it

The document would be a checklist sort of document that says

in order to provide service
the following must be met

how it looks like etc depends on the creator
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
BorisBear
Senior Itiler


Joined: Mar 10, 2008
Posts: 402
Location: Sunderland

PostPosted: Mon Mar 30, 2009 9:13 pm    Post subject: Reply with quote

It needs to cover all of the things that you need to be able to effectively manage the service:

* Service Desk Fully briefed and supplied with appropriate information for their knowledge base.
* Defects no more than X amount.
* Demarcation of responsibility for technical groups.
* SLAs, OLAs and UCs signed off and in place.
* Appropriate comms issued to users
* Maintenance schedules in place.
* Operating instructions handed over to Ops Bridge.

The list can go on and on depending on your particular circumstances/requirements which to some extent may be shaped by previous experience of handover into production, often moreso by the bad experiences where the handover was inadequate.

To steal an answer from a fellow correspondent "It depends".
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Tue Mar 31, 2009 12:22 am    Post subject: Reply with quote

Hi,

put the thinking hat on. A lot of good information has been provided here. Think about what is needed in order for the service to supported and maintained through out its lifetime.

Ask yourself Who needs What information When and How will they get the information, Make sure that sufficient training and information has been handed over before the service goes live.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
nasz
Newbie
Newbie


Joined: Jun 18, 2007
Posts: 10
Location: Adelaide, South Australia

PostPosted: Thu Apr 15, 2010 10:05 am    Post subject: Reply with quote

The SAC should work in line with the project methodology to ensure Functional Requirements and Non Functional Requirements are met during the project lifecycle. Ideally, the project lifecycle will have "gated" stages (such as Requirements, Design, Build, Test, Deploy), these should have their own SAC against them to ensure compliance to the overall engagement model (the interface between the project lifecycle and service delivery).

The SAC should cover people, process and technology for the functional and non-functionals.

The aim of the SAC is to minimise the consequences of IT unavailability to the business by conducting service assurance.
Back to top
View user's profile Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> ITIL Service Delivery All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.