bluuebunny/crossref_metadata_2025 huggingface dataset:
3.2.2 What is wrong with Reliability Engineering?
Authors: Barnard R.W.A.
Published: November 2014

Notwithstanding the implementation of reliability engineering programs by companies, it is not uncommon to observe many instances of low field reliability. This paper briefly describes the essence of reliability engineering, which has prevention of failure as primary objective. Possible reasons for the apparent failure of reliability engineering, especially as practised by the defence industry, are given. It argues that incorrect practices are often applied, frequently performed by incorrect people in the organisation, and at the incorrect time during the product or system life cycle. The value of reliability engineering as specialty area of systems engineering can be improved by learning from best practices used by industry leaders.
4.1.0 Systems Acceptance for SoS: Rail/Transit Case Studies
Authors: Hayward‐Williams C , Halliday B , Brouwer P , Hodges B
Published: November 2014

Rail/Transit systems are effectively comprised of many layered and complex systems – hence a System of Systems (SoS). Upgrading, expanding and modernizing rail/transit systems becomes a complex endeavor as portions of a rail/network are modified and then must ultimately be accepted as a complete, operational system before being introduced/integrated back into the rest of the active rail network. The multi‐layered system acceptance creates challenges that relate to planning, modeling, contracting and deployment.

SE practitioners across all industries are urged to join this SoS exchange based on rail/transit case studies and offer comparative or contrasting experiences from their domains.
4.2.2 Technology Readiness Assessment a Systems Engineering Process to Ensure All Your Pegs and Holes are Round Before Beginning Development
Authors: Walker John Bryan
Published: November 2014

Technology insertion can be like trying to fit a square peg into a round hole if the technology is not mature enough for the system beginning development. The Technology Readiness Assessment (TRA) is a process that takes it's pedigree from NASA. NASA needed a systematic approach to assess the maturity of a particular technology and a consistent comparison of maturity between different types of technology. An approach using Technology Readiness Levels (TRLs) was institutionalized when it was incorporated in the NASA Management Instruction 7100 [Mankins 1995]. This was the beginning of the TRA process. It is now a readily accepted Systems Engineering process for all major U.S.A. Department of Defense (DOD) acquisitions. The use of the TRA is expanding and should be considered for systems being considered for the sustainability of the planet. The TRA is best used up front before system development when deciding on competing technologies to be used and before production when deciding if technologies have matured enough to insure production feasibility. In this paper I shall discuss the key components of the TRA, the identification of Critical Technology Elements (CTE)s and the evaluation of those CTEs against a Technology Readiness Level scale. The purpose of the discussion is to expand the use of the TRA into other Systems Engineering technology intensive domains where continuous systems development is being performed.
4.3.1 Demonstrating professionalism through competency assessment
Authors: Holt Jon , Perry Simon , Currie Malcolm
Published: November 2014

In order to be successful in business, it is essential that we can inspire our clients with confidence. This confidence must exist at both the organisational and individual level. As practising systems engineers, it is essential that we are able to demonstrate our professionalism in everything that we do and, hence, inspire confidence in our colleagues and clients.

This paper looks at the issue of professionalism through competency assessment. The INCOSE competencies framework is used as an example of a good best‐practice model and an assessment process, known as UCAM, is introduced and discussed.

A real‐life industrial case study taken from the rail industry is presented which discusses the practical business benefits of effective competency assessment and some actual results are presented. Finally, some general comments and observations are included regarding the INCOSE competency framework.
4.3.3 Capability Engineering within Canadian Defence: Experimentation and Lessons Learned
Authors: Lalancette Claire , Lizotte Michel , Nécaille Christophe , Robbins Wayne , Waruszynski Barbara
Published: November 2014

This paper summarizes the results of an experimental evaluation conducted to assess the Capability Engineering approach developed for the Canadian Forces/Department of National Defence to facilitate decision‐making on strategic investments and divestments. This work was performed as part of the Collaborative Capability Definition, Engineering and Management Technology Demonstration Project (CapDEM TDP). Based on the systems engineering paradigm, the approach is articulated around three axes: People, Process and Materiel. The focus of this paper is on the lessons learned from Exercise Gamma, the last of three validation exercises which are part of an evaluation strategy attempting to evolve Capability Engineering from theory into practice. Lessons learned have helped to identify specific improvements as well as critical success factors for the implementation and application of Capability Engineering.
5.1.2 Designing Embedded Systems using Heterogeneous Rich Components1
Authors: Josko Bernhard , Ma Qin , Metzner Alexander
Published: November 2014

