Try ArKItect Watch videos Receive infos Contact us

Articles


CSDM’16 : Fast and extensive model based project plan building in nuclear industry
CSDM’16 : B4B, a system of system development based on systems engineering processes
CSDM’ 15 : Accelerating value creation in engineering through agile deployment of MBSE
ERTS ’14: Interoperability between a dynamic reliability modeling and a Systems Engineering process
CSDM ’13: Synchronize MBSE projects in a context of high diversity
CSDM’ 12 : How to turn spreadsheets into object oriented models
RITF 2012 : nov 12-15th
ERTS²’12 – An integrated approach to implement system engineering and safety engineering processes: SASHA Project
CSDM’11 – An integrated approach to implement ISO 15288 technical and management processes with arKItect
ICSSEA’11 – Seamless requirements management during development process
CSDM’10 – A hierarchical approach to design a V2V intersection assistance system
CSDM’10 – Seamless system engineering with arKItect
ERTS²’10 – An Advanced Engineering Framework experimented on a R&AE Electric Vehicle case
ERTS²’10 – System architecture, tools and modelling for safety critical automotive applications – the R&D project SASHA



CSDM’16 : Fast and extensive model based project plan building in nuclear industry

Authors : Christian Marie, Gilles Beuzelin, Samuel Boutin, Eric Nicole

Abstract :

Areva investigated a Model Based approach for setting up the Work Breakdown Structure of a nuclear plant project performed in collaboration with other key industrial partners of the energy domain.

Problems to be solved included:
- Manage collaboration between several industrial partners having their own processes, methods and approaches.
- Generate the Work Breakdown Structure (WBS) and Work Packages Descriptions (WPD) for the project.

Modeling benefits were:
- Convergence on a set of generic processes to be applied together with associated standard document types: specifications, justification, design, validation… documents.
- Quick production of WBS from the Product Breakdown Structure (PBS) (e.g. we issued a PBS with ~100 items and got a WBS with more than 100 Work Packages and 1000 documents and items) as a basis for cost analysis and planning.
- An objective and neutral support for project plan enabling more efficient collaboration

See our poster KI POSTER CSDM2016 PMO



CSDM’16 : B4B, a system of system development based on systems engineering processes

Authors : Yann CHAZAL, Philippe TOUSSAINT, Do-Hieu TRINH

Abstract :

arKItect SEA, a Systems Engineering (SE) modeler has been used by Renault and Bouygues Energies & Services to manage SE processes of a Batteries for Buildings (B4B) system. B4B is a concept reusing batteries of electric vehicles (second life), as a storage facility for energy management and renewables integration. The project started in 2012, was completely new from many viewpoints: new partnership with actors using different processes; innovative product and service offer connected and evolutive including safety concerns.
In order to overcome these challenges we have established a common SE model addressing the SE process: managing all SE data in a modeler, managing data consistency (requirements allocations, functional and system architecture), generating all specification documents toward developers and suppliers, enabling safety analysis faithfully with SE model.

See our poster KI POSTER CSDM2016 B4B



CSDM’ 15 : Accelerating value creation in engineering through agile deployment of MBSE

Authors : Samuel Boutin (KI) Eric Nicole (KI)

Our company Knowledge Inside (KI) has participated on November 23-25 2015 in CSDM 2015 Conference (Complex Systems Design & Management) as a partner of CESAMES the company organizing CSDM .
Samuel Boutin, founder of KI, presented to the audience a customer example in the automotive industry, the Renault company which deployed our software arKItect to help architects to collaborate in their vehicles engineering systems approach with specialists in disciplines involved in architecture definition.
His presentation is available here



ERTS ’14: Interoperability between a dynamic reliability modeling and a Systems Engineering process

Authors:

Gilles Deleuze1, Aurélie Léger1, Pierre Yves Piriou1, Sylvain Chabroux2

1EDF R&D, Clamart, France, {gilles.deleuze, aurelie.leger}@edf.fr; 2Knowledge Inside, Versailles, France, sylvain.chabroux@k-inside.com

Keywords: Systems Engineering, hybrid systems modeling, RAMS, dependability assessment, dynamic reliability, interoperability.

Abstract:

