21

Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level
Page 2: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Premium Support ModelCollaborative Support Execution

‘Roadshow’

Paul EmhovickCustomer Services Director

Page 3: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Premium Support ModelKey Elements for improved successKey Elements for improved success

•Well formed Service Requests–Business Case is clearly articulated

–Severity Level accurately reflects the level of urgency for the issue logged

–Supporting data (e.g. diagnostics) is provided

• SR (Case) Monitoring !!! (Be attentive to changes in status; need for action)

–Rapid responses maintain resource continuity to work issue

–Quality and Quantity of communication is significant when engaging virtual teams

–Make every effort to minimize ‘tag’ or ‘pinging’

• Effective Escalation (review criticality)

–Support (Support not Development is ‘Front Line’ … start w/ Duty Manager)

• Single Issue – Single SR– Facilitates better resource focus, enables better tracking and cleaner metrics

Page 4: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

• Act on Oracle Recommendations when Critical Downs• Keeps the SR at the right level of attention within Support• Facilitates faster resolution• Get it out of the “CUS” status as fast as possible

• Leverage ‘Self Service’ Standard Support Model

- Be self sufficient on SR handling procedures and Escalation procedures

- Communicate your priorities – be complete and thorough

Premium Support ModelCritical Success FactorsCritical Success Factors

Page 5: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SR MgtSR Mgt Audit SRs,

Bugs, &Alert Status

ESCALATE?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process Flow

Leverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)

Customer

Page 6: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Customer management engaged as necessary to progress/escalate SR activity. Customer management helps coordinate and participate as appropriate in periodic SR activity reviews – drive customer action to improve procedure and ensure governance of customer action in adherence with collaborative incident management process. Customer Management (incl executive layer) are engaged as part of SR escalation to their corresponding management level at Oracle e.g. Dir to Dir, VP to VP, etc.

Customer – Management

Customer resource that logs the SR via Metalink. The SR owner will collate all background information related to the issue, document the issue clearly in the SR, and provide business/revenue/project impact summary. Provides additional supporting documents on architecture/environment as required, and uploads diagnostics (RDA, ACT, trace files, dump files, etc). Works on recommended action plan and communicates in a timely manner with Oracle Support. Provides test cases as required to Support. Participates in OWC sessions and conference calls with Oracle Support. Downloads and applies recommended patches and ex ecutes the customer side of the action plan.This person is also responsible for ensuring that the SR is at the right severity level. Responsible for escalating to the Oracle Support Duty Manager in conjunction with the Customer SR management representative.This person retains ownership of the issue until SR closure and is the point person for the Oracle Support analyst for the duration of the SR.

Customer - SR owner

Key Roles Key Roles Incident Management Process Flow

Page 7: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Distinct product development organizations that control source code and participate in the incident management process to resolve product issues and SRs. Product Group involvement is key to addressing bugged issues and enhancement requests which have not been addressed via traditional Dev. led User Group or CAB activities.

PRODUCTGROUP(s) - Apps and Tech

Server Technology product development organization that provides bug response and resolution as identified by the Support BDE organization. This group does NOT work on enhancement requests and is solely reactive, functioning as a true product maintenance organization.

DDR ( Diagnostics andDefect Resolution) –

Technology

Support group that diagnoses and packages ‘bugged’ product issues to facilitate resolution assistance by product development. This group works on BUGGED service requests and issues only.

BDE (BUG DIAGNOSIS& ESCALATION)

Support resource that coordinates the activities of multiple Support Analysts by product area and geography. The Duty Manager is the 1st point of escalation in the incident management process given their familiarity with the issue problem area, related Products and respective queue(s). The Duty Manager works with the Support Analyst owning the SR to review any escalation request, and with the customer to develop an action plan to resolve.

DUTYMANAGER

