OAAIS Incident Management

8/12/2019 OAAIS Incident Management

1/19

OAAISINCIDENT MANAGEMENT

PROCESS

VERSION 2.0, REV. 07/09/09

University of CaliforniaSan Francisco

Office of Academic and AdministrativeInformation Systems (OAAIS)


2/19

UCSF Internal Use Only 2 of 19 OAAIS Incident Mgmt 07-09-09.doc

UC FSOffice of Academic and Adminis trativeInformation Systems OAAIS Incident Management Process

TABLE OF CONTENTSTABLE OF CONTENTS ......................................................................................................................................................2

DOCUMENT VERSION CONTROL ...............................................................................................................................3 STAKEHOLDER TEAM .......................................................................................................................................................3

1. INTRODUCTION ....................................................................................................................................................4

1.1. PURPOSE ....................................................................................................................................................................4 1.2. SCOPE .........................................................................................................................................................................4 1.3. DEFINITION S .............................................................................................................................................................4

2. RESPONSIBILITIES ............................................................................................................................................4

2.1. CUSTOMER .................................................................................................................................................................4 2.2. S ERVICE DESK LEVEL 1 S UPPORT .......................................................................................................................4 2.3. OAAIS S UPPORT UNIT LEVEL 1 S UPPORT .........................................................................................................4

2.4. LEVEL 2 S UPPORT .....................................................................................................................................................5 2.5. LEVEL 3 S UPPORT .....................................................................................................................................................5 2.6. TICKET ASSIGNEE ......................................................................................................................................................5 2.7. INCIDENT MANAGER .................................................................................................................................................5

3. PROCESS DEFINITION ......................................................................................................................................6

3.1. PROCESS MAP ...........................................................................................................................................................6 3.2. A CTIVITY D IAGRAM S .................................................................................................................................................7

4. RACI CHART.................................................................................................................................................................10

5. ENTRY CRITERIA........................................................................................................................................................11

6. PROCEDURE ...........................................................................................................................................................11

7. EXIT CRITERIA ....................................................................................................................................................14

8. IMPACT, URGENCY AND PRIORITY .........................................................................................................15

9. INCIDENT MANAGEMENT SERVICE LEVELS ........................................................................................16

10. INCIDENT MANAGEMENT SERVICE METRICS ....................................................................................17

11. OAAIS SERVICE SUPPORT ............................................................................................................................17


3/19



DOCUMENT VERSION CONTROL

Document Name OAAIS Incident Management Process

Process Owner Rebecca Nguyen

Version Number

Issue Date Prepared By Reason for Change

1.0 8/6/07 Terrie Coleman First draft

1.1 1/25/08 Terrie Coleman Remove Ticket Owner Role, Urgency tableupdated, Removed point of contact reference

1.2 2/22/08 Terrie Coleman Updates to the Service Levels and ServiceMetrics Sections

2.0 7/9/09 Francine Sneddon Updated to reflect Remedy 7 changes.

STAKEHOLDER TEAMDepartment Name

Academic Research Systems (ARS) Michael Kamerick

Application Services (AS) Jane Wong

Business & Resource Management (BRM) Shahla Raissi

Customer Support Services (CSS) Rebecca Nguyen

Enterprise Information Security (EIS) Carl Tianen

Enterprise Network Services (ENS) Jeff Fritz

Information and Technology Services (ITS) Heidi Schmidt

This document contains confidential, proprietary information intended for internal use only and is not to be distributedoutside the University of California, San Francisco (UCSF) without an appropriate non-disclosure agreement in force. Itscontents may be changed at any time and create neither obligations on UCSFs part nor rights in any third person.


4/19



1. INTRODUCTION1.1. PURPOSE

The primary goal of the Incident Management process is to restore normal service operation as

quickly as possible and minimize the adverse impact on business operations, thus ensuring that thebest possible levels of service quality and availability are maintained. Normal service operation isdefined as service operation within service level agreement (SLA) limits.

The Incident Management process also handles Service Requests for standard services that areagreed to be provided under SLAs.

1.2. SCOPEThe scope of the Incident Management process includes a standard set of processes, procedures,responsibilities and metrics that are utilized by all OAAIS services, applications, systems andnetwork support teams.

1.3. DEFINITIONS

An i n c i d e n t is any event which is not part of the standard operation of a service and which causes,or may cause an interruption to, or a reduction in the quality of that service.

