WORKSHOP SLA SPECIFICATION BY ETIENNE WERY Lawyer at the Paris & Brussels Bar, Partner ULYS IT OUTSOURCING SUMMIT 27/11/2003.

Slides:



Advertisements
Similar presentations
EIDE System Requirements and Specification Documents
Advertisements

Demystifying IT Contracts Terri-Lynn Thayer Executive Director Computing and Information Services Brown University NERCOMP, March 2004 Copyright Terri-Lynn.
CONTRACT TEMPLATES FOR THE AGRO SECTOR. Objectives To understand the importance of contracts To be able to promote their use in the agro sector.
Ch-2 Proposals and Contracts. Introduction Many issues have to be handled in a contract and a proposal including legal concerns, commercial arrangements.
Cloud computing security related works in ITU-T SG17
SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.
MUNIS Platform Migration Project WELCOME. Agenda Introductions Tyler Cloud Overview Munis New Features Questions.
Introduction to Integrated Library Systems
Intellectual Property Rights Regulations in Russia: Case of Government-Supported R&D Irina Dezhina Leading Researcher, Ph.D. Institute for the Economy.
Basics of Software Licensing The Good, the Bad, and the Dull (but necessary…) Hannah Alphey, September 2010.
1 Vladimir Knežević Microsoft Software d.o.o.. 80% Održavanje 80% Održavanje 20% New Cost Reduction Keep Business Up & Running End User Productivity End.
Service Level Agreement Workshop Overview –Importance of Legal Review –Document Format –Master Services Agreements –Service Attachments –Short-Form Agreements.
Management of IT Environment (5) LS 2012/ Martin Sarnovský Department of Cybernetics and AI, FEI TU Košice ITIL:Service Design IT Services Management.
CLOUD COMPUTING AN OVERVIEW & QUALITY OF SERVICE Hamzeh Khazaei University of Manitoba Department of Computer Science Jan 28, 2010.
Uniqueness of user names is enforced Customer information logged to database Require contact information as well as address address will.
Health Informatics Series
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Greg Pierce| Concerto Cloud Services Which Cloud is Right for Microsoft CRM?
IT CONTRACTS Law & Regulations Thibault VERBIEST Attorney at the Paris & Brussels Bars, Founding Partner ULYS –
Enterprise Architecture
Know More. Do More. Spend Less. January 24, 2006 Monica Loomis, Senior Sales Consultant Oracle Contract Management.
© Copyright High Performance Concepts, Inc. 12 Criteria for Software Vendor Selection July 14, 2014 prepared by: Brian Savoie Vice President HIGH.
CIS 2200 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College.
CLOUD COMPUTING For Beginners.
Waterways Forward Partnership Agreement Delft, 12 February 2010 Kick-off meeting.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Contractors & contracts
CSI315 Web Applications and Technology Overview of Systems Development (342)
Overview OTL Mission Inventor Responsibility Stanford Royalty Sharing Disclosure Form Patent View Inventor Agreements Patent.
Marija KUHAR Merkur day - Naklo, 17. october 2003 Marija KUHAR Merkur day - Naklo, 17. october 2003.
CLOUD COMPUTING  IT is a service provider which provides information.  IT allows the employees to work remotely  IT is a on demand network access.
DIRC Workshop on Software Quality and the Legal System 13 February 2004, Gray's Inn, London LEGAL ASPECTS OF SOFTWARE PROCUREMENT Jos Dumortier University.
SLA of an Outsource Process - 1 Service Level Agreements (SLAs) of an Outsource Process Michael Day MBA 731 October 29, 2007.
1 Outsourcing: Managing the relationship Example: Reclining chair project FIGURE 12.1.
James Aiello PricewaterhouseCoopers Africa Utility Week 06 International Good Practice in Procurement.
Contracting and Negotiation DOQ-IT Education Session Contracting and Negotiations.
TG7 – Business models and SLAs BEinGRID - Legal Issues ICRI – K.U. Leuven Davide M. Parrilli
Custom Software Development Intellectual Property and Other Key Issues © 2006 Jeffrey W. Nelson and Iowa Department of Justice (Attach G)
ISO / IEC : 2012 Conformity assessment – Requirements for the operation of various types of bodies performing inspection.
Cloud Computing and the Public Sector Risks and Rewards John O’Connor, Partner - Head of Technology & Commercial Contracts.
RPA1 Standard Bidding Documents for the Supply and Installation of Information Systems General Conditions of Contract and Special Conditions of Contract.
By Nicole Rowland. What is Cloud Computing?  Cloud computing means that infrastructure, applications, and business processes can be delivered to you.
Project Management Methodology Development Stage.
European Commission - DG Research - Directorate B – “Structuring the European Research Area” Jean-David MALO – Bucharest, February 12-13, NOT LEGALLY.
Free Powerpoint Templates Page 1 Free Powerpoint Templates FP7 – Secure Enterprise Remote Banking System (SERBS) Small or medium scale focused research.
LEGAL ISSUES IN CLOUD COMPUTING
Adoption and Use of Electronic Medical Records (in Federally Qualified Health Centers) and Supporting an ASP Community Care Network of Virginia, Inc.
Eversheds Digital Banking Seminar Obtaining the right technology 30 September 2015 Eve England Principal Associate.
SAM-101 Standards and Evaluation. SAM-102 On security evaluations Users of secure systems need assurance that products they use are secure Users can:
Chapter 3 Pre-Incident Preparation Spring Incident Response & Computer Forensics.
Protecting your Managed Services Practice: Are you at Risk?
Understanding The Cloud
Service Design – purpose and processes
Platform as a Service (PaaS)
Vendor Statements of Work: Your Role as an IT Professional
VENDOR ON-BOARDING PROCESS
INTERCONNECTION GUIDELINES
Contract management beyond financial close
Introduction to the Federal Defense Acquisition Regulation
ITIL:Service Design IT Services Management Martin Sarnovský
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Service level Agreements
IS4680 Security Auditing for Compliance
e-Invoicing – e-Ordering 20/11/2008
Working With Cloud - 3.
EIDE System Requirements and Specification Documents
Neopay Practical Guides #2 PSD2 (Should I be worried?)
Presentation transcript:

