bluuebunny/crossref_metadata_2025_split huggingface dataset:
11.2.2 Applying Systems Engineering in a Renewable Energy Research & Development Environment
Authors: Snyder Neil , Antkowiak Mark 
Published: November 2014

AbstractSystems Engineering (SE) practice has largely developed around a few specific industries, especially aerospace/defense and IT. SE is well understood by, and remains associated with, these industries. The classical systems engineering process starts with conceptual development of a specific system that will ultimately be produced and deployed. In the renewable energy R&D environment, neither of these normal cases apply; the work is being conducted in a culture that is generally unfamiliar with systems engineering, and the R&D activities are mostly oriented toward technology development and refinement rather than toward development of a specific deployable system. Nevertheless, systems engineering principles can be applied to enhance the management of the Research & Development (R&D) process, but significant tailoring of SE processes is required, and enhanced modeling and simulation techniques must be applied to deal with all the unknowns at a very early part of the system lifecycle. The lessons learned from several years of experience in this unique environment at the National Renewable Energy Laboratory, as well as a number of new ideas for future process enhancements, will be explored in this paper.
11.3.3 The Significance of Configuration Management in the Context of Systems Engineering
Authors: Watts Stephen , Kossmann Mario 
Published: November 2014

AbstractSystems Engineering (SE) is widely recognised to be the key discipline to develop complex products in many industries. There is strong evidence that requirements related issues are at the heart of the majority of project failures, delays or budget overruns. Yet Requirements Engineering (RE) frequently does not seem to be sufficiently interfaced or integrated with other engineering disciplines such as design, manufacturing, finance, procurement and customer services. Configuration Management (CM) is widely accepted as a key discipline to establish this traceability and enable controlled baseline evolutions or iterations within the development process. However, the traditional scope of CM in the context of SE more often than not excludes requirements in the early phases of the development process. The present paper will give a brief introduction into the importance of RE in the SE context and the significance of CM to establish traceability between the requirements, design and product, before highlighting in more detail the potential contributions of the CM discipline with an emphasis on the early phases of the SE development life cycle.
The Use of Mini‐Case Studies to Illustrate Key Systems Engineering Principles
Authors: Weaver Jonathan , Vinarcik Michael J. 
Published: November 2014

AbstractRobust systems architecture (SA) and systems engineering (SE) processes are necessary for the development of successful engineering systems. Many notable product failures can be traced to breakdowns in the architectural or systems engineering practices of the design team.Despite the increased emphasis being placed on systems engineering, many systems engineering textbooks and references focus on specific tools (such as requirements or interface management systems). The few case studies included in these works are typically not exhaustive.However, for individuals in a given working environment, developing expertise in a specific tool not used by one's workgroup adds little value. The presenters believe that it is more useful to help individuals cultivate an intuitive understanding of architectural and systems engineering issues. For that reason, they have augmented traditional SE textbooks and teaching resources with mini‐ and maxi‐case studies.Using topics drawn from throughout human history (from ancient tombs and medieval cathedrals to the Airbus A380/Boeing 787 and NASA space missions), the presenters showcase both notable successes and failures. This enhances learning and retention of key topics and enables students to internalize key SA/SE principles.Cases may be presented using a variety of media (including PowerPoint slides, audio‐visual presentations, or show‐and‐tell artifacts). They may be used as lead‐ins to a traditional classroom lecture or as the kernel of a roundtable discussion among peers in the workplace.This tutorial will demonstrate the principles the presenters use to identify case study candidates, research methods used to develop the framework of the presentations, and techniques used to develop a holistic SE mindset. Several case studies will be interleaved with the presentation; one maxi‐case (intended to be the focus of an entire class period) will be presented as the capstone of the tutorial.
Systems Acquisition and Integration
Authors: Eisner Howard 
Published: November 2014

AbstractPrinciples of systems acquisition and integration guide the system development process and hopefully contribute to the success of the process as well as resulting products. This tutorial examines acquisition guidelines in detail, especially those supported by the U. S. Department of Defense. It also explores integration notions, from those that are recommended to those that tend to lead to difficulties. Relationships between acquisition guidance and integration responses are presented. A summary stresses key principles to be considered by the practicing systems engineer and also the value of utilizing these principles. Selected topics include: the DoD 5000 series, the DAPA report, capability‐based acquisition, the “top five” systems and software issues, interoperability, and a “top dozen” integration list.
An Introduction to Knowledge Representation and Ontology Development for Systems Engineers
Authors: Kendell Elisa , Jenkins Steven 
Published: November 2014