This paper aims at boosting the level of re‐use in embedded system design. A key concept to achieve this goal is given by an appropriate heterogeneous rich component model – called HRC – which is (1) expressive enough to cover the complete development cycle from high‐level specifications to design models and which (2) addresses both functional and non‐functional aspects. HRC components are characterized by formal contracts allowing various analysis techniques to validate a design already in early design stages. The described approach has been developed jointly with the partners of the SPEEDS project.
6.2.1 Function Durability over System's Life Span
Authors: Gasser Laurent
Published: November 2014

This paper presents some of the heuristics that a system architect could use to preserve the full operational potential during the system's intended life span, and beyond. The proposed heuristics prevent a single subsystem from severely limiting the evolution and maintenance potential of the whole system. The durability of the system's function ought to have precedence on the subsystems' own evolution, resulting in improved system robustness. The scope of function durability is first exposed. Side topics are then examined and the way they relate to the system viability is discussed. The second part introduces the proposed heuristics. Rationale and illustrations are given for each of them.
9.2.1 Using SysML and UML To Develop and Implement Interoperable System Components for Engagement Simulations
Authors: Haley Thomas , Cerenzia Judith , Diederich David , Friedenthal Sanford
Published: November 2014

The Torpedo Enterprise Advanced Modeling and Simulation (TEAMS) project is an initiative funded by the Office of Naval Research to develop a cross‐enterprise, collaborative undersea warfare modeling and simulation (M&S) environment using reusable components that can be composed into simulations. This environment will include an open systems architecture and result in the sharing and leveraging of legacy and new‐development resources; it will support the development of M&S tools and the application of these tools across the lifecycle of undersea weapons. TEAMS initial model was delivered in the Unified Modeling Language (UML). When the Object Management Group (OMG) adopted the OMG System Modeling Language (OMG SysML™) specification, the Open Systems Joint Task Force of the Office of Secretary of Defense funded TEAMS to assess the utility of applying SysML in place of UML. This paper describes the torpedo M&S domain as it relates to TEAMS, discusses the application of SysML to existing UML artifacts, and assesses the utility of SysML from the TEAMS perspective.
10.2.2 Research on a Framework for Systems Engineering Tools for Australian Small and Medium Enterprises
Authors: Tran Xuan‐Linh , Ferris Timothy , Huynh Thomas V. , Shoval Shraga
Published: November 2014

To be self‐reliant and competitive in winning and maintaining defence contracts, the Australian Small and Medium Enterprises (SMEs) need to improve their systems capability. By systems capability it is meant effectual use of sound systems engineering (SE) processes and effective use of SE tools. Unlike most large organisations, the Australian SMEs have not widely employed SE processes and tools in their endeavour. In addition, the SE software tools the Australian SMEs are currently using do not appear to have effectively aided them with their work. This paper describes research to develop a framework for aiding Australian SMEs in effectively acquiring and applying SE processes and tools and thereby improving their systems capability. Specifically, the research involves a collection and analysis of information about the fundamental nature of SMEs; an exploration of relationships between SE process and tools and the Australian SMEs; the development of requirements for SE tools functionality appropriate for SME needs; and the development of framework for acquiring and applying SE tools for SMEs. It also discusses the current outcomes of this research, which consist of a comprehensive research plan, a mapping of SE activities reported in INCOSE Symposia Proceedings (1994–2006) to the Hitchins‐Kasser‐Massie (HKM) framework, and a preliminary view of relationships between SMEs and SE tools. Finally, the final results of this research may be extendable to commercial and overseas SMEs.
10.3.2 Functional Capabilities In Complex Project Engineering
Authors: Jacobs Robert , Schenker Fred
Published: November 2014

Recent performance in the acquisition of large scale defense systems has not met expectations. The acquisition community in the U.S. Department of Defense has been challenged by the department's transition to network‐centric warfare, which leverages complex system collaborations to achieve significant new capabilities. Developing systems of systems or systems of services requires evolved system engineering and project management practices, and better integration of both. This paper presents early learning in this regard from one ongoing system‐of‐systems development program, the Single Integrated Air Picture (SIAP). A “functional capability” concept evolved to become a potentially unique definition of a project that has proved useful in a system‐of‐systems development context. This paper then explains a recommended structured‐development approach built on Functional Capabilities that yields artifacts promoting communication, specification, and work phasing. It also compares the approach to the CMMI™ to demonstrate the wide process applicability of Functional Capabilities.
11.2.1 Factors Related to the Implementation of ISSE: A Quality Perspective
Authors: Cline Bryan S.
Published: November 2014

