bluuebunny/crossref_metadata_2025 huggingface dataset:
9.4.2 Incorporating Security and Survivability into the System of Systems Architecting
Authors: Singh Atmika , Dagli Cihan
Published: November 2014

System of systems (SoS) security and survivability issues have found prominence in the wake of increased importance of such large scale interconnected systems. The threats and risks associated with SoS architectures present unique challenges to system architects. SoS security and survivability practices are needed to ensure the performance and survival of the system under an intrusion. Current security engineering activities are performed independent of the system architecting process, leading to ad hoc solutions and after‐the‐fact reactions to vulnerabilities as discussed in (Evans et al. 2005). Literature on security and survivability oriented system architecting activities is far and few in between. This paper studies the major classes of threats and risks associated with SoS and the response to such vulnerabilities. Existing works were researched to outline the key characteristics of an effective security and survivability process that can be integrated with systems engineering activities. Overviews of three survivability architectures are provided on the basis of the identified criteria. Comments on the currently available solutions and future areas of emphasis are presented.
10.1.3 Evaluating Product Development Task Interactions Using Network Analysis
Authors: Collins Shawn , Yassine Ali A.
Published: November 2014

This paper proposes the integration of two useful systems engineering analysis tools, the Design Structure Matrix (DSM) and Network Analysis (NA) to study task interactions in a Product Development Process (PDP) using a small engineering company as a case study. The DSM is a matrix‐based systems engineering tool that enables streamlining of the PDP through task sequencing and simulation of project execution. NA techniques such as key players, centrality, influence, and brokerage provide methods to identify critical product development tasks and interactions to focus PDP improvement. Collecting interactions between product development tasks in matrix form provides opportunities to use DSM and NA techniques to identify highly central tasks and identify patterns of cross‐coupling between tasks and the groups performing those tasks. One benefit is the ability to describe feedback characteristics of critical PDP tasks. This is valuable when evaluating the impact of omitting, combining, or re‐sequencing task execution based on program‐specific constraints.
10.1.4 Systems Engineering for the Intelligent Enterprise – more important than you may think
Authors: Kaffenberger Ruediger
Published: November 2014

The emergence of the intelligent enterprise is very important for all of us, because the classical enterprises that govern the way of our lives are not able to cope with the pace of change we experience. For many systems engineers like me the term “Intelligent Enterprise” is not part of the daily work. Nor do we have a clear idea why Systems Engineering would be the key enabler for the formation and survival of the intelligent enterprise. I will give a short characterization of the intelligent enterprise and the kind of systems engineering required to establish and maintain it.

This is my interpretation in classical system engineering terms of some of the information collected in the “knowledge claims” compiled by the INCOSE Intelligent Enterprise Working Group (IEWG 06)
10.2.0 Panel 10.2.0: Integrating Systems Engineering with Program and Project Management
Authors: Ade R. , Mooz H. , Pyster A. , Van Gemert D. , Wartenberg M.
Published: November 2014

Program/project management and systems engineering teams must be tightly integrated or program risk skyrockets. Effective integration demands clarity of roles and underlying competencies, as well as mutually supportive processes, tools, and training. Generally, the best program/project managers have been systems engineers and the best systems engineers have been program/project managers. Career paths should encourage and enable that type of movement. The panel will highlight the diverse ways in which different organizations have approached integration between program/project management and systems engineering and will provide both an entertaining and informative discussion of the tradeoffs between those approaches. Give some thought to how you and your organization approach this topic today, then jot down some questions and bring them with you to the presentation for our panel to address. After you have heard the answers, you can decide how you will change the way you approach Systems Engineering and Project Management.
10.6.0 Panel 10.6.0: Is the Systems Engineering Profession Quantitative Enough?
Authors: Zonnenshain A. , Dori D. , Honour E. , Kasser J. , Malotaux N.
Published: November 2014

Systems Engineering (SE) is engineering, and as such it is perceived as quantitative profession. Nonetheless, consider SE to be an art with qualitative methods and intuitive approaches based on little evidence and quantitative data. What is the reality, and what are the possibilities?

We think that SE should be based on more quantitative methods, and would like to discuss ways to promote this direction by our discussion in this proposed panel. We will assess several SE aspects by assessing their quantitative/qualititative status. For each topic, we propose how to drive that aspect into more quantitative approaches & techniques. Each short presentation will be followed by participants discussion, to draw further ideas from the audience.

We consider the following key topics:

System Architecting – Art or Engineering? –How can we quantify the quality of the architecture?

Modeling & Simulation – as a central quantitative tool for system analysis, but a tool with drawbacks – What are the bounds of M&S?

Quantifying Technical Management– How can we measure technical management? – How much SE is enough? – What is the return on investment?