Industrial systems are often complex in terms of size, structure of interactions between systems, components, dynamic operational environment, ageing, etc. The dynamic reliability approach, covering a wider range of phenomena, is a convenient framework to model the behavior of such systems operating in a dynamic environment. However, there is a price to pay, e.g. in terms of data, state graphs, complexity of reliability tools, and combination of various engineering activities. In a previous study, focused on availability assessment of a large size hybrid system, two complementary approaches have been used, one using Stochastic Hybrid Automaton, and one using modeling and Monte Carlo Simulation. Both require a combination of various engineering activities, the use of computational power, data and component level models. A sound Systems Engineering process, benefiting from the improvement of most recent tools may be a fruitful approach. Although feasibility demonstrations have been done for usual approaches of dependability, the study of interoperability between dynamic reliability modeling and Systems Engineering has not the same level of achievement. We start with dynamic models based on Stochastic Hybrid Automaton, as they represent potentially the highest challenges. The case study is focused on the availability of a feed-water control system in a power plant steam generator.

On the basis of definitions of a Systems Engineering process, a Metamodel defines a framework for integrating the safety into SE processes. It supports a “hub automaton”, that is the key element for interoperability between the tools and activities needed for dynamic reliability assessment. The casual SE process supported by a tool like arKItect, supports the engineer in producing and managing the casual processes (description of functional and physical architectures, allocation of functions, preliminary assessment of requirements…).

Then, it is possible to describe the functional and failure features of the components. The RAMS engineer can model realistic failure/repairing scenarios and define redundancy policies for updating the dynamical allocation of functions caused by failure events. The “hub automaton” supports the translation of the dynamic dependability model into specific dynamic dependability tools.



CSDM ’13: Synchronize MBSE projects in a context of high diversity

Authors: Philippe TOUSSAINT (KI), Joe MATTA (KI)

Keywords: Data sharing, Synchronization, Change management, Diversity management

Abstract:

Current competitiveness and economic environment requires industrials to give priority to the optimization of developments. Different development projects are, whenever possible, grouped in a unique generic study that is later specialized into specific ones. For instance, instead of launching three projects to develop three vehicles of a new product range, automotive manufacturer launches one vehicle range development program that will be refined into three specific vehicles.

Yet it is important to consider upgradeability of each study, generic as well as specifics, and to keep all developments synchronized. Elements have to be identified with diversity criteria to control their affiliations to generic or specific studies. In such context, change management is a key issue. Teams working on specific projects shall be able not only to synchronize evolutions coming from the generic study but also to visualize and control modifications.

The main problems at hand are:

  • Synchronize data between studies
  • Manage diversity criteria
  • Manage versions

In this paper, we will investigate the possibility to manage shared data while creating or modifying them. The proposed process to control this exchange contains several topics:

  • Considering specific elements versus generic elements
  • Manage specificity as a diversity criteria
  • Share studies architecture elements using a common repository
  • Include versions management features
  • Visualize, control and propagate modifications

The result is to propose a way to efficiently share data between different studies while considering diversity criteria. This helps to optimize development costs by grouping studies, ensuring a good synchronization between teams and maintaining a good control of change management.

See our poster: KI Poster CSDM2013

 



CSDM’ 12 : How to turn spreadsheets into object oriented models

Authors : Samuel Boutin (KI) Joe Matta (KI)

Abstract :

It is very common to see engineers using spreadsheets (e.g. excel) as a small database. For instance, a data dictionary will be a spreadsheet with a column for the data identifier and then different columns for data attributes (e.g. data type, step, min and max value). An advanced use would be to add two columns for functions producing and consuming the data resulting in a cross-reference dictionary. Then many other applications exist related to project management, diversity management, requirements management and specialized fields topics. The important fact is that spreadsheets generally capture a specialized field specification and sometime very transverse project information and that together they form often a big part of a system specification.

A big part of engineering legacy data is provided in this form in many industries. This is partly due to the many functions of spreadsheet e.g. for billing and counting. So using spreadsheet allows most of the time simple checks for data integrity.  A positive aspect is that spreadsheets contain already structured data w.r.t like word or rich text descriptions. But this does not help solving a major problem in systems engineering: keep all the different spreadsheet and specification documents aligned during the life of a project.

