1 / 37

Service Level Agreement(s)

Service Level Agreement(s). Agenda. Starting points Content SLA1, 2 and 3 Acceptance procedure Impact Approval Next steps. Starting points. Sector commitment From SLA to Convention Based on consensus model Based on experiences Other solutions were possible Aimed at sound balance

coby
Download Presentation

Service Level Agreement(s)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Level Agreement(s)

  2. Agenda • Starting points • Content SLA1, 2 and 3 • Acceptance procedure • Impact • Approval • Next steps

  3. Starting points • Sector commitment • From SLA to Convention • Based on consensus model • Based on experiences • Other solutions were possible • Aimed at sound balance • Open for completion

  4. From SLA to Convention 1 2 3 Convention SLA

  5. Starting points • Sector commitment • From SLA to Convention • Based on consensus model • Based on experiences • Other solutions were possible • Aimed at sound balance • Open for completion

  6. Consensus L'obtention du consensus, qui nécessite l'élimination des objections importantes, est un principe fondamental des procédures et une condition nécessaire pour lapréparation de Normes (internationales) qui soient acceptées et largement utilisées.[ISO Directives, Part 1]

  7. Consensus Accord général caractérisé par l'absence d'opposition ferme à l'encontre de l'essentiel du sujet émanant d'une partie importante des intérêts en jeu et par un processus de recherche de prise en considération des vues de toutes les parties concernées et de rapprochement des positions divergentes éventuelles. Le consensus n'implique pas nécessairement l'unanimité. [ISO Directives, Part 1]

  8. Starting points • Sector commitment • From SLA to Convention • Based on consensus model • Based on experiences • Other solutions were possible • Aimed at sound balance • Open for completion

  9. Definition Need for data element or value SLA 1 Recording and publication in TELEBIB2 SLA 2 Standard messages SLA 3 In use in company’s and broker’s applications

  10. Coherence between SLAs

  11. Coherence between SLAs

  12. Coherence between SLAs

  13. Coherence between SLAs

  14. Coherence between SLAs

  15. Coherence between SLAs

  16. SLA1 • Description du service • Qui peut formuler une demande • Types de demandes • Procédures de demande • Traitement des demandes • Acceptation sectorielle

  17. SLA2 • Qui peut formuler une demande • Traitement des demandes • Traitement des MCIs en status 0 • Traitement des MCIs en status 1 • Acceptation sectorielle • Traduction en syntaxe

  18. Definition • Message Content Inventory (MCI) : L’inventaire des données échangées qui supporte une fonction bien spécifique de l’assurance. Une fonction est déterminée par la combinaison d’un objet, d’une action et d’un domaine tels que définis dans le TELEBIB2. Le MCI est indépendant des syntaxes d’échange.

  19. Standardisation WP Status 0 Status 1 Status 2 MCI Development Pre-implementation Analysis Preparation Implementation TELEBIB2 Centre Project group Commited user & Project group Commited user MCI Request SLA2

  20. SLA3 • Définition des paramètres • Traitement des releases • Composition • Publication • Acceptation • Implementation • Validation et certification • Maintenance

  21. Definition • Release : C’est l’inventaire des MCI’s implémentés ou à implémenter avant une certaine date (la date de release) Le release est identifié par le mois (année-mois) à partir duquel le release est estimé à être en usage.

  22. Cut-off date Release date Release date Implementation period Release period 2003 2 0 0 4 2005 Production start date(s) Production start period Compatibility assurance period Earliest production start date SLA3

  23. Approval procedure 10.02.2004 CP 26.02.2004 GOC 3 4 23.01.2004 ICT Managers 14.01.2004 Standardisation Working party 2 1 13.01.2004 SLA project group

  24. Impact • On • Standardisation Working Party • Workload • Organisation • TELEBIB2 Center • Workload • Things to develop • Users

  25. Standardisation WP • SLA1 • Handle QC requests • Create and manage QC project groups • SLA2 • Handle MCI related requests • Create and manage MCI project groups • Assign statusses • SLA3 • Fix, manage parameters • Define content of releases Workload

  26. Standardisation WP GOC Organisation Standardisation Working party MCI PG Contract Life Cycle PG Naming PG Guarantee Definition PG

  27. TELEBIB2 Center • SLA1 • Process downward compatible requests • Prepare QC project group meetings • Process results of QC project group meetings • SLA2 • Collect MCI related requests • Prepare MCI related requests for handling by the Standardisation WP. • Publish MCI in various statusses • Translate and publish MCIs into syntaxes Workload

  28. TELEBIB2 Center • SLA3 • Publish releases Workload

  29. TELEBIB2 Center • MCI related request form • MCI list • Release list • Adapt and expand the TELEBIB2 web site Things to develop

  30. Users • p.m.

  31. Next steps • Formal acceptance • Implementation • Migration • Publication & Information

  32. Formal acceptance • Final documents • Legal approval • Signature

  33. Implementation • Empowerment of the Standardisation Working Party. • Definition of the parameters for SLA3 by the Standardisation Working Party. • Development of supporting features in the TELEBIB2 Centre.

  34. Implementation • Start pilot “Relevé de Portefeuille” • Letter • Simulations • Release plan • MCI development and implementation plan

  35. Migration • Examine the need • Possible approaches • If necessary : plan the migration of the existing components (MIGs) to the environment as defined in the SLAs (MCIs).

  36. Publication & Information • Publication on the TELEBIB2 web site. • Organisation of information session(s).

  37. Credits • To the project editor • To the project group members • To occasional contributors

More Related