‘Bolting on’ security functionality in Information Technology (IT) systems late in the System Development Life Cycle (SDLC) can be expensive and adversely affect system functionality and usability. Information Systems Security Engineering (ISSE) is a specialized application of systems engineering that addresses the identification of security requirements and their successful translation into IT system design. Yet experience has shown that security is often the “sacrificial lamb” when project managers seek to trade scope to meet cost and schedule requirements despite increasing security and privacy regulation in multiple industries. Given the proper application of ISSE would preclude such choices, overcoming barriers to implementation of ISSE in the SDLC would help project managers provide targeted application of scarce resources; facilitate proper security engineering; reduce overall risk to project scope, cost and schedule; and address the most critical IT security compliance issues affecting their project.
11.3.3 A Case for System Acceptance ‐ Progressive Assurance Practices on the East London Line Project
Authors: Knott Alan , Hodges Barry
Published: November 2014

The final product of the East London Line Project (ELLP), and hence the ‘ELL System’ to be accepted, is a fully operational railway comprising an infrastructure, rolling stock and operational resources and processes. The project has defined a structure for progressively decomposing the ELL System into ‘Levels’ as first the requirements and then products are developed and has also defined a comprehensive argument structure for collecting systems assurance evidence which builds up a robust ‘Technical Case’ as the project progresses through its engineering lifecycle towards final system acceptance. This paper describes some of the fundamental systems engineering concepts and principles, which provide an important structured framework for ‘Progressive Assurance’. To conclude the paper lessons learned to date are reported and recommendations for future application of the methodology are made.
KR06 A Systems Engineering Approach to Innovation Management
Authors: Davies Paul
Published: November 2014

Traditional approaches to innovation management have generally been ‘bottom‐up’, starting from suggestion schemes centred on existing, steady‐state processes and incremental product development. This lacks a holistic view of the business, and needs reconciliation with long‐term strategy that may include disruptive technology and business model changes. This paper covers a more balanced approach to innovation management, allowing both bottom‐up and top‐down ideas generation, prioritisation, and alignment with business strategy.
KR08 Achieving Sustainable Development in Southern California: Collaborative Learning through System Dynamics Modeling
Authors: Madachy Raymond , Haas Benjamin , Bradbury Hilary , Newell Josh , Rahimi Mansour , Vos Robert , Wolch Jennifer
Published: November 2014

Southern California's gateway to international commerce is through major ports in the San Pedro Bay. The University of Southern California is working with local business and other port stakeholders to enable collaborative learning about sustainable business practices. We are using system dynamics‐based models for participants to locate leverage points that yield the highest CO2 footprint reduction for the lowest cost for the shipping of goods from China through one of the ports. As goods movement is a process in which numerous business entities connect, it also offers an opportunity for a collaborative learning approach. We model key leverage points in the supply chain to explore the affects of potential business decisions on the CO2 footprint of shipping containers. These include options for global route choices and clean technologies for ships, rails and trucks. We are expanding the models for refined route options, adding cost functions, and composite clean technology choices across the transport modalities.
KR10 An Effective Collaboration of a Modeling Tool and a Simulation and Evaluation Framework
Authors: Fernández José L. , Mármol Gloria
Published: November 2014

System modeling tools contribute to the preparation of design artifacts for subsequent stages of the system development but frequently they failed to their contribution to the evaluation of the system modeled.

In the paper, we describe the approach we developed for real‐time systems modeling and models evaluation. This approach is named PPOOA‐Cheddar because it combines the PPOOA method and tool for architecting real‐time systems with the Cheddar framework for simulation and evaluation of real‐time systems. PPOOA and Cheddar tools were developed by independent groups, so we have to adapt PPOOA, the modeling tool we developed, to be integrated with the Cheddar evaluation framework.
KR13 Extended System Engineering – ESE: Integrating Usability Engineering in System Engineering
Authors: Zonnenshain Avigdor , Harel Avi
Published: November 2014

Users waste time trying to recover from their errors, resulting in productivity loss, reduced satisfaction and accidents. Common system engineering (SE) practices typically disregard system usability. The first part of this article presents real examples of the costs of having the user outside the system boundaries. Recently, researchers have proposed a new framework for complex system engineering (CSE), in which the users are included in the Extended System (ES). CSE considers the users as special cases of cognitive, self‐adaptive system elements. With this framework, the human factors (HF) may dominate the system performance and reliability. Current CSE methodology focuses on operability of systems with fuzzy boundaries, and it does not provide the means to solve the exemplified problems of simple, well defined interactive systems. The article presents a methodology for extended system engineering (ESE), a sub discipline of CSE specializing in the features and limitations of the human operators. Typically, usability professionals are concerned about ease of use during the initial stage more than about user errors. The multidisciplinary approach of having a usability expert in the development team falls short of solving the problems, unless the interface of the information flow between the usability experts and the system engineers is well defined. The article presents the principles and means for integrating usability in system engineering, so that user errors are eliminated, and their negative effects are reduced. Part of the principles and means presented here are applicable to the interaction between any elements of any system, regardless of their intelligence.
KR15 System Development With Virtual Teams In Collaborative Development Environments
Authors: Hause Matthew , Hause Martha
Published: November 2014

