bluuebunny/crossref_metadata_2025 huggingface dataset:
9.6.2 INTEGRATION OF OPERATIONS IN PROCESS SYSTEMS: COMPLEXITY AND EMERGENT PROPERTIES
Authors: Hessami Ali G. , Karcanias Nicos
Published: November 2014

The problem of system Integration in the context of an Industrial Enterprise is a multidimensional problem with fundamental dimensions those of: (i) Purpose, goals and objectives, (ii) Overall process operations, (ii) Overall System Design/Redesign, (iii) Information, Data and Software, and (iv) Verification, validation and assurance. Each of the above areas is addressed by respective groups which consider their area as representing the entirety of the problem and they frequently ignore the other important dimensions. The aim of this paper is to consider first the general problem of integration from all its fundamental aspects and focus on the key paradigm of Global Operations. Within this area we consider the issues of system organization and in particular the problems relating to hierarchical organization of the different operational functionalities, the issues of aggregation and disaggregation and the related problems of the “top‐down” and “bottom up” approaches. System complexity is considered within this framework and the notion of emergent properties is then considered as a problem of aggregation of behaviours, which may be also seen as projections within the setup of a control and information architecture. Such an architecture is defined for the multi‐level hierarchical organisational structure that we consider. We show that systems and control concepts and problems play a central role the development of an overall integration methodology and interpreting the features of the different emergent properties. The subject of modelling emerges with a central role in the effort to develop a methodology for systems integration, as well as quantifying the predictors of relevant emergent properties. The approach introduced here is intimately linked to Multilevel hybrid systems (Hierarchy of Operations), and provides a complementary dimension to issues of System Design (and Re‐design) dominated by the theory of Structure Evolving systems [10] (in the total Design and Life‐cycle analysis) emerges as the central approach. This paper provides an overview of the subject area and focuses on the development of the general conceptual framework for integration. We additionally develop and propose a systems framework for the evolutionary integration in this paper.
10.1.2 Legacy Software System Integration
Authors: Knapper Robert J. , Brouse Peggy S.
Published: November 2014

Legacy software systems are often the subject of analyses in attempts to affect modifications to extend their useful lifetimes. For the systems engineer, reengineering legacy systems or integrating legacy systems with new development and/or off‐the‐shelf software are areas which may provide particular challenges and where effective software system analysis is critical. When analyzing a software system, a range of system artifacts may be used. These artifacts include a description of the system in natural language, program design language descriptions, flow charts, object diagrams, as well as the system code. All of these artifact types can contain equivalent information at their specific level of abstraction. However, deriving information that is needed for reengineering or integrating a legacy system from each of these artifacts cannot be performed equivalently. For example, analyzing a poorly structured system with little or no design documentation is a particularly challenging problem. Software modeling using an abstract architecture representation as a common description vehicle, such as the Unified Modeling Language or some other, can “level the playing field” by creating representations of disparate systems at the same level of abstraction. This is of importance to reengineering efforts; it shows promise for supporting and facilitating integration efforts between legacy and other systems. This paper presents a methodology to express and manipulate (i.e. restructure) system architecture‐level models, an evaluation of the integratability of those models, and proposes a decision support system framework that makes the use of the methods.
10.4.1 Sizing Systems Engineering Activities to Optimize Return on Investment
Authors: Honour Eric
Published: November 2014

This work continues significant results from the Systems Engineering Return on Investment (SE‐ROI) project that has quantified systems engineering (SE) success using extensive interviews with real programs. In prior work the project reported that effective systems engineering (SE) at a level of approximately 15% of a project cost optimizes cost, schedule, and stakeholder success measures. The project also identified a set of effective characterization parameters for quantifying SE. This work explores the relationship between the characterization parameters and the success correlations. It is shown that eight major SE activities can be “right‐sized” based on the characterization parameters of a program as an a priori estimation method to optimize the ROI of the activities. The paper shows the quantified relationships, based on the database of interviews. Two example programs demonstrate the method and illustrate the typical optimized level of SE activities.
10.4.2 Convergence of Expert Opinion via the Wideband Delphi Method: An Application in Cost Estimation Models
Authors: Valerdi Ricardo
Published: November 2014