Applications product development group that coordinates applications-based service requests AND/or enhancement request activities across the multiple applications development groups. Unlike DDR, this development organization does NOT function as a product maintenance group; but rather serves as a conduit into the applications development organization as an advocate for key Oracle customers.

APPS Triage - Applications

Support resource that works a queue of customer issues in a variety of statuses to provide resolutions and/or workarounds. The Support Analyst maintains ownership of an SR (excl. enhancement requests), throughout the incident management process and uses defined diagnostic methodology to work issues as prioritized by severity & priority.

SUPPORT ANALYST

Key RolesKey RolesIncident Management Process Flow

Page 8: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Oracle

Oracle

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Incident Management HiHi--Level Process FlowLevel Process Flow

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

CreateService Request

(SR) = TAR

Sev1 or 2

?

?Enhancement

Request

Action TBDby escalation

ESC

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

AlertSEM

ESCALATE?

ProductIssue

Go To ESC

Leverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

Track& Report

Close SR(EngageProductGroup)

Clearly documenting vital pieces of information in the SR will enable the Support Analyst to more effectively prioritize & work the SR. ØClear explanation of the problem (incl. exact error

messages, logs (alert logs from previous DB start) , traces, dumps, screen shots and anyadditional relevant data – RDA.

ØExplanation of the steps taken to troubleshoot theproblem and the findings (exact times).

ØReplication steps to reproduce the problem.

ØBusiness Impact of this issue

PrepareIssueData

Customer

Page 9: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

Sev1 or 2

?

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

AlertSEM

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)

ØSelect the correct CSI (Customer Support Identifier) number.

ØThe SR creation process entails a series of questions and RFIs. Take time and select the best available issue type template.

ØIf SR is Severity 1 provide key contact info (Mgt) to progress issue. Alert Mgt.

ØSingle issue single SR.

ØConsider requesting Oracle Web Conferencing (OWC) session to facilitate better understanding of issue.

ØEngage Oracle as soon as appropriate in customer activities to resolve the issue (e.g. conference calls, meetings).

[Reminder: MetaLink has extensive knowledge base – 55% of

CreateService Request

(SR) = TARCustomer

Page 10: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Key ‘Take Aways’Handling SRs based on severityHandling SRs based on severity

• Severity 1 SRs will be assigned immediately to the first available analyst and worked 24X7, provided the SR is entered in English. SR will be handed off as analyst shifts required and as highlighted. Requires 24X7 customer contacts availability.

• Severity 1 SRs which are not entered in English, and SRs of all other severities (2, 3 & 4), will be assigned and worked to a support analyst during normal business hours in owning country.

Page 11: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Use MetaLink to log SRs for all Severities

No loss of service or resources

Minor loss of service or resources

Severe loss of service or resources w/o acceptable workaround

Complete loss of service or resources and work cannot reasonably continue - the work is considered “mission critical”

Service Request (SR)Severity DefinitionsSeverity Definitions

Page 12: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sev

Level

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ProductIssue

Go To

ESC

Incident Management HiHi--Level Process FlowLevel Process Flow

Leverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)

ØProficiency in Duty Manager escalation is essential. The standard support model is self service.

ØNegotiate Action plan with Duty Manager. Once action plan is completed, escalation is closed.

ØA well defined BUSINESS CASE IS CRUCIAL to escalation as it allows Oracle management to effectively and promptly assign or predispose resources to resolve the issue. Incl. impact of issue (milestones, dates and cost impact if implementation project)

ØOracle Standard Product Support is a self service modelself service model and requires YOU to escalate issue and bring SR to the Duty Manager’s attention in a timely manner --allowing Oracle adequate time to respond.

Routinely escalating non-critical issues or consistently overstating the criticality of escalated SR may result in a misunderstanding of the importance or critical impact of a future escalation. Prudent use of the escalation routine enables Oracle to accurately prioritize your critical issue.

ESCALATE?

Customer

Page 13: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Escalating Service Requests• Escalating an issue means bringing management attention to the SR