AbstractEffective communication requires a common vocabulary. An ontology provides a description of the terminology, concepts and relationships for a particular area of interest. An ontology may be viewed as a declarative encoding of the meaning of the domain vocabulary terms, thus making it a key to enabling communication. For systems that are used by people whose understanding of a domain is not necessarily consistent, an explicit description of the important terms can be extremely useful.Many commercial companies have successfully deployed applications with increasing use of semantics such as taxonomy‐based search and navigation services. Rule‐based manufacturing, product configuration, and financial services systems have been relatively common in those industries for many years. Fewer organizations have successfully deployed semantically rich systems that incorporate ontology‐based metadata, sophisticated reasoning and explanation support. The technology has been around for decades, though its use for web‐based applications is relatively recent, and it remains difficult for some people to understand, let alone use effectively.This tutorial provides an overview of the knowledge representation landscape and attempts to demystify some of the “black art” of ontology development. We will outline basic methodology steps developed from a combination of
Domain analysis methodology from software engineering
IDEF methods developed for the US Department of Defense
Best practices developed through extensive experience and lessons learned, with a focus on problems in software and systems engineering
Examples from systems engineering will be provided, with emphasis on ontology development in UML using the Ontology Definition Metamodel, applications that lend themselves to vocabulary development in the Web Ontology Language (OWL), and use of the these technologies together with models developed using the OMG's Systems Modeling Language (SysML).
Technology Development Roadmaps – A Systematic Approach to Maturing Needed Technologies
Authors: Collins John W. , Pincock Layne 
Published: November 2014

AbstractPlanning and decision making represent important challenges for all projects. This paper outlines the steps used to determine technical readiness and map the path forward to systematically advance readiness to support detailed design of the Next Generation Nuclear Plant. A Technology Readiness Assessment is used to evaluate the required systems, subsystems, and components (SSC) comprising the desired plant architecture and assess the SSCs against established Technology Readiness Levels (TRLs). A validated TRL baseline is then established for the proposed physical design. Technology Development Roadmaps are generated to define the path forward and focus project engineering and research and development tasks on advancing the technologies to increasing levels of maturity. Tasks include modeling, testing, bench‐scale demonstrations, pilot‐scale demonstrations, and fully integrated prototype demonstrations. The roadmaps identify precise project objectives and requirements; create a consensus vision of project needs; provide a structured, defensible, decision‐based project plan; and minimize project costs and schedules.
Optimizing Delivery of Global Pharmaceutical Packaging Solutions, Using Systems Engineering Patterns
Authors: Bradley Jeffrey L. , Hughes Mark T. , Schindel William D. 
Published: November 2014

AbstractThe global pharmaceutical supply chain, a complex system, involves manufacturing, distribution, and commercial wholesale/retail processes. Products in this system‐of‐systems are critical to health, subject to regulation from a web of trans‐national, national, and state/provincial authorities, and subject to commercial manufacturing, marketing, and distribution practices of numerous enterprises. Introductions of change into this environment is a challenging undertaking, demanding awareness of the many forms of and constraints upon this system, while delivering at the brisk rate required by law and commerce. For example, in response to drug counterfeiting and grey markets, national and local governments are currently introducing (differing) legal requirements to uniquely label and track pharmaceutical products to the individual retail bottle/package level, as they move through distribution. This paper describes the response of a global pharmaceutical manufacturer, re‐engineering multiple global product and country‐unique pharmaceutical product packaging lines, using Systems Engineering Patterns to reduce impacts of variable requirement and design configurations.
DMP: a well‐founded decision‐making procedure
Authors: van der Pol R.W. , Wiesman F.J. 
Published: November 2014

AbstractThe article introduces DMP, a new Decision‐Making Procedure. It covers the entire decision process, is independent of the specific task type, and based on realistic insights on human cognition. Theoretically, it is more effective than known procedures. It is compiled from known procedures in various research areas and case‐studies. Next to eight main steps, such as gathering knowledge and setting goals with evaluation criteria, DMP has a separate control step for controlling iteration through the main steps. Surprisingly, the content of each step, including the control step, contains the use of (1) trial and error, (2) knowledge and reasoning, including knowledge from old cases (i.e., from experience) and recursion to a new instance of DMP – which makes DMP deep ‐ and (3) a combination thereof. DMP may serve as a core procedure for Systems Engineering, as well as for improved expert systems.
Systems Engineering and Project Management, an Ideal Partnership
Authors: Jones David J. , Masters Melissa T. 
Published: November 2014