A s e r v i c e r e q u e s t is a request from a user for support, delivery, information, advice ordocumentation, not being a failure in the IT infrastructure. A Request for Change (RFC) isrequired for non-standard services that necessitate a change in the IT infrastructure and isaddressed through the Change Management process.

The Incident Management process includes Incident Acceptance and Recording, Classification andInitial Support, Matching, Investigation and Diagnosis, Resolution and Recovery, Closure, andProgress Monitoring and Reporting

2. RESPONSIBILITIES2.1. CUSTOMER

Identifies incident/request for service Confirms incident has been resolved

2.2. SERVICE DESK LEVEL 1 SUPPORT First point of contact for customers reporting service disruption or requesting service Responsible for recording, classifying, matching, routing, resolving (unless assigned to other

support groups) and closing incidents Monitors and tracks incidents Fulfills service requests Provide customer updates as required

2.3. OAAIS SUPPORT UNIT LEVEL 1 SUPPORT Identifies incident/request for service Responsible for recording, classifying, matching, and routing incidents Confirms incident has been resolved


5/19



2.4. LEVEL 2 SUPPORT Provides business/functional support Responsible for incident investigation, diagnosis and recovery within defined priorities Fulfills service requests Provide customer updates as required Escalates incidents as required

2.5. LEVEL 3 SUPPORT Provides technical support Responsible for incident investigation, diagnosis and recovery within defined priorities Fulfills service requests Provide customer updates as required

2.6. TICKET ASSIGNEE Ticket Ownership changes as ticket is reassigned The support person to whom the Incident Ticket (classified as User Service Request) has

been routed Responsible for resolving the incident

2.7. INCIDENT MANAGER Service Desk Manager responsible for monitoring & tracking incidents owned by the Service

Desk Support Unit Manager responsible for monitoring and tracking incidents owner by their team Monitors efficiency and effectiveness of the Incident Management process Generates Incident Management performance reports Makes recommendations for process improvement


6/19

UCSF Internal Use Only 6 of 19

UC FSOffice of Academic and Administ rativeInformation Systems OAA

3. PROCESS DEFINITION3.1. PROCESS MAP

Trigger: Disruption of service or service request

OAAIS Incident Management Process Map v1.0

Classify &Provide Initial

Support

Detect &Record

Incidents

Incident Management

ConductResolution &

Recovery

Monitor & Track Incidents

The Incident Management process is used to restore normal service operation as quickly aspossible and minimize the adverse impact on business operations, ensuring that the bestpossible levels of service quality and availability are maintained. The process is also utilized tomanage fulfillment of service requests.

Input:Incident reportService request

Investigate &DiagnoseIncidents

Close Incident

Supplier (provides input)

Customer OAAIS Support Unit

ServiceRequest

?

ManageService

Requests

No

Yes


7/19



3.2. ACTIVITY DIAGRAMS


8/19




9/19




10/19



4. RACI CHART

Step #

OAAIS Incident Management

Step Description C u s t o

m e r

S e r v i c

e D e s

k

O A A I

S S u p

p o r t

U n i t

L e v e l

2 S u p

p o r t

L e v e l

3 S u p

p o r t

I n c i d e

n t M a n

a g e r

OutputDetect & Record Incidents - Service Desk

1 Detect Incident A/R2 Contact Service Desk A/R I3 Type? A/R4 Open Incident Ticket A/R

4a Monitor & Track Incidents A/R

5 Assign: Impact, Urgency, Priority A/R6 Check Solutions Database A/R7 Assess CMDB (TBD) A/R8 Document Steps Taken A/R9 Resolve? A/R

10 Notify Customer (Requester) I A/R11 Valid? A/R I12 Follow Assignment Procedures A/R I

13 Detect Incident A/R14 Type? A/R15 Open Incident Ticket A/R

16 Assign: Impact, Urgency, Priority A/R17 Check Solutions Database A/R18 Assess CMDB (TBD) A/R19 Document Steps Taken A/R20 Follow Assignment Procedures A/R21 Support Group? A/R I I

22 Review & Triage Incident Ticket A/R22b Monitor & Track Incidents A/R

23 Resolve? I I I A/R24 Implement Solution & Resolved Incident I I I A/R25 Update Incident Ticket & Notify Customer I I I A/R26 Valid? A/R A/R I27 Update Incident Ticket & Escalate to Level 3 A/R I

28 Review & Triage Ticket A/R