Technology has developed such that it allows for effective remote collaboration on system development in a team‐based environment. Two avionics examples of systems developed in such a way are the Airbus 380, and the Eurofighter, with development split between several European countries. Additionally, outsourcing has become endemic in the industry, providing advancement and much needed revenue for developing countries, but complicating development and integration issues. To illustrate the issues involved in remote collaboration, this paper investigates a study of the interactions of high and low performing distributed student teams on a development project. Results indicate that not only is communication crucial to a team's success but the process and timing of specific actions can have an impact on a team's performance. The paper also examines the system development lifecycle and how collaboration changes during the different phases of the project, and lessons to be applied to systems engineering.
KR20 From Process‐Driven to Knowledge‐Driven Requirements Engineering Using Domain Ontology
Authors: Kossmann Mario , Odeh Mohammed , Gillies Andrew , Wong Richard
Published: November 2014

The present paper discusses possible ways of how ontologies could be used to drive requirements and the requirements engineering (RE) process itself in an attempt to overcome many of the problems that large engineering‐focused companies encounter in trans‐national and multi‐disciplinary business contexts.

The current use of ontologies in the context of systems engineering (SE) is explored with an emphasis on applications in the RE domain, followed by concurrent approaches to RE. Then, the scope of RE is discussed and how it should be widened horizontally and vertically in order to more fully benefit from the positive impact of this discipline in relation to cost, schedule and quality, leading to knowledge‐driven RE rather than only process‐driven RE.

An example of a knowledge‐driven approach to RE in the form of OntoREM – a comprehensive, ontology‐driven RE methodology – is introduced, which is currently being developed at the University of the West of England in close cooperation with Airbus. Although this methodology is not yet mature enough and tested to be deployed operationally, some promising results can be expected from a series of applications of aspects of the methodology that are scheduled to be conducted in the context of the Integrated Wing Aerospace Technology Validation Programme, a GBP 34 million, multidisciplinary UK research undertaking, in the first two quarters of 2008.
Defining a Balanced Maritime Safety and Security System
Authors: Hiemstra Hans
Published: November 2014

Many systems are developed from a technical perspective. Our system engineers, and system architects have great ideas and normally we try to convince potential costumers to buy our wonderful new product. What we mostly forget is to think from the customers perspective and consider how this new product can be used in their organization. This seems like an open door, but requires a different attitude in thinking. This paper is about how we dealt with the problem of defining a Maritime Safety and Security system (MSS system) that could be sold throughout the world.
Systems Engineering and Tram Projects
Authors: Mason Chris
Published: November 2014

Complex interfaces exist in all large engineering projects. Tram projects bring particular complexity through the need to integrate major new infrastructure into an existing dense urban city fabric and engage with a wide variety of stakeholders with interfaces and requirements. This environment lends itself to a structured approach and this paper presents recent experience of applying a Systems Engineering approach to the design of a tram system.

Particular features and design challenges of tram systems are described, how they can be characterised in terms of Systems Engineering, the solutions implemented and lessons learned. The paper concludes that Systems Engineering clearly brings benefits in the complex world of trams, but whilst the industry is moving towards this approach there is still a long way to go. Clients and consultants are encouraged to actively promote Systems Engineering activities at all levels, to ensure the benefits are maximized to all.
1.1.1 Automated Metro – Ensuring Safety and Reliability with Minimum Human Intervention
Authors: Seng Yap Kwee , Wai Ng Hon , Chan Samuel , Weng Leong Kwok
Published: November 2014

Modern transit systems are very complex and have high level of automation. The introduction of fully automated metro system has greatly reduced the dependency on human to drive the train and offered greater flexibility in the system operation. Prior to the implementation of each new automated metro system, extensive study has to be undertaken to ensure that the safety and reliability of the automated system will not be compromised.

The paper describes Land Transport Authority (LTA)'s systems engineering process on safety and reliability for the design and construction of automated metro system projects in Singapore. The approach adopted has been proven to be successful through its implementation on several recent projects in achieving a high level of safety and reliability of automated metro systems.
1.1.3 Systemic Safety and Accident Modelling of Complex Socio‐technical Systems
Authors: Qureshi Zahid H. , Campbell Alistair
Published: November 2014

Modern systems such as transportation, defence, telecommunications, nuclear power plants, robots and autonomous vehicles are increasingly becoming more complex. This is leading to new kinds of system failures, safety issues and severe accidents. The traditional approaches to system design and safety analysis are not adequate to capture the complexities and dynamics of modern socio‐technical systems. This paper focuses on new approaches to safety and accident modelling of socio‐technical systems based on systems theory and cognitive systems engineering. We examine the contributions by organisational sociologists to safety in complex organisations managing and operating high‐risk technological systems. This paper recommends interdisciplinary research encompassing technology, human factors, and organisational sociology, in order to capture the complexity of modern socio‐technical systems from a broad systemic view for understanding the multi‐dimensional aspects of safety and accident causation.
1.3.2 Is There a Complete Project Plan? A Model‐Based Project Planning Approach
Authors: Sharon Amira , de Weck Olivier L. , Dori Dov
Published: November 2014