AbstractAn effective partnership of the Systems Engineer and the Project Manager on a project will greatly enhance the likelihood that the system will be delivered on schedule and on budget while meeting the needs of the end user. This is a partnership where project leadership is combined, playing to the strengths of each. Systems Engineering and Project Management represent two disciplines fundamental to the underlying success or failure of developing and deploying a complex system. Each of these disciplines has a systematic view of the system, offering each a perspective not afforded to the other development stakeholders. This partnership is paramount on a project of any complexity, how could it be over‐looked? Even if these elements alone are brilliant in their own execution, the end result could be a disaster if there is not an alignment and cohesive execution of the two disciplines.
1.2.3 Challenges Based Risk Management
Authors: Zonnenshain Avigdor , Shabtay Michal 
Published: November 2014

AbstractEvery systems engineer encounters challenges to plan and execute effective systems engineering activities during system design and development and throughout the project management. Most organizations provide standards, processes and procedures for applying systems engineering. We claim that each project is different, and project management policy & style should varies from one project to the other‐ “one size does not fit all”. We conducted a research that was based on the NTCP‐ Diamond approach for adaptive project management (Shenhar & Dvir 2004). The model claims that project management needs to be based on the strategic goals and the dimensions of the systems design including Novelty (How new the product is to its markets/customers/users?), Complexity (What is the scope of the project/product design?), Technology Uncertainty (How new the technology applied for the system is for the developers?) and Pace (How critical is your time frame?). We studied 18 projects & how the projects managers dealt with the above challenges. We found that the adaptive project management approach contributes to project success.Each project includes risks which are managed during the project life cycle. The traditional risks management process focus on technological, economical, marketing and organizational risks. We offer a Challenges Based Risk Management approach which is complement to the traditional approach. This approach is based on two risks elements:
Project challenge level‐ calculated by summing up the project challenges levels in each dimension (Novelty, Technology Uncertainty, Pace, Complexity).
Deviation from the adaptive management model.
This approach can be useful in managing project portfolio, and managing the project risk through its challenges.We offer a methodology of managing projects according to its challenges, and offer a way to minimize the project risks by minimizing the deviation from the adaptive model.
1.4.3 Applying Systems Engineering Modeling Language (SysML) to System Effort Estimation Utilizing Use Case Points
Authors: Bone Mary Alice , Cloutier Robert 
Published: November 2014

AbstractThis paper proposes that as model based systems engineering begins to play a larger role in system development it may be utilized in estimating systems effort, making model based systems engineering more valuable to system engineering. This paper proposes to extend the Use Case Points (UCP) estimating approach, used by some software engineers, to SysML for estimating the systems engineering effort. The paper reviews literature that encourages the notion of a UCP method for Systems Engineering (UCPSE). Finally the paper maps out the research plan to develop and validate the UCPSE method.
Architecture Panel
Authors: Dickerson Charles , Mavris Dimitri , Griendling Kelly 
Published: November 2014

AbstractThe Architecture Panel will offer three presentations that provide an overview of model based approaches and an introduction to a new viewpoint on Architecture and Systems Engineering:
A Brief History of Models and Model Based/Model Driven Approaches
A Relational Orientation on Architecture and Systems Engineering
ROSETTA: a Relational Oriented Systems Engineering and Technology Tradeoff
EnvironmentTime will be allowed time for questions and discussion after each presentation.The first presentation will provide a brief review of the foundational work of Tarski and Robinson on model theory and proceed quickly through the model based approaches of Wymore, Klir, Yin, and others then move through the INCOSE and OMG related initiatives on MBSE and MDA.The second presentation will introduce a new viewpoint on Systems Engineering based on mathematical relationships that is concordant with and expressive of the definition of ‘system’ specified by INCOSE and the IEEE, and the definition of ‘system architecture’ proposed by the ISO working group JTC1/SC7/WG42. This viewpoint will be referred to as Relational Oriented Systems Engineering (ROSE). In this viewpoint, relational models and their transformations are the means for abstracting systems and their engineering and design concepts. The concept of ‘definition and decomposition’ in Systems Engineering can be expressed more precisely as the formalism of ‘model specification and relational transformation’ in ROSE.The closing presentation builds on the Rosetta stone that provided a means to translate between the Greek, Hieroglyphics, and Egyptian demotic languages by exploiting a decree that provided a common text repeated in all three languages. In the same way, the ROSE Technology Tradeoff Analysis environment (ROSETTA) provides a means to translate between theoretical mathematics, subject‐matter expert driven analysis, and modeling and simulation by representing single problems using all three types of analysis while highlighting the commonalities and differences between the three different approaches to the problem. ROSETTA leverages ROSE to create a direct mapping between the Quality Function Deployment (QFD) methodology and standard quantitative conceptual design space exploration techniques leveraged in technology forecasting and trade studies.
2.1.2 Systems Engineering Provides Successful High Temperature Steam Electrolysis Project
Authors: Park Charles V. , Opare Emmanuel Ohene 
Published: November 2014

