TDT4252 / DT8802 Enterprise Modelling and Enterprise Architecture

Transcription

1 1 TDT4252 / DT8802 Enterprise Modelling and Enterprise Architecture Sobah Abbas Petersen Adjunct Associate Professor [email protected]

2 2 Lecture Today Based on the following article: Jørgensen, H. D., Karlsen, D. Lillehagen, F. Product-based Approaches and Requirements. Additional reading: A. -J. Berre, B Elvesæter, N. Figay, C. Guglielmina, S. G. Johnsen, D. Karlsen, T. Knothe, S. Lippe. The ATHENA Framework. In Enterprise II - New Challenges and Approaches, Eds. Ricardo J. Gonçalves PhD, Jörg P. Müller, Kai Mertins, Martin Zelm, 2007, pp TDT4252, Spring 2013

3 3 - Definitions Definition: is a property of a product or system, whose interfaces are completely understood, to work with other products or systems, present or future, without any restricted access or implementation. The ability of two or more systems or components to exchange information and to use the information that has been exchanged (IEEE). Initially defined for IT systems, considering exchange of information. But this is not enough.

4 4 Syntactic : If two or more systems are capable of communicating and exchanging data, they are exhibiting syntactic interoperability. Specified data formats, communication protocols and the like are fundamental. XML or SQL standards are among the tools of syntactic interoperability. Semantic : The ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model. Business : The ability for diverse business processes to work together.

5 5 ATHENA Framework (AIF) Conceptual Integration: Focuses on concepts, models, metamodels. It provides a modelling foundation for systemising various aspects of interoperability. Applicative Integration: Focuses on methodologies, standards and domain models. It provides guidelines, principles and patterns that can be used to solve interoperability issues. Technical Integration: Focuses on the technical development and ICT environment. It provides us the tools and platforms for developing and running enterprise applications.

6 6 AIF Conceptual Framework

7 7 Examples

8 8 Product Based It is about removing barriers to Interdisciplinary knowledge sharing and cooperative problem solving. Information logistics and quality management. Data exchange between companies and targeted applications for different disciplines.

9 9 Current Challenges Product design and process lifecycle management: Technical support for product design (e.g. PDM systems) often contain product related information, detached from the processes around product design and development. Lifecycle knowledge integration: within and between the lifecycle phases of the product (business object), such as design, engineering and manufacturing is important. Multiple actors are involved, e.g. designers, manufacturers. TDT4252, Spring 2013

10 10 Product Design Challenges Voices of Customers Voices of Business Product Design Voices of Technology Concept by courtesy of the Winquist Laboratory, Gothenburg.

11 11 Product Based Profiles Product Document Exchange and Management Product Data Exchange through mapping (EAI) Reference models and Semantic Mediation Shared Product Information Repository (PDM) Federated Knowledge Repository (Pragmatic web)

12 12 Product Document Management Manual data processing exchange or document management Documents include text, spreadsheets, engineering drawings, etc.

13 13 Product Data Mapping Local applications for automated data processing Data to data mapping, APIs and web services Enterprise Application Integration (EAI)

14 14 through Standards Standard format Translation Translation Local applications Mapping through global taxonomy/thesaurus Ontologies Reference model, standard or ontology Formal global model opens up for automated reasoning and rule based reconcilliation

15 15 Shared Information Repository User Interface Shared Repository and Application Services (e.g. PDM) User Interface Reference models, standards Integrating database with instance data and reference models Single global model, global execution Product data management (PDM) mysap PLM: Software That Provides the Single Source of Truth for All Product-Related Information (

16 16 Federated Knowledge Repository Configurable Role and Task Views Configurable Role and Task Views Personal Workspace Enterprise Knowledge Architecture Project Repository and Applications Company Repository (e.g. PDM) Engineering Discipline Repository & Apps. Reference models, standards Federated knowledge architecture with multiple local repositories Pragmatically emerging web of local views, local metamodels, local execution, local ownership Active Knowledge Models

17 17 Product Design Support State of the Art Enterprise Resource and Business Process Management (ERP, BPM) Voice of Business Customer Relationship Management (CRM) Voice of Customer Product Design Different approaches to product lifecycle data management (PLM, PDM) Voice of Technology Computer Aided Design and Manufacturing (CAD, CAM, CAE) Single generic perspective for all users; - no roles, views, work management and knowledge sharing support User managed information exchange, no active knowledge support for collecting experiences and improving work Sequential flows creating versioning of data and local data management problems

18 18 Supporting Early Design Phases Concept Preliminary design Detailed design Production Sales Information becomes more structured, narrow down design alternatives Higher uncertainty in the early design phases IT support is better towards the later phases in the lifecycle

19 19 Discussions Can you think of a situation where interoperability is an issue? Lecture 7: Product Modelling TDT4252, Spring 2013