29 Resolve? I I I A/R30 Implement Solution & Resolved Incident I I I A/R31 Update Incident Ticket and notify Customer

(Requester/Level 1)I I I A/R

32 Valid? A/R A/R I

33 Close Incident Ticket A/R A/R A/R

34 Generate Incident Report, including PerfomanceMetics

A/R

35 Evaluate Performance Metrics Against SLAs A/R36 Conduct Perfmance Review A/R37 Citical Issue? A/R

38 Open Incident Ticket (User Service Request) A/R A/R39 Fulfill Request? A/R A/R40 Complete? A/R I A/R41 Follow Assignment Procedures A/R A/R I I42 Review Request A/R A/R43 Fulfill Request I I A/R A/R44 Complete? A/R A/R I I45 Close Request A/R A/R A/R

Informed People who are significantly affected by the activity/decision and must be informed to ensure successful implementation

Conduct Resolution & Recovery - Level 3

Accountable The one who insures that desired outcomes are reached and has yes/no decision making authorityConsulted People who have critical expertise to contribute before a decision is made

Responsible People who do the work, facilitate it and/or organize it

Detect & Record Incidents - Service Desk

Classify & Provide Initial Support - Service Desk

Investigate & Diagnose Incidents - Level 2

Conduct Resolution & Recovery - Level 2

Detect & Record Incidents - OAAIS Support Unit

Classify & Provide Initial - OAAIS Support Unit

Investigate & Diagnose Incidents - Level 3

Close Incident

Monitor & Track Incidents

Manage Service Requests

Hand-off Change Management Process (TBD)

Hand-off Problem Management Process (TBD)


11/19



5. ENTRY CRITERIA Incident report Service request

6. PROCEDURE

ID Step Responsibility

Detect & Record Incidents Service Desk

1 Detect Incident or Need for Service

Identify a disruption of service or a need for a new service Customer

2 Contact Service DeskCustomer contacts the Service Desk to report a disruption in service or request service

Customer

3 Type?Incident go to step 4 / Service Request go to step 38

Service Desk

4 Open Incident Ticket (classified at User Service Request)Upon receiving a call (or request) from a Customer, the Service Desk Analyst enters theCustomer and incident information into Remedy

Service Desk

4a Monitor and Track Incidents

The Incident Manager is responsible for monitoring and tracking incident throughout theprocess - Go to step 22b

Incident Manager

Classify & Provide Initial Support Service Desk

5 Assign: Impact, Urgency, Priority

Using the impact, urgency, priority matrix determine and set the priority for the incident.Setting the priority begins the clock for the Service Level Agreement (SLA) associated withthat priority. At this point, Service Desk Analyst becomes the Ticket Owner.

Service Desk

6 Check Solutions DatabaseReview the Solutions database for known errors and solutions to similar incidents

Service Desk

7 Assess Configuration Management Database (CMDB) T B D Service Desk

8 Document Steps TakenUpdate the worklog in the Incident Ticket with all of the troubleshooting steps taken to resolvethe incident so far

Service Desk

9 Resolve?Yes go to step 10 / No go to step 12

Service Desk

10 Notify Customer Service Desk

11 Valid?Yes go to step 33 / No go to step 9

Customer

12 Follow Assignment Procedures

The Service Desk Analyst assigns the Incident ticket to Level 2 Support. At this stage theresponsibility for resolving the incident and communicating with the Customer passes to theassigned Support Analyst however, the responsibility for final customer contact and closure ofthe incident remains with the Service Desk Analyst.

Service Desk

Detect & Record Incidents OAAIS Support Unit

13 Detect Incident or Need for Service

Identify a disruption of service or a need for a new service OAAIS Support Unit

14 Type?

Incident go to step 15 / Service Request go to step 38 OAAIS Support Unit


12/19




15 Open Incident Ticket (classified as User Service Request)Open an Incident Ticket with all of the incident information. In the Case Type field, selectUser Service Request.

OAAIS Support Unit

Classify & Provide Initial Support OAAIS Support Unit

16 Assign: Impact, Urgency, Priority

Using the impact, urgency, priority matrix determine and set the priority for the incident.Setting the priority begins the clock for the Service Level Agreement (SLA) associated withthat priority. At this point, OAAIS Support Unit Analyst becomes the Ticket Assignee.

Notify the Service Desk if there is a disruption of service which will impact the Customer

OAAIS Support Unit

