bluuebunny/crossref_metadata_2025 huggingface dataset:
Model Driven System Design Working Group: FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN
Authors: Baker Loyd , Clemente Paul , Cohen Bob , Permenter Larry , Purves Byron , Salmon Pete
Published: November 2014

This paper presents an initial viewpoint on an emerging technology: Model Driven System Design (MDSD). In contrast, the current state of practice has been characterized as document centered. Practitioners of system design are well aware of the technical and organizational difficulties of implementing current approaches. By modeling multiple aspects of a system throughout its life cycle, this new view of system design offers dramatic gains in productivity and product quality.
TOOLS INTEGRATION INTEREST GROUP REPORT: SCENARIOS LEADING TOWARDS A CONCEPT OF OPERATIONS FOR AN INTEGRATED SYSTEMS ENGINEERING ENVIRONMENT
Authors: Schier James , Nallon John , Walker John , Kolberg David
Published: November 2014

The Tools Integration Interest Group (TIIG) is developing a Specification for an Integrated Systems Engineering Environment (ISEE) in response to the Corporate Advisory Board. To develop a system specification, one must understand the context in which the system will operate. Consequently, the TIIG is developing, in parallel, the Concepts of Operations for the Integrated Systems Engineering Environment. Initial efforts leading toward the development of the full Concepts of Operations document are defined in terms of two types of scenarios: tool‐oriented scenarios dealing with implementation issues and operation‐oriented scenarios dealing with the envisioned ISEE and how it enables systems engineers to work. This paper collects the initial seven scenarios which have been developed by members of the Tools Integration Interest Group. Five scenarios are tool‐oriented and deal with typical tool‐to‐tool data transfer procedures commonly used. Two scenarios are operations‐oriented and deal with user navigation within an integrated program database for systems engineers and the change control process for managing requirements and assessing the impact of requirements changes.
INCOSE Tools Database Working Group Status Report
Authors: Case Randy , Findley Beth , McMullen William , Sampson Mark E.
Published: November 2014

The Tools Database Working Group is delivering the second release of the Systems Engineering Tools Database at the 1996 INCOSE Symposium. This update is focused on Systems Architecture Tools and includes an update on Requirements Management Tools. The information contained within the database comes direct and unedited from the tool suppliers. It is our wish that this information will save INCOSE members (those looking for information and those providing it) time as well as provide a common framework of reference for these important tools for Systems Engineers.
METRICS WORKING GROUP 1996 REPORT
Authors: Miller William D. , Rhodes Donna H.
Published: November 2014

The INCOSE Metrics Working Group (MWG) mission is to promote shared understanding of systems engineering metrics and measurement practices, and advance the state‐of‐the‐art of metrics collection and utilization. The paper covers:

History and Progress

Meeting Activity

Strategic Goals

MWG Workproducts

Collaboration with CAWG
INCOSE Measurement Technical Committee Paper: Moving Towards an Integrated Set of Products for Measuring Systems Engineering
Authors: Widmann E. R. , Miller W. D.
Published: November 2014

This paper provides information on the INCOSE Measurement Technical Committee and its four working groups. The charter and goals are presented along with objectives for development and support of measurement products. Significant milestone events for both products and product support services are provided – the only products to receive approval, or interim approval, of the INCOSE Technical Board were developed within the Measurement Technical Committee. A description of each of the measurement products developed to date is furnished. A synopsis of the past year's activities is provided along with planned future activities. An integrated approach to development of measurement products is being pursued to permit more effective measurement and improvement of systems engineering activities. The products developed by the Measurement Technical Committee are available to become an integral part of the strategic planning activities of both industry and government.
2 A “Systems of Systems” Perspective of the Year 2000 Problem
Authors: Walker Loren Mark
Published: November 2014

A “System of Systems” perspective of the Year 2000 (Y2K) problem is crucial for any organization that owns or operates computer‐based systems that interface with other systems, especially large multi‐computer system programs. This paper focuses on the requirements, multiple systems and interfaces, functional analysis, threads, testing, and multi‐organizational Y2K coordination issues inherent in all large Y2K certification programs. In addition, the positive long‐term benefits of reengineering and documenting the program's functionality, physical architecture and products are also discussed. Special emphasis is placed on the importance of “System Threads”, key to capturing the essence of very complex system interface issues and the prioritization of resource allocations and organizational activities.

The importance of preparing for, identifying and fixing problems that remain after January 1, 2000 are also examined. Addressing these topics is essential to assure that, through end‐to‐end operation, large programs consisting of many computer‐based systems, will have a reasonably high level of confidence that: 1) the systems will operate, 2) no corruption of data will occur within the systems, and 3) output products will continue to meet customer expectations.

