bluuebunny/crossref_metadata_2025_split huggingface dataset:
Developing Strategic Systemic solutions to complex problems in the UK Defence Enterprise
Authors: Wilkinson Mike , Jordan Chris , Currie Fleur 
Published: September 2016

AbstractThis paper describes the use of an open innovation/collaboration model to provide strategic systemic solutions to complex problems in UK Defence. The model in question is the one evolved over time by the Niteworks Partnership, which was established in 2003 and now has over 160 organisational members drawn from government, academia and industry. One of the key principles of the model is ‘exploitation’, namely the capture and management of foreground ‘intellectual capital’ created within projects for subsequent re‐use by members of the Partnership. The volume and breadth of project activities, coupled with an enduring core team of technical experts, facilitates the identification of recurring problem types and solution approaches, which in some cases can be synthesised to address underlying root causes. An ever‐changing project portfolio supports testing and refinement of the developed approaches and helps to build a solid body of evidence for their efficacy. Although this process has been developed in the context of the UK Defence enterprise, it is applicable more generally. Furthermore, the strategic systemic methods emerging from the process are in themselves relevant to many domains. This paper presents the approach to developing strategic systemic solutions and describes specific methods emerging from this process, including: Continuous Capability Evolution; Styles of Architecting; Complex System Interventions, and; Capability Coherence.
Quantifying System Complexity in Design Phase Using Higraph‐Based Models
Authors: Aboutaleb Hycham , Monsuez Bruno 
Published: September 2016

AbstractThe exponential growing effort, cost and time investment of complex systems in design phase emphasize the need for a methodology, a framework and an environment to handle the system model complexity. For that, it is necessary to be able to measure the system model complexity. This paper highlights the requirements a model needs to fulfill to match human user expectations, presents a generic framework for designing complex systems, and suggests a graph‐based formalism for modeling complex systems. Finally, a way to measure system model structural complexity based on Shannon theory of information is proposed and illustrated with an example.
A practical example of a software factory: building a custom application for analysing EU Cyber Physical System (CPS) projects using Open Source software components
Authors: Palmer P. J. , Sinclair M. A. , Siemieniuch C. E. , De Henshaw M. J. 
Published: September 2016

AbstractThis paper is a retrospective analysis describing the development of a custom tool to organise data snippets derived from a substantial body of information, and a summary of the insights that this means of analysis provided in a very short time scale. The creation of data driven visualisations are of particular interest as they uncovered more cross‐domain aspects of Cyber‐Physical Systems projects than expert opinion had anticipated. These findings will be discussed fully in a second paper.The focus here is the development of the “Vulture” data scavenging tool using Open Source software as system components to create a custom application to serve the data collection and analysis requirements of a REA (Rapid Evidence Assessment) work‐package within an EU funded project, Road2CPS.
SkiPo – a sketch and flow based model to develop mechanical systems
Authors: Grundel Martin , Abulawi Jutta 
Published: September 2016

AbstractThis paper introduces a new hybrid model for the development of mechatronic and mechanical systems which can be used to bridge the mental gap between the abstract definition of a functional system architecture and the geometry‐oriented three‐dimensional computer‐aided design process. This model, called SkiPo model, defines interfaces between system components in terms of material, energy and information flow and combines this abstract approach with sketches visualizing important design decisions in a structured, semi‐standardized way. The objective of this hybrid modeling approach is to support the inevitable iteration between abstract and very detailed viewpoints of a mechatronic or mechanical system in the early stages of the development process.
A Cognitive Journey for Requirements Engineering
Authors: Feldman Yishai A. , Broodney Henry 
Published: September 2016

AbstractThe classical systems engineering practice is mostly process centric, but with the recent advances in Information Technologies, we have started to engage in model‐based and other software‐supported activities that make us more efficient and our products better. The subject of this paper is a pursuit of further improvements in the software tools supporting the systems engineers, this time an attempt to transform the regular textual requirements into computer‐readable artifacts that will enable software tools to better analyze a requirement set and to automate cross‐lifecycle exchange of information leading to increased automation and higher quality.The paper starts by describing an experiment targeted at requirements formalization, continues with the insights gained from the experiment, and finishes with the insights that the authors have reached on a reasonable and incremental roadmap to a fully synergetic interaction between Requirements Engineers and their supporting tools.
Maintenance Optimization Approaches for Condition Based Maintenance: a review and analysis
Authors: Machado Mario Marcondes , Haskins Cecilia 
Published: September 2016

