Technical Data Interoperability (TDI) Pathfinder Via Emerging Standards

The TDI project (TDI) investigates trending technical data standards for applicability to NASA vehicles, space stations, payloads, facilities, and equipment. TDI tested COTS software compatible with a certain suite of related industry standards for capabilities of individual benefits and interoperability. These standards not only esnable Information Technology (IT) efficiencies, but also address efficient structures and standard content for business processes. We used source data from generic industry samples as well as NASA and European Space Agency (ESA) data from space systems

Specifications and Development of Interoperability Solution dedicated to Multiple Expertise Collaboration in a Design Framework

This paper describes the specifications of an interoperability platform based on the PPO (Product Process Organization) model developed by the French community IPPOP in the context of collaborative and innovative design. By using PPO model as a reference, this work aims to connect together heterogonous tools used by experts easing data and information exchanges. After underlining the growing needs of collaborative design process, this paper focuses on interoperability concept by describing current solutions and their limits. Then a solution based on the flexibility of the PPO model adapted to the philosophy of interoperability is proposed. To illustrate these concepts, several examples are more particularly described (robustness analysis, CAD and Product Lifecycle Management systems connections)

Applying PLCS to EDMS/MTF at the European Organization for Nuclear Research

Estágio realizado no CERN e orientado Eva Sanchez-Corral MenaTese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 200

E-business framework enabled B2B integration

Standards for B2B integration help to facilitate the interoperability between organisations. These standards, often called e-business frameworks, guide integration by specifying the details for business processes, business documents and secure messaging. Extensible Mark-up Language (XML) is used in modern e-business frameworks instead of Electronic Data Interchange (EDI) formats. Having XML as the data format is not enough for integration, but e-business frameworks are needed to guide how XML is used. This work analyses the many partly competing and overlapping e-business frameworks how they differ in support for business processes, documents and secure messaging. In addition, the effect of standardisation organisation to the outcome of the e-business framework is studied. In this work, one e-business framework, RosettaNet, is used to tackle the challenges of product development (PD) integrations. A proof-of-concept implementation of a RosettaNet integration is provided to support PD and the lessons learned are discussed. The current specifications lack good processes for PD integrations, while they fail in specifying the concepts needed for document management. Furthermore, there are interoperability problems due to a lack of expressivity of the schema languages to encode the business documents, and the current setup of integration takes a very long time. RosettaNet has a lot of flexibility in the specifications, and thus just supporting the same standard process is not enough for interoperability. With semantic technologies, many shortcomings of the current standards for B2B integration can be solved, as they make it possible to present constraints the current technologies have problems with. This work presents a practical case of B2B integration with semantic technologies and describes the benefits of applying such technologies.Standardit tukevat organisaatioiden välistä järjestelmäintegraatiota. Integroinnin standardit määrittelevät organisaatioiden välisiä liiketoimintaprosesseja, -dokumentteja sekä määrittelevät turvallisen tavan kommunikoida. Nykyaikaiset standardit ovat XML-perusteisia vanhemman EDI-formaatin sijaan. XML:n käyttö ei ole riittävästi takaamaan integraation onnistumista, vaan tarvitaan tarkempaa sopimista, miten XML:ää käytetään integraatiossa. Joukko yritystenvälisen integroinnin standardeja määrittelee tämän. Tässä työssä analysoidaan useaa, osittain kilpailevaa, yritystenvälisen integroinnin standardia ja tutkitaan miten ne tukevat liiketoimintaprosessien, -dokumenttien ja turvallisen viestinvälityksen määrittelyjä ottaen huomioon myös standardointiorganisaation vaikutuksen lopputulokseen. Tässä työssä RosettaNet-standardia sovelletaan tuotekehitykseen liittyvissä integroinneissa. Työssä esitetään prototyyppi tuotekehitystiedon integroinnista RosettaNetin avulla ja keskustellaan saavutetuista kokemuksista. Nykyiset spesifikaatiot tuotekehitysprosesseille ovat tarpeisiin riittämättömiä, koska tuki dokumenttien hallinnan käsitteistölle on puutteellinen. Myös RosettaNetin käyttämien XML-skeemakielien puutteellinen ilmaisuvoima aiheuttaa ongelmia dokumenttien yhteentoimivuudelle. Lisäksi integraation tekeminen on hidasta verrattuna tyypillisen tuotekehitysprojektin kestoon. RosettaNetin tarjoamissa spesifikaatioissa on paljon joustavuutta, joten saman standardiprosessin tukeminen ei tarkoita, että järjestelmät ovat yhteentoimivia. Nykyspesifikaatioissa ja niissä käytettyjen skeema-kielten ilmaisuvoiman puutteet voidaan osittain paikata käyttämällä semanttisia teknologioita. Tämä työ esittää, miten integraatioissa voidaan saavuttaa semanttisia teknologioita käyttämällä parempi yhteentoimivuus.reviewe

Improving the Quality and Cost-effectiveness of Process-oriented, Service-driven Applications: Techniques for Enriching Business Process Models