This paper is based on the author's application of the topics discussed to a large multi computer based program, consisting of 100s of unique computer systems located at several locations. The concepts discussed were initiated in 1998 and are proving to be highly effective in meeting the program's Y2K certification needs.
2 Designing Standards for Open Simulation Environments in the Chemical Industries: A Computer‐Supported Use‐Case Approach
Authors: Jarke M. , Becks A. , Köller J. , Tresp C. , Braunschweig B. , Aachen RWTH
Published: November 2014

Under the double pressures of global competition and increasing environmental awareness, the importance of high‐performance simulation tools in the process industries (food, chemicals, oil, …) is rapidly growing. However, traditional simulation environments are closed monolithic systems which are extensible only by a small group of market‐leading vendors. The resulting bottlenecks in interoperability, reuse and innovationled to the CAPE‐OPEN project, in which the chemical and oil industries are defining standards for a component‐based approach to process simulation, in order to open up the market to smaller vendors and to facilitate rapid industrial uptake of academic research prototypes. For general systems engineering, the CAPE‐OPEN standardising process has at least two interesting features: (a) it has experimented on a large scale with a distributed use case approach, following a variant of the UML (Unified Modelling Language) approach for modelling, but also linking down to programming standards based on CORBA (Common Object Request Broker Architecture) and COM (Common Object Model); (b) the management of this world‐wide distributed effort has been facilitated by the use of an Internet‐based workspace co‐operation environment, augmented by advanced structuring and analysis methods from software engineering and computational intelligence.
3 Managing Future ‐ Methodology to Evaluate and Fund Innovative Ideas
Authors: Vollerthun A. , Fricke E. , Schärtl H.
Published: November 2014

A three‐phased approach for governmental as well as internal company centers is suggested to stepwise improve and evaluate proposed concepts for innovations.

The objective of this concept was to have a transparent, structured, and reproducible process to select the right innovative project in terms of political, economical, and technical objectives for funding by e.g. a governmental agency. A stepwise process and related methods, that cover technical as well as economical aspects (and related sensitivities) to come to a tentative decision which project to fund are proposed.

Before discussing critical aspects of the proposed process, aerospace‐related examples will be presented to show how the process has been applied, and how different concepts were evaluated.
1 System Simulation ‐ Examples using Smalltalk as a Modeling Tool
Authors: Kaffenberger Rüdiger
Published: November 2014

The behavior of a system in its environment is not easy to describe or to verify. Executable models are a natural solution to this problem. They give the engineer a way to explore and visualize the temporal progress of the system's state. Because Smalltalk is uniformly object oriented, it shows its virtues as a tool for modeling the behavior of systems particularly in conjunction with object oriented system analysis and system design techniques. The two examples will give a first impression of the power of Smalltalk as a modeling tool. We will show the essential components of a simulation framework, that allows an easy implementation of behavior models. Additionally we will present how Smalltalk models can be employed in the requirements phase of a project. A comparison between Smalltalk and C++ will show that Smalltalk as a system modeling tool has many advantages and only few drawbacks.
1 Embedded Systems Development Integration
Authors: STIL Guy , RAWNSLEY Brian
Published: November 2014

Most European aircraft development programmes are undertaken by consortia of geographically distributed and culturally diverse industrial organisations. Specification of avionic systems, and their realisation, is undertaken by multiple system specifiers (airframe manufacturers) and multiple avionic system suppliers, using their own methods, standards and tools. The key objective of the SPIDERS project is to reduce the cost and timescale of this distributed specification process. The SPIDERS consortium includes four aircraft manufacturers: Aerospatiale, Eurocopter France, Daimler‐Benz Aerospace Airbus, and British Aerospace Airbus. SPIDERS also includes two avionic systems suppliers, Smiths Industries Aerospace and Sextant Avionique. The programme has a central workpackage involving all of the partners, working towards definition of the New System Development Model. During the project, many improvements in processes, methods and tools were identified and evaluated. The “Current System Development Model” was first captured for each partner as a baseline. This was then harmonised and improvements incorporated to give a “New System Development Model”.
2 Incorporating Contingency Risk into Project Cost and Benefit Baselines: A Way to Enhance Realism
Authors: Fenton Robert E. , Cox Richard A. , Carlock Paul G.
Published: November 2014

