Page tree


Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
iconfalse

Before creating a ticket, have you checked the   Chatbot   ?

Chatbot checks the  Knowledge Base articles and  can help you to resolve your issue without raising a ticket.

Panel
borderColor#5495FC
bgColor#5495FC
titleColor#FFFFFF
titleBGColor#5495FC
borderStylesolid

We have different types of tickets in our DA&AI platform, in ServiceOne

Action Button
padding18px 18px 18px 18px
width300px
textIncident Request
urlhttps://wiki.solvay.com/display/IIDF/Incident+Request

Action Button
padding18px 18px 18px 18px
width300px
textEvolution/Change Request
urlhttps://wiki.solvay.com/pages/viewpage.action?pageId=894599719

Action Button
padding18px 18px 18px 18px
width300px
textService Request
urlhttps://wiki.solvay.com/display/IIDF/Service+Request

Action Button
padding18px 18px 18px 18px
width300px
textAccess Management Request
urlhttps://wiki.solvay.com/display/IIDF/Access+Management+Request

First, let's explain the difference between Incident and Evolution:


1. Open Service ONE

Image Added


2. Select the type of ticket you need


Image RemovedINCIDENT Request: You will create an incident

You will create an Incident

when the application is not working anymore or has an abnormal behavior, like missing data which used to be available in the past, very long response time, something which worked in the past and not anymore.

Image RemovedEVOLUTION Request: 



You will create an

evolution request

Evolution/Change Request in two situations:

  • When you have a  small change in something which already exists, without changing the current scope. For example, change some format in a report or dashboard, make available data in the report....
  • When  you need something new, even if it is
in
  • part of an existing application
 like to create or duplicate
  • (e.g. create a BW query, add a new KPI in a dashboard).
For this one, it
  • This is subject to validation under the TSA (Transactional Service Agreement) rules.
Please refer to this 


You will create a Service Request when you need any other kind of support from DA&AI platform.


You will create an Access Request when you need:

  • Access to a report or a given transaction in BW - "SAP Access Request"



  • Access to a dashboard in Qlik, Tableau, etc - "Corporate Dashboard Access Request Form"



  • Access to a specific tool,  like the technologies we use in DA&AI for data manipulation, processing or visualization - "Application Access Request (Generic)"


3. We will take care of it


  1. Your Service ONE request will generate a WO (work order) or INC (incident) in Helix, which will be automatically assigned to one of our DA&AI Helix Support Groups
  2. For each WO/INC, whenever there’s a change to do, DA&AI team will create a CRQ in Helix
    1. The CRQ should be created before the build starts
    2. The CRQ "
    3. The “Change Coordinator” should be the developer or PM. The “Change Manager” should be one of these “Contacts
communication to better understand.
  • You want to use an application which is not available today, or not running as usual, or the data has not refreshed correctly => This is an Incident
  • You want to change a calculation rule, or to add a new field in a report, or a new analysis axis in a dashboard => This is an Evolution | Small Enhancement (Change Request)
  • You want to promote your project in production, or receive advise on our technologies, or a new connection => This is a Service Request
  • You want to access a dashboard, or set of BW queries, or a Dataiku project => This is an Access Management Request