This paper discusses the notion of collective intelligence through the application of the Wideband Delphi method as a way to obtain convergence among a group of experts. The specific application is the definition and calibration of cost estimation models that use data collected from experts as part of their calibration. Convergence is important in this case because companies need to commit to cost estimates early in the planning cycle since so many other decisions are dependent on it. Our results demonstrate that, in most cases, convergence among experts can be achieved after three rounds of the Wideband Delphi.
11.2.3 Systems Concurrent Engineering of a “Green” Car
Authors: Alarcón Javier Efrain Gonzales , Loureiro Geilson
Published: November 2014

In this paper we present the systems concurrent engineering approach to the development of complex products for the automotive industry having as a product a “green car”. Traditional approaches focus on the product, the organizational development and product concepts of operation (CONOPS). This approach is the integration of the Systems Engineering and Concurrent Engineering approaches. Systems Engineering is a multidisciplinary and collaborative engineering approach for deriving, evolving and verifying a system solution, balanced throughout its life cycle, and that meets the expectations of stakeholders and public acceptance. Concurrent Engineering is an engineering approach that anticipates, to the initial stages of development, the product requirements from the life cycle processes such as manufacturing, assembly, testing, maintenance and logistics and disposal of the product. This paper presents the approach of Systems Concurrent Engineering. Systems concurrent engineering acknowledges that the system solution is comprised of product and organization elements. Each product life cycle concept is thought from the outset and using a top‐down approach, from the product context at a given life cycle process scenario. The systems concurrent engineering approach includes in the scope of development effort, not only the development organization, but also the other life cycle processes that a given development organization performs. The approach is exemplified using the case of the development of a ‘green car‘, a car that is environmentally friendly.
Bias Amelioration in Tradeoff Studies
Authors: Smith Eric D.
Published: November 2014

Building large and complex systems continues to be a significant challenge for today's systems engineers and integrators. This tutorial sets forth new ways of thinking that could lead to improvements in how systems engineering and integration are carried out. In particular, nine new perspectives are suggested for “thinking outside the box”. Examples are provided for each, along with a discussion of their potential benefits. In addition, thinking in groups as well as historical thinking suggestions are examined. A summary provides an overview of notions that represent departures from current mainstream approaches.
Synergistic Model‐Based Systems Engineering with SysML and OPM
Authors: Dori Dov
Published: November 2014

Model‐Based Systems Engineering (MBSE) is emerging as a pivotal paradigm, placing modeling as the underlying activity of systems' and products' lifecycle management. SysML is the OMG standard for MBSE, while Object‐Process Methodology (OPM), one of the six leading INCOSE MBSE methodologies, is in the process of becoming ISO standard and the basis for model‐based standards authoring. OPM and SysML complement each other, as each is especially suited for different lifecycle stages: OPM, which is simple and holistic, is most fit for the early conceptual stages, whereas SysML, which provides for expressing details, is good for later design stages. The tutorial introduces the principles, syntax, and semantics of OPM and SysML, highlighting their commonalities and differences, and showing how to use both in ways that promote synergy and improve critical system features, notably clarity, consistency, and completeness. The resulting model is an indispensible blueprint that puts all the stakeholders on the same page across the system lifecycle span.
Establishing and Using a Risk Management Program Effectively
Authors: Powell Mark A.
Published: November 2014

We manage risk every day of our lives. You would think all good SE's would be good risk managers. Yet many enterprises fail because some unidentified or un‐handled risk materializes. Many enterprises fail to take advantage of positive risks (opportunities) that could all but ensure success. Risk Management is not as easy as it seems it should be.

This tutorial reveals to both the new SE and the seasoned veteran looking for a refresher the secrets of Risk Management and how to make it work. We will review the basic concepts of formal Risk Management and how it is executed in Systems Engineering. We will cover in depth all seven areas of Risk Management: Identification, Analysis, Assessment, Mitigation, Accounting, Planning, and Communication. Each of these areas will be approached with a specific emphasis on how they work together to make an enterprise successful. Further, we will set up a framework for introducing Risk Management within Systems Engineering, to work synergistically by integrating it with Project Management. And as icing on the cake, we will introduce some new methods for risk assessment that make the practice much more effective.
Defining Operational Concepts using SysML: System Definition from the Human Perspective
Authors: Jorgensen Raymond
Published: November 2014

