bluuebunny/crossref_metadata_2025_split huggingface dataset:
9.3.2 A Root Cause Analysis Method using Dual Vee Model for Cause Identification Reliability Improvement
Authors: MAEJIMA Hironori , KOHTAKE Naohiko , OHKAMI Yoshiaki 
Published: November 2014

AbstractRoot cause analysis (RCA) of complex systems is important for identify countermeasures. Fault tree analysis (FTA) is one of the most commonly used tools for RCA. However FTA provides less guidance to analysts. Therefore it is difficult for them to exhaustively identify possible causes, and analysis results strongly depend on their skills.Spacecraft systems are among the largest and most complex man‐made systems and consequently require the application of systems engineering methods in their development processes. Spacecraft development is particularly difficult because spacecraft operate in a low gravity and high vacuum environment, which make realistic system level tests impossible on earth before launch. For this reason, it is common that design and manufacture are complementarily verified by analysis. However, insufficient verification often results in on‐orbit nonconformance, leading to unexpected anomalies in mission operations.This study proposes the use of the Dual Vee Model developed in recent advances on strategic systems engineering methodology for identifying the root cause of such anomalies. The proposed method facilitates exhaustive identification of possible causes. The usefulness of this approach has been demonstrated in the ADEOS‐II spacecraft which is a three‐ton class Japanese Earth‐observing satellite. The Dual Vee Model consisting of the Architecture Vee and the Entity Vee is helpful in identifying the configuration items and the development sequence for determining the process that could have caused an anomaly.
9.4.2 The NIILS Innovative Process and Approach to Manage and Measure Complex Systems Effectiveness and Availability
Authors: Leonardi C.F. Mirko , Solazzi Simeone M. , Ciambra Francesco , Sinisi Michele 
Published: November 2014

AbstractThe NIILS (Normativa Interforze per il Supporto Logistico Integrato) is a directive on the Integrated Logistic Support (ILS) process to efficiently manage the acquisition process for modern Operational Systems (Main System and Logistic Support). The NIILS directive is the Italian MoD solution to the need for the harmonization of logistic acquisition, ILS Process and Operational System Effectiveness and it is aligned to international standards and Italian standards. The concepts of the NIILS directive allows the Program Management Office (PMO) to increase the effectiveness of the ILS Process adopting a Systems Engineering approach to manage the life cycle of the Operational System and using appropriate tools to integrate System design data and ILS Process data, recorded in a shared DB (Product Common Source Data Base, PCSDB) and specified by a formal language (UML/SysML).
9.6.1 Developing Expertise in Systems Engineering: Lessons from Other Disciplines
Authors: Armstrong James R. , Wade Jon 
Published: November 2014

AbstractMuch has been written about what systems engineering is, what systems engineers do, what defines competency, and how to teach systems engineering. There has been significant research in other fields about how expertise is developed. This paper reviews key elements of that research and looks at its applicability to systems engineering and how it could be applied to improve the development of expertise in systems engineering. In particular, the role of deliberate practice is investigated and compared to the reliance on experience for development of systems engineers.
10.1.2 Towards a framework for variability management and integration in Systems Engineering
Authors: Dauron Alain , Dumitrescu Cosmin , Salinesi Camille 
Published: November 2014

AbstractThe automotive industry is faced today with the challenge of developing increasingly complex systems, but it also needs to integrate new emerging technologies while leveraging on existing designs, on previously developed assets. The concept of reuse is well described in different domains, such as software product line engineering, production, product development or marketing (as a mass customization strategy). In the automotive industry, we see systems engineering as the domain that can bridge the gap between high‐level customer requirements diversity and basic component development. The challenge is to be able to ensure traceability from customer down to components while being able to match requirement variability to component diversity and to ensure an effective management of variability at each level of abstraction or decomposition. The current paper presents an on‐going research that aims at developing a comprehensive framework for managing system variability under three main themes: development process conception, variability description and integration with current methods concerning vehicle development. Our paper will focus on the last two of these themes, presenting the needs for treating this issue and presenting a metamodel for variability representation and integration of external diversity.
11.1.2 Simulation of an Electric Utility Network and Control System in SysML
Authors: Hause Matthew , Pugnetti Fabrizio 
Published: November 2014