Capabilities of the Systems Engineer – How can we measure the skill level? – Identifying the Masters from the Journeymen.

How can we measure the quality of the System Design?
11.1.1 An Approach to a Network Centric Product Development System
Authors: Dagli  , Miller Ann , Abbott Russell
Published: November 2014

Current product development architectures range from vertically stove‐piped organizational structure to dispersed organizational entities working in a collaborative manner. Various product development methodologies have been developed to speed the communication between product team members including co‐location of the development team, email, scheduled telecom and video‐com meetings, Internet Web casting to keep all team members in contact with one another. No company has implemented a network centric product development system that links all users in the product development process together in a single system where real time communication or shared databases are used or exist. This would require a company to change it business model as a network centric product development system requires closer cooperation between and within itself, subcontractors and suppliers. As an example, both Wal‐Mart and Deutsche Morgan Grenfell have incorporated network centric systems into their business model with great success. Can the product development process be used on a network centric system? A Network Centric Product Development System requires a system configured and optimized to speed team communication and share product databases regardless of team member location or organizational affiliation.
The Evolving Joint Perspective and Meta‐systems Theory: A Case Study based on the Joint Vision Document
Authors: Palmer Kent D.
Published: November 2014

The Evolving Joint Perspective document which was the precursor to the current Capstone Concept for Joint Operations was analyzed in relation to Meta‐systems Theory in this case study which was done in the 2004 timeframe. The basic thrust of the new document is the same as the original document so this analysis is considered to still be relevant. Meta‐systems theory is proposed as a basis for Joint Forces organization. Currently the theory that is the basis of both documents is Complex Adaptive Systems Theory. The emphasis here is on the dual of that which would be Complex Adaptive Meta‐systems Theory. Both Systems and Meta‐systems Theories are said to be needed to have a complete theory for Joint Operations of Joint Forces.
Undergraduate Basics for Systems Engineering (SE), using The Principles, Measures, Concepts and Processes of Planguage
Authors: Gilb Tom
Published: November 2014

There are some very basic things that systems engineers should be taught. These things are both fundamental and classic. They are fundamental because we can reuse them in a very wide variety of SE situations. They are classic in the sense that they have a very long usefulness half‐life. They are probably useful for at least a career lifetime. When I was in my Twenties, I decided to collect, to learn and to develop these SE Basics. Now, in my Sixties, I am more than ever convinced that these fundamentals should be share with students. The fundamentals are: Principles (heuristics, laws), Measures (ways to quantify critical factors), Concepts (really useful definitions of fundamental SE ideas), and Processes (really useful SE processes). I have published these in several books and papers already. I would like to argue here why they need teaching in undergraduate systems engineering. I believe that their usefulness and longevity are demonstrated in my own work, are acknowledged by many professional colleagues and some academics, and are self‐evident upon examination. Hopefully this paper can stimulate others to adopt at least the general idea, if not my exact artefacts.
A Conceptual Glossary for Systems Engineering: Define the Concept, don't quibble about the terms.
Authors: Gilb Tom
Published: November 2014

We seem to spend a lot of our time defining terms, arguing over terms, standardizing terms, and misunderstanding terms. In connection with my development of a planning language, and its basic textbook I had to make a decision regarding my glossary. One of the formal design requirements I had set for myself was that the planning language, and its textbooks were easy to translate into other international languages. It was primarily in order to satisfy that requirement that I came up with the concept of a concept‐centered glossary, rather than the conventional term‐focused glossary (like a conventional dictionary).

The basic idea is that we focus on defining a concept, no matter how many synonyms it might have, or how many different opinions there are about what the concept should be called.
Expanding Functional Analysis to Develop Requirements for the Design of the HumanComputer Interface
Authors: McKenna Brian , Gualtieri James , Elm William
Published: November 2014

The purpose of this paper is to provide a framework for extending the functional analysis of a system to the human decision‐making agents in order to improve overall system effectiveness. The subsystems needed to accomplish the goals of the system can often be found through a functional analysis. However, the different subsystems need to be completely integrated in order for the system to be effective. This integration is often problematic within the Human‐Computer Interface (HCI), where the operator is reliant on the information provided in order to have an understanding of what is occurring within the work domain. As a functional analysis helps to define the goals to be accomplished and the subsystems that accomplish them, it follows that expanding the depth of the functional analysis will help integrate the human operator and technology through the HCI to make a more effective Joint Cognitive System (JCS). The functional analysis leads to the creation of more insightful design requirements for the HCI that directly link the work that the user must accomplish and the information needed to complete this work – making it truly user‐centered design. An example of how the functional analysis can be applied to a system is provided, comparing an HCI developed with typical design requirements to an HCI developed from an expanded functional analysis.
Using a Boundary Object Framework to Analyze Interorganizational Collaboration
Authors: Fong Allan , Valerdi Ricardo , Srinivasan Jayakanth
Published: November 2014

