Browse Topic: Traceability
The objective of this paper is two-fold. Firstly, provide guidance to best implement end to end traceability from program requirements to physical implementation, and Secondly provide techniques to review and understand large scale complex systems. Even with a Digital Engineering Environment (DEE) being an enabler towards applying Systems Engineering practices to develop large scale complex systems, many organizations are unclear on the methodology for modeling their architectures and enabling stakeholders to easily review, understand and assess those architectures. An architecture can be a conceptual, logical or physical architecture, depending on the system’s lifecycle state. For the context of this paper, the modeling environment is any System’s Modeling Language (SysML) based tool along with modeling tools for electrical, mechanical and software development and product life cycle management tool. The intended audience is any engineering organization defining end-to-end architecture within a DEE, and all stakeholders tasked with reviewing conceptual, logical and physical architecture. The outcome of this paper is to provide engineering organizations with guidance on underlying principles for modeling and understanding or assessing architecture that describe large complex systems.
Model-Based Systems Engineering (MBSE) enables requirements, design, analysis, verification, and validation associated with the development of complex systems. Obtaining data for such systems is dependent on multiple stakeholders and has issues related to communication, data loss, accuracy, and traceability which results in time delays. This paper presents the development of a new process for requirement verification by connecting System Architecture Model (SAM) with multi-fidelity, multi-disciplinary analytical models. Stakeholders can explore design alternatives at a conceptual stage, validate performance, refine system models, and take better informed decisions. The use-case of connecting system requirements to engineering analysis is implemented through ANSYS ModelCenter which integrates MBSE tool CAMEO with simulation tools Motor-CAD and Twin Builder. This automated workflow translates requirements to engineering simulations, captures output and performs validations. System Architecture Model is created in CAMEO with requirements and structure diagram. Motor-CAD is used to calculate motor performance and efficiency map. Twin Builder is used to develop an integrated system (EV) model and calculate vehicle level performance characteristics such as vehicle range, acceleration and gradeability etc. Trade studies are performed to evaluate design alternatives. Ansys ModelCenter empowers engineers and decision makers by providing early requirement verification capabilities thereby reducing re-work and enhancing efficiency in product development.
Systems Engineering is a method for developing complex products, aiming to improve cost and time estimates and ensure product validation against its requirements. This is crucial to meet customer needs and maintain competitiveness in the market. Systems Engineering activities include requirements, configuration, interface, deadlines, and technical risks management, as well as definition and decomposition of requirements, implementation, integration, and verification and validation testing. The use of digital tools in Systems Engineering activities is called Model-Based Systems Engineering (MBSE). The MBSE approach helps engineers manage system complexity, ensuring project information consistency, facilitating traceability and integration of elements throughout the product lifecycle. Its benefits include improved communication, traceability, information consistency, and complexity management. Major companies like Boeing already benefit from this approach, reducing their product development time. In the academic environment, competitions such as Formula SAE BRAZIL, Baja, and AeroDesign offer students opportunities to face real challenges like multidisciplinary optimization and prototype testing. Therefore, this work aims to develop the preliminary architecture of an Unmanned Aerial Vehicle (UAV) for the SAE BRAZIL AeroDesign competition, using the MBSE approach. This allows integrating decisions from various departments into a single repository, generating customized maps and tables to represent the created traceability. The UAV architecture focuses on aerodynamics and its impact on landing and takeoff performance. The secondary objective is to provide a study of best practices for teams participating in the SAE BRAZIL AeroDesign competition and for industries facing systemic challenges in their products. Utilizing the MagicGrid method, SysML language, and relevant aeronautical references, the results include interconnected maps and tables that maintain updated information, enable quick verification of aircraft configurations against competition requirements, and reduce the need for constant manual rework.
The IncQuery AUTOSAR-UML Bridge is an innovative solution for Assisted Documentation Creation and Automated Handover, aiming at driving a paradigm shift in integrated digital engineering in the automotive domain. The AUTOSAR-UML Bridge is addressing a well-known gap in the engineering ecosystem of automotive design, where the co-design of AUTOSAR models and other model-based artifacts is often hampered by tedious workflows involving manual syncing of model contents between AUTOSAR and UML/SysML tools. The Bridge is aiming at streamlining the workflow by generating high-quality UML models from AUTOSAR projects, with built-in ISO26262 and ASPICE compliance. Automotive software architects and systems engineers spend a lot of time with creating ISO26262-compliant documentation, by creating UML models from AUTOSAR architecture designs, or establishing traceability between requirements captured in SysML and design artefacts that exist in both modeling languages. However, as a project progresses and the work of engineers diverges, keeping AUTOSAR and UML/SysML in synch can be a tedious, slow, and error-prone task – especially when you are already grappling with tight timelines and limited resources. The AUTOSAR-UML Bridge mitigates these workflow issues, by providing assistance for Automotive Software Architects to expedite documentation creation by generating UML models from AUTOSAR for architecture design. Moreover, it assists Automotive Software Engineers with transitioning to detailed design by adding UML-based internal behavior and interface descriptions to AUTOSAR projects. The IncQuery AUTOSAR-UML Bridge's seamless integration with Sparx Systems Enterprise Architect helps to streamline the overall design process. Furthermore, it can also work with LieberLieber’s LemonTree, to enable agile iterations where collaborating architects and engineers can easily merge changes from AUTOSAR into the corresponding UML model, without having to redo or delete anything.
In support of developing complex systems, integrating requirements from various source standards, such as the Military Standard (MIL-STD) series and others, presents a significant challenge. This paper explores the development of Model-Based System Engineering (MBSE) Systems Modeling Language (SysML) projects that incorporate MIL-STD requirements. The study begins by defining the critical need for integrating multiple standards into MBSE projects, emphasizing the importance of adhering to MIL-STD requirements when invoked by the customer. The study further defines the limitations inherent in managing standards independently and propose a unified approach within a SysML-based framework. The research introduces a systematic methodology for mapping MIL-STD requirements and other relevant standards onto SysML constructs, ensuring traceability and consistency throughout the system development lifecycle. Comparing traditional methods with the use of MBSE methods highlight the advantages of an integrated approach in terms of reducing redundancy, enhancing traceability, and improving overall system development efficiency. In conclusion, this research paper asserts that a comprehensive methodology for encompassing MIL-STD requirements and constraining data in new MBSE SysML projects is the recommended approach. This approach bridges the gap between complex standards and system development, promoting efficiency, compliance, and traceability. It serves as a valuable resource for engineers, project managers, and organizations engaged in the development of systems requiring compliance with MIL-STDs.
The automotive industry has seen accelerating demand for electrified transportation. While the complexity of conventional ICE vehicles has increased, the powertrain still largely consists of a mechanical system. In contrast, vehicle architectures in electrified transportation are a complex integration of power electronics, batteries, control units, and software. This shift in system architecture impacts the entire organization during new product development, with increased focus on high power electronic components, energy management strategies, and complex algorithm development. Additionally, product development impact extends beyond the vehicle and impacts charging networks, electrical infrastructure, and communication protocols. The complex interaction between systems has a significant impact on vehicle safety, development timeline, scope, and cost. A systems engineering approach, with emphasis on requirements definition and traceability, helps ensure decomposition of top level requirement for subsystem development as well as compatibility between systems. This paper addresses common methodologies and tools within the systems engineering discipline to overcome integration complexity for the E-Mobility sector. Focal points of the systems engineering discipline, including architecture, requirement definition, and integration, are examined in the context of overall product lifecycle. Impact on functional safety is a key consideration, which is integrated into every phase of product development in accordance with ISO 26262. Systems engineering is an essential role for integration of subsystem and component level activities into a coherent framework using the V-model for product development.
Sometimes an innovation comes along that changes the manufacturing landscape. Pro Spot International has created a unique Cobot Spot Welding solution. By bringing this new tool to the sheet metal fabrication market, the company aims to bring game-changing gains in productivity, reliability, traceability, and ergonomic safety to the manufacturing world.
It’s no secret that bringing a novel idea for a safety-critical application from concept to market can take a ton of time, dedication and smarts, along with a whole lot of luck. Since it’s initially uncertain the idea will even work, a proof of concept (PoC) seems a logical place to start, focusing specifically on science while other considerations like the rigorous traceability requirements to comply with standards can be worried about far down the road.
Industrial Internet of Things (IIoT) technologies can lead to a dramatic increase in production quality and throughput but they're often not the plug-and-play solutions that many companies in the manufacturing sector may expect. To get the most value from an IIoT solution, manufacturers need to thoroughly understand the nature of their operations and invest in a robust, real-time traceability system to collect relevant data in a proactive and systematic way.
ABSTRACT Prototype Warfare represents a paradigm shift in how the US Department of Defense (DoD) executes acquisition of defense systems in a manner that is significantly faster than traditional acquisition. At its core, Prototype Warfare shifts focus from large fleets of common one-size-fits-all exquisite systems to small quantities of rapidly fielded, highly tailored systems that are focused on specific capabilities within a specific theater to address a specific (and typically urgent) requirement. This paper does not address the programmatic or policy implications of implementing Prototype Warfare, but instead provides an approach to achieving Prototype Warfare from a technical perspective. The key to executing a Prototype Warfare program is to establish and execute a robust Mission Engineering practice that uses the operational context of a system to drive performance requirements, allowing the modeled end use of the system to be root of all requirements traceability. “Success no longer goes to the country that develops a new fighting technology first, but rather to the one that better integrates it and adapts its way of fighting….” -The National Defense Strategy (2018)
Abstract The Integrated Systems Engineering Framework (ISEF) is an RDECOM solution to capture, leverage, and preserve/reuse Systems Engineering (SE) knowledge generated throughout a system’s lifecycle. The framework is a system of tools designed to support decision making with confidence through embedded SE process management, high quality data visualizations, and system lifecycle information traceability. A web based tool architecture supports near zero IT footprint and allows real time collaboration between team members. The Combat Vehicle Prototype program is a large S&T effort within the Army community to create a virtual demonstrator to influence the next Future Fighting Vehicle program of record. The program is made up of “leap-ahead” technology development efforts pursuing TRL 6 demonstrations. These technologies are being coordinated with the CVP central program office to ensure an effective system level concept is transitioned at the end of the program. This paper will begin by providing an overview of current capabilities within ISEF as well as in-development and funded efforts to come in the near future. Next, it will discuss the implementation of the ISEF toolset on the CVP program, success stories, and areas for improvement through continued development.
The manufacturing of medical components must meet standards of accuracy, reliability, quality, and traceability that equal and sometimes exceed those required for aerospace and nuclear parts. In addition, global competition and efforts to restrain health care expense create great pressure to maximize productivity and reduce manufacturing costs. Tooling manufacturers are helping medical partmakers meet these challenges with a selection of milling tools custom-engineered for the machining of complex orthopedic replacement components.
As the demands of traceability and compliance are put on manufacturers, using a laser provides permanent marking of a variety of information, including 2D bar codes, serial numbers, company information, and logos.
The use of lasers to mark surgical instruments has become of greater significance, however, the parameters used in these applications are not always fully appreciated. The medical industry, in particular, has utilized laser technology primarily to mark, weld, and cut medical devices for years. Lasers address the need for microscopic applications: to cut widths measurable in microns, spot welds with heat affected zones barely visible to the unaided eye, and highly resolved biocompatible markings that enable traceability of instruments and implants. In common with other industries, medical devices and pharmaceutical businesses turn to lasers for a one-step, fast, flexible, permanent, and a highly automated marking process.
ABSTRACT The Advanced Systems Engineering Capability (ASEC) developed by TARDEC Systems Engineering & Integration (SE&I) group is an integrated Systems Engineering (SE) knowledge creation and capture framework built on a decision centric method, high quality data visualizations, intuitive navigation and systems information management that enable continuous data traceability, real time collaboration and knowledge pattern leverage to support the entire system lifecycle. The ASEC framework has evolved significantly over the past year. New tools have been added for capturing lessons learned from warfighter experiences in theater and for analyzing and validating the needs of ground domains platforms/systems. These stakeholder needs analysis tools may be used to refine the ground domain capability model (functional decomposition) and to help identify opportunities for common solutions across platforms. On-going development of ASEC will migrate all tools to a single virtual desktop to promote a more seamless and consistent user experience. The capability to read data stored in remote DOORS databases will be added to enable broader collaboration across RDECOM and the Army. This paper will provide an overview of the current state of the Advanced Systems Engineering Capability (ASEC) framework, highlight the growth and diversity of the ASEC user base and its applications to the Army/DoD and explain the roadmap for continued ASEC development and deployment.
Proposes adoption of an industry standard marking protocol to assure the authenticity of high-reliability electronics. The protocol is seen as a key ingredient in the industry's effort to control counterfeit electronic parts escapes. The specifications of the marking protocol have been informed by the experience of the authors, who are currently participating in a DNA marking program mandated by the Defense Logistics Agency. The protocol would set out these criteria for an effective marking program: Simplicity Proven uncopyability Reportability: transparency and ease of oversight Legal validity: empowering of law enforcement Quick ramp-up and seamless implementation Extreme fidelity and absolute character of results - reliability of the mark at a very high level Universal adoption
ABSTRACT Systems Engineering is an interdisciplinary approach that concentrates on the design and application of the whole as distinct from the parts. For complex systems, this includes the challenge that the behavior of the system as a whole is not intuitively understood by understanding the components. Classic System Engineering models establish a perception of a beginning and an end of the systems engineering process. Unfortunately, a long period between product launch and discovery of unexpected behavior for systems may occur with a protracted lifecycle. A Systems Engineering approach based upon the “control theory” model establishes a high correlation between interdisciplinary models to facilitate feedback throughout the system lifecycle to tune capabilities to user satisfaction. This close coupling extends well beyond tracing of requirements to qualification testing fulfillment as practiced in the traditional “V” model. The system itself is a traceability link providing lifecycle feedback control on the current fulfillment of requirements versus expected fulfillment. The institution of this approach will establish a Systems Engineering feedback measure of user satisfaction from system inception to retirement, rather than merely a front-end design activity.
A report discusses the development of a highly complex system of distributed-computing, multidisciplinary design-optimization software, called "CJOpt," for use in research on model 4 of the High-Speed Civil Transport (HSCT) airplane (HSCT4.0). The emphasis in the report is on the application of formal software configuration management (SCM) to ensure the integrity of, and the traceability of changes in, the optimization software.
Items per page:
50
1 – 42 of 42