Towards A Method for Developing Reference Enterprise Architectures

In most economic sectors organizations face rapid environmental changes like regulations. Such changes can force them to adjust both their organizational and operational structure. For instance, in the energy utility sector numerous developments moved German Public Utilities (PUs) towards a liberalized market. Nowadays PUs have to stay competitive while managing a heterogeneous information technology (IT) landscape. We address this demand for aligning business and IT by combining the holistic perspective of Enterprise Architecture Management (EAM) with the characteristic of reference modeling to reuse knowledge in a problem domain. Therefore, we utilize configurative reference modeling within Design Science Research (DSR). The artefact at hand is a method for developing a Reference Enterprise Architecture (R-EA), which is applied in the problem domain of PUs. Our contributions are the (i) adaptation of Configurative Reference Modelling (CRM) to develop a R-EA and (ii) a procedure how to elicit knowledge for R-EA development method

A voice-based annotation system for collaborative computer-aided design

In this paper, we describe a voice-based interaction mechanism to annotate 3D models directly from a computer-aided design (CAD) modeling environment. The audio signal is captured and automatically transcribed to a textual 3D note, which is attached to the geometry and made available to other product information and business processes across the enterprise via a product data management system. Our approach provides a more natural and intuitive method to capture design and engineering knowledge that is particularly effective when large amounts of information need to be communicated. We discuss the rationale of the software architecture and the value of this modality for capturing knowledge in a collaborative engineering context. Finally, we examine the results of an experiment to validate our proposal. Our results show that 3D annotations are an effective mechanism to communicate design knowledge, which suggests the need for further developments in the areas of multimodal interaction methods and interfaces for CAD and collaborative tools

The impact of conceptual structures on transaction and enterprise architecture practices

This research hypothesises is Conceptual Structures using the Resource Event Agent (REA) ontology adds value when defining a Transaction Oriented Architecture (TOA) for Enterprise Systems. Enterprise Systems drive global economic growth through well-designed implementations that provide organisations with multiple benefits, including streamlined business processes, increased efficiencies, improved productivity and decreased costs. Conversely, poorly implemented Enterprise Systems can lead to poor operating results. Most Enterprise Systems still use traditional methods of storing economic data mirroring the double-entry bookkeeping system, which can cause several problems, including data loss and repetition. Enterprise Systems must capture transaction data in a format available to multiple business processes to fulfil their goals. This thesis provides an overview of the currently available frameworks for Enterprise Architecture design. It details the problems that are observed and experienced during the completion of real-world Enterprise System development projects. The basis of the Transaction Concept is then presented as the general solution, leading to a TOA for Enterprise Systems. The Transaction Pyramid describes TOA through three layers of transactions: Enterprise, Business, and Database. The Design Science Research Methodology (DSRM) is used as the primary research methodology to provide a framework to this research. Together with the secondary research method of Action Research to provide a more granular basis for DSRM Step 3 : "Design and development", which required multiple minor iterations of the cyclical process of Action Research to produce the required artefacts. The case study approach is used also as a secondary research method for empirical inquiry and investigation required for DSRM step 4: "Demonstration". A Knowledge Management System is defined to validate TOA, and artefacts are implemented for an Automated REA (AREA) based on Protégé Frames to underpin TOA as a Proof of Concept. AREA provides a fully- edged, TOA design tool for Enterprise Architecture using the REA ontology. AREA's Knowledge Repository uses Conceptual Structures through a) the ISO Common Logic standard's Conceptual Graph Interchange Format (CGIF) to store and transmit the TOA using an REA ontology, and b) Formal Concept Analysis (FCA) for validation. AREA is then demonstrated and evaluated using two industrial case studies as exemplars. These Findings support the research's hypothesis and its contribution to knowledge

Architectural design decisions that incur technical debt — An industrial case study

