PART III ASSESSMENT AND CONCLUSIONS OF THE STUDY
11 CONCLUSIONS
11.3 Recommendations
There should be a practical implementation of the modelling method sug-gested in this study and the Knowledge Interface Model in a company pro-viding industrial services. The process model or activity model depicting sales, design, planning, production and delivery functions of a company should be a real-life model. The Operational Node Connectivity Descrip-tion should reflect the organisaDescrip-tion of the company and the informaDescrip-tion exchange properties should be selected among critical and important ones to the company.
During a practical implementation of the Knowledge Interface Model, it could be extended with a number of system views (see Table 4) depicting the ICT-infrastructure of the company. The model could be extended to cover also customer - supplier interface.
From theoretical point of view this study could be expanded towards or-ganisational renewal capabilities which are needed when a manufacturing company moves into the business of industrial services. The other direc-tion could be competences and their reladirec-tion to informadirec-tion exchange and knowledge sharing.
REFERENCES
Arnold, S. (2005). Standard Systems Engineering in the Business Environment. FINSE seminar. 26.5.2005. Helsinki.
ATIS (2000). ATIS Telecom Glossary 2000. T1.523-2001. Alliance for Telecommunications Industry Solutions. Available at <URL:
http://www.atis.org/tg2k/> Approved February 28, 2001 by ANSI.
BestServ. (2003). Feasibility Study. Final Report. Helsinki: Teknologia-teollisuus ry.
Booch, G., Rumbaugh, J. & Jacobson, I. (1999). The Unified Modeling Language User Guide. Reading, Massachusetts: Addison-Wesley.
Burns, T. & Stalker, G.M. (1994). The management of innovation. Revised edition. Oxford: Oxford University Press.
DoDAF (2004a). DoD Architecture Framework Version 1.0. Deskbook.
DoD Architecture Framework Working Group. 9 February 2004. Available at <URL: http://www.defenselink.mil/nii/doc/>.
DoDAF (2004b). DoD Architecture Framework Version 1.0. Volume I:
Definitions and Guidelines. DoD Architecture Framework Working Group.
9 February 2004. Available at <URL: http://www.defenselink.mil/nii/doc/>.
DoDAF (2004c). DoD Architecture Framework Version 1.0. Volume II:
Product Descriptions. DoD Architecture Framework Working Group. 9 February 2004. Available at <URL: http://www.defenselink.mil/nii/doc/>.
Gherardi, S. & Nicolini, D. (2003). To transfer is to transform: The
circulation of safety information. In Nicolini, D., Gherardi, S. & Yanow, D.
Knowing in organizations. A practice-based approach. Armonk, NY: M.E.
Sharpe Inc.
Heskett, J., Sasser, W. & Schlesinger, L. (1997). The Service Profit Chain.
New York, NY: Free Press.
Hirsjärvi, S., Remes, P. & Sajavaara P. 1997. Tutki ja kirjoita. Helsinki:
Tammi.
IEEE. (2000). IEEE standard 1471-2000. Recommended Practice for Architectural Description for Software-Intensive Systems. Available at
<URL: http://www.ieee.org>.
IFEAD. (2004). Trends in Enterprise Architecture. How are organizations progressing? Report of the second measurement. November 2004.
Amersfoort, The Netherlands: Institute for Enterprise Architecture Developments.
ISO/IEC (2002). ISO/IEC 15288:2002(E). International standard. Systems engineering - System life cycle processes. First edition. Geneva: ISO copyright office.
ISO/IEC (2003). ISO/IEC TR 19760:2003(E). Technical report. Systems engineering - A guide for the application of ISO/IEC 15288 (System life cycle processes). First edition. Geneva: ISO copyright office.
Kosonen, V. (2004). BestServ. Industrial Service Business Strategy.
Generic Framework and Case Examples. Helsinki: Teknologiateollisuus.
Luhmann, N. (1995). Social systems. Stanford, CA: Stanford University Press.
Mackay, H. (1998) The good listener. Sydney: Pan Macmillan. (First published as: Why don't people listen? 1994).
Malhotra, Y. (1996). Enterprise Architecture: An Overview. BRINT Institute. Available at <URL: http://www.kmbook.com/enterarch.htm>.
McGregor, J. (2004) Software Architecture. Journal of Object Technology, Volume 3, No. 5, May - June 2004, pages 65 - 77.
Miller, F.J. (2002). "I = 0 (Information has no intrinsic meaning)"
Information Research, 8(1), paper no. 140. Available at <URL:
http://InformationR.net/ir/8-1/paper140.html>.
NIST (1993). Federal Information Processing Standard Publications 183.
Integration Definition for Function Modeling (IDEF0). Available at <URL:
http://www.itl.nist.gov/fipspubs/>.
Nuutila, E. & Törmä, S. (2004) Text Graphs: Accurate Concept Mapping with Well-Defined Meaning. In Cañas, A. Novak, J. & Gonzáles F., editors, Concept Maps: Theory, Methodology, Technology. Proceedings of the First International Conference on Concept Mapping. Pamplona, Spain, Sep. 14-17, 2004. Volume 1, pages 477-485.
Oliva, R. & Kallenberg, R. (2003). Managing the transition from products to services. International Journal of Service Industry Management, Volume 14, No 2, pages 160 - 172.
Pöyhönen, A. (2004). Modeling and measuring organizational renewal capability. Acta Universitatis Lappenrantaensis 200. Lappeenranta:
Lappeenrannan teknillinen yliopisto, Digipaino.
Ring, S., Nicholson, D., Thilenius, J. & Harris, S. (2004). An Activity-Based Methodology for Development and Analysis of Integrated DoD Architec-tures. Paper presented at the 2004 Command and Control Research and Technology Symposium. 15. - 17.7.2004. San Diego, California, USA.
Schekkerman, J. (2004a). How to survive in the jungle of Enterprise
Architecture Frameworks. Creating or choosing an Enterprise Architecture Framework. 2nd edition. Canada, Victoria: Trafford.
Schekkerman, J. (2004b). A Comparative Survey of Enterprise Architecture Frameworks. The Open Group, Enterprise Architecture Practioners’ Congress. 20. – 22.4.2004. Brussels, Belgium.
Shannon, C. (1948). A Mathematical Theory of Communication. Reprinted with corrections from The Bell System Technical Journal, Vol. 27, pp. 379–
423, 623–656, July, October, 1948. Available at <URL: http://cm.bell-labs.com/cm/ms/what/shannonday/paper.html>
Spender, J.-C. (1996a). Organizational knowledge, learning and memory:
three concepts in search of a theory. Journal of Organizational Change, Volume 9, No 1, pages 63 - 78.
Spender, J.-C. (1996b). Making knowledge the basis of a dynamic theory of the firm. Strategic Management Journal, Volume 17, pages 45 - 62.
Ståhle, P. (1998). Supporting a system’s capacity for self-renewal.
Helsinki: Yliopistopaino.
Ståhle, P. (2003). Lecture in the Graduate School of Intellectual Capita and Knowledge Management. 20 September 2003, Tampere University of Technology, Finland.
Ståhle, P. & Grönroos, M. (2000). Dynamic Intellectual Capital ™.
Knowledge Management in Theory and Practice. Helsinki: WSOY.
Ståhle, P. & Hannula, M. (2004). Editors of: Perspectives on
organizational knowledge and it’s measurement. Graduate School in Intellectual Capital and Knowledge Management. Available at <URL:
http://www2.lut.fi/ickm/>.
Ståhle, P.; Ståhle, S. & Pöyhönen, A. (2003). Analyzing dynamic intellectual capital: System-based theory and application. Acta
Universitatis Lappenrantaensis 152. Lappeenranta: Lappeenrannan teknillinen yliopisto, Digipaino.
Sveiby, K-E. (1998). What is information? Available at <URL:
http://www.sveiby.com/articles/Information.html> Created Oct 1994, up-dated 31 Dec 1998.
TOGAF. (2003). The Open Group Architecture Framework. Version 8.1.
Enterprise Edition. December 2003. Available at <URL: http://
www.opengroup.org/architecture/>.
Vehkavaara, T. (1999). Toimintatieto laajennettuna tietokäsityksenä eli Miten ja miksi meillä on taito toimia tarkoituksenmukaisesti. Tampereen Yliopisto, filosofian lisensiaattityö. Tampere.
Zachman, J. (1987). A Framework for Information Systems Architecture.
IBM Systems Journal 26 (No 3, 1987).
NOTION: All URLs were checked per date 30 August 2005 and they were available and in the same condition as they were on the date referred.