The U.S. military is facing a plethora of challenges as a result of tightening procurement budgets and the need to acquire new capabilities to operate in modern war environments. This requires integrating legacy systems with developing technologies in what is loosely defined to be a System of Systems. Most Systems of Systems require some integrator to manage and operate the system interfaces. In addition to technical integration challenges, these system integrators have the difficult undertaking of integrating various organizations. The boundary object framework proposed by this paper provides a tool for systems integrators working in System of Systems or any type of complex system to identify and categorize communication, coordination, and collaboration interfaces and address possible failures.
Meeting the Need for Defence Systems Engineers
Authors: Cropley David H , Campbell Alistair
Published: November 2014

Australia is entering a period of forecast skills shortages in defence industry. The growth in demand for new complex defence systems, stimulated by Federal Government spending, has highlighted the need for additional systems engineers and systems integration specialists. At the same time, the size of many companies in the Australian defence industry mitigates against strategic investment in programs to address their skills needs. This situation is compounded by strong growth in Australia's resources sector, fuelled by high prices for minerals, and the consequent competition for the same engineering professionals. This impacts on Australia's capacity to achieve self‐reliance in defence capability.

Concurrent to this skills shortage, however, is a widespread recognition by all levels of government that action needs to be taken. The Skilling Australia's Defence Industry (SADI) initiative will inject approximately A$200 million over the next 10 years into programs to address the skills shortage. The initiative, run by Australia's Defence Materiel Organisation (DMO), has already allocated significant funding to companies that are engaging in new activities to address their skills requirements. This paper describes one such activity – the creation of a new Masters degree in Military Systems Integration.
From Research to Reality: Making COSYSMO a Trusted Estimation Tool in Your Organization
Authors: Valerdi Ricardo , Miller Chris
Published: November 2014

As the COSYSMO model transitions from the development phase into the adoption phase, industry stakeholders are beginning to embrace the model and integrate it into their existing measurement processes. To date, much of the guidance provided by the COSYSMO development team has been focused on the usage of the model. In the adoption phase, users need guidance on how to adopt the model as they work to convince management to invest resources in competition with other process improvement initiatives.

This paper outlines a process which provides guidance on the piloting and institutionalization of COSYSMO designed to help scope the effort needed for successful adoption and implementation. The process has been developed as a result of interactions with over a dozen organizations that have participated in the industry calibration of the model and have begun to integrate the model into their internal processes. The knowledge obtained from working with these organizations is reflected in this process.
Biologically Inspired Systems Concepts –A personal history
Authors: Friedman George
Published: November 2014

Abstract

Biologically inspired systems concepts – witch include artificial intelligence and artificial life – represent an enormously rich and – to many – fascinating source of ideas for future systems engineering architectures and designs. However, this source has been fraught with many failures and is often controversial. The author has had the fortune to be exposed to many successes as well as failures in this field and attempts to summarize over 60 years of these experiences, with lessons learned.
1.1.1 Designing the Construction Process
Authors: Aslaksen Erik W. , Brouwer Paul , Schreinemakers Paul J.P.
Published: November 2014

After its initial development in the telecommunications industry (Hall 1962, Bode 1967), systems engineering flourished mainly in the defence and aerospace industries. As a spin‐off from the development in these areas, systems engineering itself has developed and grown to accommodate many more domains all over the world. One of these domains is the construction industry. This paper elaborates on the tailoring of systems engineering principles to a construction industry environment: governments, railroads, city boards, highways and a lot of steel and concrete. It examines the equivalence between this domain and the more traditional systems engineering processes as a path to recasting systems engineering in a language that would make it more immediately useful and acceptable in the construction. Finally, the paper discusses some features of the implementation of such a reformulation undertaken within the Dutch construction industry, illustrating the communalities for applying Systems Engineering within the construction domain throughout the world.
1.1.2 Do It Right, Do It Early; Do It Early, Do It Right: Reshaping the DoD SE Investment Paradigm
Authors: Loren Jeff , Bullard Randy
Published: November 2014

The first standard deviation of a normal distribution curve overlaid on the Department of Defense (DoD) acquisition life cycle “wall chart” generally aligns with Milestones (MS) / Key Decision Points (KDP) B and C, which bound the System Development and Demonstration (SDD) phase. Taking this overlay to represent Systems Engineering (SE) effort supports the contention that, historically, the Services and their industry partners have done reasonably well in the practice and management of large amounts of post‐contract‐award SE. Much of this effort focuses on the fundamental activities of requirements decomposition and allocation needed for detail design to proceed.