In this paper we investigate the possibility to upload a wide variety of spreadsheet descriptions into a synchronized system specification. To reach this goal, we proceed with the following steps:

-       Provide a semantics to each spreadsheet

-       Link this semantics to a part of a DSL (Domain Specific Language)

-       Organize the semantics of all spreadsheets together

-       Import the spreadsheet content in a unified model

So as a result, we raise for many organizations the opportunity to leapfrog from a wide variety of semi-structured specifications to a synchronized multi-aspect specification which is at the same time a model based design approach.

This concept extends more generally to the possibility to transform a database into an object oriented model and conversely. We also discuss how this relates to UML profiles, BMPN, and DSL initiatives.

Get the full article



RITF 2012 : nov 12-15th

Knowledge Inside present a paper with RENAULT.

From November 12 to 15th, runs the symposium RITF: Research and Innovation for the transport of the future.
Knowledge Inside present a publication “Model Based approach applied on complex systemrepresentation: R&AE Electrical Powertrain project”.

A key challenge in system design is the ability of synchronizing the work of several teams operating on different aspects of the system. The publication highlights the model based approach to complex systems design by using arKItect SEA in a practical case.

Read the abstract

 



ERTS²’12 – An integrated approach to implement system engineering and safety engineering processes: SASHA Project

Authors
Hycham Aboutaleb (KI), Mohamed Bouali (KI), Morayo Adedjouma (Delphi), Emilia Suomalainen (KI)

Abstract
In a purpose of a safe system design, the SASHA project partners, through the graphical software arKItect® have implemented a design process coupling the system engineering process with the safety engineering process. They address especially automotive area through the ISO 26262 standard that appears as an answer for a unified requirements set to fulfill in the purpose of safe vehicle design. The cited standard needs a combined approach to be implemented (workflows, administration, models representation. This paper aims at showing how this safety engineering process is integrated in the whole system design process as proposed and implemented in SASHA project including the system specifications phase and the system design process. This enables to perform the system risk analysis, which is the second step in the safety engineering process.

Keywords
system modeling, safety engineering process, safety analysis, system architecture, integration of systems and safety engineering

Register or log-in to see the downloadable content




CSDM’11 – An integrated approach to implement ISO 15288 technical and management processes with arKItect

Authors
Hycham ABOUTALEB, Samuel BOUTIN – Knowledge Inside (KI)

Abstract
The product life cycle management is a very important issue in the industrial processes in such way that it impacts all the activities related to the product. One of the well-known standards to address this issue is the ISO 15288 which enclose a set of processes that cover the life cycle of a product including Technical Processes (including system design) and Management Processes (including work breakdown and management). The heterogeneous targets of the processes lead to quasi complete separation between studies that cover technical processes and those that cover management processes. In addition only few studies cover the interactions between the two processes. However, a modification in one of the two processes has a strong impact on the other.

Our solution, based in an implementation based on arKItect software, aims to gather the two processes (technical and management) in the same representation space and to “break the wall” between them. The proposed methodology is built into 3 main steps:
1) Capture, refine and formalize Requirements;
2) Identify needed System Concepts;
3) Suggest several System Solutions.

All elements stated in this methodology share the same storage and representation space which allows making an easy traceability and impact analysis processes.

Register or log-in to see the downloadable content




ICSSEA’11 – Seamless requirements management during development process

Authors
Mohamed BOUALI, Hycham ABOUTALEB, Samuel BOUTIN – Knowledge Inside (KI)

Abstract
In a purpose of efficient requirement management, the company Knowledge Inside (KI), through its software arKItect® has implemented different requirement management methods. This paper aims at showing different items contributing to requirement management activities as proposed and implemented by KI in several industrial projects. Authors limit their contribution to practical issues in requirement statement, refinement, verification, validation, etc. and the close connection between requirements management processes and other processes in the system development cycle. Then, different representations (or modeling) of requirements: as objects, as flows and hybrid representations will be treated. The choice of one representation instead of another implies some consequences that will be shown.

Keywords
Requirements Management, Refinement, Traceability, System Engineering

Register or log-in to see the downloadable content




CSDM’10 – A hierarchical approach to design a V2V intersection assistance system

Authors
Hycham Aboutaleb (KI), Samuel Boutin (KI), Bruno Monsuez (Ensta)