A key objective of any Service-driven architectural approach is to improve the alignment between business and information technology (IT). Business process management, service composition, and service orchestration, play major roles in achieving this goal. In particular, they allow for the process-aware integration of business actors, business data, and business services. To optimize business-IT alignment and to achieve high business value, the business processes implemented in process-aware information systems (PAISs) must be defined by domain experts, and not by members of the IT department. In current practice, however, the information relevant for process execution is usually not captured at the required level of detail in business process models. In turn, this requires costly interactions between IT departments and domain experts during process implementation. To improve this situation, required execution information should be captured at a sufficient level of detail during business process design (front-loading). As another drawback, existing methods and tools for business process design do not consider available Service-oriented Architecture (SOA) artifacts such as technical service descriptions during process design (look-ahead). Both front-loading and look-ahead are not adequately supported by existing business process modeling tools. In particular, for many process aspects, appropriate techniques for specifying them at a sufficient level of detail during business process design are missing. This chapter presents techniques for enabling front-loading and look-ahead for selected process aspects and investigates how executable process models can be derived from business process models when enriched with additional information

Embedding Service Logic into Business Model Design: The Case of Predictive Maintenance for Industry 4.0

Diffusion of new technology can be approached as a good marriage between business model innovation and technological innovation. With maturing and converging technological innovations ranging from Internet-of-Things, Artificial Intelligence, Blockchain to digital platforms comes a fundamental shift in how companies can do business and what can be offered. They enable greenfield services (i.e. services not pre-existing), including servitization of existing products to compete. Whilst businesses are experimenting with services for emerging domains like industry 4.0, research embedding service logic in business model design for delivering and diffusing greenfield services is nascent. Using a Design Science approach, this paper contributes a method (SL-BMD) for designing service logic embedded business models that forefronts how to incorporate the customer’s perspective. We instantiate and evaluate SL-BMD by charting the experimental journey of a Predictive Maintenance offering for manufacturing settings, and highlight implementation considerations for SL-BMD and the experimental case chosen

Ontology-Based Data Integration in Multi-Disciplinary Engineering Environments: A Review

Today's industrial production plants are complex mechatronic systems. In the course of the production plant lifecycle, engineers from a variety of disciplines (e.g., mechanics, electronics, automation) need to collaborate in multi-disciplinary settings that are characterized by heterogeneity in terminology, methods, and tools. This collaboration yields a variety of engineering artifacts that need to be linked and integrated, which on the technical level is reflected in the need to integrate heterogeneous data. Semantic Web technologies, in particular ontologybased data integration (OBDI), are promising to tackle this challenge that has attracted strong interest from the engineering research community. This interest has resulted in a growing body of literature that is dispersed across the Semantic Web and Automation System Engineering research communities and has not been systematically reviewed so far. We address this gap with a survey reflecting on OBDI applications in the context of Multi-Disciplinary Engineering Environment (MDEE). To this end, we analyze and compare 23 OBDI applications from both the Semantic Web and the Automation System Engineering research communities. Based on this analysis, we (i) categorize OBDI variants used in MDEE, (ii) identify key problem context characteristics, (iii) compare strengths and limitations of OBDI variants as a function of problem context, and (iv) provide recommendation guidelines for the selection of OBDI variants and technologies for OBDI in MDEE

A reference architecture for archival systems with application to product models

Pas de résumé en françaisNowadays, a major part of the information is in digital form. Digital preservation is essential to allowpeople to access information over time. From a computer science perspective, two major objectiveshave to be met to enable digital preservation: developing archival systems to manage the preserveddigital information, and select information representations that will facilitate the preservation. For complexinformation such as product models, these two objective are particularly hard to meet. Archivalsystems have to operate in a complex environment, interact with many different systems, and supportmay different business functions. Product model representations do not use all the possibilitiesof computer interpretation.Regarding the development of archival systems, the key is to determine what has to be described toprove that the archival system can effectively support the digital preservation. The Reference Modelfor an Open Archival Information System (OAIS) proposes a terminology to describe and comparearchives. The Audit and Certification of Trustworthy Digital Repository (ACTDR) provides criteria forthe certification of archives. One issue with these efforts is that there is not guidance on how to usethem within archival system descriptions.This thesis proposes a method called Reference Architecture for Archival Systems (RAAS) to describearchival systems implementations. RAAS relies on the DoD Architecture Framework to describethe various aspects of the archival systems. Moreover, RAAS provides an archival-specificterminology inspired by the OAIS Reference Model. RAAS also explains how the archival systemdescription can help for the ACTDR certification.RAAS is applied to a product model preservation case, to describe the various aspects of the archivalsystem. This description includes the interactions involving the archival systems, the archival systemfunctions, the definition of the preserved content, and the definition of the metadata. This descriptionformally refers to the OAIS terminology, and provides ACTDR certification evidence.This thesis also address the representation of product models by proposing the translation of productmodels from STEP to OWL. STEP is a standard for product model representation. The use ofOWL enables semantic relationship to enrich product information, and improve the search and theunderstanding of this information using data integration.The methodology used in this thesis can apply to other types of information, such as medical recordsDIJON-BU Doc.électronique (212319901) / SudocSudocFranceF

A Model Driven Approach to Model Transformations

The OMG's Model Driven Architecture (MDA) initiative has been the focus of much attention in both academia and industry, due to its promise of more rapid and consistent software development through the increased use of models. In order for MDA to reach its full potential, the ability to manipulate and transform models { most obviously from the Platform Independent Model (PIM) to the Platform Specific Models (PSM) { is vital. Recognizing this need, the OMG issued a Request For Proposals (RFP) largely concerned with finding a suitable mechanism for trans- forming models. This paper outlines the relevant background material, summarizes the approach taken by the QVT-Partners (to whom the authors belong), presents a non-trivial example using the QVT-Partners approach, and finally sketches out what the future holds for model transformations