Kathy

 

There will be many opinions on this, so I would suggest you analyse from a
different angle. You need to consider:

 

1.       Reporting Requirements

2.       Service Level Agreements

3.       Routing Rules

4.       Approval Rules

5.       Task categorisations

6.       Resolution Categorisation

7.       Categorisations for incident vs Change vs Problem vs etc

8.       Multi tenancy of all the above (if applicable)

9.       Maintaining all of the rules above

 

Once you understand that, it'll help drive how the Categorisations need to
be set up.

 

To answer your questions specifically:

 

1.       The advantage of Model 2 is the flexibility you can use to create
Products AND operational Categorisations. Remember with op Cats none of the
tiers are mandatory (common customisation though) so an end user can select
0, 1, 2 or all 3 tiers.

2.       No but if you do combine them consider how you would implement CMDB
in the future and thus have to rework your categorisations.

 

Personally I find your second option the best, a very high level descriptor
(Failure) followed by a second describing the area (Performance) followed by
a layer of extra granularity (Connectivity) for example. 

 

Matt

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Kathy Morris
Sent: 18 March 2010 9:39 PM
To: [email protected]
Subject: Operational and Product Categorization

 

** 

Hello,

 

We are trying to figure an approach for operational and product
categorizations:

 

A technical write-up suggested the following for Operational
Categorizations:

 

Model #1

Tier 1:  install (verb)

Tier:2:  Telecommunication (service) Software

Tier 3:  Voicemail (CMDB Asset)

 

I remember reading that there was some value in having the CMDB asset on
Tier 3.

 

Model #2 option was:

request

network

create account

 

With Model #2, the CMDB asset is not listed, and we would need to combine
the Ops with the product categorizations in order to capture the asset.
What are the advantages of one option over the other? 

 

Is there any loss if we just use the Operational categorizations?  Are these
6 fields (Ops and Prod categories) mandatory usually? or are just the Ops
normally required fields?

 

I am building the service catalog to start building Operational
Categorizations.  Does anyone have any recommendations; lessons learned.
This is painful.  I have a team that just wants to map the CTI's  into the
Operational Categorizations.

 

 

 

 

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers
Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to