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: | ||
{{g}}A [[service catalog]], per someone’s lovingly curated original research on Wikipedia, is: | {{g}}A [[service catalog]], per someone’s lovingly curated original research on Wikipedia, is: | ||
:“..a means of centralizing all services that are important to the [[stakeholder|stakeholders]] of the enterprises which implement and use it. Given its digital and virtual implementation, via software, 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. | :“...a means of centralizing all services that are important to the [[stakeholder|stakeholders]] of the enterprises which implement and use it. Given its digital and virtual implementation, via software, 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, firing people.</ref> | :“''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, firing people.</ref> | ||
| Line 17: | Line 17: | ||
===Come the [[apocalypse]]=== | ===Come the [[apocalypse]]=== | ||
The [[service catalog]] is also of a piece with the [[risk taxonomy]] in its conviction that the forward needs of the organisation are perfectly understood, anticipated, and pre-determined. There is nothing new under the sun. Unless we are on the brink of apocalypse | The [[service catalog]] is also of a piece with the [[risk taxonomy]] in its conviction that the forward needs of the organisation are perfectly understood, anticipated, and pre-determined. There is nothing new under the sun. Unless we are on the brink of apocalypse — ''the'' [[apocalypse]] that is: the one with horsemen, not just any old calamity — logically, this view is wildly mistaken. As the [[JC]] never tires of reminding us, [[Risk]]s, challenges and opportunities present themselves from undetected crevices in the [[space-time continuum]]. They are not languishing in plain sight within the pages of your [[playbook]]. | ||
It is at just the moment when existential threats emerge, unbidden, from the poorly-sewn seams of your [[risk taxonomy]], that you ''don’t'' want your risk controllers going “sorry, but according to the [[service catalog]], that’s not my problem". | It is at just the moment when existential threats emerge, unbidden, from the poorly-sewn seams of your [[risk taxonomy]], that you ''don’t'' want your risk controllers going “sorry, but according to the [[service catalog]], that’s not my problem". | ||
| Line 24: | Line 24: | ||
As that earnest collaboration on Wikipedia quoted above notes, the idea of a service catalog originated in the software management. In any decent sized organisation, pitches for new software will come in from all sides, and carefully curating the the IT “estate” is profoundly important. | As that earnest collaboration on Wikipedia quoted above notes, the idea of a service catalog originated in the software management. In any decent sized organisation, pitches for new software will come in from all sides, and carefully curating the the IT “estate” is profoundly important. | ||
But software is dumb. It follows rules. It can only do what it was bought to do. To augment or change the application to which your software is dedicated, to meet a new challenge or opportunity | But software is dumb. It follows rules. It can only do what it was bought to do. To augment or change the application to which your software is dedicated, to meet a new challenge or opportunity — that requires judgment. An executive decision. Only a person can make an executive decision.<ref>[[AI]] freaks who beg to differ : [mailto:enquiries@jollycontrarian.com mail me] if you want an argument. I’m game. </ref> | ||
Though at times it might not seem like it, your human [[employee]]s are ''not'' dumb animals however much tethering them to a service catalog might make them feel like it. But you have employees precisely ''because'' they can make judgements, and take executive decisions, ''and do imaginative stuff you weren’t expecting them to when a tricky situation calls for it''. '''Software cannot do this. Not even Deep Mind'''. | Though at times it might not seem like it, your human [[employee]]s are ''not'' dumb animals however much tethering them to a service catalog might make them feel like it. But you have employees precisely ''because'' they can make judgements, and take executive decisions, ''and do imaginative stuff you weren’t expecting them to when a tricky situation calls for it''. '''Software cannot do this. Not even Deep Mind'''. | ||