Context: During software development, some architectural design decisions incur technical debt, either deliberately or inadvertently. These have serious impact on the quality of a software system, and can cost significant time and effort to be changed. While current research efforts have explored general concepts of architectural design decisions and technical debt separately, debt-incurring architectural design decisions have not been specifically explored in practice. Objective: In this case study, we explore debt-incurring architectural design decisions (DADDs) in practice. Specifically, we explore the main types of DADDs, why and how they are incurred in a software system, and how practitioners deal with these types of design decisions. Method: We performed interviews and a focus group with practitioners working in embedded and enterprise software companies, discussing their concrete experience with such architectural design decisions. Results: We provide the following contributions: 1) A categorization for the types of DADDs, which extend a current ontology on architectural design decisions. 2) A process on how deliberate DADDs are made in practice. 3) A conceptual model which shows the relationships between the causes and triggers of inadvertent DADDs. 4) The main factors that influence the way of dealing with DADDs. Conclusion: The results can support the development of new approaches and tools for Architecture Technical Debt management from the perspective of Design Decisions. Moreover, they support future research to capture architecture knowledge related to DADDs

Towards the development of the framework for inter sensing enterprise architecture

[EN] Inter-enterprise architecture (IEA) is a new concept that seeks to apply the tools and methodologies of enterprise architecture (EA) in a collaborative context, in order to model collaborative organizations in an inclusive manner. According to the main enterprise architectures proposed to this point, an EA should be conformed at least for a framework, a methodology and a modelling language. Sensing enterprise (SE) is an attribute of an enterprise or a network that allows it to react to business stimuli originating on the Internet. These fields have come into focus recently, and there is not evidence of the use of IEA for modelling a SE, while finding an interesting gap to work on. Thus, this paper proposes an initial framework for inter sensing enterprise architecture (FISEA), which seeks to classify, organize, store and communicate, at the conceptual level, all the elements for inter-sensing enterprise architectures and their relationships, ensuring their consistency and integrity. This FISEA provides a clear idea about the elements and views that create collaborative network and their inter-relationships, based on the support of Future Internet.This work was supported by the European Commission FP7 UNITE Project, through its Secondment Programme and the Universitat Politecnica de Valencia ADENPRO-PJP project (ref. SP20120703).Vargas, A.; Cuenca, L.; Boza, A.; Sacala, I.; Moisescu, M. (2016). Towards the development of the framework for inter sensing enterprise architecture. Journal of Intelligent Manufacturing. 27(1):55-72. https://doi.org/10.1007/s10845-014-0901-zS5572271Adaba, G., Rusu, L., & Mekawy, M. (2010). Business-IT alignment in trade facilitation: A case study. In organizational, business, and technological aspects of the knowledge society. Communications in Computer and Information. Science, 44(112), 146–154.Afsarmanesh, H., & Msanjila, S. (2008). Inter-organizational trust in VBEs. In L. Camarinha-Matos, H. Afsarmanesh, & M. Ollus (Eds.), Methods and tools for collaborative networked organizations (pp. 91–118). New York: Springer.Afsarmanesh, H., Camarinha-Matos, L., & Ermilova, E. (2008). VBE reference framework. In L. Camarinha-Matos, H. Afsarmanesh, & M. Ollus (Eds.), Methods and tools for collaborative networked organizations (pp. 35–68). New York: Springer.Arango, M., Londoño, J., & Zapata, J. (2010). Arquitectura empresarial- Una visión general. Revista Ingenierías Universidad de Medellín, 9(16), 101–111.Audy, J., Lehoux, N., & D’Amours, S. (2012). A framework for an efficient implementation of logistics collaborations. International Transactions in Operational Research, 19(5), 633–657.Boza, A., Cuenca, L., Poler, R., Michaelides, Z., & Systems, Enterprise Information. (2014). The interoperability force in the ERP field. Enterprise Information Systems,. doi: 10.1080/17517575.2013.866697Camarinha-Matos, L., & Afsarmanesh, H. (2005). Collaborative networks: A new scientific discipline. Journal of Intelligent Manufacturing, 16(4–5), 439–452.Camarinha-Matos, L., & Afsarmanesh, H. (2008). Collaborative networks: Reference modeling. New York: Springer.Camarinha-Matos, L., Afsarmanesh, H., & Ollus, M. (2008). ECOLEAD and CNO base concepts. In L. M. Camarinha-Matos, H. Afsarmanesh, & M. Ollus (Eds.), Methods and tools for collaborative networked organizations (pp. 35–68). New York: Springer.Chalmeta, R., & Grangel, R. (2003). ARDIN extension for virtual enterprise integration. The Journal of Systems and Software, 67(3), 141–152.Chen, D., Vallespir, B., & Doumeingts, G. (1997). GRAI integrated methodology and its mapping onto generic enterprise reference architecture and methodology. Computers in Industry, 33(2), 387–394.Choi, Y., Kang, D., Chae, H., & Kim, K. (2008). An enterprise architecture framework for collaboration of virtual enterprise chains. The International Journal of Advanced Manufacturing Technology, 35(11–12), 1065–1078.CIMOSA Asociation. (1996). CIMOSA Primer on key concepts, purpose and business value.Council of Supply Chain Management Professionals CSCMP. (2010). CSCMP. Glosary of terms. from http://cscmp.org/resources-research/glossary-terms . Accessed 9 February 2013Coutinho, C., Cretan, A., Ferreira, C., Ghodous, P., & Jardim-Goncalves, R. (2014). Service-based negotiation for advanced collaboration in enterprise networks. Journal of Intelligent Manufacturing,. doi: 10.1007/s10845-013-0857-4Cuenca, L. (2009). Marco arquitectónico para la propuesta IE-GIP. Extensión de la arquitectura CIMOSA. Aplicación a una empresa del sector cerámico. Tesis Doctoral Universidad Politecnica de Valencia.Cuenca, L., Boza, A., & Ortiz, A. (2011). An enterprise engineering approach for the alignment of business and information technology strategy. International Journal of Computer Integrated Manufacturing, 24(11), 974–992.Cuenca, L., Ortiz, A., & Boza, A. (2005). Arquitectura de Empresa. Visión General. Gijón: IX Congreso de Ingeniería de Organización.Dong, X., Liu, Q., & Yin, D. (2008). Business performance, business strategy, and information system strategic alignment: An empirical study on Chinese firms. Tsinghua Science and Technology, 13(3), 348–354.Ermilova, E., & Afsarmanesh, H. (2007). Modeling and management of profiles and competencies in VBEs. Journal of Intelligent Manufacturing, 18(5), 561–586.Estimali, H., Gardesh, H., & Sikari, S. (2010). Validating ITIL maturity to strategic business-IT alignment. In 2nd International conference on computer technology and development (ICCTD 2010).European Commission European Society and Media. (2007). Dygital Business Ecosystems. In F. Nachira, P. Dini, A. Nicolai, M. Le Louarn, & L. Rivera (Eds.). http://www.digital-ecosystems.org/book/ . Luxembourg: Office for Official Publications of the European Communities. Accessed 15 October 2012Executive Branch of the U.S. Federal Government. (2012). A Common Approach to Federal Enterprise Architecture. The White House. http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/common_approach_to_federal_ea.pdf . Accessed 13 August 2013Franco, R., Gomez, P., Ortiz, A., & Navarro, R. (2012). Integrated approach for interoperability in collaborative networs and service-based ecosystems. In R. Poler, G. Doumeingts, B. Katzy, & R. Chalmeta (Eds.), Enterpise interoperability V (pp. 329–339). London: Springer.Force, I. F. I. P.-I. F. A. C. Task. (1998). GERAM: Generalised enterprise reference architecture and methodology. International Federation for Information Processing, 1(2), 30.Future Internet Enterprise Systems (FInES) Cluster. (2012). FInES Research Roadmap 2025. From http://cordis.europa.eu/fp7/ict/enet/documents/fines-research-roadmap-v30_en.pdf . Accessed 13 October 2013Henderson, J., & Venkatraman, N. (1993). Strategic alignment: Leveraging information technology for transforming organizations. IBM Systems Journal, 32(1), 472–484.Hu, Q., & Huang, D. (2006). Using the balanced scorecard to achieve sustained IT-business alignment: A case study. Communications of the Association for Information Systems, 17, 181–204.ISO 15704. (2000). Industrial automation systems–Requirements for enterprise-reference architectures and methodologies.ISO/CEN 19439. (2006). Enterprise integration–Framework for enterprise modelling.Kilger, C., Reuter, B., & Stadtler, H. (2008). Collaborative planning. In H. Stadtler & C. Kilger (Eds.), Supply chain management and advanced planning-concepts, models software and case studies (pp. 263–284). Berlin, Heidelberg: Springer.Kosanke, K., Vernadat, F., & Zelm, M. (1999). CIMOSA: Enterprise engineering and integration. Computers in Industry, 40(2), 83– 97.Lankhorst, M. (2009). Enterprise architecture at work: Modelling, communication and analysis. New York: Springer.Luftman, J. (2004). Assessing business-IT alignment maturity. Communications of the Association for Information Systems, 4, 99.Maes, R. (1999). Reconsidering information management through a generic framework. Amsterdam: Universiteit van Amsterdam, Department of Accountancy & Information Management.Mehandjiev, N., & Grefen, P. (2010). Dynamic business process formation for instant virtual enterprises. London.Mekawy, M., Rusu, L., & Ahmed, N. (2009). Business and IT alignment: An evaluation of strategic alignment models. In best practices for the knowledge society. Knowledge, Learning, Development and Technology for All, 49, 447–455.Moisescu, M., Sacala, I., Stanescu, A., & Serbanescu, C. (2012). Towards integration of knowledge extraction form process interoperability in future internet enterprise systems. Information Control Problems in Manufacturing, 14(1), 1458–1463.Ortiz, A. (1998). Propuesta para el Desarrollo de Programas de Integración Empresarial en Empresas Industriales. Aplicación a una Empresa del Sector Cerámico: Tesis Doctoral Universidad Politécnica de Valencia.Palmer, C., Harding, J., Swarnkar, R., Das, B., & Young, R. (2013). Generating rules from data mining for collaboration moderator services. Journal of Intelligent Manufacturing, 24, 313–330.Pijpers, V., Gordijn, J., & Akkermans, H. (2009). Aligning information system design and business strategy–A starting internet company. In the practice of enterprise modeling. Lecture Notes in Business Information Processing, 15, 47–61.Plaza, J., Burgos, J., & Carmona, E. (2010). Measuring stakeholder integration: Knowledge, interaction and adaptational behavior dimensions. Journal of Business Ethics, 93, 419–442.Romero, D., Galeano, N., & Molina, A. (2010). Virtual organisation breeding environments value system and its elements. Journal of Intelligent Manufacturing, 21(3), 267–286.Sacala, I., Moisescu, M., & Repta, D. (2013). Towards the development of the future internet based enterprise in the context of cyber-physical systems. In 2013 19th International conference on control systems and computer science (CSCS), (pp. 405–412).Santana, R., Daneva, M., van Eck, P., & Wieringa, R. (2008). Towards a business-IT aligned maturity model for collaborative networked organizations. In 12th International conference on advanced information systems engineering.Schekkerman, J. (2004). Enterprise architecture validation. Achieving business-aligned and validated entreprise architectures. Institute For Enterprise Architecture Developments (IFEAD). http://enterprise-architecture.info/Images/Extended%20Enterprise/Extended%20Enterprise%20Architecture2.htm . Accessed 10 October 2011Schekkerman, J. (2006). Extended enterprise architecture framework essentials guide. Retrieved 2012 from Institute For Enterprise Architecture Developments (IFEAD). http://enterprise-architecture.info/Images/E2AF/Extended%20Enterprise%20Architecture%20Framework%20Essentials%20Guide%20v1.5.pdf . Accessed 23 September 2012Stadtler, H. (2009). A framework for collaborative planning and state-of-the-art. OR Spectrum, 31, 5–30.Stelzer, D. (2010). Enterprise architecture principles: Literature review and research directions. Service-Oriented Computing. Lecture Notes in Computer Science, pp. 12–21.Swarnkar, R., Choudhary, A., Harding, J., Das, B., & Young, R. (2012). A framework for collaboration moderator services to support knowledge based collaboration. Journal of Intelligent Manufacturing, 23, 2003–2023.The, OPEN GROUP. (2011). TOGAF. http://www.opengroup.org/togaf/ . Accessed 18 November 2011U.S. Department of the Treasury. (2000). Treasury enterprise architecture framework. http://www.treasury.gov/Pages/default.aspx . Accessed 23 November 2011United States Department of Defense. (2010). Department of defense architecture framework. http://dodcio.defense.gov/dodaf20/dodaf20_capability.aspx . Accessed 28 November 2011Vargas, A., Boza, A., & Cuenca, L. (2011). Towards interoperability through Inter-enterprise collaboration architectures. In R. Meersman, T. Dillon, & P. Herrero (Eds.), On the move to meaningful internet systems: OTM 2011 workshops. Lecture Notes in Computer Science, Vol. 7046, pp. 102–111.Vargas, A., Boza, A., Cuenca, L., & Sacala, I. (2013a). Inter-enterprise architecture and internet of the future. Technological Innovation for the Internet of Things, 394, 25–32.Vargas, A., Boza, A., Cuenca, A., & Ortiz, A. (2013b). Towards a framework for inter-enterprise architecture to boost collaborative networks. In On the move to meaningful internet systems: OTM 2013 workshops. Lecture Notes in Computer Science, 8186, 179–188.Vargas, A., Boza, A., Cuenca, L., & Ortiz, A. (2014). The importance of strategic alignment in enterprise collaboration. In J. C. Prado-Prado & J. García-Arca (Eds.), Annals of industrial engineering 2012 (pp. 71–78). London: Springer.Vernadat, F. (2003). Enterprise modelling and integration: From fact modelling to enterprise interoperability. Enterprise inter- and intra-organizational integration: Building international consensus. Series: IFIP Advances in Information and Communication Technology, 108.Vesterager, J., Tølle, M., & Bernus, P. (2002). VERA: Virtual enterprise reference. GLOBEMEN final plenary: In GMNBook.Wang, X., Zhou, X., & Jiang, L. (2008). A method of business and IT alignment based on enterprise architecture. In IEEE international conference on service operations and logistics, and informatics, pp. 740–745.Zachman, J. (1997). Enterprise architecture: The issue of the century. Database Programming and Design, 1–13