Abstract
The key challenge in enhancing intersection safety is to identify vehicles that have a high potential to be involved in a collision as early as possible and take preven¬tive action thereof. Such a system design and implementation needs an analysis phase during which the system is analyzed and decomposed. Given that most large-scale complex engineering systems need to be simplified and layered before being designed, a hierarchical approach is necessary to ensure a global and struc-tured understanding of the whole system, including involved stakeholders, use cases and associated requirements. Despite the fact that use cases in themselves are quite intuitive, the process around them is a much bigger challenge since it usually varies from one situation to another. In this paper we analyze and model a cooperative intersection safety system using a hierarchical method to represent use cases. This approach simplifies the understanding of the intersection crossing problem by applying transformations that reduce its complexity. We also show that we get a first functional architecture of the system based on the use cases analysis.

Keywords
Intersection, Collision, Complexity, Use case, Hierarchy, Vehicle-to-vehicle System

Register or log-in to see the downloadable content




CSDM’10 – Seamless system engineering with arKItect

Authors
Hycham Aboutaleb (KI), Samuel Boutin (KI), Sylvain Chabroux (KI)

Abstract
According to INCOSE, System Engineering is an interdisciplinary approach and means to enable the realization of successful systems. To follow INCOSE guidelines, a platform that covers both phases (specifications and design phases) and steps is needed. arKItect® is a tool that offers a seamless environment for System Engineering, covering the specification phase steps (System Life Cycle,  Requirements statement, System Use Case, Functions definition, Requirements allocation) and the design phase steps (Requirements Refinement, Internal Functional analysis, Requirements Allocation, System Definition, Internal functions allocation). In this poster, a vehicle is roughly designed, with a view dedicated to each step of the design.

Keywords
Intersection, Collision, Complexity, Use case, Hierarchy, Vehicle-to-vehicle System

Register or log-in to see the downloadable content




ERTS²’10 – An Advanced Engineering Framework experimented on a R&AE Electric Vehicle case

Authors
Sylvain Chabroux (KI), François Colet (Renault), Joe Matta (KI)

Abstract
This article describes modeling activity experimented on an Advanced engineering case of Zero Emission Vehicles at Renault. A key advantage of our approach is that system architecture and requirements management at all the stages of the system life cycle are managed in a unique data model and unique database. It reviews conceptualization and production process of a complex system. It presents a spectrum of activity modeling techniques, ranging from a widely used systems engineering diagram, to continuous flow modeling. The techniques include use case definition, requirements elicitation, system architecture definition and finally Electric and Electronic architecture. The article also describes refinements of modeling activity using arKItect© tool.

Keywords
system modeling, project process, use case, requirement and architecture modeling, model in the loop, fault injection

Register or log-in to see the downloadable content




ERTS²’10 – System architecture, tools and modelling for safety critical automotive applications – the R&D project SASHA

Authors
J. Langheim (ST),  B. Guegan (ST), L. Maillet-Contoz (ST), K. Maaziz (Delphi), G. Zeppa (Delphi), F. Philippot (ESG), S. Boutin (KI), H. Aboutaleb (KI), P. David (UTC)

Abstract
SASHA is a project involving complementary partners leveraging on MBSE know-how in a cooperative and cross experienced environment contributing to a better understanding of the new ISO26262. However, the introduction of this new standard requires a change in the development process, in the communication between the partners in the supply chain and the development of new tools helping to minimize the impact of additional requirements on the development process through this new standard. This article will first expose the challenges of safety critical automotive applications, before presenting the SASHA use case. Then, the Model Based System Engineering (MBSE) approach, which frames the ISO 26262 application in SASHA, will be introduced. The arKItect® tool supporting this methodology is detailed followed by the introduction of the TLM language used for microcontrollers design and validation within SASHA developments.

Keywords
functional safety, model based design, mechatronics, driver assistance, development tools, dependability, system architecture partitioning, multiple core architecture

Register or log-in to see the downloadable content





Copyright © Knowledge Inside 2010-2013 - arKItect is a trademark of Knowledge Inside. Patent pending - Legal Information

Knowledge Inside
SAS au capital de 336 250 euros au RCS Versailles 488 446 543
Siège : 7C rue Jean Mermoz - 78000 Versailles - France