Work as a Service
Improving work within and among enterprises is of pressing importance. We take a services-oriented view of both doing and coordinating work by treating work as a service. We discuss how large work engagements can be decomposed into a set of smaller interconnected service requests and conversely how larger engagements can be built up from smaller ones. Encapsulating units of work into service requests enables assignment to any organization qualified to service the work, and naturally lends itself to ongoing optimization of the overall engagement.
A service request contains two distinct parts: coordination information for coordinating work and payload information for doing work. Coordination information deals with business concerns such as risk, cost, schedule, and value co-creation. On the other hand, payload information defines the deliverables and provides what is needed to do the work, such as designs or use-cases. This general two-part decomposition leads to a paradigm of work as a two-way information flow between service systems, rather than as a business process that needs to be implemented or integrated between two organizations.
Treating work as information flow allows us to leverage extant understanding of information systems and facilitates information technology support for work using mainstream service-oriented architectures (SOA). Significant benefits from this approach include agility in setting up large engagements to be carried out by distributed organizations, visibility into operations without violating providers’ privacy or requiring changes to internal processes, responsiveness to unpredictability and change, and ongoing optimizations over competing business objectives.
KeywordsWork encapsulation service decoupling information flow
- 2.Bacon, D.F., Bokelberg, E., Chen, Y., Kash, I.A., Parkes, D.C., Rao, M., Sridharan, M.: Software economies. In: Proc. FSE/SDP Workshop Future Softw. Eng. Research (FoSER), pp. 7–12 (2010)Google Scholar
- 3.Bagheri, S., Oppenheim, D.V.: Optimizing cross enterprise collaboration using a coordination hub. In: Proc. SRII 2011 Global Conf. (2011)Google Scholar
- 5.Benkler, Y.: The Wealth of Networks. Yale University Press, New Haven (2006)Google Scholar
- 6.Bollier, D.: The Future of Work. Aspen Inst., Washington (2011)Google Scholar
- 8.Chaar, J.K., et al.: Work packet delegation in a software factory, Patent Application Publication US 2010/0031226 A1 (2010)Google Scholar
- 10.Goldratt, E.M.: Critical Chain. North River Press (1997)Google Scholar
- 12.Malone, T.W.: The Future of Work. Harvard Business School Press (2004)Google Scholar
- 14.Mintzberg, H.: Mintzberg on Management. Free Press, New York (1989)Google Scholar
- 15.Norta, A.H.: Exploring Dynamic Inter-Organizational Business Process Collaboration. Ph.D. thesis, TU-Eindhoven (2007)Google Scholar
- 17.Oppenheim, D.V., Bagheri, S., Ratakonda, K., Chee, Y.M.: Agility of enterprise operations across distributed organizations: a model of cross enterprise collaboration. In: Proc. SRII 2011 Global Conf. (2011)Google Scholar
- 20.Tapscott, D., Williams, A.D.: Wikinomics. Portfolio Penguin, New York (2006)Google Scholar
- 24.Varshney, L.R., Oppenheim, D.V.: Coordinating global service delivery in the presence of uncertainty. In: Proc. 12th Int. Research Symp. Service Excellence Manage, QUIS12 (2011)Google Scholar
- 26.Wiredu, G.O.: A framework for the analysis of coordination in global software development. In: Proc. Int. Wksp. Global Softw. Dev. Practitioner, pp. 38–44 (2006)Google Scholar