Project planning and control are the essentials of project management. The first steps of the project planning require some knowledge of the concept of the product that the project is expected to deliver. The initial project plan, scope of work, Work Breakdown Structure, and allocation of resources rely on understanding of at least the top‐level product functionality, architecture, and concept of operation. The project planning and control is an iterative process of derivation, refinement, and simulation of the product model, while maintaining traceability and coherence between the product model and the project plan at all levels. Nevertheless, existing representations or views for project planning, such as Gantt, PERT, and DSM, contain only a portion of the entire set of relationships among project entities. This paper outlines a model‐based approach to project planning, in which a joint project‐product OPM model is the basis for the various project management views.
3.1.1 Defining an Integration Readiness Level for Defense Acquisition
Authors: Sauser Brian J. , Long Michael , Forbes Eric , McGrory Suzanne E.
Published: November 2014

There is a tremendous need to analyze system interoperability within Defense for both government and industry. Part of this challenge is the need for a metric that can be used as a common ontology and assess the state of interoperability in system's development and acquisition. Previous research developments have created an Integration Readiness Level (IRL) that complements the well‐established Technology Readiness Level (TRL) of the Department of Defense. This paper expands upon this work with the objective of presenting a verified and validated IRL and supporting guide of critical maturation criteria. We will review the foundations of this IRL, describe our development of a “guide” to support the IRLs, present the results of a survey to assess the criticality of decision criteria in the “guide,” and conclude with a discussion of the results and their implications to defense acquisition.
3.1.2 Interoperability: a reliability challenge across systems and humans; illustrated by health care examples
Authors: Muller Gerrit
Published: November 2014

End‐to‐end functionality is often the result of cooperation between many systems. We will discuss interoperability of systems, including the humans involved. Root causes of interoperability problems are inconsistencies between the models of the world within the system and the actual situation in the world. The dynamics of time complicates interoperability even more.

Standards play a crucial role in facilitating interoperability. Unfortunately, compliance to standards is no guarantee for interoperability. Interoperability is required at many levels, from single technical systems to social systems. Abstraction is one of the means to cope with increased interoperability scope. However, rather detailed implementation issues may cause dangerous interoperability problems.

Interoperability has many dimensions: technical, applicational, social, and cultural. The ownership for interoperability is unclear. This unclear ownership in such multi‐dimensional problem space explains why interoperability is so difficult to achieve.
3.2.1 Proposal of method to estimate of the probability to fulfillment product's functional requirements
Authors: Semabukuro Rosely , de Paula José Roberto , Taranti Christian Giorgio Roberto , de Sousa Damiani José Henrique
Published: November 2014

This work proposes a method to estimate the probability of meeting functional requirements of complex products. The method uses concepts and techniques from Systems Engineering and from Reliability. Functional interactions represented in the Functional Flow Block Diagrams (FFBD) are translated into a correspondent configuration of the reliability block diagram (RBD), according to the method's conventions. After that, a reliability value is attributed to each component block, and using reliability evaluation methods the probability of meeting a particular functional requirement is estimated. An application example is presented by missile's subsystem.
3.2.3 Development of OMS/MP for the System Reliability
Authors: Lee Kyoung‐Haeng , Kwon Yong‐Soo , Kim Chul‐Whan
Published: November 2014

This work describes an essential process of reliability analysis in weapon systems. The OMS/MP providing essential data of RAM analysis must be prepared by user. However, data acquisition quantified by operational environment of the systems and related instructions are now insufficient to the reliable systems acquisition. OMS/MP based RAM factor is an essential requirements in reliability model analysis. The process of reliability analysis is also often done with an insufficient understanding of OMS/MP. This work proposed the improved reliability analysis process with RELEX. It is shown that the process is a good reasonable by its application of the weapon systems.
3.4.4 Building a Systems Engineering Framework for London Overground using Experiences from the East London Line Project (ELLP)
Authors: Hodges Barry , Knott Alan
Published: November 2014

London Overground is a passenger rail service under the responsibility of the Mayor of London, which is managed by Transport for London (TfL) and is operated by London Overground Rail Operations Limited (LOROL). London Overground forms part of the UK national rail network and Network Rail is the Infrastructure Manager (IM) as defined under the UK railways regulations except for a relatively short section of the East London Railway (ELR), for which Rail for London (RfL) is the IM. The current plan is for RfL to extend its IM duties to new routes such as the extensions of the ELR and to parts of the Crossrail route. The £1bn East London Line Project (ELLP) was responsible for the development of the ELR and the innovative Systems Engineering practices employed on that project have been reported in previous papers.