Knowledge-based Engineering in Product Development Processes - Process, IT and Knowledge Management perspectives

Product development as a field of practice and research has significantly changed due to the general trends of globalization changing the enterprise landscapes in which products are realized. The access to partners and suppliers with high technological specialization has also led to an increased specialization of original equipment manufacturers (OEMs). Furthermore, the products are becoming increasingly complex with a high functional and technological content and many variants. Combined with shorter lifecycles which require reuse of technologies and solutions, this has resulted in an overall increased knowledge intensity which necessitates a more explicit approach towards knowledge and knowledge management in product development. In parallel, methods and IT tools for managing knowledge have been developed and are more accessible and usable today. One such approach is knowledge-based engineering (KBE), a term that was coined in the mid-1980s as a label for applications which automate the design of rule-driven geometries. In this thesis the term KBE embraces the capture and application of engineering knowledge to automate engineering tasks, regardless of domain of application, and the thesis aims at contributing to a wider utilization of KBE in product development (PD). The thesis focuses on two perspectives of KBE; as a process improvement IT method and as a knowledge management (KM) method. In the first perspective, the lack of explicit regard for the constraints of the product lifecycle management (PLM) architecture, which governs the interaction of processes and IT in PD, has been identified to negatively affect the utilization of KBE in PD processes. In the second perspective, KM theories and models can complement existing methods for identifying potential for KBE applications.Regarding the first perspective, it is concluded that explicit regard for the PLM architecture decreases the need to develop and maintain software code related to hard coded redundant data and functions in the KBE application. The concept of service oriented architecture (SOA) has been found to enable an the explicit regard for the PLM architecture.. Regarding the second perspective, it is concluded that potential for KBE applications is indicated by: 1.) application of certain types of knowledge in PD processes 2.) high maturity and formalization of the applied knowledge 3.) a codification strategy for KM and 4.) an agreement and transparency regarding how the knowledge is applied, captured and transferred. It is also concluded that the formulation of explicit KM strategies in PD should be guided by knowledge application and its relation to strategic objectives focusing on types of knowledge, their role in the PD process and the methods and tools for their application. These, in turn, affect the methods and tools deployed for knowledge capture in order for it to integrate with the processes of knowledge origin. Finally, roles and processes for knowledge transfer have to be transparent to assure the motivation of individuals to engage in the KM strategy