• When to escalate- Key/critical milestone at risk … significant business impact - Need to communicate business issues to Support/Dev management- Unhappy with the response or speed of response from Oracle

•Effective escalation:- As appropriate i.e. earlier is better- Mgmt layers ‘aligned’ as engagedOracle/Customer e.g. Dir to Dir, VP to VP

- Adhere to process, no ‘end arounds’(Support Mgmt coordinates forOracle X-LOB)

Support Engineer

Manager /Escalation Manager

Senior Manager or Director

V.P. or Executive

Customer

Page 14: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sevlevel

?Enhancement

Request

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)When the Duty Manager contacts you, tell the manager what action(s)

you need to be taken on your SR - review the issue in detail, including the business impact, and provide relevant contact(s).

Before you hang up, get the Duty Manager’s name; make sure youunderstand the next steps (action plan), who owns them and the timeframes (if appropriate) for next steps to be completed. Ask to have the action plan documented in the SR

Once the action plan is completed the escalations is complete.

Action TBDby escalation

Customer

Page 15: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sevlevel

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)

MONITOR THE SERVICE REQUEST … be attentive to changes in status, the need for customer actionØProvide all error codes, logs, traces, dumps, screen shots

and any additional relevant data – All occurrances

ØConsider requesting Oracle Web Conferencing (OWC)

session to affect teaming to progress activity to resolvethe issue.

ProvideAssistance

or Data

Customer

Page 16: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sevlevel

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support = self service.A

Track& Report

Close SR(EngageProductGroup)

MONITOR THE SERVICE REQUEST … analysts work multiple SRs; rapid responses maintain resource continuity to work the issue

ØDocumentation is essential – answer all questions and record action plans

after each update with clear ownership of activities/tasks

ØQuality and quantity of communication is significant – make every effort to

minimize SR ‘tag’ or ‘pinging’

ØIssues are commingled with those of other customers in the standard

support SR stream, as prioritized by severity & priority

ØGCS does not provide RCA

WorkSR

(Update MetaLink)

Customer

Page 17: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sevlevel

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt ESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customerl Owned Process – ‘Standard Support’ = self service.A

Track& Report

Close SR(EngageProductGroup)

Audit SRs,Bugs, &

Alert Status

ØThe routine monitoring of higher severity SRs and key issues provides additional focus on Customer issues

ØStay ‘up to date’ with alert status will promote action in advance of product de-support notices

Customer

Page 18: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

Close S

R (U

pdate MetaLink)

SUPPORTANALYST

DUTYMANAGER

BDE(BUG DIAGNOSIS& ESCALATION)

APPS Triage - Applications

DDR ( Diagnostics andDefect Resolution) - Technology

PRODUCTGROUP(s)

SR Mgt

PrepareIssueData

CreateService Request

(SR) = TAR

Sevlevel

?Enhancement

Request

Action TBDby escalation

ESCOrac

leOrac

le

Support

Support

Oracle

Oracle

Product

Product

Dev.Dev.

SRSRMgtMgt

Audit SRs,Bugs, &

Alert StatusESCALATE

?

Work S

R (U

pdate MetaLink)

ProvideAssistance

or Data

Needassist.or data

?

ProvideCustomer

Input or Data

WorkSR

(Update MetaLink)

SRResolved

?

ESC

RequestAssistance

?

BUG?

EngageProd Dev

?

EngageProductGroup

?

ESCALATE?

ProductIssue

Go To ESC

Incident Management HiHi--Level Process FlowLevel Process FlowLeverage OWC to Work SR

Leverage OWC to Work Issue/SR

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NoNo

No

No

No

No

No

No

No

?Enhancement

RequestYes

No

A

B

B = Oracle controlled escalation.= Oracle IM Process.= Customer Owned Process – ‘Standard Support’ = self service.A

Close SR(EngageProductGroup)

ØTracking and reporting raises the level of management awareness to customer product issues

