Browse Topic: Traceability

Items (21)
Feedback on Application of MBSE to an Avionics Subsystem2018-01-192210/30/2018
In avionics domain, currently most engineering efforts and costs come from integration, verification and validation activities. Each error found on requirements during product verification or validation requires a full engineering cycle to manage the change: impact analysis, design, realization, integration, verification and validation again. Hence, ensuring early and continuous validation of requirements in the engineering life cycle, becomes more and more crucial. In this paper, a Model-Based Systems Engineering (MBSE) approach is proposed. The proposed approach relies on SysML models and is composed of modelling tasks to capture requirements and to structure functional interfaces and functions. This approach has been applied in the frame of SAE ARP4754A aerospace recommended practices. This paper also provides feedback about the application of the proposed approach on an industrial avionic case study known as the Onboard Maintenance System by a team mainly used to document centric approach until recently. The feedback concerns the practical use of models to support functional part of the following processes: requirements capture, requirements validation, and top-level part of development of system architecture. After presenting the pilot case, results are given and discussed on several points: the lessons learned during and after application of the MBSE approach to identify use cases, to define black box scenarios, and to build the top-level functional architecture. Comments about the approach are given, e.g. use cases granularity, modelling stop criterion, communication between systems. Then, measured advantages and drawbacks of this modelling approach are discussed. The paper finally describes the challenges identified for wider adoption in the company and the remaining points of attention when extending the approach on a larger project.
Tang, JianZhu, ShaofanFaudou, RaphaelGauthier, Jean-Marie
Five Strategies for Improving Aerospace Supply Chain Quality Management and Performance2014-01-22319/16/2014
Aerospace suppliers face the daunting task of constantly improving time-to-market, reducing cost of quality and turning compliance into a competitive advantage. Managing to these constraints while staying profitable is a challenge faced by the entire aerospace supply chain face today. The intent of this presentation is to share five lessons learned on how aerospace suppliers can optimize for these three constraints while growing their businesses. The first is electronically enabling traceability both within a multi-tier supply chains and throughout suppliers. Automating traceability at the shop floor improves quality management and accelerates compliance. Specific methodologies and metrics used to accomplish this will be provided. Second, lessons learned from implementing Manufacturing Execution Systems (MES) showing how shop floor visibility has a direct effect on supplier performance is illustrated with case studies and metrics. Third, lessons learned in making compliance pay by benchmarking performance to AS9100C, ISO9001, and ITAR standards is provided. Fourth, integrating engineering, program management, project management office, accounting and finance workflows together provides exceptional insight into the value of a project in real-time. Examples and metrics of performance will be provided illustrating this point as well. The final lesson learned is that having a single, unified system of record across a diverse aerospace supply chain leads to greater gains in collaboration and communication, leading to proven profitability gains.
Columbus, Louis
Innovation in Product Data Management to Unlock the Efficiency Potential of the Company2013-01-21239/17/2013
From a past perspective, System Engineering was able to control the product data accuracy with respect to its requirements and towards product certification and delivery avoiding operational disruptions in the development lifecycle. But we usually do it by increasing the complexity of the product data management and administration what makes heavier the product integration. The trends indicate that the product complexity is intensifying and that the increasing load rate of changes will create serious efficiency disruptions if we persevere with today System Engineering approaches. New System Engineering paradigm is then proposed. It conducts to an innovative management of product identification and business integration. It is supported 4 key pillars: The Semantic Product Identification The Business Driven Intelligence The Product Life-Cycle Social Management The Data Management of Things It is highlighted the wide range of possibilities that could offer new product data aggregation laws based on correlating semantic context information. The other elements of the new PDM paradigm add an apparatus of synergy, management and lean architecture principles of the solutions. The benefits of a new integrated Systems Engineering will grant: 1) better data continuity and integration across domains, lifecycle & supply chain; 2) intensify data re-use; 3) create easy data access, consistency & transparency; 4) enable flexible interfaces between business processes; 5) Ease traceability of information and processes; and 6) Increase user acceptance on PLM solution approaches.
Martinez-Ablanedo, Moises
Continuity of a System Engineering Referential Repository Applied on an Aerospace Use Case2012-01-214210/22/2012
A major challenge of a System Engineering approach lies in its ability to promote an efficient Process/Method/Tools environment that leads to an efficient and accurate System Referential Repository. The key factor is the definition of a centralized system referential repository that is shared by the various stakeholders involved in the success of industrial projects, including customers, system architects, hardware and software development suppliers, validation and safety teams. This paper describes the development of a use case modeled with the most appropriate tool-chain that fulfills the above System Engineering expectations. Based on standard documents (INCOSE Handbook, ARP4754) and on experience achieved by the development of many System Engineering projects, a methodological approach is defined. This approach includes the complete process from textual requirements, to operational description, to functional breakdown, to technical architecture, and finally to certified software generated from models. An aerospace use case is selected that covers the main steps of this System Engineering approach. Based on an existing benchmark framework that includes cartography of tools, criteria, test means and use cases of several System Engineering tools, the SCADE® tool chain is selected because it offers an appropriate solution for the approach. The main tool that is used is SCADE System, which is suited for the System Engineering steps of the approach, including operational and functional analysis, architecture definition and allocation. Several graphical views of the Use Case, including subsystem parts, are developed for operations, functions, interfaces, components, all using a subset of the SysML standard (IBDs and BDDs diagrams) that is embedded into SCADE System. The SCADE Suite tool, for control logic and algorithm design, is also used for the modeling of some parts of the software behavior. The consistency checks and traceability links applied to the several layers of information embedded into the System Referential Repository are provided by the SCADE tool-chain. As demonstrated by the Use Case, SCADE System is tailored to the main requirements of the System Engineering process. SCADE System's graphical representation facilitates the communication among all of the teams. A System Referential Repository is built that is continuously used and enriched by all of the project stakeholders in the course of the development. Next step consists of improving some other System Engineering key tasks, such as modeling and simulation of a sequence of operations and functions, discrete modeling and simulation (state/event/transition) for the behavior of functions, continuous modeling and simulation for the behavior of the component of the product architecture, and support for the safety analysis based on FMEA generated from model.
Vuillemin, Bruno
Items per page:
1 – 21 of 21