17 Check Solutions Database

Review the Solutions database for known errors and solutions to similar incidents OAAIS Support Unit

18 Assess Configuration Management Database (CMDB) T B D OAAIS Support Unit

19 Document Steps Taken

Update the worklog in the Incident Ticket (classified as User Service Request) with all of thetroubleshooting steps taken to resolve the incident so far

OAAIS Support Unit

20 Follow Assignment ProceduresSelect the appropriate support analyst from the assignment document and assign the incidentfor resolution. At this stage the responsibility for resolving the incident and communicatingwith the Customer passes to the assigned Support Analyst.

OAAIS Support Unit

21 Support Group?

Level 2 go to step 22 / Level 3 go to step 28

Business/Functional Incidents are assigned to Level 2 SupportTechnical Incidents are assigned to Level 3 Support

OAAIS Support Unit

Investigate and Diagnose Incidents Level 2

22 Review and Triage Incident Ticket

Review the escalated incident in order to understand the issue.

Consult the Problem Management Database for known errors. If necessary, contact theCustomer, OAAIS Support Unit or the Service Desk to gain further clarity of the incident.Begin diagnosis of the incident

Level 2 Support

22b Monitor and Track Incidents

The Incident Manager is responsible for monitoring and tracking incident throughout theprocess Go to step 34

Incident Manager

Conduct Resolution and Recovery Level 2

23 Resolve?Yes go to step 24 / No go to step 27

Determine if the incident can be resolved without making any system update and inform thecustomer of the solution. When the Level 2 Support Analysis is unable to resolve the incidentit is escalated to Level 3 Support.

Level 2 Support

24 Implement Solution and Resolve Incident

Resolve the incident by implementing the necessary solution. Level 2 Support

25 Update Incident Ticket and Notify Customer

Document the resolution in the Work Info tab area of the Incident Ticket and change thestatus of the Incident Ticket to Resolved. Contact the Customer with the solution to theincident

Level 2 Support


13/19




26 Valid?Yes go to step 33/ No go to step 23

Validate the resolution has corrected the incident.

Customer

OAAIS Support Unit

27 Update Incident Ticket and Escalate to Level 3Document the steps taken to diagnose/resolve the incident in the worklog of the IncidentTicket. When the Level 2 Support Analyst is unable to resolve the incident it is escalated toLevel 3 Support. At this stage the responsibility for resolving the incident and communicatingwith the Customer passes to the assigned Support Analyst.

Level 2 Support

Investigate and Diagnose Incidents Level 3

28 Review and Triage Incident TicketReview the escalated incident in order to understand the issue.

Consult the Problem Management Database for known errors. If necessary, contact theCustomer, OAAIS Support Unit or the Service Desk to gain further clarity of the incident.

Begin diagnosis of the incident

Level 3 Support

Conduct Resolution and Recovery Level 3

29 Resolve?

Yes go to step 30 / No hand-off to Change Management Process

The Level 3 Support Analyst determines if the incident can be resolved without making anysystem updates and informs the customer of the solution. If system updates are required theLevel 3 Support Analyst will initiate the Change Management process

Level 3 Support

30 Implement Solution and Resolve Incident

The Level 3 Support Analyst resolves the incident by implementing the necessary solution. Level 3 Support

31 Update Incident Ticket and Notify Customer

Document the resolution in the Resolution tab area of the Incident Ticket and change thestatus of the Incident Ticket to Resolved. Contact the Customer with the solution to theincident

Level 3 Support

32 Valid?Yes go to step 33 / No go to step 29

Validate the resolution has corrected the incident.

Customer

OAAIS Support Unit

Hand-off to Change Management Process TBD

Close Incident

33 Close Incident Ticket

The Ticket Assignee is responsible for closure of the Incident Ticket (classified as User ServiceRequest)

Service Desk

Level 2 Support

Level 3 Support

Monitor and Track Incidents

34 Generate Incident Report, including Performance Metrics Incident Manager

35 Evaluate Performance Metrics Against SLA Incident Manager

36 Conduct Performance Review Incident Manager

37 Critical Issue?

Yes go Hand off to Problem Management Process / No go to step 34 Incident Manager


14/19




Hand-off to Problem Management Process (TBD)

Manage Service Requests

38 Open Service RequestOpen an Incident Ticket with all of the required information. In the Case Type field, selectUser Service Request.

Service Desk

OAAIS Support Unit