Knowledge-based Engineering in Product Development Processes - Process, IT and Knowledge Management perspectives

Product development as a field of practice and research has significantly changed due to the general trends of globalization changing the enterprise landscapes in which products are realized. The access to partners and suppliers with high technological specialization has also led to an increased specialization of original equipment manufacturers (OEMs). Furthermore, the products are becoming increasingly complex with a high functional and technological content and many variants. Combined with shorter lifecycles which require reuse of technologies and solutions, this has resulted in an overall increased knowledge intensity which necessitates a more explicit approach towards knowledge and knowledge management in product development. In parallel, methods and IT tools for managing knowledge have been developed and are more accessible and usable today. One such approach is knowledge-based engineering (KBE), a term that was coined in the mid-1980s as a label for applications which automate the design of rule-driven geometries. In this thesis the term KBE embraces the capture and application of engineering knowledge to automate engineering tasks, regardless of domain of application, and the thesis aims at contributing to a wider utilization of KBE in product development (PD). The thesis focuses on two perspectives of KBE; as a process improvement IT method and as a knowledge management (KM) method. In the first perspective, the lack of explicit regard for the constraints of the product lifecycle management (PLM) architecture, which governs the interaction of processes and IT in PD, has been identified to negatively affect the utilization of KBE in PD processes. In the second perspective, KM theories and models can complement existing methods for identifying potential for KBE applications.Regarding the first perspective, it is concluded that explicit regard for the PLM architecture decreases the need to develop and maintain software code related to hard coded redundant data and functions in the KBE application. The concept of service oriented architecture (SOA) has been found to enable an the explicit regard for the PLM architecture.. Regarding the second perspective, it is concluded that potential for KBE applications is indicated by: 1.) application of certain types of knowledge in PD processes 2.) high maturity and formalization of the applied knowledge 3.) a codification strategy for KM and 4.) an agreement and transparency regarding how the knowledge is applied, captured and transferred. It is also concluded that the formulation of explicit KM strategies in PD should be guided by knowledge application and its relation to strategic objectives focusing on types of knowledge, their role in the PD process and the methods and tools for their application. These, in turn, affect the methods and tools deployed for knowledge capture in order for it to integrate with the processes of knowledge origin. Finally, roles and processes for knowledge transfer have to be transparent to assure the motivation of individuals to engage in the KM strategy