Because of their one‐time nature, most capital investment projects are characterized by substantial uncertainty in economic analysis. Virtually all of the underlying data are best‐estimate assumptions (e.g., unit prices, sales volume, production costs, etc.) that cannot be known accurately or validated easily. Nevertheless, decision‐makers frequently tend to minimize or misunderstand cost and benefit risks when approving investment decisions. This paper discusses a methodology being used in the U.S. Federal Aviation Administration (FAA) systems engineering process for improving the quality of capital investment decisions, as well as the subsequent performance during project execution, by explicitly incorporating contingency risk into the project baselines and the investment decision criterion. It is adapted from and draws heavily on the ideas of Dr Steven Book and his colleagues of the Aerospace Corporation, who originally developed many of these concepts for the U.S. Air Force.
3 MUSSAT – A TOOL FOR MODEL‐BASED SYSTEM ENGINEERING OF COMMERCIAL SATELLITE SYSTEMS
Authors: Wilke M. , Quirmbach O. , Negele H. , Fricke E. , Igenbergs E.
Published: November 2014

This paper describes an approach to improve data quality and to reduce the development times for commercial satellites by introducing a software‐tool for the model based design of satellite systems. This tool is called MuSSat – Modelling and Simulation of Satellite Systems. It is being developed to support the early phases of satellite development similar to the Project Design Center (PDC) of NASA's Jet Propulsion Laboratory (Shishko 1997).

Basis of the approach and the supporting software tool is a modelling methodology developed at the Institute of Astronautics at the Technical University of Munich.

The tool MuSSat provides the user with the means to easily and quickly model all components – and the various interdependencies between them – of a satellite system and to compare various alternative designs. Thus MuSSat enables a company to improve its performance and agility in the new market segment of commercial satellite applications by supporting integrated concurrent engineering.
4 Managing the Emergent Properties of the Design
Authors: Burrowes Darren , Squair Matthew
Published: November 2014

A key role for the systems engineering effort on a complex project is to manage the emergent properties of the design leading to an optimum design. This paper examines issues related to the management of the emergent properties of the design and proposes management methods.
1 Controlling Rapid Change through Systems Engineering the Organization
Authors: Hihn Jairus , Wheeler Rebecca , Zak Haya
Published: November 2014

A new approach to change management has been developed and applied at the Jet Propulsion Laboratory (JPL). It's main focus is on aligning the organization with the strategic plan; and understanding the internal organizational relationships that impact change, which ultimately determine an organizations ability to be transformed and renewed. The new approach regards the strategic plan of a company as the standard by which progress and achievement are measured. Purposeful interventions should generate a company movement along a strategic course, and tracking that movement is essential for managing change. This paper presents an overview of DYNOMO, or the DYNamic Organizational Model which was developed to assist in the measurement and analysis of organizational state. The paper concludes with summaries of two applications.
2 Systems Methodology for Real‐Time Information Systems
Authors: Cropley David H , Cook Stephen C
Published: November 2014

This paper describes the application of novel systems concepts and methodologies to the design and implementation, or more generally the acquisition, of complex real‐time information systems. A hybrid methodology is proposed that combines contemporary ‘soft’ systems thinking with traditional hard systems engineering methodology, to result in an acquisition life cycle appropriate to such systems. This approach acknowledges the difficulties faced when applying hard systems engineering practice to real‐time information system projects with barely definable goals, significant human interaction and where implementation technology is evolving faster than the “system solution” can be designed and developed. The paper outlines the basic concepts of systems thinking that underpin the design of complex systems. Essential elements of traditional hard systems engineering, along with their failings, are described. Soft systems concepts are described and related to the problem of real time information systems. A novel systems methodology for real‐time information systems is proposed. This methodology is then examined in the context of the development of innovative combat system architectures for future naval surface combatants.
3 Architecture for a Process Meta‐System
Authors: Gundrum Valerie
Published: November 2014

This paper discusses using a four‐view architecture description, namely the physical, functional, behavioral, and product views to describe a site's “process system.” Defining this architecture will allow better understanding and usage of the process elements.

To understand what a process meta‐system is, we can start with the definition of system as the compilation of hardware, software, and operator/user actions, designed in a configuration that will meet user needs and produce the desired products. For this paper, a process meta‐system refers to the infrastructure that is used by its stakeholders, in order to select, tailor, implement and assure a process that will create the right system.

The impetus for this formulation was the realization that many companies, including my own, had a support structure for defining, documenting, instructing, and deploying process and methods, but there was confusion about the activity sequence, roles, responsibilities, approvals, tailoring, and compliance. The approach of this paper is that a process infrastructure is comprised of physical components on which functions are performed, in a time‐sequenced manner, resulting in the necessary work products. These include: a clear understanding of the sequence of activities, an understanding of the inter‐relationship of the program personnel and process owners, timely tailoring and utilization of process assets, and cross‐discipline understanding of roles and responsibilities.
4 Estimating Risk Adjusted Cost or Schedule Using Fuzzy Logic
Authors: Bellagamba Laurence
Published: November 2014