AbstractThis paper describes two Systems Engineering Studies completed at the Idaho National Laboratory (INL) to support development of the High Temperature Stream Electrolysis (HTSE) process. HTSE produces hydrogen from water using nuclear power and was selected by the Department of Energy (DOE) for integration with the Next Generation Nuclear Plant (NGNP). The first study was a reliability, availability and maintainability (RAM) analysis to identify critical areas for technology development based on available information regarding expected component performance. An HTSE process baseline flowsheet at commercial scale was used as a basis. The NGNP project also established a process and capability to perform future RAM analyses. The analysis identified which components had the greatest impact on HTSE process availability and indicated that the HTSE process could achieve over 90% availability. The second study developed a series of life‐cycle cost estimates for the various scale‐ups required to demonstrate the HTSE process. Both studies were useful in identifying near‐ and long‐term efforts necessary for successful HTSE process deployment. The size of demonstrations to support scale‐up was refined, which is essential to estimate near‐ and long‐term cost and schedule. The life‐cycle funding profile, with high‐level allocations, was identified as the program transitions from experiment scale R&D to engineering scale demonstration.
2.2.2 What is Technical Integrity and How to Measure It?
Authors: Edwards Michael 
Published: November 2014

AbstractThe impact of formal technical regulation and certification frameworks on the technical integrity of complex systems is poorly understood. In researching this problem the author is seeking a means by which to measure technical integrity. Technical integrity is defined and discussed, in both the context of complex systems for the Australian Defence Force and in wider civilian and military contexts. Technical integrity is defined as being composed of two separable attributes that reflect the intended, desired emergent properties of a system and the minimisation of unintended, undesired emergent properties. An approach for formulating a composite measure of technical integrity is developed from this definition and is presented for critical review.
2.4.2 A Framework for Supporting the Transition to Lean Systems Engineering
Authors: Grünwaldt Steffen , Hofstetter Wilfried K. , Palm Herbert 
Published: November 2014

AbstractLean Thinking has long been recognized as an important approach to sustainable and comprehensive improvement of products as well as business processes. In the area of systems, the Lean approach is particularly attractive because of its joint improvement of systems engineering effectiveness and efficiency. Yet, to date no comprehensive framework has been put forth for managing the transition to lean systems engineering in a real‐world product development organization engaged in day‐to‐day business. This paper presents a novel 3‐stage framework for managing the transition to Lean Systems Engineering, with special focus on aspects such as lean awareness and target definition as well as active participation of employees and for capability build‐up during the transition phase in order to ensure top‐to‐bottom buy‐in. The framework is based on actual consulting experience of the authors; for three recent example transitions the application of the framework is discussed. Based on these application experiences, a number of significant conclusions with regard to the proposed framework can be drawn covering the effectiveness of people‐related measures, value stream analysis and design activities. Significant opportunities for further work remain, in particular in the areas of further application of the framework, correlation of current and future state scenarios and associated transition strategies with standard management consulting case scenarios as well as further development of lean training exercises for systems engineering methods as applied to product development.
3.1.2 System Verification and Validation through Reliability, Availability, Maintainability (RAM) Analysis & Technology Readiness Levels (TRLs)
Authors: Opare Emmanuel Ohene , Park Charles 
Published: November 2014

AbstractThe Next Generation Nuclear Plant (NGNP) Project, managed by the Idaho National Laboratory (INL), is authored by the Energy Policy Act of 2005, to research, develop, design, construct, and operate a prototype fourth generation nuclear reactor to meet the needs of the 21st Century. A section in this document proposes that the NGNP will provide heat for process heat applications. As with all large projects developing and deploying new technologies, the NGNP is expected to meet high performance and availability targets relative to current state of the art systems and technology. One requirement for the NGNP is to provide heat for the generation of hydrogen for large scale productions and this process heat application is required to be at least 90% or more available relative to other technologies currently on the market.To reach this goal a RAM Roadmap was developed highlighting the actions to be taken to ensure that various milestones in system development and maturation concurrently meet required availability requirements. Integral to the RAM Roadmap was the use of a RAM analytical/simulation tool which was used to estimate the availability of the system when deployed based on current design configuration and the maturation level of the system.
Organization of 147 Lean Enablers for Systems Engineering into the 26 INCOSE Systems Engineering Processes
Authors: Oppenheim Bohdan , Secor Deborah 
Published: November 2014

AbstractThe organization of 147 Lean Enablers for Systems Engineering into the 26 INCOSE Systems Engineering processes in the INCOSE Handbook will be described. The methodology used will be presented. The organization has been approved by the Lean SE Working Group during the IW meeting. A draft of the new Appendix for the Handbook submitted to the Handbook Working group will be illustrated.