Uses cases & scenarios are an effective means of assessing system operation from the user's perspective. Rather than focus on obscure “functional requirements”, which are oftentimes elusive to grasp and difficult for the end‐user to understand, this tutorial explores how an operational concept based on use cases & scenarios can be used to focus on the user's perspective of the system, with subsequent improvements in the completeness and understanding of the functional requirements. This tutorial explores why an Operational Concept document is written, what the Operational Concept is, and how it can be effectively applied on your project through use case & scenario descriptions and SysML diagramming. Tutorial includes a workshop format to apply lessons learned and discuss strategies. SysML concepts explored include use case diagrams and activity diagrams to express main use case scenarios, alternate courses, exception cases, and extension use cases.
1.1.1 Development of Patrolling Schemes for Improved Border Security Performance through an Evolutionary Approach
Authors: Muaafa Mohammed , Ramirez‐Marquez José Emmanuel
Published: November 2014

The potential danger of unauthorized cross‐border activities is a considerable national and trasnational security threat that has raised international concern over enhanced border control. In many cases, the vast size and geographical diversity of international borders increase the complexity of border security missions. Such situations require an optimal surveillance strategy to help prevent and deter suspicious activities along borders. This paper focuses on developing patrolling schemes that deploy personnel to patrol designated areas previously suspected for having unauthorized cross‐border attempts. A multi‐objective optimization model is proposed to design patrolling schemes that minimize vulnerability and cost. An evolutionary algorithm is used to generate a Pareto set of optimal solutions, which are characterized by the routes of patrol units. Illustrative examples are provided to discuss the effectiveness of the model.
1.2.3 Designing a Knowledge Management System (KMS) for a complex engineering environment
Authors: Saraf Neha , Siemieniuch Carys
Published: November 2014

This paper forms a part of the Engineering Doctorate (EngD) project sponsored by EPSRC and Thales UK. The aim of this project is to design a knowledge management system (KMS) to be applied in a complex engineering environment in the military electronics domain, by identifying and addressing issues in the sponsor organisation, Thales UK. This paper discusses the systems engineering approach taken during the requirement analysis phase and describes the key issues emerging which will impact on the design of the KMS. After giving a brief introduction of the project and methodology used in the project, the paper presents a creation of a theoretical baseline built to understand the questions involved in creating KMS (section 3), an investigation carried out in the company environment to explore existing KM issues (Section 4 and 5), and a dual case study approach undertaken to further investigate KM (section 6). The paper is concluded by summarising the key achievements of the research and outlining the approach for future steps for formal requirement generation.
1.3.1 How to use systems architecture to specify the operational perimeter of an innovative product line
Authors: BERREBI Johanna , Krob Daniel
Published: November 2014

In industrial companies, it can be observed that research and development departments encounter difficulties during the innovation phase. Indeed, searchers have a tendency to optimize technologies in an unorganized way. As a result, they often end up with products that do not fit with the industrial needs and are stored on shelves. The emergence of new products in an industrial perimeter should be the result of a careful study of the context, environment constrains, and stakeholder's needs which have to be translated into requirements building a frame for innovation. This article's aim is to propose a suitable methodology (system architecture) to manage and supervise innovation in order to create or improve a product. We will apply this methodology to a wireless sensor network system which is an innovative product research field launch by the rising aeronautic need to lighten aircrafts. As this system's final purpose is to be installed on aircrafts, we will try to build a family of modular systems with common basic module and specific compatible modules.
1.6.1 xFFBD: towards a formal yet functional modeling language for system designers
Authors: AIZIER Bruno , LIZY‐DESTREZ Stéphanie , SEIDNER Charlotte , CHAPURLAT Vincent , PRUN Daniel , WIPPLER Jean‐Luc
Published: November 2014