A method is presented to quickly and inexpensively obtain risk adjusted cost or schedule estimates so many system implementation options can be compared to find the best performer for a given cost. Cost or schedule consequences are modeled as a function of technical maturity and proposal risk. Technical maturity assesses how much of the system already exists. Proposal risk assess the uncertainty of of the cost and schedule estimates. Fuzzy logic is used as an alternative to probability to estimate the risk adjusted cost and schedule. Using fuzzy logic reduces the time required to interview and interpret domain expert's assessments of risk sources and consequences, while still capturing any uncertainty in the expert's opinion. Using fuzzy logic provides a single number for risk adjusted cost or schedule that does not require interpreting a cumulative probability density function.
3 Parametric Cost Modeling of Space Missions Using the Develop New Projects (DNP) Implementation Process
Authors: Rosenberg Leigh , Hihn Jairus , Roust Kevin , Warfield Keith
Published: November 2014

This paper presents an overview of a parametric cost model that has been built at JPL to estimate costs of future, deep space, robotic science missions. Due to the recent dramatic changes in JPL business practices brought about by an internal re‐engineering effort known as develop new products (DNP), high‐level historic cost data is no longer considered analogous to future missions. Therefore, the historic data is of little value in forecasting costs for projects developed using the DNP process. This has lead to the development of an approach for obtaining expert opinion and also for combining actual data with expert opinion to provide a cost database for future missions. In addition, the DNP cost model has a maximum of objective cost drivers which reduces the likelihood of model input error. Version 2 is now under development which expands the model capabilities, links it more tightly with key design technical parameters, and is grounded in more rigorous statistical techniques. The challenges faced in building this model will be discussed, as well as it's background, development approach, status, validation, and future plans.
4 The Safety Processes of a Prime Contractor
Authors: Irvine R A
Published: November 2014

This paper is a précis of a study commissioned by the Director of Engineering at BAe Systems and Services. It takes the study of Safety Management Systems from other mature industries and decomposes the task into a series of steps based on the nature of the risks to a system. It describes the safety management of a system using an approach that is not prescriptive about the system and its environment but recognises that an assessment of the risk posed by the system should be assessed qualitatively.

It addresses the development of the assessment of risk posed by this system over a Systems Lifecycle and application to a flexible living safety case that is more true to the real risks than a prescriptive testing regime at the outset of the project. The changing nature of a system throughout its lifecycle is addressed, right up to disposal in an environmentally friendly and ultimately safe manner.
2 Lessons Learned Teaching Systems Engineering to Practicing Engineers with Mixed Backgrounds
Authors: Boppe Charles W.
Published: November 2014

A Systems Engineering subject was taught to a group of 60 practicing engineers within the context of MIT's Systems Design & Management Program during the Summer Session of 1998. Several MIT graduate students were also attending with engineers whose experience ranged between 3 and 24‐years. Industries represented included aerospace, software, office equipment, telecommunications, computers, automotive, and machine tools. This paper describes the content and implementation of the course. Particular attention is devoted to the feedback that was provided by the students and the lessons learned that could benefit similar subjects taught to both graduate students and experienced engineers with different backgrounds, needs, and expectations.
3 Simulation Based Acquisition An Ongoing Look
Authors: Frost Robin , Thomen Dave
Published: November 2014

Simulation Based Acquisition (SBA) is a joint Industry and Department of Defense initiative to define an acquisition process that employs a robust, collaborative use of simulation technology to integrate the process across acquisition phases and programs. The intent of the initiative is to reduce the time, resources and risk associated with acquisition while enabling the Integrated Product and Process Development (IPPD) and the quality of the product. In 1998, a Joint SBA Task Force developed an SBA Road Map. This document presented an approach to bring about SBA. This paper will review the background and concept of SBA, and summarize the SBA Road Map that forms the basis for any Implementation Plan.
4 A Human Centered Design Environment for Complex Systems
Authors: Crisp Harry E. , Hoang Ngocdung T. , Schmidt Richard
Published: November 2014

An integrated engineering environment is described wherein capabilities are provided for addressing the role of human operators and decision makers in complex systems. The manner in which the environment supports the implementation of a human engineering process as an integral part of a standard systems engineering process is described. The capabilities of a prototype Human Centered Design Environment currently under development are discussed.
1 The Development of Engineering Processes for a Diverse Engineering Enterprise
Authors: Gates P J , Fearon E A
Published: November 2014

The development of a robust engineering process for a diverse engineering enterprise must not only accommodate a wide range of engineering activity but must also take into account other business functions as part of an overall business process. The development of a robust approach to the engineering aspects of the business process, based on existing practice but drawing upon advances in Systems Engineering, is described. This approach draws heavily on the interrelationships of process, milestones and baselines.
2 Triority: The Advantages of Simultaneous Deployment of Integrated Product Teams, Object Oriented Analysis/Design and Formal Inspections
Authors: Rosser Larri Ann
Published: November 2014