This paper consolidates the experiences and knowledge from the ELLP into a number of ‘lessons learned’. It then proceeds to describe how the development of a framework of systems engineering practices for RfL's new IM role has benefited from the experiences on the ELLP.
4.1.1 A Case Study of the Effects of Platform Software Selection on Information System Maintenance Cost ‐ An Example of Enterprise Search System Establishment ‐
Authors: Shimazu Keiko , Mori Kaoru , Morita Souhei , Okumura Yusuke
Published: November 2014

Enterprise search systems have been focused on since around 2005. However, there are very few case‐study reports/papers how to build enterprise search systems and how to provide their superior cost performance. We propose an importance of maintenance cost for system management, especially after system launch. Search engines, well known as Internet search, are generally employed as middleware of enterprise search systems. We tried an experimental study of estimating the system maintenance cost, in order to validate our assumption; the maintenance cost of enterprise search systems is based on an installation cost of those middleware search engines whose main characteristic is said to be simplicity of installation. We employed multiple search engines and performed experiments. We acquired results that the maintenance cost required for the installation of search engines. The results confirmed that our assumption is true to some extent.
4.2.2 LARGE SCALE SYSTEMS ENGINEERING OF HOUSING IN SINGAPORE
Authors: CHIA Eng Seng
Published: November 2014

This paper examines how the Housing Development Board (HDB) of Singapore provides low cost housing in addition to achieving other social, economic and political goals. It uses the large‐scale systems engineering framework to analyze these goals, the boundaries HDB has to maintain or overcome and the continuous improvements it had achieved. Finally it examines some of the lessons learnt and the challenges that HDB faces in the future. The human dimension of such an undertaking is especially important and will be highlighted throughout the paper.
4.3.1 Research on Creativity Education Incorporating Systems Engineering—An Example with “Intelligent Taiwan”
Authors: Peng Willy Y.S. , Hsu Victoria
Published: November 2014

Upon the arrival of the era of science and technology and information, pluralism and diversification become important trend of industrial development. Facing the rapid industrial revolution and information explosion, human being's creativity has attracted attention; a lot of studies have been done on creativity, resulting in many theories, which have been applied in various areas in recent years.

This research focuses on Taiwan's current technology policy, known as “Intelligent Taiwan”, and discusses the possible future Intelligence systems and issues related to continuous development of humanism. We also propose a Three‐Dimensional systems engineering framework (5‐layer extendable mode), which is adaptable to the future blue print and full of creativity. According to the introduction of the multi‐layer value of human, nature, and esthetics, which is developed as the structure of the proposed Three‐Dimensional framework, we further discuss the different value perspectives, life‐style, and future influence, of systems engineering thinking. In addition, in this paper we also recommend a new thinking of the systems engineering education to link the creativity education. Hence we can expect that the talents trained in the educational way would develop more mew methods, new conceptions, and new theories in the intelligent systems. In this case, our society can become more wholesome, have more excellent engineering creativities, develop continuous new innovations, and finally achieve the intelligent life – Sustainable Humanity and Nature Symbiosis.
4.3.3 Enabling Collaborative Decision Making: A Process for Integrating Novel Systems Engineering Tools and Methods for Renewable Energy Portfolio Analysis
Authors: Ender Tommer R. , Haynes Comas , Murphy Jonathan , McDermott Tom
Published: November 2014

Increasingly complex problems drive systems engineers to develop novel decision making processes. The breadth of complex problems demands the interaction of various groups, each focusing on specific areas but all addressing a higher level common cause. The process brought forth in this paper integrates a series of methods, some widely accepted and others which are novel in nature. Quality Function Deployment is used to capture customer desires and focus engineering level requirements. Multi‐Attribute Decision Making is used to identify system configurations when multiple and competing objectives exist, which is a situation where traditional optimization struggles. The process of surrogate modeling is introduced to rapidly access elements of modeling and simulation, a necessary step to analyze system options. The very integration of these methods enables collaborative decision making. A proof of concept is presented where each of these methods is applied to aid in the portfolio analysis of renewable energy system options for a remote off‐grid site.
7.1.2 Architecting as a Means of Bounding Risk in the Future
Authors: Kepchar Kenneth J
Published: November 2014