Analyses of DoD cost and schedule overruns have long pointed to optimistic technology maturation expectations and inadequately defined requirements as causal factors. It is almost axiomatic that process output quality directly reflects the suitability of input attributes. We suggest overlaying the near‐exponential “cost of change” curve on the above construct to support the case that early SE investment, focused on crafting and refining requirements, minimizes “churn” and rework in SDD. The objective is to have realistic, achievable requirements and technology paths at program launch, reducing the risk of breaching cost and schedule baselines.
1.1.3 Propositionofa Formal Frameto Facilitatethe Applicationof Processesin Systems Engineering
Authors: Rochet Samuel , Baron Claude , Malgouyres Hugues , Esteve Daniel
Published: November 2014

In this paper, we are interested in “good practices” of Systems Engineering synthesized in processes of Systems Engineering. We will show that it necessarily exists gaps between the processes described by standards of Systems Engineering and such they are applied in industry. These gaps can create a loss of “good properties” detrimental to a good management of projects. By a modeling and a formal validation of processes, we will show it is possible of insure a conservation of these properties, or at least to verify they appear in effectively applied processes.
1.2.1 Early History of Systems Engineering (Part 3) – 1950's in Various Engineering Sources
Authors: Ferris Timothy L.J.
Published: November 2014

In a pair of papers in the 2007 Symposium the early history of systems engineering, from the perspective of the IRE publications was presented. This paper extends this work with a discussion of the early history of systems engineering from the perspective of other publications produced by engineers within the engineering community. This paper reviews the matters identified and compares the findings with the findings from the corpus reviewed earlier. The differences are discussed with a particular view to understanding why different parts of the engineering community came to different positions.
1.2.2 Assumptions / Promises ‐ Shifting the Paradigm in Systems‐Engineering
Authors: Engel Avner , Winokur Michael , Döhmen Gert , Enzmann Marc
Published: November 2014

In the field of embedded systems, the need for increased competitiveness necessitates the shortening of the development lifecycle. Engineering activities, that in the past were conducted serially, must often proceed in parallel in order to reduce time‐to‐market. This causes the concurrently working design‐teams, to rely on preliminary information that has not yet been finalized. As a result, substantial rework is required throughout the development process, consuming as much as 50% of the total engineering effort.

This paper describes early results from the European Commission supported SPEEDS (Speculative and Exploratory Design in Systems Engineering) project. The objective of SPEEDS is to construct theory and tools for concurrent system development which will reduce the overall systems development cost and time to market.

We propose a shift in systems development paradigm, relying on the formal use of contracts composed of Assumptions and Promises (A/P), analogous to Bertrand Meyer's “design‐by‐contract” model proposed in the early 90's. Such assumptions and promises may be related to both technical and management domains, where contracts are defined at all levels of design abstraction. Horizontal A/Ps analysis (Consistency) and vertical A/P analysis (Composability) may be conducted, leading to early discovery and correction of technical or management incompatibilities emanating from invalid assumptions.

SPEEDS utilize several enhanced COTS modeling tools, giving users the ability to apply design‐by‐contract to Model Driven Systems‐Engineering in all phases of the development lifecycle.
1.2.3 Getting the Message Across ‐ Creating Accessible Guides to Promote the Adoption of Systems Engineering Good Practices
Authors: Armitage Tim , Elliott Bruce , Chin Deborah , Kastenhuber Ed , Krueger Michael E.
Published: November 2014

The authors believe that better deployment of Systems Engineering (SE) would benefit the rail and transit sector. They have formed an INCOSE working group to develop guidelines which advance this objective, starting with the topic of requirements engineering.

Although there is already sound guidance on requirements engineering, its influence within the sector has been limited. In hopes of changing this, the authors have created a short requirements guide, illustrated with practical examples and written in plain language. The authors' premise is that the benefits of increased accessibility outweigh any loss in comprehensiveness and precision.

The guide is being produced following an iterative process involving peer review by INCOSE groups. The current working version is attached to this paper. The authors believe that following this guide would benefit rail and transit projects. The approach described may be of value to other SE practitioner trying to convince skeptics of the value of SE.
2.2.1 Collaborative Systems Thinking Research: Exploring systems thinking within teams
Authors: Lamb Caroline T. , Rhodes Donna H.
Published: November 2014