WORKSHOP SLA SPECIFICATION BY ETIENNE WERY Lawyer at the Paris & Brussels Bar, Partner ULYS IT OUTSOURCING SUMMIT 27/11/2003

OVERVIEW OF WORKSHOP General theory about the SLA Duration 1/2hour SLA workshop Duration 1hour Workshop discussion and correction Duration 1/2hour Questions Duration 1/2 hour

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

DEFINITION OF THE SLA Service Level Agreements (SLA) are: An SLA is a legal contract that specifies the contractuable deliverables, terms and conditions between the service provider and the end-user The SLA is a formal, legally binding, statement of expectations and obligations between a service provider and its customer or customers

USE OF THE SLA AN SLA is used in outsourcing contracts An SLA answers to the following questions: Who delivers which service when? What happens if problems arise? What is the service and how is the service quality assessed? How to work changes into the SLA?

PURPOSES OF USING AN SLA Identifies and defines customer’s needs Provides a framework for understanding Simplifies complex issues Reduces areas of conflict Encourages dialog in the event of disputes Eliminates unrealistic expectations Plays as a marketing instrument Plays as a partnership instrument Transforms a “best effort obligation” into an “obligation of result”

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

An ASP is a company that delivers and manages applications and computer services to subscribers/clients via the Internet or a private network DEFINITION OF AN ASP Classical outsourcing ASP

ASP vs. CLASSICAL OUTSOURCING Transfer of personnel Higher level of maintenance Supplies mostly “standard applications” Hardware belongs to/hired by the ASP Hardware located at ASP

Customer ASPISV VAR IAPSI BO P …. ASP CHAIN

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

Customer ASPISV VAR IAPSI BO P …. ZONE OF INFLUENCE OF SLA Zone of influence of SLA

NETWORK SLA HOSTING SLA APPLICATION SLA SUPPORT SERVICE SLA SLA DOMAINS

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

ASPIC BEST PRACTICES Application service providers consortium (ASPIC) and World Intellectual Property Organization (WIPO) set up best practices: To build up good relationship between ISP and customer To avoid conflicts

ASPIC BEST PRACTICES (I/III) Infrastructure Data Center Server Load balancing Clustering Geographic Redundancy Connectivity Network architecture Scalability Connectivity Options Security Authentication Access Control Integrity Confidentiality Non-repudiation Security of Hardware Security of Software

ASPIC BEST PRACTICES (II/III) Application Application management Intellectual Rights Property Databases Pricing Application Preparation Sharing of liabilities Sharing of tasks Maintenance of the Application Maintenance Maintenance of the application Maintenance of the system Maintenance of the Network Reports Help-Desk

ASPIC BEST PRACTICES (III/III) Implementation Choice of application Preparation of the Platform Installation Configuration and Customisation Conversion / migration of data Reports Tests Integration Training of the customer

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

Main subjects to cover (I/III) 1. Introduction and purpose 2. Service to be delivered a) Uptime b) System response time c) Lost data d) Customization e) Change control f) Billing responses g) Report generation h) Other issues

Main subjects to cover (II/III) 3. Performance, tracking and reporting 4. Problem management 5. Fees and expenses 6. Customer duties and responsibilities 7. Warranties and remedies 8. Security

Main subjects to cover (III/III) 9. IPR and confidential information 10. Legal compliance and resolution of disputes 11. Termination 12. Examination of clauses- descriptions

SERVICE LEVELS Target level Minimum acceptable level Unacceptable level Bonus price Negotiated price Price reduction Contract termination Service level

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

MAJOR SLA FAILURES Negotiation problems Specification of efforts versus specification of results Unclear service specification Incomplete service specification Incomplete cost management « Dead-end » SLA documents Exit Management

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

WORKSHOP (I/II) Aim of the workshop Identify major problems when writing an SLA On service provided On service levels based on the organisation’s specificity Costs How to handle major issues

WORKSHOP (II/II) Workshop process Divide audience in 3 groups, each group represents a major SLA party Customer Service provider Parallel service provider Each group will react towards different given clauses Analyse clauses and try to find major issues about the SLA

CLASSIFY MAJOR ISSUES SLA failures Negotiation problems Efforts vs. Results Unclear service specification Incomplete service specification Incomplete cost management “Dead-end” SLA Exit Management

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

LESSONS LEARNED Does your SLA include: A specified level of customer support? Provisions for system and data security? A guaranteed level of system performance such as sub-second response time? Continuous system availability? In case of failure to deliver, is there a designated contact person who can address the issue? Enforcement procedure? Refund? Termination and choice of new ASP without penalty?

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

SLA SPECIFICATION: CHALLENGES Scope and Methodology Pre-understanding Service level management & service process management Knowing the actors and following a structured approach

TABLE OF CONTENT General concepts about the SLA General concepts about the ASP The SLA inside an ASP Writing of an SLA ASPIC best practices Main subjects to cover SLA failures Workshop Lessons learned SLA specification : Challenges Questions

QUESTIONS I would be pleased to answer your questions