Traditional architecture development efforts have deferred most risk considerations until after the functional architecture has been established and the imbedded concepts are being turned into operational solutions. This paper discusses a framework that moves Risk Management “upstream” and integrates it into the architecture development process. Including risk management at the architectural development stage provides early insight into the delicate balancing act between the benefits anticipated vs. risks incurred in selecting (or not selecting) features of candidate architectures to address stakeholder needs driving the scope and context of the architectural choices. Thus, application of risk management during architectural development provides a proper balance between risk and opportunity, avoids potential unacceptable risks where appropriate, and takes a proactive and well‐planned role in anticipating and responding to risks prior to implementation.
8.3.1 How to Achieve the Most Important Requirement
Authors: Malotaux Niels
Published: November 2014

The most important requirement for most projects is time ‐ time for completion. Still, most projects are late. Isn't it weird that projects apparently judge all other requirements more important than the requirement of time while time is one of the most important requirements? Both Project Management (responsible for the project) and Systems Engineering (responsible for the product) are responsible for the consequences of ignoring this important requirement. This paper describes why it is important to be on time, what measures we can take to make sure we are on time (and which often applied intuitive measures don't work!), and how we can use Evolutionary Planning techniques to make sure that we will be on time, or, if that is simply impossible, to take the consequence. These techniques allow us in the early stages of our project to predict and to optimize what will be ready at a certain time.
10.1.4 Application of a Global Systems Engineering Competency Framework
Authors: Arnold Eileen
Published: November 2014

This paper was written to provide a competency model implementation example, emphasizing a usable competency framework as a continuation of the well‐received International Council on Systems Engineering International Symposium 2008 paper entitled, “Global Systems Engineering Competencies: A Business Advantage (Arnold, 2008). The framework addresses activities in the form of a case study for implementing a global East Meets West, 3‐D Systems Engineering competency model at a hypothetical company, Global Avionics Proactive Systems (GAPS). The motivations for the development of this framework are based on the author's perceived business need for visualization of the lean, rapid creation and deployment of a 3‐D competency framework usable at several layers of a global enterprise, applicable to a wide range of industry, government, and academic situations.
An Optimization‐based Composite Indicators Approach to Performance Assessment
Authors: ZHOU Peng , ZHOU Dequn , POH Kim Leng
Published: November 2014

Composite indicators (CIs) approach has been widely accepted as a useful tool for assessing system performance at macro level. Several recent studies have shown that the weighted product (WP) method, a multiple criteria decision analysis method, may be a good choice in constructing CIs. However, a problem in its application is the subjectivity in determining the weights for sub‐indicators. This paper extends the WP method and proposes an optimization‐based approach to constructing CIs. The proposed approach requires no prior knowledge of the weights for sub‐indicators. The weights used can be generated by solving a series of multiplicative DEA type models that can be transformed into equivalent linear programs. Additional information on the weights can be easily incorporated into the proposed models. A case study on assessing the performance of APEC economies towards sustainable energy development is finally presented to illustrate the use of the approach.
Tutorial Human Side of Systems Architecting
Authors: Muller Gerrit
Published: November 2014

Architects play a crucial role in creating systems that fit well in the human needs. The creation of these systems requires many human interactions between all stakeholders. The background of architects, however, is completely different, mostly technical. We bring insight in the human aspects of systems architecting and we provide an approach with related tools to address the human aspects.
1.3.1 Design principles for Ultra‐Large‐Scale (ULS) Systems
Authors: Sillitto Hillary G
Published: November 2014

Ultra‐Large‐scale Systems (ULSS)1 are a major new challenge for systems and software engineering. Current engineering practice is ahead of the science — we are building systems we do not know how to characterise or analyse, and whose behaviour we cannot fully predict. ULS are characterised by complexity, dominated by emergence, and exist in a state of constant reconfiguration and evolution; all of which make untenable a reductionist approach to engineering and a “closed system” approach to specification and certification.

This paper recommends ten design principles and five design practices for ULS systems, drawing on known systems engineering practice and an understanding of how complexity science is applied in other domains. The paper offers practitioners a strategy and a practical approach to deal with ULS systems — or indeed any system that is larger scale and more complex than those they are accustomed to dealing with—and shows academics some possible routes to addressing the research challenges set out in the SEI report on ULS systems.
1.4.1 Reducing Risk for the Next Generation Nuclear Plant
Authors: Beck John M. , Opare Emmanuel O. , Heydt Harold J. , Oswald Kyle B.
Published: November 2014

The Next Generation Nuclear Plant (NGNP) Project, managed by the Idaho National Laboratory (INL), is directed by the Energy Policy Act of 2005, to research, develop, design, construct, and operate a prototype forth generation nuclear reactor to meet the needs of the 21st Century. As with all large projects developing and deploying new technologies, the NGNP has numerous risks that need to be identified, tracked, mitigated, and reduced in order for successful project completion.