AbstractModeling of the electric utility network is normally done using bespoke or custom tools and programs rather than generic modeling languages. This requires the engineer to develop the complete simulation system from scratch. In addition, it is difficult to model from different viewpoints and levels of abstraction. The models are normally created from a single perspective to solve a specific problem or analyze the system from a single point of view. The Systems Modeling Language (SysML) was developed by INCOSE and the OMG to provide general purpose modeling language for systems. Most published examples of SysML are of electro‐mechanical software intensive systems in the aerospace and transportation industries. This paper documents a work in progress by the author to develop a model of an example electric utility network, including the user interface to show how SysML can be used to model complex systems of systems. In addition, it shows how a simulation tool integrated with SysML provides a means of integrating multiple paradigms as well as a Human Computer Interface to the simulation.
11.3.3 System concurrent engineering of a Star Sensor
Authors: Loureiro Geilson , Fialho Márcio Afonso Arimura , de Sá Santos Rabello Ana Paula 
Published: November 2014

AbstractThis paper presents the system concurrent engineering approach applied for the development of an autonomous star sensor. Traditional approaches focus solely on one aspect, that can be either the product, the development organization or the product operation. In those approaches the overall view of the inherent complexity in the development of a product, its life cycle processes and their performing organizations are not taken into consideration. Contrasting with those approaches, the system concurrent engineering performs, simultaneously, stakeholder analysis, requirements analysis, functional analysis and implementation architecture analysis for the product, its life cycle processes and their performing organization. From this, requirements and attributes are captured for the product and its life cycle processes organization, and the relationships between them are identified. Key conclusions are that the impact, traceability and hierarchy links promote the anticipation of the life cycle process requirements to the early stages of systems architecting. Late changes are avoided and development costs are significantly reduced, while satisfaction of stakeholders over the product life cycle is increased.
11.5.2 A NASA Space Communications and Navigation SysML Profile Adaptation
Authors: Barnes Patrick 
Published: November 2014

AbstractThe NASA Space Communications and Navigation (SCaN) Office has been conducting trade studies to investigate integrating its three independent space networks into an integrated space network. SCaN has also chosen to use a model‐based systems engineering approach for the trade studies. SysML, being a general‐purpose modeling language for systems engineering, was chosen to model the Operational Process Flow for each of the three, independent space networks, as well as for a common, integrated network. This paper describes how the base SysML profile was modified to meet the purposes of the trade study investigating network monitoring and control. Though the methodology described in this paper, neither completely adheres to, nor completely deviates from, standard SysML usage, a working form of SysML modeling has been developed for the network monitoring and control trade study and future anticipated trade studies.
Development of Systems Engineering People to support Major Transformation Plans in Thales (Process, Roles, Methodology & related tools)
Authors: Mornas Odile , Mazzella Roland , Weywada Catherine Laporte , Sigogne Anne , Pancher Patricia 
Published: November 2014

AbstractThales is a major actor as systems provider both on civil and military electronic domains. Engineers innovate, design and develop System Solutions, economically viable, and compliant with Stakeholders needs.For Thales, transformation plans are going on to improve performance and quality in Systems Engineering: it concerns a new Enterprise Reference system, named “CHORUS 2.0” including redefinition of roles and processes, but also enhancement of methods and tools for Model‐Based Systems Engineering and risks mitigation.Thus, many concerns are about HR issues. Thales has defined dedicated career paths for Systems Engineering. Staffing people on critical SE jobs have been developed and are deployed for all the entities of the Company.This paper presents the strategy implemented by Thales to support this critical challenge.
HAZOP Analysis of Product Requirements for Early Failure Mode Identification
Authors: Eubanks Fritz 
Published: November 2014

AbstractSafety risk assessment begins with hazard identification, followed by elicitation of causes that could result in those hazards. Cause identification early in the design phase is function‐based by necessity, since components and sub‐systems are not fully defined. These system functions are defined by the product requirements. Applying HAZOP guideword analysis to product requirements can provide a list of initial hazard causes and functional failure modes of the system. This method provides early insight into safety risk controls that should be planned for and implemented early in the product design, when cost and schedule impacts are lowest.
Investigating Alternative Concepts of Operations for a Maritime Security System of Systems
Authors: Mekdeci Brian , Ross Adam M. , Rhodes Donna H. , Hastings Daniel E. 
Published: November 2014

