437 research outputs found
Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience
No full textInternational audienceBehrang MORADI, Nicolas DACLIN, Vincent CHAPURLAT ([email protected]) LGI2P, Ecole des Mines d'Alès Systems of Systems Engineering A system of system (SoS) is an integration of a finite number of constituent systems which are independent and operable, and which are networked together for a period of time to achieve a certain higher goal. 1 [Jamshidi, 2009]. SoS are composed of separate constituent systems and have a majority of the following five characteristics 2 [Maier, 1998]: Operational independence-constituent has a purpose of its own and can be operated independently, without the need to interact with other systems. Managerial independence-constituent are controlled by different authorities (or system owners), they not only have operational independence but are, actually, operated independently. Emergent behavior-behaviors are only exhibited at the SoS level and cannot be achieved by any of the constituent systems operating independently of the other constituent systems. Evolutionary development-SoS is not created once and for all, but evolves as constituent systems, or functions thereof, are added, removed, or modified. Geographical distribution-the concern of SoSE is primarily with the information exchange between constituent systems. Fig.1. A Transport System-of-Systems Resilience Ability to prevent, prepare for, respond to, adapt to disruptions and to mitigate the consequences as well as to recover in timely and efficient manner including preservation, restoration of services 3 [Cutter et al. 2013]. Fig.2. Illustration of essential resilience capabilities
Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience
No full textInternational audienceBehrang MORADI, Nicolas DACLIN, Vincent CHAPURLAT ([email protected]) LGI2P, Ecole des Mines d'Alès Systems of Systems Engineering A system of system (SoS) is an integration of a finite number of constituent systems which are independent and operable, and which are networked together for a period of time to achieve a certain higher goal. 1 [Jamshidi, 2009]. SoS are composed of separate constituent systems and have a majority of the following five characteristics 2 [Maier, 1998]: Operational independence-constituent has a purpose of its own and can be operated independently, without the need to interact with other systems. Managerial independence-constituent are controlled by different authorities (or system owners), they not only have operational independence but are, actually, operated independently. Emergent behavior-behaviors are only exhibited at the SoS level and cannot be achieved by any of the constituent systems operating independently of the other constituent systems. Evolutionary development-SoS is not created once and for all, but evolves as constituent systems, or functions thereof, are added, removed, or modified. Geographical distribution-the concern of SoSE is primarily with the information exchange between constituent systems. Fig.1. A Transport System-of-Systems Resilience Ability to prevent, prepare for, respond to, adapt to disruptions and to mitigate the consequences as well as to recover in timely and efficient manner including preservation, restoration of services 3 [Cutter et al. 2013]. Fig.2. Illustration of essential resilience capabilities
Formalization, Evaluation of non-functional properties for system of system engineering: Application to Resilience
No full textInternational audienceBehrang MORADI, Nicolas DACLIN, Vincent CHAPURLAT ([email protected]) LGI2P, Ecole des Mines d'Alès Systems of Systems Engineering A system of system (SoS) is an integration of a finite number of constituent systems which are independent and operable, and which are networked together for a period of time to achieve a certain higher goal. 1 [Jamshidi, 2009]. SoS are composed of separate constituent systems and have a majority of the following five characteristics 2 [Maier, 1998]: Operational independence-constituent has a purpose of its own and can be operated independently, without the need to interact with other systems. Managerial independence-constituent are controlled by different authorities (or system owners), they not only have operational independence but are, actually, operated independently. Emergent behavior-behaviors are only exhibited at the SoS level and cannot be achieved by any of the constituent systems operating independently of the other constituent systems. Evolutionary development-SoS is not created once and for all, but evolves as constituent systems, or functions thereof, are added, removed, or modified. Geographical distribution-the concern of SoSE is primarily with the information exchange between constituent systems. Fig.1. A Transport System-of-Systems Resilience Ability to prevent, prepare for, respond to, adapt to disruptions and to mitigate the consequences as well as to recover in timely and efficient manner including preservation, restoration of services 3 [Cutter et al. 2013]. Fig.2. Illustration of essential resilience capabilities
A formal verification framework and associated tools for enterprise modeling : application to UEML
No full textThe aim of this paper is to propose and apply a verification and validation approach to Enterprise Modeling that enables the user to improve the relevance and correctness, the suitability and coherence of a model by using properties specification and formal proof of properties
An Interface Pattern Model for Supporting Design of Natively Interoperable Systems
No full textPart 3: Industrial PapersInternational audienceThis article focuses on the interoperability feature seen as a specific requirement. Indeed, any complex system (e.g. a train, an organisation or an IT system) need to interact with other systems, thereby forming a heterogeneous environment. All these systems are not necessarily designed to function properly and efficiently with one another, whether from a conceptual, technical, behavioural or organizational standpoint. This paper highlights what seems to be relevant in terms of conceptual definitions and modelling framework whenever a (group) of engineer(s) intends to design what we call here a “natively interoperable system” or, at least, a system maximizing its interoperability capabilities. To proceed, as a first prerequisite, a definition of the concept of interoperability is here proposed for complex system engineering. The second prerequisite consists of establishing the needs of a design team assigned to design such “natively interoperable system”. An interface pattern model with sufficient generic, formal and pragmatic qualities is then proposed and illustrated briefly
Interoperability as a Key Concept for the Control and Evolution of the System of Systems (SoS)
No full textPart 1: Full PapersInternational audienceA coalition of enterprises wanting to collaborate, and more generally a Collaborative Network of Organizations (CNO), can conceptually be assimilated as a System of Systems (SoS) presenting a number of characteristics to respect all over its life cycle. Interoperability is one of these characteristics (both functional and non-functional), which is from our point of view, essential in order to guarantee the control of the SoS, its behavior and the fulfillment of its mission(s). Moreover, it ensures the reaction of the SoS to deal with some risky situations and with potential local or global deficits during its functioning. In this paper, we propose to determine the relation between the current level of interoperability of the SoS and its functioning whatever may be its situation. A matrix shows how this relation evolves taking into account several characteristics of the SoS, particularly its capacity to respect interoperability requirements (Compatibility, Interoperation, Autonomy and Reversibility) and the so-called analysis perspectives of the SoS: Performance, Integrity and Stability. This relation is requested in order to permit and to guide SoS behavioral simulation currently in development. Thus, a set of indicators is derived and formalized
A contribution for dismantling of nuclear facilities: a functional pattern for dismantling operations and indicators design and management
No full textInternational audienceOptimizing nuclear installation decommissioning and dismantling operations is an ongoing quest. Faced with the complexity of this activity, the Model Based System Engineering promotes relevant principles and modeling techniques. It motivated then the definition of a functional generic pattern model of the waste package production line and the decommissioning of the facility. It proposes a global and generic functional architecture of such system aiming to reduce the level of the pollutant. This pattern is coupled with a process of logistics. Six functions are combined to define this functional pattern. The application of this pattern model to a case of waste recovery in a pit shows the relevance of model-based system engineering approach, reducing the weight of the history in the development of scenarios by optimizing the control means for the nuclear safety and product quality
A contribution to the System of Systems Engineering : multi-view modeling and analyzing the the impact of the interoperability
No full textUn Système de Systèmes (SdS ou System of Systems - SoS) est un système complexe résultant de l'assemblage de composants existant ou à créer, de nature hétérogène (e.g. des systèmes techniques ou socio techniques appelés sous-systèmes, dispositifs techniques, acteurs ou organisations, ou encore des infrastructures plus ou moins complexes pouvant être perçues comme des SdS). Cet assemblage est nécessaire à ces composants pour agir et interagir avec d'autres composants afin de réaliser une mission commune, éventuellement limitée dans le temps et qu'aucun de ces composants ne pourrait réaliser seul. De fait, un SdS possède des caractéristiques particulières comme l'hétérogénéité, la possible émergence de propriétés et de comportements durant les interactions entre les composants et à leurs interfaces, la préservation de l'autonomie managériale et opérationnelle de ces composants, la répartition géographique de ces composants, un cycle de vie particulier, etc. L'Ingénierie Système (IS ou Systems Engineering - SE) propose et promeut un ensemble de concepts, de processus maintenant standardisés, l'usage incontournable de modèles (on parle alors de Model Based Systems Engineering – MBSE) et de bonnes pratiques pour concevoir et réaliser des systèmes complexes. Du fait de ses caractéristiques particulières, la conception et le développement d'un SdS (SoS Engineering - SoSE) est elle-même particulière même si elle emprunte à l'IS nombre de traits communs. En effet, le choix et l'assemblage des composants, leurs besoins en termes d'interfaces pour faciliter leurs interactions entre eux et avec l'environnement du SdS, les propriétés et comportements émergents entres autres caractéristiques, impliquent des efforts de la part des personnes en charge d'un SdS. Il faut alors, pour les aider dans leurs tâches, conceptualiser et développer des langages, méthodes et outils supports. Le SoSE a en effet des besoins particuliers de modélisation, de vérification, de validation de modèles. Il nécessite également de disposer de moyens de simulation et d'évaluation du comportement global du SdS et de ses propriétés, par exemple, lorsqu'il doit faire face à des événements redoutés (e.g. ajout, modification ou retrait d'un composants, évolution de la mission, etc.). Le but est que ces personnes puissent progresser en confiance et leur donner les moyens de fournir des modèles de SdS avec lesquels l'analyse des propriétés du SdS devient possible, avant même d'alimenter les activités de décision et d'optimisation en cours de conception du SdS. Ce travail s'intéresse à une propriété importante pour les SdS et leurs composants : l'interopérabilité. Elle est vue ici comme une exigence sommative des capacités et des capabilités des composants à être et rester compatibles, à inter opérer efficacement, à rester autonome pendant l'interaction et à la réversibilité de la relation d'interaction lorsque celle-ci s'achève. L'interopérabilité garantit donc ou, à défaut, maximise la capacité d'un composant à travailler sans perte et harmonieusement avec un autre composant, dans différentes situations et avec un niveau de performance attendu, tout en respectant un ensemble d'autres exigences venant des parties prenantes impliquées ou concernées par le SdS visé.Cette thèse consiste à formaliser et à développer une méthode pour accompagner la modélisation, la vérification de modèles et l'analyse de l'interopérabilité dans un SdS. En conséquence elle repose sur 1) un ensemble de concepts et de relations entre ces concepts pour décrire un SdS et la propriété d'interopérabilité, 2) des langages spécifiques de modélisation (DSML) pour manipuler ces concepts et relations et donc créer des « modèles » de SdS, 3) d'un processus opératoire et 4) d'outils de modélisation, de vérification des modèles, de simulation du comportement et d'évaluation de l'interopérabilité et de son influence sur la performance, la stabilité et l'intégrité du SdS en cours de fonctionnement.A System of Systems (SdS) is a complex system which is seen as a group of, in most cases, existing and heterogeneous entities (e.g. technical systems or socio-technical called subsystems, actors or organizations or even complex infrastructures that can be considered as SoS) assembled together in order to interact, during a timeframe to produce some kind of capabilities, products or services and to achieve a global mission that a system alone cannot fulfill. Moreover, the SoS has some particular characteristics such as: Operational Independence and Managerial Independence (autonomy), Evolutionary Development, Emergent Behavior, Geographic distribution, Connectivity and Diversity etc. The systems engineering (SE) provides and promotes a set of concepts, principles, processes, standards, an essential use of models (Model Based Systems Engineering - MBSE)and a good practice to design and conduct complex systems. However, even if the System of Systems Engineering (SoSE) shares some common features with the SE, SoS characteristics, assembling, interfacing and interactions between its entities, induce an additional effort, required from the persons responsible of the SoS, over the SE. Therefore, and in order to help these persons in their tasks, it is necessary to conceptualize and develop languages, methods and tolls supports. The SoSE has special needs in terms of modeling and models' verification and validation. Moreover, it requires to have means to simulate and evaluate the global behavior of the SoS and its properties, for example, when it has to face dangerous events (e.g. adding, removing or modifying a component, mission's evolution etc.). The aim is to help designers and engineers to progress in confidence by giving them the means to have SoS models with which the analysis of the SoS properties becomes possible. In this work, a particular attention is given to an important property of the SoS and its components: the interoperability. It is seen here as a summative requirement of components capacities and capabilities to remain compatible, to interoperate and to remain autonomous during the interactions and reversible after it. The interoperability guarantees or, by default, maximizes the capacity of a component to work, harmoniously and without any loss, with another component, in various situations and with an expected level of performance while respecting a set of requirements (stakeholders involved or concerned by the SoS).This thesis consists in formalizing and developing a method to support modeling, model's verification and the analysis of the interoperability in a SoS. Therefore, it is based on 1) a set of concepts and relationships between these concepts to describe a SoS as well as the interoperability property, 2) Domain Specific Modeling Languages (DSMLs) to manipulate these concepts and relationships and thus creating a SoS' model, 3) an operating process and 4) a modeling and verification tools, simulating behavior and evaluation of the interoperability and its impact on the SoS performance, stability and integrity while it is operating
Contribution to the development of interoperability in enterprise : towards an anticipative approach to detect interoperability problems in collaborative processes
No full textL'interopérabilité revêt un enjeu majeur pour l'industrie et son absence peut être vue comme un des principaux freins à un travail collaboratif pertinent et efficient. C'est particulièrement le cas dans le cadre de processus collaboratifs aussi bien publics (inter entreprises) que privés (intra-entreprise). Il parait donc pertinent d'analyser et de détecter d'éventuels manques ou défauts d'interopérabilité dans des (parties d') entreprises impliquées dans un processus collaboratif avant même que ce processus ne soit implémenté. Les recherches sur l'interopérabilité ont montré l'intérêt de mesurer et d'évaluer l'interopérabilité avec la proposition de cadres et de modèles de maturité. Cependant, la détection et l'anticipation de problèmes d'interopérabilité restent peu étudiés et outillés. Les travaux de recherche proposés dans cette thèse se développent dans un contexte d'ingénierie de processus guidée par les modèles. Ils se proposent d'utiliser des techniques de vérification formelle pour détecter différents types de problèmes ou de présomption de problèmes d'interopérabilité. Ceci implique, dans un premier temps, de définir les besoins particuliers en interopérabilité devant être pris en compte dans un contexte collaboratif. Dans un second temps, il est nécessaire de formaliser ces besoins en un ensemble d'exigences d'interopérabilité, de manière aussi formelle que possible. Ceci abouti à la proposition de trois classes d'exigences d'interopérabilité respectant le cycle de vie d'un processus collaboratif : les exigences de compatibilité, les exigences d'interopération et les exigences de réversibilité. Enfin, ces exigences doivent être vérifiées en se référant aux modèles du ou des processus étudiés.Interoperability is becoming a crucial issue for industry and a lack of interoperability can be seen as an important barrier to a collaborative work, especially on collaborative process both public (inter-enterprise) and private (intra-enterprise). Indeed, interoperability characterises the ability of any enterprises to interact within a collaborative process. Prior to any effective collaboration, it is necessary to inform enterprises that aim to work together, if they are able to interoperate. Researches in interoperability have shown the benefits of the measurement and the evaluation of interoperability through the proposition of several frameworks and maturity models. However, approaches to detect and anticipate interoperability problems are either not existing or few considered. The research works proposed in this thesis are developed in a context of process engineering-driven models and propose to use formal verification techniques to detect different types of problems or suspected problems of interoperability. On the one hand, this means to be able to define the specific needs of interoperability. On the other hand, it requires to formalise these needs as a set of requirements that are unambiguous and, as formal as possible. Three classes of interoperability requirements are defined: compatibility requirements, interoperation requirements and reversibility requirements. Finally, interoperability requirements must be checked according to the studied process model
Contribution to systems architecture evaluation in System Engineering context applied to mechatronic systems
No full textLa conception d'un système complexe est une étape cruciale. Ce constat est particulièrement vrai dans le cadre de la conception de systèmes mécatroniques, multi technologies et nécessitant une approche pluridisciplinaire et collaborative. Nous nous plaçons ici dans le cadre de l'Ingénierie Système (IS) qui se focalise sur la définition des besoins et des exigences, la recherche de concepts, puis la définition d'architectures fonctionnelles et organiques d'un système. L'IS promeut pour cela un certain nombre de concepts, de processus et une démarche maintenant éprouvés en industrie, souvent normalisés tout en faisant l'objet de nombreux travaux de recherche. En particulier, nous nous intéressons ici à un processus dit support de l'IS, le processus d'évaluation. Nous nous focalisons particulièrement sur l'évaluation de l'efficacité puis la comparaison des différentes solutions d'architectures fonctionnelles et organiques d'un système mécatronique qui émergent invariablement de la conception. Le but de ce processus est de guider et d'aider au choix, parmi ces architectures candidates mais souvent incomplètes ou à tout le moins immatures en début de conception, d'une solution permettant de maximiser la satisfaction des besoins de toutes les parties prenantes du système. La mise en œuvre de cette évaluation se heurte à plusieurs difficultés. Tout d'abord, la vision consensuelle et unifiée de données, informations et connaissances mais aussi des activités proprement dites d'évaluation, ‘au-dessus' des métiers impliqués dans la conception, reste limitée. C'est un premier verrou traité dans ces travaux car son absence est ainsi un frein à l'évaluation objective et partagée d'une solution. Pour contribuer à cette vision consensuelle, il est proposé un modèle conceptuel des données de l'évaluation en ingénierie système. Ensuite, l'estimation des conséquences des choix tout au long d'une conception résolument itérative et qui procède donc à petits pas, le traitement d'objectifs multiples voire contradictoires et la prise en compte de l'incertitude propre à la conception sont autant de problèmes classiques en conception. C'est le verrou central sur lequel ce travail a porté. L'estimation des choix de conception est traitée d'abord par une formalisation des liens de traçabilité entre les exigences, fonctions et composants de la conception. Cette formalisation est un préalable à la détection et correction des incohérences des liens de traçabilité en vue de l'identification automatisée des impacts potentiels des choix d'élément d'architecture sur les différents critères de satisfaction du système à faire. Une articulation entre les modèles de comportement du système à faire et les modèles de décision est ensuite proposée pour agréger le degré de satisfaction des objectifs de la conception, et ainsi assurer la gestion des objectifs multiples voire opposés des parties prenantes. Des techniques d'évaluation qualitative sont enfin proposées afin de trier les alternatives de solution de conception selon leur degré de satisfaction en tenant compte du niveau de maturité croissant mais incertain de la solution. Enfin, on peut regretter le manque d'un environnement de travail permettant de modéliser le système et de procéder aux analyses et évaluations de la solution. Les deux contributions synthétisées ci-dessus ont donc fait l'objet d'une intégration dans un atelier d'IS existant, offrant ainsi un continuum entre activités de conception et activités d'évaluation. Le résultat est ainsi un guide méthodologie outillé pour l'évaluation de systèmes mécatroniques en conception. Mots clés : Ingénierie Système, conception, évaluation, système complexe, système mécatronique, solution d'architecture, traçabilité, analyse qualitative.The design step of a complex system is crucial. This observation is particularly true, when considering mechatronic, multi-technological systems, which require a multidisciplinary and collaborative approach. Our work is based on the System Engineering (SE) framework, which focuses on the needs and requirements definition, the conceptual design, and the definition of functional and organic architectures of a system. For this purpose, SE promotes some concepts, processes, and an approach currently widely practiced in the Industry, and even standardized while being a much studied research topic. More precisely, we are interested in a so-called support process of SE, the evaluation process. We are focusing on the effectiveness evaluation and then on the comparison of different functional and organic architecture solutions of a mechatronic system, which emerge invariably from the design. The goal of this process in guiding and helping to choose a solution among candidate architectures, often incomplete or immature in preliminary design, allows maximizing the satisfaction of the systems' stakeholders needs. However, the implementation of this evaluation faces to many difficulties. The consensual and unified vision of data, information, knowledge, and evaluation activities, above specialized engineering teams involved in the design, is still limited. Indeed, the lack of this common vision limits the objective and shared evaluation of a given solution. This is a first problem that we are addressing in our work. To contribute to this common vision, a conceptual model of evaluation data in SE is proposed.Subsequently, the estimation of the choices made all along such an iterative design, and which therefore proceeds by small steps, the management of multiple objectives sometimes contradictory and the consideration of the uncertainty inherent to design are classic problems in design. This constitutes the main problem which our work is answering. The estimation of the consequences of design choices on the system performance is first addressed by a formalization of traceability links between the requirements, functions, and components of the design. This formalization is prior to the detection and correction of inconsistencies of traceability links, in order to automatically identify potential impacts of the architectures' elements choices on different satisfaction criteria of the System Of Interest (SOI). An articulation between the SOI behavioral models and decision models is afterwards proposed for aggregating the satisfaction level of the design objectives, and then ensure the management of multiple and even contradictory objectives of the designers. Qualitative evaluation techniques are finally proposed for sorting the alternative design solutions according to their satisfaction level while considering the increasing maturity level but uncertain of the solution.Lastly, we often denote the lack of integrated environment for modeling the system and proceeding to the analyses and evaluations. The two above synthesized contributions have been integrated into a SE framework, offering a continuum between design activities and evaluation ones. The result is thereby a methodological and tooled guide for mechatronic systems evaluation during design. Keywords: System Engineering, design, evaluation, complex systems, mechatronics, architecture solution, traceability, qualitative analysis
- …