AbstractThis study contains a preliminary review of recent maintenance optimization applications, collected from different industries. The idea is to meet and discuss promising approaches, implementation aspects and critical elements, in order to provide guidance for further research. Starting from a set of applications, analyzed under a systems engineering approach, the study proposes a conceptual map to represent the ontology of condition‐based maintenance programs and suggests some guidelines for developing an implementation plan.
Helping Undergraduate Students of any Engineering Discipline Develop a Systems Perspective
Authors: Simoni Mario , Andrijcic Eva , Kline Bill , Bernal Ashley 
Published: September 2016

AbstractThe complexity of problems that engineers are being asked to solve is increasing rapidly. Effective solutions often require the integration of mechanical, electrical, computer software, chemical, and/or biological components. In order to manage this complexity, it is becoming important for all engineering students to learn how to approach the solutions to these problems using a systems perspective (Baldwin 2014). In order to better motivate this approach to students the authors are introducing it within courses of their own engineering discipline. The authors are adapting traditional systems engineering concepts to create a framework of system models that can be introduced into courses of any engineering discipline at any level. Through the process of learning how to create these models, students gain an understanding of what is meant by a systems perspective and how this perspective can help them to solve problems. This paper discusses which systems models were incorporated into undergraduate curriculum and how each model is broken‐down into pieces that are easier for undergraduates to understand and faculty to teach.
Introducing MBSE By using Systems Engineering Principles
Authors: Hallqvist Jonas , Larsson Jonas 
Published: September 2016

AbstractThis paper describes one possible way how to introduce MBSE into an organization. It is based on a real example from a development organisation in aerospace industry. In this example the start of the introduction of MBSE had an innovative enthusiasm, thereafter followed by stagnation of progress. A change in point‐of‐view on why MBSE should be used was made and as a consequence the entire work methodology was considered a Development Enabling system. At this point Systems Engineering principles were applied in order to determine the need and to find a solution. A description of pitfalls and other lessons are included but it will not cover application of SysML or any architectural frameworks. One point in this paper is that introducing MBSE is not a technical task, it is a change process affecting a very complex system where the most important system elements are humans.
Testing of Autonomous Systems – Challenges and Current State‐of‐the‐Art
Authors: Helle Philipp , Schamai Wladimir , Strobel Carsten 
Published: September 2016

AbstractAutonomous systems are on the rise. However, the challenge to test autonomous systems to ensure their safe and fault‐free behaviour is not solved yet. This is especially critical when we consider the fact that autonomous systems are often safety‐critical systems envisaged to interact with humans without explicit human supervision. This paper points out why testing autonomous systems is such a challenge and provides an overview of the current state‐of‐the‐art theory and practice. The gathered information is then condensed into guiding points for the way forward.
Towards the Automation of Model‐Based Design Verification
Authors: Schamai Wladimir , Helle Philipp , Albarello Nicolas , Buffoni Lena , Fritzson Peter 
Published: September 2016

AbstractModeling and simulation of complex systems is at the heart of any modern engineering activity. Engineers strive to predict the behavior of the system under development in order to get answers to particular questions long before physical prototypes or the actual system are built and can be tested in real life. One of the critical questions is whether a particular system design fulfills or violates requirements imposed on the system under development. In this paper, we discuss an approach to model‐based design verification by simulating system dynamic behavior including formalized requirements. We illustrate the approach on a case study – the verification of a new design for flight control surfaces activation against requirements. The contributions of this paper are the evaluation of a new requirements formalization approach using the recently developed Modelica Requirements Library, and the discussion of solutions for automating the simulation model composition.
Concurrent Structured Analysis SE method applied to a solar irradiance monitor satellite
Authors: Maria Rodrigo Britto , Fraulob Halph Macedo , Chiaki Adrielle , Coronel M. Gabriel G. , Rohling Adair , Loureiro Geilson 
Published: September 2016