39 Fulfill Service Request

Yes go to step 40 / No go to step 41 Service Desk

OAAIS Support Unit

40 Complete?Yes go to step 45 / No go to step 39

Customer

OAAIS Support Unit

41 Follow Assignment ProceduresSupport Analyst refers the request to the appropriate location

Service Desk

OAAIS Support Unit

42 Review Request Level 2 Support

Level 3 Support43 Fulfill Request Level 2 Support

Level 3 Support

44 Complete?

Yes go to step 45 / No go to step 43 Customer

OAAIS Support Unit

45 Close RequestThe Ticket Assignee is responsible for closure of the Incident Ticket (classified as User ServiceRequest)

Service Desk

Level 2 Support

Level 3 Support

7. EXIT CRITERIA Incident or Service Request has been resolved to customers satisfaction


15/19



8. IMPACT, URGENCY AND PRIORITYIncident priority is assigned when the Remedy Ticket is opened and is determined primarily on thebasis of urgency and impact.

The following tables are guidelines for establishing priority. Priorities are subject to be revised byhigher support levels.

IMPACT TABLE

RANK DESCRIPTION

1. Extensive/Widespread:

Entire department, floor,branch, line of business, orexternal customer affected.

2. Significant/Large:

Greater than 100 peopleaffected.

3. Moderate/Limited:

Between 2199 peopleaffected.

4. Minor/Localized:

Less than 20 people affected.

URGENCY TABLE

RANK DESCRIPTION

1. Critical: Impacts EnterpriseImpacts Multiple Business Units.

2. High:

Process stopped, customer cannot work System and/or serviceunavailable. No work aroundavailable.

3. Medium:

Process affected; certainfunctions are unavailable tocustomers.

System and/or service isdegraded. May or may not havework around available.

4. Low

Process affected; certainfunctions are unavailable tocustomers.

System and/or service.Inconvenienced but still available(Work, Excel, etc). Work aroundavailable.

Impact of the incident extent of the deviation from the normal service level, in terms of thenumber of users or business processes affected. Major incidents are those for which the degree ofimpact on the user community is extreme. Incidents for which the timescale of disruption (to evena relatively small percentage of users) becomes excessive may also be regarded as major.

Urgency of the incident the acceptable delay, to the user or business process, in solving theincident.

Incident priority may be adjusted when incidents are escalated to Level 2 or Level 3 support basedon further analysis of the issue and may also change over the life of the incident (i.e., affects moreusers or during critical periods). The Service Level Agreement clock will be reset whenever theincident priority is changed on the Remedy Ticket. When the priority of a ticket is changed, theincident owner is responsible for communicating the change to the customer.


16/19



9. INCIDENT MANAGEMENT SERVICE LEVELSThese Service Level definitions can be used as a general guideline to assist with theimplementation of Incident Management. Please refer to the OAAIS Service Catalog for ServiceLevel Agreements that contain Service Levels definitions developed for each specific line of service.

Incident Management Service Level

Priority DefinitionResponse Time Target Resolution

Critical Major incident that isaffecting a large groupof users or criticalbusiness processes.

Notice of the issue to relevant users andcommunication of the expected downtime musttake place within 1 hour

Plan for incident resolution must be developed andcommunicated within 2 hours

< 4 hours

High Significant incident thatis causing work to slow

or stop.

Response to the customer must take place within4 business hours

Plan for resolution must be developed andcommunicated within 8 business hours

< 12 hours

Medium Incidents that may beimpacting work but forwhich there is a work-around.


Plan for resolution must be developed andcommunicated within 48 business hours

< 10 business days

Low Incidents with lowimpact or where awork-around is easilyfollowed.


Plan for resolution will be communicated at thetime work begins

Planned

Escalation of an incident can take place at any time and at any support level in the resolutionprocess, as defined in the Service Level Agreement.

Functional escalation involving personnel with more specialist skills, time or accessprivileges to solve the incident.

Hierarchical escalation involving a higher level of organization authority, when it appearsthat the current level of authority is insufficient to ensure that the incident will be resolvedin time and/or satisfactorily.


17/19



10. INCIDENT MANAGEMENT SERVICE METRICSThese Service Metrics definitions are an interim guideline to assist with the implementation ofIncident Management. As The OAAIS Service Cataloged is defined, Service Level Agreementsoutlining the appropriate Service Metrics will be developed for each specific line of service.

Category Description Measure Target

