82,891
edits
Service catalog: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|devil| | {{a|devil| | ||
[[File:Argos catalog.jpg|450px|thumb|center|A [[service catalog]] yesterday. Argos recently got rid of them, interestingly.]] | [[File:Argos catalog.jpg|450px|thumb|center|A [[service catalog]] yesterday. Argos recently got rid of them, interestingly.]] | ||
}}A [[service catalog]], per someone’s lovingly curated original research on Wikipedia | }}A [[service catalog]], per someone’s lovingly curated original research on Wikipedia: | ||
: | :“''...the [[service catalog]] acts, at a minimum, as a digital registry and a means for highly distributed enterprises to see, find, invoke, and execute services regardless of where they exist in the world. This means that people in one part of the world can find and utilize the same services that people in other parts of the world use, eliminating the need to develop and support local services via a federated implementation model.Centralizing services also acts as a means of identifying service gaps and redundancies that can then be addressed by the enterprise to improve itself”<ref>In other words, by firing people.</ref> | ||
In other words, you write down everything each machine, system, application — or employee<ref>One of these kids is not like the others. One of these kids is not the same.</ref> — is meant to do. It is a way of atomising, articulating and mapping every function in the organisation, with a view to [[operationalisation|operationalising]] every role. | |||
This exercise will do two things: | |||
:(1) excite the [[middle manager|management]] layer who will regard it some kind of master key that unlocks all unrealised “[[redundancy|efficiencies]]”, and | |||
:(2) licence [[jobsworth|those at the coalface who are so disposed]], on loyal grounds of ''preserving the integrity of the control environment'', to decline any invitation to take action or responsibility not explicitly assigned to them in the catalog. | |||
A [[service catalog]], that is to say, is ''a jobsworth’s charter''. | |||
It is hard to fault this logic, should logic be your constant and only frame of reference. All my “services” cost something, and must be [[shredding|allocated]] back to a cost centre. The starting assumption must be that all valuable services have been catalogued and assigned to a particular group in the organisation. One should ''not'' carry out an uncatalogued service: it is either ([[Q.E.D.]])<ref>Ironic use of [[Q.E.D.]] here, by the way.</ref> unnecessary and as such unshreddible, or it ''is'' shreddible, but only because it is in someone ''else’s'' [[service catalog]] and therefore it is ''their'' problem, not yours. By all lights, going “off catalog” is [[waste]]ful at best and liable to trigger [[turf-war]]fare between [[risk controller]]s, all of which will be meat and drink to the censorious wagging fingers of your [[internal audit]] folk when they come to visit. Self-inflicted wounds, all. | It is hard to fault this logic, should logic be your constant and only frame of reference. All my “services” cost something, and must be [[shredding|allocated]] back to a cost centre. The starting assumption must be that all valuable services have been catalogued and assigned to a particular group in the organisation. One should ''not'' carry out an uncatalogued service: it is either ([[Q.E.D.]])<ref>Ironic use of [[Q.E.D.]] here, by the way.</ref> unnecessary and as such unshreddible, or it ''is'' shreddible, but only because it is in someone ''else’s'' [[service catalog]] and therefore it is ''their'' problem, not yours. By all lights, going “off catalog” is [[waste]]ful at best and liable to trigger [[turf-war]]fare between [[risk controller]]s, all of which will be meat and drink to the censorious wagging fingers of your [[internal audit]] folk when they come to visit. Self-inflicted wounds, all. | ||