Kokonaisarkkitehtuurin kehityksen prosessimalli ja kuvaustarpeet Case-yritykselle

Yrityksissä ajankohtainen sana ja asia on tehostaminen. Yrityksien liiketoiminnan pitää koko ajan tehostua ja kehittyä jotta toiminta olisi kustannustehokasta. Tehostamiseen liittyvä ongelmia ovat mm se, että prosessien alati muuttuessa järjestelmät eivät pysy samassa kehitystahdissa ja ne ovat osaltaan myös hyvin vanhoja ja niitä ei ole integroitu toisiin järjestelmiin. Järjestelmistä, saati prosesseista ei ole välttämättä tehty kuvauksia jotka auttavat kehitystyössä. Yrityksissä henkilöstön vaihtuvuus voi myös aiheuttaa ongelmia viedä kehitystä systemaattisesti eteenpäin. Kokonaisvaltaiselle toiminnan, tiedon ja tietojärjestelmien hallintamenetelmälle on tarvetta. Onnistunut yrityksen tarpeisiin soveltuva kokonaisarkkitehtuuri ja siihen liittyvä kehityksen prosessimalli voisi osaltaan ratkaista ja ennalta ehkäistä monia ongelmia joita yritys kehityshankkeissaan kohtaa. Kokonaisarkkitehtuuri ja siihen liittyvät osiot näyttäytyvät asiaan perehtymättömälle monimutkaisena ja laajana asiakokonaisuutena. Kokonaisarkkitehtuuri pitää sisällään arkkitehtuurin hallintamallin, arkkitehtuurimenetelmän sekä arkkitehtuurilinjaukset- ja kuvaukset sekä laajan kirjon asiaan liittyvää terminologiaa. Opinnäytetyön tarkoituksena oli perehtyä ja tutkia kokonaisarkkitehtuuria yleisesti sekä kolmea valittua kokonaisarkkitehtuurimenetelmää, TOGAFia, JHS 179:ä ja Kartturia, ja näiden pohjalta muodostaa Case–yritykselle soveltuva kokonaisarkkitehtuurin kehityksen prosessimalli sekä kuvaustarpeet. Opinnäytetyön tarkoituksena oli myös opinnäytetyön tekijän oman osaamisen laajentaminen kokonaisarkkitehtuurista. Opinnäytetyön tutkimusongelma oli, minkälainen kokonaisarkkitehtuurin kehityksen prosessimallimalli saadaan Case-yritykselle käyttöön yhdistäen kolme viitekehystä ja minkälainen luettelo kuvaustarpeista saadaan koostamalla yhteen arkkitehtuuriviitekehyksien kuvaussuositukset. Opinnäytetyö sisältää kaksi tapaustutkimusta joiden taustalla oli kerätä ymmärrystä organisaation kokonaisarkkitehtuurista ja mitä siitä yrityksessä tiedetään ja miten arkkitehtuuria käytetään. Opinnäytetyön päätutkimus toteutettiin suunnittelututkimuksena. Suunnittelututkimus soveltuu hyvin tietojärjestelmäkehitykseen, jossa pyrkimyksenä on muodostaa tekninen ratkaisumalli käytännön tutkimusongelmaan. Opinnäytetyön tuotoksena syntyi kolmen valitun viitekehyksen pohjalta koostettu kokonaisarkkitehtuurin kehitysprosessimalli, sekä luettelo kuvaustarpeista joiden avulla yrityksessä voidaan kartoittaa, mitkä kuvaukset ovat jo olemassa. Opinnäytetyön tuloksena myös opinnäytetyön tekijän ymmärrys kokonaisarkkitehtuurista laajeni. Opinnäytetyön tuloksissa todetaan, että kokonaisarkkitehtuuri on saatu arkkitehtuuriviitekehyksien osalta vaikuttamaan haastavalta kokonaisuudelta ja sitä se onkin, mikäli arkkitehtuuriviitekehyksiä sellaisenaan noudattaisi. Yksityisellä puolella organisaatioiden kannattaa ottaa vain arkkitehtuurimenetelmien parhaimmat osiot omaan käyttöönsä. Kokonaisarkkitehtuurissa on kyse siitä, että tarvittavat kuvaukset ovat kunnossa ja ne ovat niitä tarvitsevien saatavilla yhteisessä sijainnissa, yrityksen strategia on selvillä eli mitä kohti edetään ja etenemisessä käytetään sovittua kehitysprosessimallia. Yhtä lailla tärkeää on johdon ymmärrys ja sitoutuminen noudattamaan arkkitehtuuria. Opinnäytetyön artefakti ei ole yksilöllinen lopputulos pelkästään valitun yritykseen tarpeisiin vaan muutkin yritykset voivat hyödyntää kokonaisarkkitehtuurityötä suunnitellessaan. Opinnäytetyöstä rajattiin pois arkkitehtuurin hallintamalli mikä määrittelee roolit ja vastuut arkkitehtuurityöhön liittyen. Tämän todettiin olevan hyvä jatkotutkimusaihe.The current word and issue in companies is efficiency. The company’s business must constantly improve and develop so that the operation is cost-effective. Problems related to efficiency are that when processes are changing constantly the systems cannot keep up the same pace of development and they are also very old and not integrated with other systems. The descriptions of the systems or processes which would help in development work have not necessary been done. Staff changes in companies can also cause problems to taking development forward systematically. There is a need for a comprehensive management method for operations, information and information systems. Successful and suitable enterprise architecture and a development model for the company’s needs could help solve and prevent many of the problems that the company faces in its development projects. Enterprise architecture and the sections related to architecture includes complicated and wide content for the uninitiated. Enterprise architecture includes a management model, a method and policies as well as descriptions and a broad spectrum of terminology. The aim of this thesis was to examine enterprise architecture in general, as well as the three chosen enterprise architecture models, TOGAF, JHS 179, and Kartturi, and on the basis of these to construct a suitable architecture process model for the chosen case company. Also, the purpose of this thesis was to expand the author’s own knowledge of enterprise architecture. The research problem of the thesis was what kind of an enterprise architecture development process model is provided for the case company by combining three architecture models and what kind of a list of the description needs is obtained by combining the recommendations of the architecture descriptions. The thesis includes two case studies whose aim was to gather understanding of the company’s enterprise architecture and what they know about it and how they are using the architecture. The main research of this thesis has carried out as a design research. Design research is well suited to information system development where the aim is to form a technical solution model to a practical research problem. As a result of the thesis a process model was composed based on the three selected frameworks and a list was made of the requirements that enable the company to identify which descriptions are already in place. In addition, as a result of the thesis the author’s understanding of the overall architecture was expanded. It is noted in the results that enterprise architecture has been made to seem like a challenging set and it is, if frameworks were followed as they are. In the private sector organizations should take only the best sections of the architectures for their own use. Enterprise architecture is a question of the necessary descriptions being in order and that they are available for those who need them and descriptions are in a common location, the company’s strategy is clear and the agreed development process model is used to proceed towards it. Equally important is the management’s understanding and commitment to comply with the architecture. The artifact of the thesis is not only the result of the unique needs of the selected company because other companies take advantage of it for planning their architecture work. The management model of architecture, which defines the roles and responsibilities of the work related to architecture was not included in the thesis. This will be a good topic for further research

Linking design and manufacturing domains via web-based and enterprise integration technologies

The manufacturing industry faces many challenges such as reducing time-to-market and cutting costs. In order to meet these increasing demands, effective methods are need to support the early product development stages by bridging the gap of communicating early design ideas and the evaluation of manufacturing performance. This paper introduces methods of linking design and manufacturing domains using disparate technologies. The combined technologies include knowledge management supporting for product lifecycle management (PLM) systems, enterprise resource planning (ERP) systems, aggregate process planning systems, workflow management and data exchange formats. A case study has been used to demonstrate the use of these technologies, illustrated by adding manufacturing knowledge to generate alternative early process plan which are in turn used by an ERP system to obtain and optimise a rough-cut capacity plan