AbstractThe traditional Systems Engineering approach on systems development leans toward the product in development, in all levels of abstraction, while the traditional concurrent engineering approach focuses on both product and organization simultaneous development, although considering only lower levels of abstraction. For complex systems, the Concurrent Structured Analysis method is a better fit for the SE process, since it considers both the product and organization simultaneous development, in all levels of abstraction. The underlying concepts of this method were applied to the development of a solar irradiance monitor satellite. Several analyses were performed on selected scenarios of the system life cycle processes to exemplify the application of the concepts. The final outcome was a proposal design of the product and the organization needed to implement its life cycle processes. It was noted that the same scenario can influence the product and the organization, both requiring to be considered in the analysis.
Product Line Thinking – Applying System Thinking to Product Lines
Authors: Le Put Alain 
Published: September 2016

AbstractThis paper describes the problems encountered when implementing Product Lines. It reminds what the System Thinking approach is and the way it already has been used to solve problems related to System Engineering. System thinking proves to be very efficient to solve the problems arising both when setting up of a product line and when working in a product line organization. The “Product Line Thinking” definition may be then proposed as a new concept. One of the three business cases addresses the deployment of product lines to Very Small and Medium Enterprises (VSME).
Merit of Adaptable Pairing as an Agile Systems Engineering Knowledge Management Practice
Authors: Leroux Chris , Dove Rick 
Published: September 2016

AbstractDriven by customer demands and global competition, systems engineers often experience dramatic project shifts and rapid technological advances that can place great strains on an engineering organization. In addition, project teams also deal with changing personnel, mistakes or rework, and slow engineering response times to unplanned needs. These external and internal factors can lead to reduced quality, increased costs, and slipped schedules. An effective knowledge management architecture is a necessity in today's engineering environment, and should be treated as an important project activity. Due to constantly evolving projects and project teams, knowledge management must be able to adapt based on current needs and resources. The purpose of this paper is to present knowledge management issues that must be addressed during an engineering project, and to propose a useful operational architecture for knowledge management. This architecture will provide an image of how agile knowledge management can be used by systems engineers to counter the turbulence in today's technical work forces, and how it can be integrated into existing organizational structures. The proposed architecture is best described as adaptable pairing, where two or more individuals engage in knowledge sharing and assignment swapping to complete a specific project task. The pairing architecture will address three common knowledge management problems that may negatively impact project quality, cost, and schedule – uninformed decision making, lengthy response delays, and rework. Intents and traits of adaptable pairing may be appropriate for any industry, however, evidence will focus primarily on technology industries engaged in contract projects. Historical evidence of successful pairing in the world of software engineering is presented at the end of the paper.
Introduction to the Agile Systems Engineering Life Cycle MBSE Pattern
Authors: Schindel Bill , Dove Rick 
Published: September 2016

AbstractEngineered and other systems are under pressure to adapt, from opportunities or competition, predators, changing environment, and physical or cyberattack. Ability to adapt well enough as conditions change, especially in presence of uncertainty, is valued. Systems (including developmental and life cycle management) that adapt well enough, in time, cost, and effectiveness, are sometimes called “agile”. As environmental change or uncertainty increase, agility can mean survival. Agile systems and agile systems engineering are subjects of an INCOSE 2015‐16 discovery project, described elsewhere. This paper introduces the underlying MBSE‐based Agile Systems Engineering Life Cycle Pattern being used to capture, analyze, and communicate key aspects of systems being studied. More than an ontology, this model helps us understand necessary and sufficient conditions for agility, different approaches to it, and underlying relationships, performance couplings, and principles. This paper introduces the framework, while specific findings about methods and practicing enterprises studied will be reported separately.
Painting Systems: From Art to Systems Architecting
Authors: Salado Alejandro , Iandoli Luca , Zollo Giuseppe 
Published: September 2016

AbstractSystems engineering has successfully contributed to develop complex systems in industries such as defense, space, energy, or transportation. Systems in those industries have in common their engineered or socio‐technical natures. However, systems engineering has been understood for a long time as both an art and a science. As a matter of fact, principles and practices of systems engineering have been exhibited in the creation of film original score, a major artistic endeavor. Therefore, it is sensible to investigate if and how the similarities and differences between the application of systems engineering in the development of engineered systems and the pursue of artistic endeavors can help in improving the understanding and practice in both domains. Specifically, this paper discusses how the same concepts are applied in artistic painting and in system architecture to reduce complexity and achieve elegance.
Modeling‐Simulation‐Analysis‐Looping: 21st Century Game Changer
Authors: Marvin Joseph W. , Schmitz Jeffrey T. , Reed Robert A. 
Published: September 2016