Although the eFFBD formalism dates back to the 1990s (or even, in a simplified form, the 1950s), it seems that it is still not as much used by the Systems Engineering community as it could. Indeed, eFFBD is a modeling language focusing on functional paradigm i.e. allowing functional and behavioral modeling and reasoning about a system. Currently, it is often confronted or compared to other languages such as SysML for activity modeling (activity diagrams) based on object paradigm. This paper aims to demonstrate the interest and the potential advantages for systems designers, like most of the discipline‐oriented designers to dispose of an enriched (conceptually and semantically) eFFBD modeling language called here xFFBD. This has to be a credible framework for modeling, communicating and reasoning about complex systems. After shortly recalling the history, the key concepts and capabilities of eFFBD, this paper compares eFFBD with other formalisms considered here as relevant for the study, Petri nets and SysML. Several leads are then identified and discussed in order to improve the eFFBD language and to provide a first draft version of xFFBD specification.
2.2.1 Decision Management (DM) as the engine for scalable cross domain Systems Engineering (SE)
Authors: Mendonza Pradeep , Fitch John A.
Published: November 2014

Decisions create the future in any industry or human endeavor. A robust Decision Management (DM) capability is the key enabler for accelerating the benefits of Systems Engineering (SE) discipline to new domains. Effective Decision Management is comprised of three elements: 1) decision patterns; 2) DM methods engine; 3) decision‐centric information model.

INCOSE can leverage DM as an engine for SE outreach to new industries and domains. DM is highly scalable and integrates knowledge from many processes and stakeholders. A “decisions‐first” outreach strategy offers a clear value proposition to the primary stakeholders who must be convinced of the benefits of SE discipline. Existing decision‐makers gain a new set of techniques that improve decision quality, speed and execution. Subject matter experts gain a method for influencing designs with their unique knowledge and preserving their knowledge in the form of decision patterns. Project managers gain the ability to proactively identify and prioritize decisions and manage their impact on project cost/schedule baselines. Solution developers gain a better understanding of the upstream decisions that drive their requirements.

Most of the cross‐domain benefits of DM can be demonstrated through rapid‐payback pilots without commitment to wholesale adoption of more comprehensive, complex and costly SE frameworks. The authors propose to engage INCOSE's Decision Analysis working group as the forum for investigating the cross‐domain applicability of DM.
2.6.2 Sociotechnical systems resilience
Authors: Ruault Jean‐René , Vanderhaegen Frédéric , Luzeaux Dominique
Published: November 2014

Systems engineering deals with artificial systems conceived by human beings. These systems are combinations of elements aiming at one or more definite goals. Sociotechnical systems consist in technical parts, concerning systems engineering issues, and in human and organizational parts, concerning medical and social sciences issues. Resilience reports to the capacity of sociotechnical systems to adjust faced with disturbing events, to adapt and learn the adequate rules of adaptation, when the disturbances are out of the specified perimeter of the system's adaptation mechanisms. After having characterized resilience, the article highlights its relevance to the field of the sociotechnical systems. Then, sociotechnical systems' resilience is articulated with systems engineering and architecture in order to evolve systems engineering processes, engineering models, system architecture and enabling systems. Lastly, the article underlines the fact that systems engineering is necessary and owes being supplemented of good practices of management which contribute to the of sociotechnical systems resilience.
3.1.2 Machine Learning technologies for the Requirements Analysis in Complex Systems
Authors: Nardini M. , Ciambra F. , Garzoli F. , Croce D. , Cao D. De , Basili R.
Published: November 2014