AbstractFor complex systems of systems, such as those required to perform maritime security, system architects have numerous choices they may select from, both in the components and in the way the system operates. Component choices, such as the length of a wing or the number of ground control stations, are often considered in tradespace studies, but this paper highlights the operational choices that are often overlooked. Using an unmanned vehicle system of systems as an example, the importance of considering operational choices as well as the highly interdependent nature of operational and component choices is demonstrated, further strengthening the case for careful consideration of operational variables early in the concept phase of the design process. Finally, a high‐level methodology for generating and evaluating operational choices is introduced.
Maestro – A model‐based systems engineering environment for complex electronic systems
Authors: Bajaj Manas , Scott Andrew , Deming Douglas , Wickstrom Gregory , Spain Mark De , Zwemer Dirk , Peak Russell 
Published: November 2014

AbstractIn this paper we present Maestro, a model‐based systems engineering (MBSE) environment for design and simulation of complex electronic systems using Orchestra—a simulation tool developed at Sandia National Laboratories. Maestro is deployed as a plugin for MagicDraw and uses Orchestra domain‐specific language (DSL) which is based on SysML. Maestro enables a model‐based design and analysis approach that replaces the traditional document‐based systems engineering process. It provides a unified graphical modeling environment to domain experts who have had to depend on drawing tools for defining system architecture and manual transcription of system topology in creating complex simulation models.
Modelling Governance within Business Architecture using Topic Mapping
Authors: Bryant Peter 
Published: November 2014

AbstractThis paper uses an industry case study to demonstrate how to guide executive decision makers through an organization design process as part of a transformation planning activity.The key idea is to derive a set of business‐specific topics from mission statements and strategies and then use these to create an aligned set of organisation structures (role definitions) and governance structures (governance body terms of reference). For example, the topic of ‘legislative compliance’ reflects a business concern for which a member of the executive team will usually be accountable. To address this concern, and ensure there are no surprises during external audits, a governance body may be identified (or newly established) for which this topic is one of the agenda items.The technique uses a simple modelling approach that enables Terms of Reference to be derived for both individual roles and management bodies in a coherent manner. The case study will reference the Governance Framework developed using this method.This paper extends existing practice within Enterprise Systems Engineering, the application of Systems Engineering methods to enterprise design and management. Specifically the model‐based technique enables logical analysis of this organisational design problem.In summary
Using Topic Mapping leads to a richer, and more integrated, Business Architecture.
As business drivers change, the logic leading to current organisational structures can be reviewed and revised to align with the new situation.
Topic Mapping helps to ensure that there is effective ownership (in the RACI sense) of the business‐critical concerns within the organisation.
My COCOMO: Building Your Own Incremental Software Build Estimation Tools
Authors: Pickard Andrew C. , Nolan Andy J. 
Published: November 2014

AbstractThis paper describes work performed in Rolls‐Royce to develop an Incremental Software Build Cost and Schedule estimation tool. The software builds incorporated in the analysis were performed over a period of 10 years with a reasonably consistent team of engineers and software development environment ‐ hence many of the environmental factors developed in software estimation tools like COCOMO (1) were effectively held constant in this study. This allowed the correlation to concentrate on measuring the effects of team size and process change on cost and schedule estimates. These correlations have been integrated with the COCOMO model to create a system that can account for team size for both cost and schedule estimation – “My COCOMO”.The first part of the paper describes factors that can influence the measurement of “effort” and how these may add noise to correlations.The second part of the paper describes how team size can be incorporated into the estimation model to reduce scatter in predictions, and concludes by showing how the resulting correlations can be incorporated into an incremental software build estimation tool which accounts for the level of cost and schedule risk the project is prepared to take when developing a software build.The third part describes the effect of a process change that was introduced and the statistical verification of the significance of the process change on the effort required for software builds.
A Custom Requirements Database for the California High‐Speed Train Project: Or: “You're going to need a bigger boat”
Authors: Petty Matthew 
Published: November 2014