As systems engineers, we tend to take a focused, sequential approach to getting things done. We list the tasks that must be performed, determine which one to begin with, implement it, and move on to the next. We call this establishing priority, and accept this as the right way to achieve our goals. My experience with Integrated Product Development, Object Oriented Engineering and Formal Inspections suggests that sometimes you need a little something more – I call it triority, because making all three of these initiatives your top priority is the key to success.
3 Capturing and Leveraging Essential Organizational Knowledge via Dynamic Roadmaps
Authors: Hansell Todd , DeGregorio Gary
Published: November 2014

In many companies today, technology, capability, and product planning information is maintained in a haphazard collection of overhead slides, spreadsheets, and private databases by a set of disconnected “experts” and updated sporadically (usually just in time for the next review!). This information is often quite sparse and poorly supported by knowledge and supporting data, often being held only in the heads of the “experts.” Therefore, it is often difficult to leverage as external technology and market forces continue to change. In an attempt to improve the technology planning process and to provide the basis from which a company can develop its roadmap planning as a competitive asset, a set of methods, tools, and workshop‐based training have been developed. These assist the technology strategists, systems engineers, marketing professionals, and product development managers in creating, leveraging, and maintaining an organization's critical knowledge in a dynamic fashion.
4 Customer in the Loop (CIL) ‐ The Product Development Cycle Model‐
Authors: Wenzel Stefan , Negele Herbert
Published: November 2014

Product development is a business process where a great number of different functionalities and internal and external interests are intertwined. Involvement of human beings, traditional development structures, specific external conditions and internal resources let almost every development process appear as one of a kind.

The modeling and documentation of processes is a prerequisite for reengineering and continuous improvement of development systems. International case studies conducted by the Institute of Astronautics revealed the usefulness of a method which fits to all product development systems in general and provides a principal classification of the different processes involved. In addition, this method should be flexible enough to derive the particular profile of a product development system analyzed. This paper describes the Product Development Cycle Model (PDCM), a new and robust approach which meets these requirements. Starting and ending with customers' requirements, the PDC‐Model especially highlights the importance and impact of strongly interconnected loops and control cycles within a product development system.

First we explain typical characteristics that can be used to describe development processes. Then we explain the Product Development Cycle and its distinct sub‐cycles. Finally, we show a current example from a case study.
1 Fifty Ways to Save Your Budget Reduced Cost Systems Engineering Process Improvement
Authors: Sheard Sarah
Published: November 2014

Although assessments using systems engineering (SE) capability models are being performed for more organizations than ever before, few organizations want to fund a 5‐ to 7‐day “standard” appraisal1. Because of budget pressures, and because assessment expertise is growing within the industry, methods for reducing costs are receiving increasing attention. This paper prioritizes fifty ways to reduce the cost of performing systems engineering process improvement, including assessments. Many of these methods are based on experiences and materials of the Software Productivity Consortium, and others are collected from INCOSE papers.
2 A CMM For All Disciplines
Authors: Cusick Kerinia , Bruce Jim
Published: November 2014

Not all disciplines have the benefit of a Capability Maturity Model (CMM) that they can use to focus and guide their improvement activities. Honeywell Space Systems Operations, in cooperation with SECAT LLC, developed a “generic Capability Maturity Model” which included only project and organizational management topic areas, and was designed to be applicable to all disciplines. The model, called the IPDP CMM, was developed in early 1998. The first assessment was performed in the Fall of 1998 for 8 individual disciplines. A rating profile was developed for each discipline, and strengths and weaknesses both common across the organization and unique to each discipline were identified. A few lessons learned for improving the model and the assessment method were found during the assessment which are discussed in this paper, but generally all of the teams found the results applicable and particularly helpful in focusing their improvement efforts. The goal of this paper is to present what was done, the rationale for the decisions, the lessons learned and the benefits of developing and using a generic CMM.
4 Overcoming Barriers to Systems Engineering Process Improvement
Authors: Sheard Sarah A. , Lykins Howard , Armstrong James R.
Published: November 2014

Neither systems engineering nor process improvement is new. Since 1992, INCOSE papers and others have been reporting success in documenting and improving processes. A considerable body of process improvement literature is available, particularly related to improvement of software development processes. Even systems engineering process improvement is gaining in popularity, judging from the increasing number of INCOSE papers detailing various efforts. Yet the nature of systems engineering poses challenges over and above those seen in other process improvement efforts. This paper focuses on identifying and resolving typical barriers to improving the systems engineering process.
1 Summary of Results from the Risk Management Program for the Mars Microrover Flight Experiment
Authors: Shishko Robert , Matijevic Jacob R.
Published: November 2014