Requirement Analysis is a relevant application area for a variety of Semantic Technologies related to the extraction, disambiguation and exploitation of the knowledge derived from technical requirement documents. Most methods rely on shallow language processing technologies for the automatic extraction of core concepts (e.g. components/devices, their parts and functionalities) and norms (e.g. constraints on the use of components). Few works have been devoted to study paraphrasing (i.e. textual equivalence between requirement definitions) for consistency checking and redundancy elimination. We propose here a distributional method to train a kernel‐based learning algorithm (i.e. SVM), as a cost‐effective approach to validate requirements from text in support of Requirement Analysis in the design of a Complex Systems, i.e. Naval Combat Systems. These latter are complex systems based on software components able to manage all the Combat System Equipment in different mission scenarios. We will describe the application of Recognition of Textual Entailment (RTE) techniques based on data‐driven learning methods to this scenario. While modeling the asymmetric logical relation of entailment between two textual descriptions (i.e. an hypothesis and its thesis), RTE can be here applied to the validation step of compositions between system functionalities described in the requirement specification texts. Early evidences are here discussed, as a proof of the strong applicability of the method to the general case and to other realistic scenarios in System Engineering.
3.4.2 Putting the System Back Into Systems Engineering
Authors: Eng Bernhard Meyer M
Published: November 2014

This paper opens with some observations that underline the confusion regarding systems engineering, even amongst its fraternity. It proposes a “return to the roots” to revisit the definition and understanding of systems and systems engineering. A three‐dimensional Systems Engineering Space (SE‐Space) is introduced that combines system, engineering, and time. These “dimensions” are described to gain an understanding of their importance and relevance in systems engineering. Emphasis is placed on the generic nature of a system and its attributes or characteristics, as they apply to the realisation stage of systems. Concepts of this proposed Generic Systems Engineering (Generic‐SE) approach are illustrated with reference to a sample rotorcraft environment, emphasising a hierarchical structuring. It concludes with an appraisal and mapping of ISO/IEC 15288 processes against this proposed Generic‐SE approach. This demonstrates the versatility of a generic systems engineering approach, which encourages this back to the roots appeal.
4.2.1 Platforms for Engineering Experimental Biomedical Systems
Authors: Mosteller Matthew , Ghodssi Reza , Austin Mark , Yang Shah‐An
Published: November 2014

The systematic design, validation, and verification of systems for biomedical experiments in laboratory and clinical applications are complex activities due to the highly stochastic nature of biological systems. This paper presents a platform framework for the modeling of these biological components in the context of system‐level analysis, facilitating early validation and verification of biomedical devices. Looking forward, the capabilities of this platform enable the development of more efficient and effective experimental biomedical systems.
4.4.2 MBSE Feasibility Study to improve PLM Business Solution System Specification and Design
Authors: Marco Alemanni , Angelo Corallo , Elena Latino Maria , Scarl Dhitech , Elena Valfrè
Published: November 2014

Ambiguous requirements are the main cause of failure in PLM business solution applications development. SysML used in a Model‐Based Systems Engineering (MBSE) development process can mitigate this primary source of error. MBSE moves system engineering practices from document‐centric to model‐centric approach in which the model becomes the primary systems engineering artefact to represent system specification and design. The adoption of this new approach requires careful consideration of the cultural change, adequate training, and a new methodology.

This paper describes the feasibility study, results and lesson learned on the MBSE maturity acquired in Alenia Aermacchi Information System and Engineering departments applying MBSE to Product Life‐Cycle Management (PLM) and Document Management. It is based on the University of Salento expertise about modelling languages and on the Alenia Aermacchi experience on System Engineering. SysML has been used as standard language, IBM Harmony Methodology as system engineering methodology and IBM Rhapsody as modelling tool.
5.1.2 Entering a Brave New World: Applying Systems Engineering to American Infrastructure Projects
Authors: Hoehne Oliver M.
Published: November 2014

Systems Engineering is a well accepted engineering discipline in most industries, including information technology, defense, aerospace, automobile, and medicine, across the globe. When it comes to railroad infrastructure projects in the United States, however, these projects inevitably rely on the Plans, Specifications and Estimate (PS&E) process used in the construction industry. Large scale conventional rail projects are highly complex. Large scale high‐speed rail systems are even more so. Systems Engineering inevitably has a fundamental impact on the traditional engineering approach of railroad infrastructure projects, perhaps not unlike what the introduction of electrification did during the steam locomotive era, as depicted in Figure 1.