Track& Report

Customer

Page 19: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

MetaLinkSupport Tools

http://http://www.oracle.com/support/seminars.htmlwww.oracle.com/support/seminars.html•• Working Effectively with SupportWorking Effectively with Support

Learn how to save time and work effectively with Support be it; Learn how to save time and work effectively with Support be it; Oracle, PeopleSoft, JD Oracle, PeopleSoft, JD Edwards or Siebel support. Obtain details on leveraging your supEdwards or Siebel support. Obtain details on leveraging your support investment and port investment and customer best practices. Understand support terminology, tools, customer best practices. Understand support terminology, tools, and the escalation process.and the escalation process.

•• Introduction to MetaLink or Customer ConnectionIntroduction to MetaLink or Customer ConnectionAttend a live demo showing the various features available withinAttend a live demo showing the various features available within these separate Support these separate Support Portals for our Oracle, PeopleSoft, JD Edwards and Siebel customPortals for our Oracle, PeopleSoft, JD Edwards and Siebel customers. Learn how to log a ers. Learn how to log a Service Request (SR) and how to have a SR, a patch or other impoService Request (SR) and how to have a SR, a patch or other important news item sent to rtant news item sent to you automatically by email.you automatically by email.

•• Advanced MetaLink or Customer ConnectionAdvanced MetaLink or Customer ConnectionAttend our Advanced Seminars and learn from the experts how to eAttend our Advanced Seminars and learn from the experts how to exploit the Search and xploit the Search and Advanced Search functions, how to use the Knowledge Browser/BaseAdvanced Search functions, how to use the Knowledge Browser/Base, how the Administrator , how the Administrator functions work, and much more.functions work, and much more.

•• MetaLink: Software Configuration ManagerMetaLink: Software Configuration ManagerThis seminar helps you learn how to use the Software ConfiguratiThis seminar helps you learn how to use the Software Configuration Manager effectively to on Manager effectively to create and manage configurations, manage projects around those ccreate and manage configurations, manage projects around those configurations, run onfigurations, run HealthChecksHealthChecks, and save time logging and resolving Service Requests. , and save time logging and resolving Service Requests.

Page 20: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level

MetaLinkSupport Tools

http://http://www.oracle.com/support/seminars.htmlwww.oracle.com/support/seminars.html• Support Diagnostic for E-Business Suite 11i

This seminar will give you an opportunity to learn all the details about Support Diagnostics for E-Business Suite 11i, including a live demonstration using real examples. This 90-minute seminar is directed towards E-Business Suite 11i users who log Service Requests with Support and DBA's who will be installing and maintaining Support Diagnostics.

• Maintenance WizardThe Maintenance Wizard guides you through the maintenance and upgrade processes. The tool presents maintenance and upgrades as step-by-step processes; enables validation of each step, tracks the completion of the step, and maintains a log and status; is a multi-user tool that enables the system administrator to give different users assignments based on any combination of category, product family, or task level; automatically installs many required patches for you; and provides project management utilities to record the time taken for each task, completion status and project reporting.

• Advanced Support Tools—DB Specific and DB/Apps SpecificGet the most out of MetaLink's advanced proactive tools and resources, including personalization through My Headlines, search tips and techniques, the Knowledge Browser, and Software Configuration Manager. Learn how to use proactive tools such as the Remote Diagnostic Agent (RDA), the Ora-600 Lookup Utility, Install Healthchecks, and a menu of over 300 SQL Scripts. Also covers Support Diagnostics and a section on best practices when working with Oracle Support and how to use the Escalation process. (Note: DB-specific sessions focus only on the relevant proactive DB tools, while the Apps/DB sessions cover all available tools related to both the DB and the e-Business Applications Suite.)

Page 21: Premium Support Model - GUORS · Premium Support Model Key Elements for improved success •Well formed Service Requests –Business Case is clearly articulated –Severity Level