On 4 July 1997, the Mars Pathfinder landed on the surface of Mars carrying the first planetary rover, known as the Sojourner. Formally known as the Microrover Flight Experiment (MFEX), the Sojourner was a low cost, high‐risk technology demonstration, in which new risk management techniques were tried. This paper summarizes the activities and results of the effort to conduct a low‐cost, yet meaningful risk management program for the MFEX. The specific activities focused on cost, performance, schedule, and operations risks. Just as the systems engineering process was iterative and produced successive refinements of requirements, designs, etc., so was the risk management process. Qualitative risk assessments were performed first to gain some insights for refining the microrover design and operations concept. These then evolved into more quantitative analyses. Risk management lessons from the manager's perspective is presented for other low‐cost, high‐risk space missions.
2 Optimizing Systems Engineering for a Commercial Product Line: A Case Study in International Air Traffic Control
Authors: McGuire Kathleen
Published: November 2014

The development of the ASR‐12 international air traffic control (ATC) radar offers a case study in a shift from the more formal processes and products of the 1980's U.S. government contracts to a commercial product line environment. Both the radar development team and the product had to transition to new approaches. By effectively optimizing the SE process for this new environment, it is the key cost‐effective framework to optimize the product.
4 Incorporating Cost into the Front End of the Radar Systems Engineering Process
Authors: Church Douglas G.
Published: November 2014

This paper describes an initiative to incorporate cost into the initial stages of the design process to get the best cost‐performance value in radar systems design. Tools were developed at Northrop Grumman to provide the design community visibility as to how performance requirements affect the hardware cost. Detailed hardware cost and systems performance models have been developed and applied to ongoing radar development programs at Northrop Grumman giving systems engineers and hardware designers tools they need to optimize their designs. This paper provides a summary of the approach, describes the tools that were developed, addresses lessons learned in implementing the process and gives examples of the type of trades that can be performed using the tools. The approach is easily extended to non‐radar system designs. The process described reduces the possibility of overlooking a better design solution and avoids major changes late in the development cycle.
1 Systems Engineering On‐Time Deliveries
Authors: Warmkessel Joyce M.
Published: November 2014

The typical systems engineering application focuses on developing and delivering products which meet an acquirer's specified requirements, with emphasis on performance requirements. As currently practiced, however, systems engineering is not considered as a mechanism for identifying and reducing the amount of development rework – a major cause of project delays and cost overruns. Yet two elements of the systems engineering process, in conjunction with system dynamics analyses, can be used to reduce both the amount of rework required and the time required to identify the need for such rework.
2 Systems Engineering and the Joint Strike Fighter: The “Flagship” Program for Acquisition Reform
Authors: Struth Robert G.
Published: November 2014

ABSTRACT

The Joint Strike Fighter (JSF) program represents the largest potential aircraft contract for the U.S. Department of Defense (DoD) in the foreseeable future. It will provide replacement strike fighters for the U.S. Air Force, the U.S. Navy, and the U.S. Marine Corps, as well as for the United Kingdom and probably many other non‐U.S. services. The objective of meeting the different needs of many services with variants of a single airplane is a very difficult challenge, especially when the number one consideration is affordability.

As part of the plan to achieve an affordable solution, the JSF program will be conducted under the DoD's acquisition reform initiatives begun in 1994. These initiatives mandate a new and innovative way of doing business, canceling many government military
2 Designing an Optimal Product Introduction Process for an Extended Enterprise in the Aerospace Sector
Authors: Clegg Ben , Boardman John , Boardman Alison , Mason‐Jones Rachel
Published: November 2014

The process of introducing complex new aerospace products is such that a single company can rarely claim to possess the entire technical expertise, resource base, or investment capital required to fully accomplish it. Therefore, it is a growing trend for aerospace companies to require a provisional understanding between their suppliers, partners, or customers before engaging in the development of any substantially new products. Such a group of companies forms the embryonic ‘extended enterprise’ (EE) which may be thought of as a 'system of systems' where each of the sub‐systems is an individual company. This extended enterprise may continue to work together and become cohesively bound by contractual obligation into a fully fledged EE; which should be capable of sustainable competitive product realisation. The benefits of shared new product development means that system engineering expertise and commercial risk is shared. However, the main disadvantage is that project management complexity increases, which lengthens product lead‐time and raises costs. The question that must asked is, when and how do the individual systems become effectively bound to make up a single system?
1 Development of a Skills and Knowledge Taxonomy Aligned with the EIA/IS 731–1 Systems Engineering Capability Model
Authors: Widmann E. R. , Hudak G. J. , Hudak T. A. , Anderson G. E.
Published: November 2014

