Service catalog: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 2: Line 2:
[[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>
:“''... acts 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.  
So, 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:  
This exercise will do two things:  
Line 50: Line 50:
*[[Operationalisation]]
*[[Operationalisation]]
*[[Outsourcing]]
*[[Outsourcing]]
{{ref}}
{{ref}}