本論文旨在探討以產品資料標準格式及資訊技術與工具，發展資訊整合模式，其目標是連結電腦輔助設計與電腦輔助製造功能，並結合產品資料管理共用資料庫及型態管理作業，達到同步管理，以實現同步工程作業。資訊整合使自研發、設計、製程規劃、及製造之電腦輔助作業的資料得以連結及共用，形成共通性資訊作業環境，有效提昇產品開發與製造之同步流程管理。為達此一目的，必須以符合國際產品資料表示與交換標準定義整合運作系統所使用的產品共通性資料，以利在電子化環境下，企業體內之上下游廠商可透過此標準定義配合網際網路技術，分享彼此產品資料管理系統中的產品資料，降低資料交換的誤差，並加速產品資料交換的速度。本研究以探討XML及STEP為基礎，首先分析產品生命週期管理之資訊需求，就設計、製程規劃、及製造管理之不同系統，釐清資料管理之資料表達規範，其次以IDEF方法進行產品資料管理之流程分析，並以Zachman資訊系統基礎架構框架各觀點進行資訊需求及架構分析，最後以國防工業體系之中心工廠為例，進行個案實証研究探討資料整合模式與流程分析之可行方法。 研究結果發現，提出三點建議供企業實行資訊整合之參考： 一、 企業流程再造BPR是工作流程、組織結構、資訊技術及工作內容等之合理化與重新設計，使績效大幅改善。 二、 雖有大量投資，但整合後系統的顧客價值不一定增加，例如：業務模式無法吸引更多的客戶時，系統整合後的價值也不一定增加。電腦系統整合的困難度應有企業內充分且全面性溝通的時間。 三、 將所有的資訊應用建置於同一超級資訊平台上作業，很難做到。分散式應用程式讓企業在建置資訊系統時不論在採購上或建置上都更為彈性，企業可依需要不斷的擴充系統，而不需在初期即一次購足。資訊服務網（Web Services）的發展促使企業應用整合EAI技術能滿足此一需求。 本研究係以應用於國防工業體系之中心工廠整合性製造管理資訊系統發展模式為例，國防工業是軍公民營企業合作發展模式，其具有穩定、不易外移、及能帶動相關產業發展之特性，相關產業的資訊整合均面對類似的問題。期能藉由本研究之結果，提供企業進行資訊整合時之參考，使其產品資料能於電子化環境中即時而正確地共用與分享。 / In today’s economy, product lifecycle has been significantly shortened. All manufactures are faced with the challenge of making high quality products within a short product introduction time while reducing costs as low as possible. Product lifecycle management （PLM）is an emerging solution and information integration is a core to address this challenge. Without an efficient methodology to integrate data and processes, PLM would be impossible. This research explores thus the methodology and IT requirement for the integrated product manufacturing information management system, with the following research goals: 1. To investigate the methodology needed by manufacturing companies to implement the integrated product manufacturing information management system to achieve PLM. 2. To investigate the information integration framework for the integrated product manufacturing information management system. Based on analytic method originated from Zachman Framework, this research conducted a case study on a defense industry. The core of this case study is to identify the Framework provides a means for organizing the models of Enterprise Applications Integration (EAI) into useful categories. Model is composed of multiple modeling methods integrated in a way that is sufficient to describe the system. The main models are： (1). Information models for the representation of product data are being developed as an international standard (ISO 10303) informally called STEP. STEP (STandard for the Exchange of Product model data) is designed to enable the exchange of product data between heterogeneous computer systems used throughout the product life cycle. (2). A neutral model of engineering and management data, developed based on the eXtensible Markup Language (XML), can be a standard interchangeable information representation for manufacturing information integration in PLM, and is developed in this research. (3). During several of the BPR steps, the critical process pieces are identified and designed together using IDEF Models. A last, with respect to enterprise information technology integration, this research comes to the conclusions as follows: 1. The primary goal of a BPR effort is to document the current and future business process and to ensure stakeholder buy-in and support. 2. Enterprise information integration is still relatively new, and its best practices are not fully disseminated, which helps to explain why Zachman Framework and analysis tools are important. 3. Since the structure of the data changes too rapidly, integration at the physical source level does not work. Web Services provide a distributed computing technology for revealing the business services of applications on the Internet or intranet using standard XML protocols and formats. It enables EAI to be an ongoing process of creating a flexible, standardized enterprise infrastructure that allows new IT-based applications and business processes to be easily and efficiently deployed.

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)

Notre thèse porte sur la Modélisation d'Entreprise et plus particulièrement sur une vision Ingénierie Système de celle-ci afin de faciliter son application « à minima » en entreprise. Alors que la modélisation d'entreprise arrive à maturité scientifique et technologique, force est de constater que sa pratique est encore trop peu courante. En outre, il n'existe pas à proprement parler de tâche de modélisation, de maintenance et de gestion de modèles dans l'entreprise. La question s'est alors posée de la relation d'interopération entre les systèmes, d'un Système-Entreprise évolutif, le plus souvent composé de façon ad-hoc de sous-systèmes (COTS), qui ont pour particularité d'encapsuler leur propre Savoir-Faire et leurs Ingénieries respectives, en incluant le Système-Produit (son besoin, son projet, ...) à la source de chaque recomposition « à la demande » du Système-Entreprise. Un des objectifs de nos travaux est donc de faciliter l'interopération entre les ingénieries de ces systèmes interopérants (autour du produit A Faire) et l'Ingénierie du Système-Projet d'Entreprise (Pour Faire). Nous nous sommes alors inspirés de la proposition de Kuras pour formaliser notre Système-Entreprise (en fait son Ingénierie) dans une sorte de « Système de Systèmes d'Information » (SdSI) en tenant compte de ses aspects récursifs et multi-échelles dans un contexte organisationnel évolutif. De plus, en nous appuyant sur la théorie des patterns, nous avons identifié puis dérivé le « composite-pattern» pour mieux décrire la nature « Tout et Partie » de l'Holon Système-Entreprise utilisé par Kuras pour extraire le patron de conceptualisation le plus adéquat. Parmi tous les points de vue d'un système, cette dérivation nous permet de représenter ceux du Système A Faire et ceux du Système Pour Faire avec son contenu d'Ingénierie associée guidée par le cadre de modélisation de Zachman. Nous avons outillé notre proposition de cadre d'Ingénierie Système Basée sur des Modèles (ISBM) en étendant le méta-modèle de l'outil « MEGA Modelling Suite » ainsi qu'en développant les interfaces utilisateurs nécessaires et nous l'avons appliqué à l'Ingénierie d'un Système de Traçabilité d'un Produit dans le contexte d'un scénario PLM plausible entre l'AIPL et DIMEG.

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)