The INCOSE Corporate Advisory Board has set a high priority on the generation of a skills and knowledge taxonomy aligned with the EIA/IS 731–1 Systems Engineering Capability Model (SECM). For an organization to grow in systems engineering capability when implementing the EIA/IS 731‐1 SECM, individuals within that organization must also grow in increasing levels of competency. This paper describes the establishment within the INCOSE Technical Board of a special team to generate the needed taxonomy and presents preliminary results of their efforts. A brief account is provided on the general importance of capability models, which establishes a background for this high priority task. Key features of the EIA/IS 731‐1 SECM, to which the taxonomy is to be aligned, are summarized. The development approach for the taxonomy is described. A foundation is presented for the taxonomy's architecture, which is comprised of three highly congruent models. The paper closely ties the taxonomy to elements of the EIA/IS 731‐1 SECM. An example demonstrates the application of the taxonomy to the development of a set of enabling skills for the conduct of risk management per the EIA/IS 731‐1 SECM. The paper concludes with a description of future activities. The completed document will be entitled The Taxonomy Of Systems Engineering Competency, with subtitle Enabling Growth In Systems Engineering Capability Aligned With The EIA/IS 731‐1 Systems Engineering Capability Model.
1 Development of Internet in Latin America: The role of Academic Network Systems and their future
Authors: Aguilar Santiago R.
Published: November 2014

The role of academic network systems was pivotal for the development and expansion of Internet in Latin America. Most of the first Internet points‐of‐presence (POPs) in the region were implemented within the academic and scientific community. Today, deregulation is fostering a wave of competition and privatization through the region. The academic networks are facing a more competitive regulatory environment on the one hand, but also facing strong monopolies of basic telecom services on the other hand. It is necessary for regulatory agencies to establish and enforce clear and open regulations to help the survival of the academic networks. However, it is also necessary for the academic Internet providers to implement creative and aggressive strategies to continue providing communications services to universities, high schools and research and scientific institutions.
3 The Sociological Impact of Computers and The Internet on The Elderly
Authors: Ward Edward E.
Published: November 2014

This paper explores the growth of the use of computers and the Internet by the elderly. For the purpose of this paper, elderly is defined as someone 60 years or older. This paper begins with a short history of the environment in which this segment of the population has developed. It also includes an introduction to the Internet and computers and their effect on society. It discusses how the elderly receive information and education on computers and the Internet. It also explores the different uses that the elderly use the Internet for and compare them with society in general. The paper discusses how government agencies offer their services to the elderly on line. It demonstrates the impact that the Internet is having on the lifestyle, quality of life and day to day life of the elderly. Included also is a look at the expansion of the utilization of the Internet by the elderly. This paper presents a conclusion and a look into the future as the “Baby Boomers” reach retirement age.
2 Risk‐based Decision Support
Authors: Roberts Barney B. , Fussell Louis
Published: November 2014

Risk Management is often accomplished in a segmented and incomplete process. The engineering design team will worry technical risks, the mission planning team will worry mission success, and the program management team will worry about cost and schedule risks. None of these issues are independent. Schedule reductions or cost reductions will cause technical risks which may compromise mission success. Likewise a solution to a mission risk will create technical risks which directly impacts cost and schedule performance.

Risk‐based decision support is a process of examining the entire risk environment of a decision issue and presenting not just a point value to a decision maker, but the risk impacts, uncertainty, and the risk drivers for the solution options.

Current hot topics such as DoD's CAIV (Cost as an independent variable) and NASA's “Faster, Better Cheaper” (FBC) approach to projects and programs are concepts that beg for an integrated approach to risk management. The previous culture was to approach risk as “reduce all risk at any cost”. The current environment demands that risk be a traded resource along with cost, schedule and mission performance. Decisions must be made such that an acceptable mix is achieved.

Our approach is designed to integrate these risks into a common framework. It is designed to be a part of the program manager's decision‐making process. All decisions are made within a context of understanding the total integrated risk to the project.
3 Sources of Performance Risk in Complex System Development1
Authors: Browning Tyson R.
Published: November 2014

Developing complex systems is an exercise in uncertainty reduction and risk management. This article continues a previous paper, synthesizing research findings from literature and interviews with experienced product development managers and system engineers at a major aerospace company regarding the sources of uncertainty underlying one category of risk, product performance risk. Relationships between sources of performance uncertainty are shown using a causal framework. Consequences of performance uncertainty and shortfalls are also discussed. The goal of this preliminary work is to highlight areas for increased attention in planning and management processes, while providing a systems view of the effects of certain actions.
1 Structured Engagement
Authors: Boardman John , Fairbairn Allen
Published: November 2014