This technical paper presents a case study illustrating how Systems Engineering is being combined with the established Plans, Specifications and Estimate approach, and how the $65 billion California High Speed Train Project (full Phase 1 in 2010 dollars) is benefitting from the values of Systems Engineering [1].

This paper provides a brief overview of the California High‐Speed Train Project, describes the Systems Engineering (SE) objectives, discusses how SE was planned and implemented, and demonstrates how Systems Engineering is benefitting the design of the California High‐Speed Train Project (CHSTP).
5.3.2 Information Technology (IT) Project Management Failures: Historical and Evolutionary Walk through from a Social Dynamic Perspective – A Primer to “Preemptive and Adaptive Project Management”
Authors: Stoica Rosana , Brouse Peggy
Published: November 2014

Despite the evolution and sophistication of project management, a great percentage of IT projects are still failing. For centuries projects have experienced complex social interdependencies. This paper treats projects within a social context and proposes the investigation of projects management challenges by applying the “social” lens. This construct serves as a primer to introduce system dynamics principles to project management applications to further the current understanding of project “soft” factors and their interdependencies. The authors conclude that a systems dynamic approach using social lens provides the appropriate construct for a new paradigm in IT project management: “Preemptive and Adaptive”. Intangible Soft Factors (ISF's) concept is introduced. The authors hypothesize that this construct provides the appropriate balance to further investigate the ability to successfully manage IT project outcomes by means of understanding the disguised yet bonding and exceedingly influential “social” forces overlooked as a dominant project agent.
6.5.2 MBSE Supports Manufacturing System Design
Authors: Batarseh Ola , McGinnis Leon , Lorenz Jim
Published: November 2014

To date, Model Based Systems Engineering (MBSE) has been deployed primarily in the product design domain. However, manufacturing system design problems are equally challenging, but there are many fewer design support tools in the hands of system designers. This paper describes how MBSE principles and methods can be used to make a powerful analysis tool readily accessible to manufacturing systems engineers. The MagicDraw™ SysML tool was used to create a domain specific language for electronics assembly, and the tool itself was customized to present an interface that was relatively easy for the manufacturing domain experts to use to create descriptions of products, resources, and processes. The domain specific language was mapped to a metamodel of the Arena™ discrete event simulation language, and the ATL© model transformation tool was used to automate the generation of the an instance of a simulation model from an instance of the electronics assembly system. The use of this kind of analysis automation can reduce by up to a factor of ten the time required to develop such simulation models.
7.7.1 Getting the right requirements right
Authors: Kasser Joseph
Published: November 2014

Research has shown that there is an on‐going consensus that:

good requirements are critical to the success of a project

the current requirements paradigm produces poorly written requirements and

ways of producing better requirements have been around for more than 20 years.

So, instead of producing yet another paper on how to write better requirements, this paper begins by posing the following question: why do systems and software engineers continue to produce poor requirements when ways to write good requirements have been documented in conference papers and textbooks? The paper then documents findings from research into the problem via the systems thinking perspectives and hypothesises that there are two requirements paradigms; the original A paradigm and the current B paradigm which is inherently flawed. The paper then dissolves the problem of poor requirements by applying technology to reduce the need for most of the requirements written today.
8.4.1 Assessing Uncertain Benefits: a Valuation Approach for Strategic Changeability (VASC)
Authors: Fitzgerald Matthew E. , Ross Adam M. , Rhodes Donna H.
Published: November 2014

This paper describes a new technique for investigating the value of changeability in complex engineering systems early in the design process. The work is an extension of Epoch‐Era Analysis, a framework that models contextual uncertainties over a system's lifecycle as a sequence of finite‐duration periods of time. Strategies, defined as statements of intended change mechanism usage, are used to identify executed change mechanisms across the various contexts. Changeability is then evaluated in both time‐independent (multi‐epoch) and time‐dependent (era) domains, using a proposed set of metrics designed to explore different dimensions of value. A case study demonstrates the application of the technique to a conceptual space system.
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

Root 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

The 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

Much 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

The 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

Modeling 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

This 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

The 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

Thales 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

Safety 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

For 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

In 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

This 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

This 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

The 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.