AbstractWhat if you could present to your boss and customers the expected performance characteristics of a new system in its target mission environment during concept development and before the first requirement or line of software is written? This paper follows up our IS 2014 paper, Uncertainty Quantification (UQ) in Complex System of Systems (SoS) Modeling and Simulation (M&S) Environments, and presents a new technique for system modeling and simulation that enhances insight and decision making based on quantified performance data. We describe how graph computing technology, readily available open source toolboxes and different systems thinking can “change the game” for systems engineers in the 21st Century.
Assessing System Development Risks
Authors: David Matthew 
Published: September 2016

AbstractSystem development projects can fail for lots of different reasons. Those reasons may or may not have been predicted as risks during the development lifecycle. If they weren't predicted, then it is likely that the project team members lacked the level of competence necessary to deliver a system with that level of difficulty. If they were predicted, then it is likely that there was insufficient corporate governance (or assurance), which let the project continue through its lifecycle carrying too much risk. This paper will explore methods on the practical implications of:
‐ Assessing the level of system development difficulty.
‐ Allocating a team of sufficient competency.
‐ Identifying adequate resources.
‐ Tailoring an appropriate amount of governance.
Product System Families at Rolls‐Royce: A Case Study in Enterprise Transformation
Authors: Holt Jonathan , Brown David , Walker Andy 
Published: September 2016

AbstractThis case study describes the initial stages of Product System Families, a project to develop generic, reusable system design artefacts applicable to the complex systems with which Rolls‐Royce equips its aerospace products. Using the example of a gas turbine tip clearance control system, the system thinking behind Product System Families is outlined and the development of the generic artefacts themselves is described, together with the challenges of developing them within the fast‐moving, complex enterprise that is Rolls‐Royce's engineering function. The ultimate aim is to have much of the product design captured in a series of ‘house styles’ which represent the most advanced, optimized solution and can then be customized quickly and cost‐effectively to specific customer needs.
A framework for integrating reliability and systems engineering: proof‐of‐concept experiences
Authors: Hosseini Hossein Neizan , Welo Torgeir 
Published: September 2016

AbstractReliability plays a significant role in systems engineering. Adopting the reliability and systems engineering in the early system lifecycle may lead to better quality of the final product as well as more efficient usage of the resources use to launch the product. However, there is presently no concrete framework illustrating how reliability engineering can be integrated into the systems engineering life cycle. This article discusses the development of a new, integrated reliability and systems engineering framework. The approach has been applied in a case study in the form of a student project, including a multi‐disciplinary student team aiming to design, develop, build and validate the energy efficiency of a concept vehicle. Integrating traditional systems engineering strategies with reliability engineering best‐practices was found to significantly enhance not only the quality of the final product, but also to reduce the budget and time due to less late engineering changes and subsequent design iterations.
Exploring System Space with Graph Theory
Authors: Peterson Troy 
Published: September 2016

AbstractAs today's Cyber Physical Systems (CPS) become more and more complex they provide both incredible opportunity and risk. Model Based Systems Engineering (MBSE) provides organizations a timely opportunity to address the complexities of Cyber Physical Systems. MBSE tools, languages and methods are having a very positive impact but are still in a formative stage and continue to evolve. Moreover, the Systems Modeling Language (SysML) has proven to be a significant enabler to advance MBSE methods given its flexibility and expressiveness. Unfortunately the number of people who know SysML well is relatively small. To bring the full power of MBSE to the larger community, system models can be rendered in intuitive forms to support broad understanding of system models. More specifically, Graph Theory has proven to be very effective in the design, analysis, management, and integration of complex systems. Use of Graph Theory and dynamic visualization can help teams gain insights, build intuition and ultimately help speed the innovation process.
Interface Management for a NASA Flight Project using Model‐Based Systems Engineering (MBSE)
Authors: Vipavetz Kevin , Shull Thomas A. , Infeld Samantha , Price Jim 
Published: September 2016

AbstractThe goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven‐step approach to interface management used in several prior NASA flight projects. The seven‐step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment‐X (MISSE‐X) project. The MISSE‐X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition; writing good interface requirements; utilizing interface working groups; developing and controlling interface documents; handling interface agreements; the use of shadow documents; and the importance of interface requirement ownership, interface verification, and product transition.