We discuss the management of the large product development process which necessarily involves a web of firms. Optimisation at the level of the firm means sub‐optimisation at the web level or the extended enterprise. Reductions in costs and lead times, for product development in the large, is only possible by recognising that effort is distributed across a market value chain. In this paper we describe a framework for ‘structured engagement’. This will support key decision‐makers in performing concurrent design of the architectures for the product, the processes, and the chain that delivers the required competencies (skills and technologies.
2 Integrating Government and Commercial Requirements – Serving Two Masters
Authors: Bayer Steve , Boese Gary , Hart Dan , Bonniksen Chris
Published: November 2014

The world market for launching satellites increased dramatically during the Preliminary Engineering and Manufacturing Development Phase of the United States Government's Evolved Expendable Launch Vehicle procurement program. This coincided with the U.S. Government's increased emphasis on acquisition reform ‐ insight versus oversight. These events brought about the following issues:

Development funds could only support a single design for both government and commercial customers,

Government and commercial requirements needed to be merged,

The government needed assurance that its requirements would be preserved, and

Government insight requirements had to be satisfied.

The Boeing Company integrated and managed the Government Evolved Expendable Launch Vehicle (EELV) System Performance Requirements (SPR) and the Boeing commercial customer launch requirements into the Boeing Delta IV launch system development program. This paper describes the organization of the specification tree, the integration and flow‐down of requirements, requirements change management, the requirements verification, and the lessons learned from these activities.
4 Risk Management in the Department of Defense
Authors: Schaeffer Mark D.
Published: November 2014

Since 1995, the Department of Defense (DoD) has increased its emphasis on risk management and changed the approach to its implementation. This presentation briefly summarizes the relationship between risk management and the DoD acquisition reform initiatives instituted by the Department in 1994–95, the evolution of risk management within DoD to its current state, and the contributions of the DTSE&E‐chaired Risk Management Working Group.

Despite progress, there is still considerable work to be done to improve the effectiveness of risk management in DoD. This presentation discusses the following future and ongoing initiatives to achieve that end:

Institutionalizing risk management as a normal management function in DoD acquisition programs,

Implementing risk management,

Sharing information,

Improving risk management training.
4 Technology Assessment Tool (A Systems Engineering Approach to Assessing U.S. Department of Energy Technology Proposals)
Authors: Rynearson Michael A. , Nonte John , Richardson John G. , Sebo Donald E. , Cooper W. Brooks , Theriault Rudy J.
Published: November 2014

This paper discusses the system design of a Technology Assessment (TA) tool that can be used to quantitatively evaluate new and advanced technologies, products, or processes. Key features of the tool include organization of information in an indentured hierarchy; questions and categories derived from the decomposition of technology performance; segregation of life‐cycle issues into six assessment categories; and scoring, relative impact, and sensitivity analysis capability.

An advantage of the tool's use is its ability to provide decision analysis data, based on incomplete or complete data.
1 Systems Engineering Through Stages
Authors: Stevens R. J. , Brook P.
Published: November 2014

Systems engineering demands repeated exploration of requirements and practicality through all parts of the development and operational life cycle. Development and usage must proceed in a series of stages, in which systems engineering processes interact with the organisational decision‐making. This paper defines a systems engineering approach based on established concepts from the innovation, product management and systems engineering literature. This model suggests that a unified systems engineering approach can be applied to all of development, including innovation, prototyping and evolutionary development.
2 System Engineering and Marketing
Authors: Paul David J. , Kenley C. Robert
Published: November 2014

Using models to capture requirements and to initialize operations concepts for new product development has received attention in the Eighth Annual INCOSE Symposium in Vancouver, with the result that the requirements handling process itself is more efficient. The document‐driven design methodology is replaced with models that state subsystem‐level requirements in executable form. However, most “models” are product‐focused and do not incorporate a methodology to clarify and quantify customer needs in relation to that product. This paper outlines a method that has been used by the authors in projects varying in size from church building programs to large satellite programs and involves both marketing and system engineering disciplines.
3 The Common Denominator
Authors: Karas Len , Rhodes Donna H.
Published: November 2014

This paper presents the systems engineering methodology in use at Lockheed Martin Federal Systems (LMFS) in Owego, New York. This LMFS‐Owego methodology has evolved over a fifteen‐year period, through evaluation, selection, and synthesis of many successful techniques used for systems analysis and design. The most recent enhancement to the methodology is theOperational Description Template, which serves as acommon denominatorfor optimal systems development. We discuss the problem that the methodology addresses, overview the process to which the methodology is applied, describe the methodology, and discuss initial results of the application of this method.