This paper describes ongoing research that seeks to develop an empirical basis for collaborative systems thinking, defined as “an emergent behavior of teams resulting from the interactions of team members and utilizing a variety of thinking styles, design processes, tools, and communication media to consider system attributes, interrelationships, context and dynamics towards executing systems design”. This type of thinking is critically important to addressing engineering systems challenges, and the research seeks to inform and enable effective systems engineering practice in contemporary engineering enterprises. Focusing on the aerospace domain, collaborative systems thinking is examined through the alignment of enterprise culture and standard technical processes. This paper draws on a variety of literature to compose a definition of collaborative systems thinking and propose a research agenda going forward.
2.2.2 MEASURING ORGANIZATIONAL RESPONSES TO STRESS: A LONGITUDINAL STUDY OF PRODUCT DEVELOPMENT TASK NETWORKS
Authors: Collins Shawn T. , Bradley Joe A. , Yassine Ali A.
Published: November 2014

This paper uses Network Analysis (NA) to study task interactions in a product development process (PDP). It explores the impact of significant organizational stress on changing information flow patterns in the PDP at a small engineering company. The analysis identifies structured patterns of centralization, role specialization, and formalized control in the PDP. This validates themes from organizational behavior and quality management literature regarding how organizations change in response to stress. These trends are difficult to uncover with Systems Engineering techniques such as the Design Structure Matrix (DSM) and N2 method. The results offer several findings. First, reducing variation in task outputs is an understandable approach to controlling a PDP. However, it is important to reduce variation in task inputs as well. Second, tasks, like people, can have varying roles and burdens in terms of how they share information. Companies that want to support multiple concurrent projects must make sure their PDP tasks have an appropriate distribution of labor. Finally, transitivity can identify both valuable and ineffective iteration among groups of tasks. This provides a metric of effective concurrency in a PDP.
3.3.1 Optimizing Resource Allocation Decisions
Authors: Wilson Mark A.
Published: November 2014

The paper explains how the analytical hierarchy process (AHP) theory of decision‐making can be used to create justifiable, traceable resource allocation decisions in a resource‐constrained organizational environment. By thinking about the decision as a six step process of: (1) framing the decision to be made, (2) identifying alternatives, (3) modelling‐evaluating the trade study, (4) choosing an alternative, (5) conducting sensitivity analysis, and (6) implementing the selected alternative, key stakeholders can better understand how to reliably and repeat‐ably make justifiable, traceable resource allocation decisions in the context of an enterprise systems framework.
3.4.1 Systems Engineering Project: Zero Population Growth by 2020
Authors: Pietras Sherry L.
Published: November 2014

The scientific conclusion as to the primary cause of global warming is human beings. Human use of fossil fuels causes carbon dioxide emissions and the resultant green house effect. To avoid the fast approaching point of global melt down will require halting the population growth. No amount of technological advances to clean emissions will preclude the accumulation of gases in our atmosphere without stabilizing the population causing these emissions. The United Nations (UN) estimate for world population by 2050 is 10.5 billion, a prediction of doom. The current world population is 6.7 billion, if growth slows down to 7.5 billion by 2050 global warming may stabilize. The consequences of global warming are evident today, such as melting of the polar caps, resultant floods and rising coastal waters. To stabilize the situation and avoid disaster something must be done. Imagine you are the Systems Engineer selected to propose the ‘Zero Population Growth by 2020’ project. First you pick up your INCOSE Systems Engineering Handbook and then what would you do?
3.4.2 Applying the Human Views for MODAF to the conception of energy‐saving work solutions
Authors: Bruseberg Anne
Published: November 2014

Network enabled working capabilities are a central development theme for both civil and military domains, given technology trends and human interaction needs. Enterprise Architectures are essential modelling aids to support high‐level planning of such systems, with an operational perspective. MODAF, the Ministry of Defence Architectural Framework, is one such tool for UK defence applications. This paper introduces complementary modelling elements for MODAF to better account for the Human Factors concerns of Enterprise Architectures. A set of Human Views is proposed and a civil application to the implementation of a tele‐working scheme is explored.
4.2.3 A Systems Approach to the Transition of Emergent Technologies into Operational Systems – Herding the Cats, the Road to Euphoria and Planning for Success
Authors: Austin Marc F. , York Donald M. , Zakar Joseph D. , Pettersen Leonard A. , Duff Eva M.
Published: November 2014

The prosecution of the National Security Agency's mission has evolved from the relatively static, industrial age, Cold War communications environment to the ubiquitous, high speed, and multi‐functional technologies of today's information age. In an Agency whose success depends on acquiring and deploying the latest technologies for collecting and protecting information, a system engineering approach is mandated to successfully transition and manage the complexity of new technologies.

Using such a systems approach, this paper proposes a model and a process for technology transition. The development of the technology transition model is based upon NSA's need to establish a repeatable, reliable and predictable technology transition process at an enterprise level. The model is established using a systems view, is based on the principles of systems life cycle planning, a business case, and critical decision points for any technology transition activity.