A Risk Management Plan (RMP) was created to outline the process the INL is using to manage the risks and reduction strategies for the NGNP Project. Integral to the RMP is the development and use of a Risk Management System (RMS). The RMS is a tool that supports management and monitoring of the project risks. The RMS does not only contain a risk register, but other functionality that allows decision makers, engineering staff, and technology researchers to review and monitor the risks as the project matures.
3.4.1 So what is “in service systems engineering”?
Authors: Kemp Duncan
Published: November 2014

This paper has been produced to help the INCOSE UK In‐Service Systems working group understand the different perspectives of in service systems engineering. It describes four related perspectives of systems engineering in service systems, specifically:

The paper concludes that that it is considerable benefit to considering all four perspectives, as:

Managing the system through life to ensure it remains safe and delivers the required performance by monitoring the material state of the system against its design intent and commissioning update, upkeep and upgrade as necessary.

Improving the system performance by upgrading and updating the system to meet a new/existing requirement.

Using the system to deliver operational services by defining the services to be delivered, designing and implementing them and continuously improving them

Reducing the cost of the system and managing obsolescence by optimising the system's supply network

They increase the range of options to improve system effectiveness and reduce cost of ownership

They highlight some of the reasons why in‐service systems are so difficult to change

The show some of the cultural misunderstandings that can occur between the systems engineering and in‐service support communities.

Finally this paper has confirmed the benefits of Checkland's soft systems in clarifying a complex situation.
3.4.2 An Initiative to Strengthen Guidance on the Systems Engineering of Systems which are Already in Service: First Progress Report
Authors: Elliott Bruce , Panter Glenn
Published: November 2014

A number of INCOSE members believe that, while the principles underpinning SE remain the same across the lifecycle, some of the issues concerned with sustaining existing systems are more problematic than when realising new systems, and the existing SE Body of Knowledge is not as strong in these areas as it could be.

A working group within the UK Chapter of INCOSE has been working for two years to strengthen SE guidance to serve better the large number of systems engineers who are working on systems that have entered service. An international working group has been formed to take the work further. It is timely to provide a report on the work to date so that the emerging conclusions can be scrutinised, challenged and improved upon and this paper provides just such a report.
4.3.2 Requirements Engineering for Trusted Embedded Systems
Authors: Fernández José L. , Alonso Rubén , Gómez Francisco , Jouvray Christophe , Rouxel Yann , Pérez Antonio
Published: November 2014

Trusted computing is a complex and multidimensional issue, and its application to embedded systems has some particularities not found in business and desktop computing. Trust for embedded systems differs from traditional trust because these systems have physical accessibility, resource constraints and real‐time requirements.

In this paper, we describe the approach followed to specify trust requirements for the ITEA2 project TECOM (Trusted Embedded Computing)1. Using these requirements, the project partners developed embedded systems in diverse areas such as home control, video surveillance, digital content delivery, automotive, and communications gateways for remote maintenance.

The approach for the engineering of trust requirements presented here is based on two principles: a common conceptual model to identify the trust concepts for embedded systems and their relationships, and a well‐defined process to elicit and specify embedded systems requirements.
4.4.1 Dimensions of Understanding of Systems Engineering
Authors: Ferris Timothy L.J. , Peng Willy Y.S. , Hsu Victoria
Published: November 2014

This paper continues work begun by Hitchins with the development of the 5‐layer model of systems engineering. Hitchins' work was later extended to form the Hitchins‐Kasser‐Massie representation of systems engineering, HKM Framework, which adds a time dimension related to the stages of a project. The HKM Framework describes the layers of concern and the stages and types of projects at which they are dominant interests. In this paper we introduce a solid space concept to the HKM Framework based on Maslow's Hierarchy of Needs and Palmer's Modes of Being. The additional dimensions are useful to guide thinking about the purpose of the product system which is the focus of the project and the kind of existence which it has at the various stages of development. These additional dimensions are expected to be useful in the development of a framework for developing processes to guide the development through an appropriate path to achieve the desired outcome.
4.5.1 Requirements Analysis and Modeling Process (RAMP) for the Development of Complex Systems
Authors: Fanmuy Gauthier , Salinesi Camille , Hammami Omar , Roussel Jean‐Claude , Dauron Alain , Szczepaniak Richard , Picci Laurence
Published: November 2014

Requirement Analysis and Modeling Process (RAMP) is a new project born recently in France from a joint initiative between 3 major industrial companies belonging to different domains (Aerospace, Automotive, Energy), 2 SMEs (Service consulting, Tool supplier) and 3 Research Lab & Universities in order to improve the efficiency and quality of requirements expressed in natural language during the development of complex systems. Starting from a common view of the problem from industrial partners and the state of art in Requirement Engineering and Modelling, this project intends to deliver short & mid term solutions based on existing tool as well as promising research tracks in this field though a singular partnership organisation under the umbrella of AFIS (French Chapter of INCOSE).