AbstractThe California High‐Speed Train Project (CHSTP) is a large‐scale, multi‐discipline infrastructure project to build 800 miles of high‐speed railroad from Los Angeles to San Francisco and beyond. It is the first true high‐speed rail line in the U.S., and as a result faces unique engineering and regulatory challenges. Existing U.S. federal and state safety regulations do not address the full range of safety requirements included in high‐speed rail safety regulations in Europe and Asia. For the CHSTP it was therefore necessary to develop a set of requirements that reflected existing U.S. regulations and incorporated best worldwide high‐speed rail practices. This paper describes how a requirements management database was developed to document, link, manage and understand the requirements, and support the U.S. Federal Rail Administration (FRA) regulatory change process. Expansion of the database highlighted the need for a more robust set of Systems Engineering (SE) processes and tools.
6.4.1 How Cost Effective is your V&V?
Authors: Pickard Andrew C. , Nolan Andy J. 
Published: November 2014

AbstractThere are many reasons for Verification and Validation (V&V) including their use to mature a product and reduce the overall development costs. However, there are many V&V approaches that can be applied, from review through modeling, analysis and testing. How effective are these at finding issues with the product? How cost effective are they? Does it matter when the approaches are performed, or in what sequence? This paper examines the Verification and Validation approaches applied during the development of gas turbine engine control and monitoring systems. How cost effective are they? In some cases it is a requirement of the Certification process that certain Verification approaches are used – but if an approach is not cost effective, would you also use it during development of the product?
5.2.2 Complexity Measures to Predict System Development Project Outcomes
Authors: Sheard Sarah A. , Mostashari Ali 
Published: November 2014

AbstractWhile it is broadly accepted that complexity makes system development harder, there is no concrete understanding of which types of complexity have the most significant impact. Looking beyond current literature which describes complexity or measures the complexity of a system, this research seeks complexity measures that directly affect development project outcomes: project cost overrun, project schedule delay, and system performance shortfalls. A set of complexity measures was developed based on a comprehensive literature analysis and ranking via a trade study. The effect of those measures on project outcome was studied for 75 systems development efforts, primarily in the aerospace and defense sector. The findings indicate that among the dozens of complexity measures discussed in the literature, the three measures with the most significant impacts on development outcomes in these projects were: number of hard‐to‐meet requirements, degree of cognitive fog, and stability of stakeholder relationships.
How to Select Integration Strategy for your Project?
Authors: Frank Moti , Harel Amir , Orion Uzi 
Published: November 2014

AbstractThis paper deals with the integration process in multidisciplinary technical systems projects. The paper reviews the objectives of the integration process, planning and managing principles, as well as the pitfalls and difficulties associated with this process. Various integration approaches are described and analyzed. A method for comparing integration approaches in systems projects is suggested.
8.5.1 Process Modeling for Requirements Engineering: A Medical System Case Study
Authors: Berenbach Brian , Rea Diane , Schneider Florian 
Published: November 2014

AbstractThe Unified Requirements Modeling Language (URML) was created to support early systems engineering; permitting the capture of process, potential variation points, hazards, threats and mitigations during the elicitation process. It has been used on Siemens projects, but to date they have been proprietary, precluding public exposure and limiting the critical review needed to refine and improve the language. To that end, a standard medical process, phlebotomy, was modeled in detail to determine the efficacy of the language. One of the authors of this paper is an expert in the area of medical diagnostics and provided the domain expertise. The modeling experience exceeded our expectations, and provided some unanticipated benefits. The results of our study are presented in this paper.
7.2.3 Efficiency Management in Spaceflight Systems
Authors: Murphy Karen 
Published: November 2014

AbstractEfficiency in spaceflight is often approached as “faster, better, cheaper – pick two”. The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.
10.2.1 “Composable Capability” – Principles, strategies and methods for capability systems engineering
Authors: Sillitto H G 
Published: November 2014

AbstractCurrent systems engineering approaches for Capability Systems Engineering are difficult to understand and are not deployed consistently. Language is a barrier to understanding. A top‐down approach to “capability” still seems intractable. The traditional system focus of defence acquisition has been the “equipment”. Force elements have been constructed bottom up from equipment. Inevitably such bottom‐up integration leads to unintended emergent properties in operational “force elements”.This paper proposes that: improved operational readiness, performance and interoperability can be achieved by applying a systems engineering methodology in which the “system focus” is the force element, not the individual equipment; it is possible to identify a finite set of stable, well characterised building blocks (Force Elements) from which a wide variety of task force structures can be put together, providing almost infinite variety of capability solutions; that by thus re‐framing the problem we can contain the complexity explosion, giving more benefit with less difficulty; and that using such an approach top‐down will allow better statements of need, requirements and acceptance criteria to be passed to the acquisition community and supply chain.