IncidentResponse Time

The time it takes IT Servicesto acknowledge receipt of anincident and communicate aproblem resolution plan.Incident response time istracked by tier (1-3).

An incident must be acknowledged and an incidentresolution plan communicated within:

Critical: response = 1 hour / plan = 2 hours

High: response = 4 hours / plan = 8 hours

Medium: response = 24 hours / plan = 48 hours

Low: response = 24 hours / plan = when workbegins

Service Level ismet 90% of thetime.

IncidentResolution Time

The time that elapses betweenacknowledged receipt of an

incident and incidentresolution. When the incidentoccurs during scheduleddowntime, resolution timeswill start from the end ofdowntime.

Target resolution by priority:

Critical 4 hours High 8 hours Medium 10 days Low as planned

Extensions to expected resolution time must beagreed with the customer.

90% of allincidents are

resolved by thetarget resolutiontime.

ServiceAvailability

The time the service isavailable according to theservice hours specified in theservice level agreement.

Time a service was down in minutes. 99.5% averageavailability overthemeasurementperiod.

11. OAAIS SERVICE SUPPORT

Service Level 1 Level 2 Level 3

Auto Access OAAIS Service Desk ITS ITS

Effort Reporting System (ERS) AS Help Desk UCOP UCOP

Individual Identifier System (IID) OAAIS Service Desk ITS ITS

Payroll Personnel System (PPS) OAAIS Service Desk AS AS

Residents & Fellows System (RFS) OAAIS Service Desk AS AS

Desktop LAN Support (DLS) DLS CSS CSS

mail@UCSF OAAIS Service Desk CSS CSS

Copyright Enforcement EIS EIS EIS

Security Related Incident Response OAAIS Service Desk / EIS EIS EIS

SSL Certificates (Server) OAAIS Service Desk / EIS EIS EIS

Access Management (AM) ITS ITS ITS

Change Management (CM) ITS ITS ITS


18/19




Computer Operations (C0) ITS ITS ITS

Production Services (ProdSvcs) ITS ITS ITS

Accounts Fund Profile Program (AFP) AS Help Desk AS AS

Budget System Local (BSL) OAAIS Service Desk AS AS

Department System (DEP) AS Help Desk AS AS

PeopleSoft AS Help Desk AS AS

Student Financial Aid (SFA) OAAIS Service Desk AS AS

Campus Locator System (CLS) OAAIS Service Desk CSS ITS

Directory.ucsf.edu OAAIS Service Desk CSS CSS

Listserv OAAIS Service Desk CSS ITS

Online Pager Ordering OAAIS Service Desk CSS CSS

Remedy OAAIS Service Desk CSS CSS, AS

Webpage Hosting OAAIS Service Desk CSS ITS

Enterprise Desktop and Mobile Encryption OAAIS Service Desk / EIS EIS EIS

Intrusion Detection OAAIS Service Desk / EIS EIS EIS

Perimeter Security OAAIS Service Desk / EIS EIS EIS

Remote Access VPN OAAIS Service Desk / EIS EIS EIS

Security Support Professional (Viruses, Spam,Access Control)

OAAIS Service Desk / EIS EIS EIS

Infrastructure Services (IS) ITS ITS ITS

Computer Forensics OAAIS Service Desk / EIS EIS EIS

E-Discovery OAAIS Service Desk / EIS EIS EIS

External Security Review OAAIS Service Desk / EIS EIS EIS

Policy Compliance OAAIS Service Desk / EIS EIS EIS

Security Awareness, Training & Education OAAIS Service Desk / EIS EIS EIS

Systems Administration (SA) ITS ITS ITS

UCSF Campus Network Services OAAIS Service Desk OAAIS ENSNOFS NOCOAAIS ENS

NOFS/Vendor

UCSF Campus Voice ServicesOAAIS Service Desk OAAIS ENS

NOFS FieldServices

OAAIS ENSNOFS /AT&T


19/19



Database Administration (DBA) ITS ITS ITS

Ad Hoc Reporting OAAIS Service Desk ITS ITS

Data Warehouse (Cognos) OAAIS Service Desk ITS ITS

WebLinks Financials AS Help Desk AS ITS

WebLinks HR/PayrollAS Help Desk AS ITS

Date post:	03-Jun-2018
Category:	Documents
Upload:	missoum12
View:	217 times
Download:	0 times

OAAIS Incident Management

Documents