The latter part of the paper demonstrates how the principles of Portfolio Management can be used in conjunction with the technology transition model to enable strategic systems planning, ensure technology readiness, and guarantee a focus on technology relevance and feasibility.

Effective methods, such as the one proposed in this paper, for the transition and infusion of new technologies into mission will enable NSA to maintain its preeminence in a global environment of rapid technology change.
4.4.1 A System‐of‐Systems Framework for the Future Hydrogen‐Based Transportation Economy
Authors: Duffy Michael , Sandor Debra
Published: November 2014

Today, almost 60% of the petroleum consumed in the United States is imported. The nation's current transportation system of systems (SoS) relies almost exclusively on refined petroleum products, accounting for over two‐thirds of the oil used in the United States each day. As a nation, we must work to reduce our dependence on foreign sources of oil in a manner that is affordable, ensures national energy security, and preserves environmental quality. In the long term, a potential solution to the nation's transportation energy problems is an operational hydrogen‐based transportation economy. Transitioning to any alternative transportation fuel on a national scale will require the creation of a robust and cost‐effective system of systems that operates in concert with the dynamics of today's mature and highly‐networked transportation infrastructure. Using a supply‐chain point of view to trace the flow of transportation fuels through the necessary SoS, this paper addresses the current petroleum‐based economy for transportation, the U.S. Department of Energy's (DOE's) vision for a future hydrogen‐based transportation economy, and the significant challenges associated with such a massive market and infrastructure transformation.
4.4.3 Applying Principles for Sustainable Design to Sustainable Management of a Natural System
Authors: Frank Moti , Zeitouni Naomi
Published: November 2014

The idea that a system design must be sustainable as regards its impact on environmental concerns throughout its life cycle, as much as meeting the customer's requirements, is not new to Systems Engineering. However, in recent years, society's awareness about sustainability issues has increased and numerous papers, books, and conferences have dealt with this important subject. The current paper examines the way in which the system engineering community should be prepared in an age where there is a strong social demand to build systems according to an approach that takes both social and environmental variables into account. The paper focuses on the issue of the sustainable design of systems and presents several principles of sustainable design. The second part of the paper presents a case study that relates to the designing of a groundwater preservation system, as an example of implementing some principles of sustainable design. The paper advances the systems engineering body of knowledge by gathering principles for the sustainable design of systems.
5.4.1 Design for Sustainability – The Challenge for Systems Engineering
Authors: Zonnenshain Avigdor , Sheps Isaac
Published: November 2014

Organizations should continually aspire to “meet the needs of the present without compromising the ability of future generations to meet their own needs”. This is the essence of the sustainability approach and of sustainability management in organization and businesses. Sustainability is a perfect system concern which involves stakeholders of all kinds, deals with the entire lifecycle of products and systems, incorporates economic, environmental and social considerations in management and engineering, and entails new risks and opportunities to be managed by the organizations. We propose an integrated model for the design and management for sustainability in business. This model relies on some key Systems Engineering methodologies and Quality Management approaches. Also described is some of our experience with sustainability progress in both our companies – RAFAEL and Carlsberg‐Srbija.
6.1.2 Systems Architecting for Sustainable Delivery of Value
Authors: Huynh Thomas V. , Osmundson John S.
Published: November 2014

Requirements need be established for architecting a large scale, complex system for sustainable delivery of value to users. In this paper, we describe a general methodology to establish requirements on design of a complex system to provide sustainable delivery of value. The methodology involves a system architecture paradigm, a sustainability analysis, and the derivation of design requirements. The methodology is described in concrete terms as it is applied to an ad hoc sensor network, which is required to provide sustainable delivery of information for use within the context of a missile defense system. Bounds are then established on the network connectivity and interoperability measures. This work demonstrates a methodology to enable designing requirements for architecting a system for sustainable delivery of value.
6.3.1 Secure Adaptive Response Potential (SARP): A System Security Metric
Authors: Simpson Joseph J , Miller Ann , Dagli Cihan H
Published: November 2014

System design, development and operational activities are monitored and evaluated to facilitate proper system security management in all phases of the system life‐cycle. Effective system security metrics must address all phases of the system life‐cycle as well as the associated organizational elements that interact during the system life‐cycle to produce and operate the system of interest. A single system security metric, built from multiple components, is presented here as a fundamental system management security metric. This single technical security metric is used to support and evaluate the allocation of corporate and program resources, including time and budget.
6.4.2 Life extension of Civil Infrastructural works ‐ a systems engineering approach
Authors: van der Laan Jan M.
Published: November 2014

This paper discusses the application of Systems Engineering in projects where large civil structures like bridges, ship locks, weirs and tunnels are being renovated and prepared for a new phase in their life cycle. In the Systems Engineering literature there is little attention given to life extension of such structures. Some of the typical problems with renovation projects of civil infrastructure works are described, and based on that a practical approach is presented using Systems Engineering principles. This results in a few simple process models who also close the gap that exists between Systems Engineering standards and Asset management standards. These models can be used to plan and execute these kinds of projects in a systematic way.
7.1.0 How Should We Respond to the Next Global Terrorist Attack or Natural Disaster Event
Authors: Mackey W , Sutton S , Jackson S , Tulodieski C , Nolte J , Long J , Carl J
Published: November 2014

During the past few years, natural disasters including the major earthquakes in Pakistan, the Tsunami floods of Indonesia, and the hurricanes and destruction in New Orleans, LA and the Gulf Coast region of the United States have caused major loss of life, injury and significant loss of property.

During the same period, insurgent attacks in Iraq, subway bombings in London, fire attacks on the city of Paris, and continued threats of terrorists throughout the world have placed life at risk.

Terrorism is the systematic use of violence and force as a means of coercion through fear and intimidation. As we have seen since World War II and experienced first hand since the terrorist attacks of September 11, 2001, the calculated murder of political personalities has given way to the random killing of innocent people and civilian populations.

Natural disasters are perhaps even more threatening. Are we building systems and responding in a way that permits these communities to respond properly and be resilient to these kinds of events? How can the discipline of systems engineering assist in preparing for, responding to, recovering from and mitigate against the risks of natural disasters and terrorist events.

Since September 11, 2001, INCOSE through its Anti‐Terrorism International Working Group (ATIWG) has focused the principles, techniques, and practices of systems engineering on how to reduce and eradicate international terrorism. We have taken this opportunity to expand emergency preparedness efforts to natural disasters as well.

Through the ATIWG sponsoring of panels at previous INCOSE symposia (2002–2007), writing papers for publication (2003), a tutorial (2004), an Insight Issue (2006) and working group activities, the systems engineering community has discussed the application of collaborative engineering environments, simulation and modeling, religion, system solutions to defend against terrorism, psychology, and root causes of terrorism to address the vulnerabilities of systems as well as the attack responses to threats.

This panel continues the INCOSE application of systems engineering to these international problems by discussing the proper responses, recovery and resiliency of society and the systems it builds to natural disaster events and terrorist attacks.
7.3.3 Intuition and the Systems Engineer: Learning from Management
Authors: Bosman Reinier A. , Wiersma Erik J.W.F.
Published: November 2014

Since the 1970's the industry and information technology has had to cope with a rapidly changing environment. To deal with this, management had to accelerate their decisions and found that top level managers often applied intuition for important decisions. Intuition can be immediate, and is usually a sort of feeling which direction should be taken.

Systems Engineering (SE) nowadays has also to cope with the same environment as management, to deal with complex design decisions with inadequate data and under time pressure. This paper discusses whether intuition can be a factor to make the practice of Systems Engineering an even more effective and complete methodology to assure the quality of technology.
7.5.0 Global SE: The Reality and the Challenges
Authors: Valerdi R , Yeo T S , van der Linden H H , Loureiro G , Fernandez J L
Published: November 2014

The discipline of systems engineering has made significant strides in expanding throughout the world. INCOSE now boasts 7,000 members but, compared to other organizations such as IEEE and PMI, there are still many opportunities for broader international reach. With international expansion as a strategic priority for INCOSE, significant challenges remain to be addressed. The most critical is the adaptation of the INCOSE model across different technical cultures. This panel will explore these issues from their own perspectives which include Singapore, the Netherlands, Brazil, Spain, and the United States.
8.3.2 It's More Than Just Numbers: How to Implement a Qualitative Risk Analysis Approach
Authors: Lane Courtney E.
Published: November 2014

Engineers often feel more comfortable using quantitative methods to solve problems; their approach to risk management is no exception. Quantitative methods are not always the best solution for effective risk management, though. For example, countless hours have been spent by risk management teams trying to determine which risk is more important. Is a risk scored 9.0 any more important than a risk scored 8.5? Maybe so, but the factors that make it more important such are often difficult, if not impossible, to quantify. By applying quantitative techniques to qualitative data, or by using unproven data in complicated risk analysis models, managers may not receive an accurate representation of their ‘top’ risks and may base critical decisions on poor information. This paper will discuss when qualitative risk analysis techniques are most appropriate, examine common challenges associated with qualitative analysis, and discuss solutions for overcoming them.
9.1.1 Method & Tools for constrained System Architecting
Authors: Voirin Jean‐Luc
Published: November 2014

This paper describes a system or software architecture engineering approach, named ARCADIA (ARChitecture Analysis & Design Integrated Approach), based on architecture‐centric and model‐driven engineering activities. It targets systems whose architecture is largely constrained by issues such as performance, safety, security, when these issues must simultaneously be taken into account to find the best architectural compromise out of them. Tools supporting the method allow formalizing these constraints, modeling the architecture, and evaluating its compliance with these constraints in an iterative and short‐loop way, while capitalizing engineering know‐how.
9.2.2 Evaluating Aspects of Systems Modeling Languages by Example: SysML and OPM
Authors: Grobshtein Yariv , Dori Dov
Published: November 2014

As systems are becoming larger and more complex, the challenge of developing quality systems efficiently is on the rise. While traditionally document‐centric approaches have been used, in recent years the benefits of model‐based systems engineering have been acknowledged. Recognizing the importance of modeling as a key factor in managing system development complexity, the selection of the modeling language to be used should be considered. This work evaluates aspects of two systems modeling languages: SysML – OMG's Systems Modeling Language and OPM – Object‐Process Methodology. The evaluation was done on the basis of a concrete sample problem, in which multiple aspects of the system were modeled in both SysML and OPM. Some of the findings, which were generalized from the case study, suggest that OPM is usually advantageous in presenting the system different hierarchy levels and combining structure with behavior, while SysML is more convenient for modeling detailed views of some aspects.
9.3.2 Design to Decision Objectives – Decision Support in the Aircraft Engineering Process
Authors: Lochow Tim , Schmidt‐Schaeffer Tobias , Mauritz Axel
Published: November 2014

The aircraft development process is a very complex, iterative and decision driven process. For future aircraft development programs, running within extended enterprises, involving several stakeholders and giving consideration to changing objectives from infrastructural aspects to environmental impacts, the need for decision support is eminent.

To address these issues, and improve the development process by a better process flow, avoidance of unnecessary iteration loops, reduction of lead time and development costs, an approach will be presented called Design to Decision Objectives (DtDO). This approach describes a flexible Decision Support Framework (DtDO Framework) that can be tailored to the specific needs of the various decision situations within an extended enterprise. Further it provides means to complement the company knowledge base in terms of decisions along the entire engineering process.
10.2.1 Improving the Practice of Systems Engineering at JPL
Authors: Jones Ross
Published: November 2014

JPL has been investing in a focused effort to improve its practice of systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks. This paper describes JPL's approach to improving the practice of systems engineering. It describes the general approach used and how they address the three key aspects of change: people, process and technology. It describes plans and progress in each of those three dimensions of change and concludes with some initial work in acquiring systems engineering metrics.
11.1.1 Using Natural Value‐Centric Time Scales for Conceptualizing System Timelines through Epoch‐Era Analysis
Authors: Ross Adam M. , Rhodes Donna H.
Published: November 2014

A traditional approach to system design is to optimize the system with regard to a set of system objectives, as defined in a given context. This approach falls short when designing systems that are capable of delivering sustained value to stakeholders in the face of a rapidly changing world. In order to achieve this value robustness, systems should be designed using natural value‐centric time scales, as defined by their contexts, for conceptualizing system timelines. Epoch‐Era Analysis is an approach that provides for visualization and a structured way to think about the temporal system value environment. This paper discusses Epoch‐Era Analysis as central to a tradespace exploration process for system design comparison and selection, invoking passive or active value robustness design strategies. The analysis can also serve as a socio‐technical bridge, integrating the tradespace exploration activities of architects and engineers, which may be traditionally independent efforts in contemporary engineering programs.
11.1.2 A Process Modelling Framework for Formal Validation of Panama Canal System Operations
Authors: Johnson John , Austin Mark A.
Published: November 2014

In this paper we develop a process modeling framework for the evaluation and formal validation of Panama Canal system operations. Component‐ and architecture‐level processes are organized into a three level hierarchy and modeled in LTSA. Safety and progress requirements are formally expressed as processes that can be evaluated through compositional and search processes, respectively.
11.2.2 A Framework for System Resilience Discussions
Authors: Sheard Sarah
Published: November 2014

This paper presents a framework for discussions of system resilience. The framework has five aspects: time periods, system types, events, resilience actions, and properties to preserve. The five time periods are well defined, but the other four aspects vary according to author, type of system, and purpose of the discussion, so what is presented is the variation that occurs among definitions.

The framework is followed by a cataloging of principles for creating emergence, including a number of rubrics. Finally the paper discusses factors affecting resilience, including improving resilience, tradeoffs, and loss of resilience. An appendix details specific definitions and distinguishers from related properties.