bluuebunny/crossref_metadata_2025 huggingface dataset:
From Agile Systems Engineering to Agile Safety Engineering
Authors: Lawson James R.
Published: September 2016

As an alternative to the more traditional v‐model, the application of the principles of agile systems engineering to safety engineering is investigated. Objectives for agile safety engineering are derived from the agile manifesto. A framework combined with a selection of techniques is proposed to satisfy these objectives. The framework is supported by multiple entry points which facilitate the rapid assessment of the safety of a safety critical system with respect to probability budgets and the rapid reassessment as necessary to remove conservatism. A hybrid approach which combines the virtues of a piece‐part and functional FMEA and eliminates unnecessary effort is described.

It is concluded that an iterative step‐by‐step approach to safety engineering is possible. Also, it is proposed that the information resulting from an iterative approach and its availability early to guide the product development of the safety critical system is likely to result in the system being safer.
Steel‐making Plant Engineering Guide Development Based on Systems Engineering Standards: Feasibility Study and Concept Design
Authors: Lee Taekyong , Salim Shelly , Lee Joongyoon
Published: September 2016

Engineering industry is considered as a key industry which will drive the future of Korea. However, Korean engineering companies have recently made a huge loss and the lack of engineering capability is pointed out as a main cause of this situation. Unlike Korean engineering companies, world leading engineering companies have their own systems Engineering Standards/Guides ensuring successful fulfillments of the feasibility study, concept design and basic design processes.

An Engineering standard for an organization is an essential means to shorten the time for engineering design, to maintain the engineering quality and to secure the engineering efficiency in the development of the complex system. One of the main reasons of Korean Engineering companies' lack of engineering capability is the absence of the Engineering standard.

In the paper, we have developed a steel‐making plant Engineering standard based on a systems engineering standard. We used both ISO/IEC/IEEE 15288 and NASA SE Handbook as main reference standards. First, we have introduced a lifecycle definition and a product breakdown structure of a general steel‐making plant. Then we have introduced detailed engineering processes of feasibility study and concept design phase. Finally we have introduced exit criteria for outputs of feasibility study and concept design phase to assess the degree of achievement.
Technology Readiness Level as an Exit Criteria of Early Life Cycle Phases for Steel‐making Plant
Authors: Salim Shelly , Lee Taekyong , Lee Joongyoon
Published: September 2016

Projects on steel‐making plant follow the stages of steel‐making plant system life cycle. In each life cycle stage, there are exit criteria to be fulfilled before a project can continue to the next stage. Among the exit criteria, we focus on one of the technical exit criteria, that is, the technology maturity. Technology maturity is measured using technical readiness level (TRL) and TRL concept has been largely adopted by numerous organizations and industry. However, the assignment of a certain TRL as one of the exit criteria of life cycle stages are not well adapted. In other words, TRL is not considered as a critical exit criteria of a system life cycle stages. In this paper, we would like to propose that the TRL should be one of the exit criteria of each life cycle stage. In this research, we propose a steel‐making plant system life cycle, define the technical readiness level for a steel‐making plant, and assign a target TRL for each life cycle stage as an exit criteria of that stage. The benefits of target TRL assignment to the life cycle stages are as follows: (1) the technical risk of developing/inserting a technology can be controlled on each life cycle stage, (2) the cost incurred if the technology to be developed/inserted is failed can be analyzed in each life cycle stage, and (3) as a standardization effort of technology readiness at each industrial plant life cycle stage. By directly assigning target TRL for each life cycle stages, we look forward to a more coordinated (in terms of exit criteria) and highly effective (in terms of technical risks identification and eventually project failure prevention) technology development and assessment processes.
Integration of SE Design Principles in a Capstone Design Course: Airborne Birdstrike Countermeasure
Authors: Newcamp Jeffrey M.
Published: September 2016

This paper describes a Systems Engineering capstone design course at the United States Air Force Academy that evaluated aural and visual birdstrike mitigation technologies and their feasibility for integration onto aircraft. The course sought to solve a real‐world problem for an actual customer using a multidisciplinary team that followed a structured Systems Engineering approach. It is shown that an undergraduate team can produce a patent pending technology given proper motivation, resources and guidance. This project's principal requirement was to thwart birdstrikes up to 10,000 feet above ground level and below 250 knots calibrated airspeed. The chosen solution technology combined a speaker system capable of producing a sound pressure level of 135 dBA and utilized existing aircraft landing lights pulsed at a rate of 0.75 Hertz.
“Fifty Shades of Agile”: AN ANALYSIS OF DIFFERENT PERSPECTIVES OF AGILE SYSTEMS ENGINEERING
Authors: Kemp Duncan , Akroyd‐Wallis Kirsty , Mactaggart Ivan , Evans Rhianne , Harrison Kris , Woodcock Hazel
Published: September 2016

Although Agile is well‐defined, and relatively widely‐used within the software engineering field, applying Agile to Systems Engineering (SE) is still under debate. While some feel that Agile SE offers potential to improve customer satisfaction and reduce cost, risk and time to market, it is unclear how well Agile approaches apply to SE.

This paper explores diverse rationales for applying Agile SE, various types of systems it can be applied to, and different Agile SE approaches, showing that there is no single definition of Agile. Views range from: a high tempo approach to systems delivery analogous to Agile software, radical tailoring of conventional SE against fixed requirements, using agile software techniques to develop SE documents and models, to using Agile as a sales mechanism with no real understanding of chance of success. These perspectives are analysed against the 12 Agile software principles, Snowdon's Cynefin Framework and Ring's Value Cycle, concluding with 14 observations about Agile SE approaches.
Collaborative Model‐based Systems Engineering for Cyber‐Physical Systems, with a Building Automation Case Study
Authors: Fitzgerald John , Gamble Carl , Payne Richard , Larsen Peter Gorm , Basagiannis Stylianos , Mady Alie El‐Din
Published: September 2016

We describe an approach to the model‐based engineering of cyber‐physical systems that permits the coupling of diverse discrete‐event and continuous‐time models and their simulators. A case study in the building automation domain demonstrates how such co‐models and co‐simulation can promote early cooperation between disciplines within a systems engineering process before the expensive commitment is made to integration in physical prototypes. We identify areas for future advances in foundations, methods and tools to realise the potential of a co‐modelling approach within established systems engineering processes.
Model Base Systems Engineering used in developing a Telescope Manager
Authors: le Roux Gerhard
Published: September 2016

Various tools, tutorials and examples exist about the idea of doing development based on models of information (MBSE) as apposed to the traditional document driven approach. Yet, the practical examples of achieving this are still relatively few. An unguided modelling approach can easily lead to “modelling for modelling's sake”, paying for expensive management tools – and creating diagrams that makes the project more complex instead of simpler.

This paper is a case study on the efforts to move to a model based development for a large complex system by looking at early conceptual and preliminary design stages of the Telescope Manager project – particularly taking into consideration how it transforms from a functional to a physical design.

The aim is to see if general principles and concepts can be derived upon which future Systems Engineers can make use, of before embarking on a similar venture.

The study will define the problem area and scope of modelling required for the Telescope manager.

Then the study will give a critical examination of various strategies and actions undertook regarding the use of MBSE for the Telescope Manager.

The study will conclude with a derived set of concepts and principles based on the evaluation results that may be used in the future.

Lastly the study will comment on what the future looks like for MBSE and give some recommendations in terms of preparing for what comes next.
Designing a Systems Engineering Process and Toolset for the Giant Magellan Telescope
Authors: Hardie Kayla , Trancho Gelys , Miles John W.
Published: September 2016

The Giant Magellan Telescope (GMT) Project has used Cognition Cockpit™ to facilitate and implement systems engineering processes such as operational concept development, requirements development and management, interface management, failure modes and effects analysis, hazard analysis, and verification. This paper discusses the structure of the GMT Systems Engineering process, the flowdown of requirements throughout this process, and how Cockpit features are utilized to ensure traceability within the project.
Implementing a Structured Verification Framework to Improve Verification Requirements Quality
Authors: Haskins Bill
Published: September 2016

Verification is a process for developing evidence to show that the design satisfies the requirements. The verification process starts early in a development program and the verification requirements are defined in the verification text of a requirements document, as defined in MIL‐STD‐961, Defense and Program‐Unique Specifications Format and Content. Papers have been written to describe how to develop quality design requirements to ensure the requirements are unambiguous and verifiable, as required by ISO/IEC/IEEE 29148:2011 and related commercial and military standards, but few papers have been written to describe how to develop quality verification requirements for each design requirement. This paper describes a formal structured verification framework for developing consistent, high‐quality verification requirements, which includes using specific sentence structures to write the verification requirements with mandatory and optional elements.
Case Study: A Model Based Systems Engineering (MBSE) Framework for Characterising Transportation Systems Over the Full Life Cycle
Authors: Scott William , Fullalove Richard , Arabian Gary , Campbell Peter
Published: September 2016

Development of transport infrastructure has significant challenges including acquisition lag, phased evolution, multiple disparate stakeholders and environment‐specific issues. The Asset Standards Authority (ASA) at TfNSW is introducing MBSE to address these challenges. Instrumental to the introduction is the development of a framework that structures the available data and provides guidance and traceability between the data sets. This framework combines the enterprise‐level drivers with the lower level drivers such as standards to outline a generic conceptual design for a transport system. This conceptual design is then used to guide future system development. The outcome is future project information based on greater, enduring understanding of the transport system.
Developing and implementing systems engineering and project management processes at CSiT – A small Canadian company in public transportation
Authors: Laporte Claude Y. , Tremblay Nicolas , Menaceur Jamil , Poliquin Denis , Houde Ronald
Published: September 2016

A project was created to define and implement project management and systems engineering processes at CSinTrans Inc. (CSiT), a Canadian company, founded in 2011. CSiT specializes in the integration of communication and security systems in transit industry such as trains, subways and buses as well as railway stations, subway stations and bus stops. ISO/IEC 29110 standard and guides for systems engineering have been used as the main reference for the development of these processes.

The project's history, purpose and rationale that prompted CSiT to adopt this recently published standard are presented. The implementation of the standard is described. The reflections and decisions made during the implementation are presented. The lessons learned are discussed. Recommendations and advice for organizations wanting to implement ISO/IEC 29110 are described.

ISO 29110 has helped raise the maturity of the organization by implementing proven practices and developing consistent work products from one project to another. ISO/IEC 29110 was a good starting point to align processes with specific practices of CMMI® Maturity Levels 2 and 3. ISO/IEC 29110 has also helped CSiT with developing light processes as well as remaining flexible and quick in its ability to respond to its customers.
Faster is Better and Cheaper
Authors: Geurts Wouter J.W.
Published: September 2016

A movement with increasing momentum in the software world is DevOps. In DevOps development staff and operations staff work together in one integrated team producing and operating software. DevOps initiatives report shorter cycle times (time to production of features) and less business disruption. Contrary to Agile, DevOps has not been initiated by a small group thought leaders communicating a manifesto. Every company doing DevOps, or wanting to do it, has its own specific definition and approach. In this paper we analyze the DevOps movement to its core values and connect it to documented Systems Engineering knowledge. We show that DevOps (extending (Scaled) Agile) is an improvement movement addressing almost all the Systems Engineering practices. Yet the (re)introduction of System Engineering processes would not provide the same effect because DevOps/Agile adds a strong drive on organizational change management with focus on cultural fit. Where in the past improvement parameters had been quality or (implementation) cost, the improvement parameter now is production speed (cycle time). Improving quality or cost can lead to slowness, focus on speed will increase quality and cost. Where the Agile movement increases speed introducing focus on stakeholder collaboration and small increments of (software) products. DevOps in its ultimate form accelerates the speed introducing a single role owning service accountability and total cost of ownership, thereby providing engineers a central place in the business.
Efficiency Management in Spaceflight Systems
Authors: Murphy Karen
Published: September 2016

Efficiency in spaceflight is often approached as “faster, better, cheaper – pick two”. The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.
Managing Installation Tolerances through System Modeling and Tolerance Budgeting
Authors: Henanger Thomas , Muller Gerrit , Picacia Luca
Published: September 2016

Contractors in the oil and gas industry are facing challenges when installing subsea production systems (SPS) in deep waters. The installation relies on engineering of the systems with high accuracy levels and narrow clearances on the interfacing surfaces to meet required installation tolerances. To ensure that all installation tolerances requirements are met, there is a need for a systematic governing process of managing, controlling, and verifying them. Engineers define installation tolerances through qualification activities of components and technologies. Extensive systems and complex installation sequences generate tolerance chains affecting the interfacing components. The verification of the installation consequently requires a significant effort.

The research focus is on how system modeling and tolerance budgeting would help the process of managing installation tolerances of a subsea production system in the context of preventing late verification, potential late design changes, and errors in installation. Use of system modeling made it possible to visualize the installation of the system of interest, and systematically structure relevant information. The visualization supported the researchers to develop an understanding of the tolerance chain for the system of interest. Based on the models, we were able to put together a tolerance budget calculating the theoretical worst‐case scenario of installation on a chosen critical misalignment. Our research showed that the systems engineering (SE) effort had a positive impact on the process, considering the cost of the effort relative to the potential cost of the preventable scenarios.
Infrastructure/Train Borne Measurements in support of Railway System Performance Modelling
Authors: Barson Lloyd , Fung Wilson , Toossi Amir
Published: September 2016

Ever increasing demand and the need for improving the capacity of the rail network in the UK has led the industry to investigate new ways for optimising the capacity utilisation. The recent systems modelling studies have highlighted the criticality of using the available data sources to better understand the system behaviour and underlying factors impacting the system's performance among which Common Cause events play a substantial role. In this paper the current infrastructure‐borne and train‐borne measurement systems will be introduced. The processing of this data for use in modelling Common Cause events is discussed and opportunities for further integration of the various data layers are highlighted.
Reinventing the ConOps for Innovative Systems Development
Authors: Zhao Yang‐Yang , Sjöberg Peter , Leifer Larry J. , Dersten Sara
Published: September 2016

In an ever rapid changing world of today, enterprises cannot leverage only on past success. Striving for an innovation success demands traditional systems engineering methods (i.e. ConOps in our case) to be updated. This study points towards the benefits for such a company to leverage the usage of the ConOps together with the needfinding of a design‐inspired method – design thinking, and therefore introduce the User‐focused ConOps. Through two construction equipment development case studies we show the importance of User‐focused ConOps from it is created until the system validation.
Therapy for projects
Authors: Pickard Andrew C , Nolan Andy J , Russell Jennifer L , Beasley Richard
Published: September 2016

Have you ever worked on a project where you know things aren't going well, but you don't know why or what to do about it? Many managers may admit that team culture and behavior can be the source of significant problems, or the reason for success. The team members of a low performing project may be aware that the project has “problems” but it can be hard to characterize the issues and therefore identify meaningful improvements.

The Graves Model, developed in the 1950's showed that the ways of thinking and behaving, used to help understand individuals, could also be applied to projects, organizations and even nations. Groups of people exhibit the same “psychological” behaviors as an individual.

This paper has made the assumption that a group of individuals working together, for instance in a project team, can exhibit the same ways of thinking as an individual, and therefore practices for helping individuals can equally be applied to the group's culture and behavior. The paper is not a proof of concept but a proposal of how common psychological conditions may be used to diagnose and treat the culture and behavior of projects or even organizations. The paper is to encourage further investigation into the possibility of benefiting from significant research that has been performed by the mental health industry.

This paper describes the development and application of a Project Health Evaluator tool, based on 11 common psychological conditions. The tool consists of a set of 110 symptoms; the evaluation is based on observations the evaluator selects as being applicable to the project. Then at the click of a button, an assessment of the health of the project is provided, together with a set of recommended actions to help the project recover.
A Process for Capturing the Art of Systems Engineering
Authors: Owens III “Skip” Clark V. , Sekeres Carrie , Roumie Yasmeen
Published: September 2016

There is both an art and a science to systems engineering. The science of systems engineering is effectively captured in processes and procedures, but the art is much more elusive. We propose that there is six step process that can be applied to any systems engineering organization to create an environment from which the “art” of that organization can be captured, be allowed to evolve collaboratively and be shared with all members of the organization. This paper details this process as it was applied to NASA Launch Services Program (LSP) Integration Engineering Branch during a pilot program of Confluence, a Commercial Off The Shelf (COTS) wiki tool.
Overview of an Emerging Standard on Architecture Processes – ISO/IEC 42020
Authors: Martin James N
Published: September 2016

A new, emerging standard on architecture practices is under development as ISO/IEC 42020. This paper provides an overview of the key concepts in this standard and the rationale for these ideas. The standard defines six architecture‐related processes: governance, management, conceptualization, evaluation, elaboration, and enablement. These are comprised of 37 activities, having five to eight tasks specified for each activity. It is expected that these processes will be incorporated into the next version of INCOSE's Systems Engineering Handbook and in the Guide to the Systems Engineering Body of Knowledge. This standard can be used as a foundation for organizational training and guidebooks on architecture management and development.
The SoS‐VEE Model: Mastering the Socio‐Technical Aspects and Complexity of Systems of Systems Engineering (SoSE)
Authors: Hoehne Oliver
Published: September 2016

Today, almost all defense systems are part of one or more system of systems (SoS, Dahmann and Baldwin 2014). Failure to consider SoS context early and throughout acquisition can result in significant risk to the effectiveness or successful fielding of the system (DoD 2008). The SoS‐VEE model has been developed recognizing the complexity of SoS Engineering (SoSE), and that the acquisition and fielding of constituent systems (CS) in a SoS environment entails more than simply integrating physical systems. The SoS‐VEE model focuses on early SoSE activities and addresses the socio‐technical aspects of integrating people, processes, and products associated with the constituent system(s). The paper describes in a step‐by‐step process how the SoS‐VEE was derived, its underlying principles, and uses an Unmanned Aerial Vehicle (UAV) operating as a constituent system of the NATO Alliance Ground Surveillance (AGS) system of systems as an example to illustrate the practical application of the SoS‐VEE model. The predominant viewpoint of this paper is from the systems engineer concerned with the acquisition or development of a (constituent) system of interest (UAV) in a System of Systems environment (NATO AGS SoS). The paper demonstrates how the systems engineer will be enabled to successfully integrate the constituent systems horizontally (physically) and vertically (socio‐technically) into the larger SoS using the SoS‐VEE model.
A Case Study of a Successful System: The Scottish Lighthouses from the 18th to the 21st Century.
Authors: Sillitto Hillary
Published: September 2016

In the late 18th century, the period in which Robert Louis Stevenson's novel Kidnapped was set, up to 20% of the cargo in ships sailing round the Scottish coast was lost to shipwreck. This level of financial loss made the ship owners willing to pay for safety systems to reduce the risk to their investment. There followed an astonishing period of engineering and organisational innovation to deploy a complex socio technical system that has continually delivered value for over two centuries. The 100 or so lighthouses built by the Stevenson family, all of them still standing and most of them still operating, were engineering marvels in their own right. But even more marvellous in many ways was the socio technical system the Stevensons and the Northern Lighthouse Board built to operate the “lighthouse capability”. The paper will show how all components of modern capability management were developed to exploit the technology in an enduring and continuously evolving system‐of‐systems that made the wild seas off Scotland relatively safe for seafarers. Of particular interest is the long term strategic planning across multiple lines of development: as the light houses were automated, the inevitable workforce reduction was achieved by retirement and redeployment, not by redundancies. This whole story is an excellent example of “through‐life capability management” of an “enduring system”. The paper also shows that modern approaches to systems architecting can be generalised – and that all perspectives offered by modern architecting methods are needed – to describe a two‐century‐old system! The case study also demonstrates the need to describe a system‐of‐systems at multiple levels, and a method for doing this.
Healthcare Facility Commissioning – The Transition of Clinical Services
Authors: van der Watt Riaan , Erasmus Louwrence
Published: September 2016

A public multi‐disciplinary primary‐level hospital delivers clinical services to both in and out patients within its catchment area. A multi‐disciplinary hospital is a healthcare facility of which the commissioning or transition into operations is a complex process that can last several months. This paper treats a hospital's clinical services using a systems perspective on healthcare services delivery within the context of the systems hierarchy level definitions used in South Africa to relate the inward and outward commissioning of a hospital to the concepts of systems engineering and services science. A hospital can be viewed as a system of systems containing several tangible and intangible elements identified through the clinical services blueprint that during commissioning can be related to useful systems engineering ideas from large‐scale infrastructure projects. The relationship between the clinical services blueprint and the Systems Breakdown Structure (SBS) is very important and must be coordinated with the Work Breakdown Structure (WBS) and Organizational Breakdown Structure (OBS) during commissioning. The concepts put forward in this paper should enable hospital project and commissioning managers to gain insights into the integration of systems from a holistic perspective during design to achieve an integrated and optimized commissioning schedule to achieve overall operational readiness.
“Systems Engineering helping to raise public awareness”
Authors: TERRIEN Olivier
Published: September 2016

Oty Productions SAS is a French company specialized in raising awareness and popularizing technical domains. Until 2013, Project Management was classical and mainly chronological. When we decided to develop a project with a new illustrated book, we adopted concepts and tools proposed by the INCOSE. Written as a testimony, this paper demonstrates their possible translation into a ‘raising awareness’ problem.

Based on a project named “Crow versus Crow”, this paper shows notions and methods applied during the engineering phase of a system addressing a non‐initiated and young audience about Electronics which is everywhere in today's life. This document describes how these tools were used in the realm of books and conferences. It shows achieved results through this way of proceeding and compares them to those of previous projects.

Since this systematic approach in an unusual field of application for the INCOSE was relevant and successful, this paper lays the foundations of our next project for years to come. Convinced of these principles and practices, Oty Productions has started a project to raise awareness about systems and to popularize their engineering processes.
A Framework for Small Satellite Architecture Design
Authors: Qaisar Sana U. , Ryan Michael J. , Tuttle Sean L.
Published: September 2016

The availability of miniaturized, commercial‐off‐the‐shelf (COTS), low‐cost satellite components has encouraged the design and development of “small” satellites by relatively inexperienced organizations and individuals seeking low‐cost and fast‐delivery missions with “good enough” reliability requirements, through non‐traditional risk‐taking approaches. Currently, there are no standards or guidelines for optimal architecting of such plug‐and‐play satellites. Consequently, the accepted trade‐off, between the available limited resources and the reliability compromise, in the architectural design space, is likely to be sub‐optimal, resulting in a sub‐optimized capability. In this paper, we propose a systematic framework for informed and optimal decision making which allows the designer to dynamically explore a multitude of solutions derived from relevant COTS databases, to determine an architecture that optimizes the system reliability under the given constraints. The proposed framework is demonstrated through the presentation of a commercial Cube‐Satellite example based on real data. This work can potentially contribute to small satellite standardization efforts.
Infrastructure System Restoration Planning Using Evolutionary Algorithms
Authors: Corns Steven , Long Suzanna , Shoberg Tom
Published: September 2016

This paper presents an evolutionary algorithm to address restoration issues for supply chain interdependent critical infrastructure. Rapid restoration of infrastructure after a large‐scale disaster is necessary to sustaining a nation's economy and security, but such long‐term restoration has not been investigated as thoroughly as initial rescue and recovery efforts. A model of the Greater Saint Louis Missouri area was created and a disaster scenario simulated. An evolutionary algorithm is used to determine the order in which the bridges should be repaired based on indirect costs. Solutions were evaluated based on the reduction of indirect costs and the restoration of transportation capacity. When compared to a greedy algorithm, the evolutionary algorithm solution reduced indirect costs by approximately 12.4% by restoring automotive travel routes for workers and re‐establishing the flow of commodities across the three rivers in the Saint Louis area.
Learning Systems Engineering Lessons from an Electric Vehicle Development
Authors: Swart Gerhard
Published: September 2016

The Joule Electric Vehicle (EV) was developed “from a clean sheet” by Optimal Energy, a South African start‐up company established in 2005. In the seven years to its liquidation in 2012, the company grew to 108 people, built up significant international partnerships, developed substantial in‐house technology and performed three development iterations culminating in four market‐testable prototypes.

Developing a vehicle from scratch requires a different approach to the traditional automotive development processes, which are optimised for evolutionary vehicle improvements and cost reduction.

Developing a new EV in a new organisation without legacy processes or manufacturing infrastructure presents additional challenges but also provides opportunity to work “top‐down”, focussing on the real “mission requirements” instead of being trapped by legacy practices, design concepts and infrastructure. Systems engineering “best practices” may be applied to a larger extent and the concept of passenger mobility can be optimised for electric propulsion instead of accepting the traditions of fossil‐fuel power.

This paper provides highlights of the unique challenges and opportunities related to EVs, and presents the tailored development process that was established for the Joule EV.
Enterprise Systems Engineering for Improving Cross‐enterprise Effectiveness
Authors: Sitton Miri , Reich Yoram
Published: September 2016

Enterprise system engineering (ESE) is an emerging practice arising in the last decades, hand in hand with the maturing of system engineering (SE). However, ESE differs significantly from SE, due to the enterprise's unique property as a system of unsynchronized arrays of systems. This property might lead to severe issues, such as cross‐enterprise failures, lack of decision‐support information for cross‐enterprise decisions, long delays in integration tests and unexpected emergent behavior. Existing approaches including ESE frameworks and Systems of Systems (SOS) engineering do not fully address this property. This paper presents a new ESE framework named EPIC (Enterprise Processes Integrative Collaboration), enabling the coordination between unsynchronized arrays of systems within the enterprise and even further across several enterprises. EPIC was implemented successfully in two large‐scale cases from the aerospace and transportation disciplines. Similarly, EPIC may be applicable in other disciplines in order to obtain better enterprises by improving cross‐enterprise operational processes and interoperability.
A Survey of Technology Readiness Level Users
Authors: Tomaschek Katharina , Olechowski Alison , Eppinger Steven , Joglekar Nitin
Published: September 2016

The Technology Readiness Level (TRL) method, used to assess the maturity of a technology, has been applied in different industries for over 40 years. TRLs assist engineers in managing risks, communicating development progress and specifying deliverables. As TRLs have been adopted in more industries, the original scope of TRL application has expanded and challenges in use have emerged. Little is known about the TRL user community and its opinions of the method, or of the method's practical challenges. A global industry survey, conducted with professional TRL users, investigated the relative importance of 15 previously identified challenges of TRL use. We find that the top four most critical TRL challenges as identified by our respondents are system‐related; they include the topics of integration, interfaces, system modifications, and overall system maturity. The results reveal a need for an extension of the TRL method from a component‐readiness‐context to a system‐readiness‐context.
Trade Study of Alternative Controls and Power Distribution Architecture in Subsea Processing
Authors: Eide Halvor Mehlum , Haskins Cecilia
Published: September 2016

This paper reports on a trade study of feasible concept alternatives for control and low voltage power distribution architecture for subsea process stations. Subsea gas compression is a new process station technology that is responding to the market need for extending the lifetime of existing subsea gas fields. These subsea process stations are deployed in deeper water, farther offshore and in harsher environments. The demand for a more efficient, less complex, and cheaper solution is pushing the technology development and screening for alternative concepts. The SPADE methodology has guided a trade study of concept opportunity exploration for alternative distribution architectures. The Pugh matrix demonstrated its ability to provide a simple overview of the multiple factors in a decisionmaking situation, with extensions for risk and opportunity assessment.
Understanding Services: Understanding Stakeholders
Authors: Ashlin Stephen J , Cardow Iain , Crawford Alan , Davies John K , Farncombe Andrew , Mason Peter
Published: September 2016

There are many different services in general use today. New ones are being developed driven by the move from customers owning equipment to it being provided by suppliers as a service. We all know what services are, we use them every day. All the systems we develop and deliver end up providing or supporting some sort of service. The aim of the INCOSE UK Service Systems Engineering Working Group is to identify areas of the engineering lifecycle, the methods, and the techniques that need to be different for engineering services as opposed to ‘traditional systems engineering’ for the engineering of products.

When INCOSE was formed there were various definitions of ‘What is a System?’ it took time to sort out but now is not normally an issue. Today established standards; SEBOK, DoDAF, MoDAF, Open Group, ITIL, CMMI; have different definitions of a Service. These differences are not just differences in wording driven by stakeholder views that can lead to significant differences of what is expected in delivering services. To understand and successfully deliver services, we need to understand and relate such definitions, and then use them within our engineering of services.

In this work we have used Case Studies for Services that cover various areas of interest for businesses in INCOSE UK and used them to establish the scope of our work. The use of the term ‘Service’ has been extracted from literature together with definitions. The definitions have been grouped, related and where necessary re‐worded to provide a map of terms and the various definitions extracted from literature understood using this map.

The use of Service Oriented Architecture (SOA) outside the IT Sector has been considered, along with previous work in this area, as the architecture for understanding Services. We have illustrated this through simple application to one of the case studies. This is a different but complementary approach to understanding services and work with further case studies is needed to understand how it can best be applied.
An Initial Bibliometric Analysis and Mapping of Systems Engineering Research
Authors: Oosthuizen Rudolph , Swart Ignatius , Pretorius Leon
Published: September 2016

Systems engineering is still a growing field that depends on continuous research to develop and mature. Research in systems engineering is difficult and the classic approaches for other engineering disciplines may not be sufficient. Additional methods and tools from business and social sciences are required to address all the issues in systems engineering. This paper performs a bibliometric analysis on the Systems Engineering journal from INCOSE to capture and discuss the status and trends of research in the field. This is also complemented by keyword parsing of the journal papers to develop a structure for classification of systems engineering research. This will be used for formulating a research approach tailored for systems engineering.
Leveraging tradeoff, bridging the gap among disciplines
Authors: Caron Françoise
Published: September 2016

The systems analysis process builds on decisions rooted in results from quantitative tradeoff studies. A consensus on its activities is widely shared and documented by norms and handbooks: ISO/IEC/IEEE 15288:2015, INCOSE Systems engineering handbook.2015 and NASA handbook.2007. Nonetheless, the development of methodologies supporting traceability between the systems analysis process and the other systems engineering processes is still an open area of research, especially within the framework of model‐based approaches. As a result, documents justifying architecture choices are still produced by consolidating data manually; and what is more, data evolution is also verified manually. Such time‐consuming tasks have no real added value but are potential sources of error. Tooling the capitalization of the tradeoff data—including the rationales based on parameter values and their evolutions from project milestone to project milestone—would significantly facilitate the production and integrity of the documentation of architecture justification. This article reports on the results of our research in this direction.
Engineering Experience‐Driven, Solution‐Dependent Logistics Support Stakeholder Requirements for new Members in a Federation of Systems
Authors: Sols Alberto
Published: September 2016

Federations of systems are ubiquitous. Many organizations use families of systems of similar nature, which do not have any interaction with each other, but that are somehow related in purpose or functionality and are used collectively. Such a family is known as a federation of systems (FoS). Federations of systems show an inflow and outflow of members and allow users to gather substantial experience. This permits a special approach to the engineering of requirements for new members, which are to join an FoS. Stakeholder requirements are to be solution‐independent. Yet, an FoS presents an outstanding possibility to users for benefiting from the gathered experience and from the existing logistics support resources of the members of the family, to state the requirements for new members of the family such that the overall logistics support structure of the FoS and its associated costs are minimized. This paper shows the logistics support elements for which requirements can be written, based on gathered experience. Numerous cases are mentioned in which such approach lead to a significant improvement of the overall cost/effectiveness ratio, optimizing the effectiveness of the use of the logistics support resources, while minimizing associated costs, logistics footprint and response time.
Comparison of global cerebral blood flow measured by phase‐contrast mapping MRI with 15O‐H2O positron emission tomography
Authors: Vestergaard Mark Bitsch , Lindberg Ulrich , Aachmann‐Andersen Niels Jacob , Lisbjerg Kristian , Christensen Søren Just , Rasmussen Peter , Olsen Niels Vidiendal , Law Ian , Larsson Henrik Bo Wiberg , Henriksen Otto Mølby
Published: September 2016

Purpose

To compare mean global cerebral blood flow (CBF) measured by phase‐contrast mapping magnetic resonance imaging (PCM MRI) and by 15O‐H2O positron emission tomography (PET) in healthy subjects. PCM MRI is increasingly being used to measure mean global CBF, but has not been validated in vivo against an accepted reference technique.

Materials and Methods

Same‐day measurements of CBF by 15O‐H2O PET and subsequently by PCM MRI were performed on 22 healthy young male volunteers. Global CBF by PET was determined by applying a one‐tissue compartment model with measurement of the arterial input function. Flow was measured in the internal carotid and vertebral arteries by a noncardiac triggered PCM MRI sequence at 3T. The measured flow was normalized to total brain weight determined from a volume‐segmented 3D T1‐weighted anatomical MR‐scan.

Results

Mean CBF was 34.9 ± 3.4 mL/100 g/min measured by 15O‐H2O PET and 57.0 ± 6.8 mL/100 g/min measured by PCM MRI. The measurements were highly correlated (P = 0.0008, R2 = 0.44), although values obtained by PCM MRI were higher compared to 15O‐H2O PET (absolute and relative differences were 22.0 ± 5.2 mL/100 g/min and 63.4 ± 14.8%, respectively).

Conclusion

This study confirms the use of PCM MRI for quantification of global CBF, but also that PCM MRI systematically yields higher values relative to 15O‐H2O PET, probably related to methodological bias.

Level of Evidence: 3

J. Magn. Reson. Imaging 2017;45:692–699.
Effect of normal aging on the structure of marginal division of neostriatum as measured by MR phase imaging and diffusion tensor imaging
Authors: Chen Zhiye , Liu Mengqi , Liu Mengyu , Li Jinfeng , Shan Han , Liu Shuangfeng , Lou Xin , Shu Siyun , Ma Lin
Published: September 2016

Purpose

To investigate the structural changes of marginal division (MrD) which is the high intensity zone between globus pallidus and putamen on phase image in the human brain.

Materials and Methods

The structural changes of MrD were investigated based on MR phase imaging and diffusion tensor imaging (DTI) data at 3.0 Tesla (T) MR scanner in 72 volunteers. Phase value, including high iron components (HIC), low iron components (LIC), LIC ratio, and average iron components (AIC), were obtained using histogram analysis about the head of caudate nucleus (CA), globus pallidus (GP), putamen (PU), and MrD. The structural measurement of MrD was applied on corrected phase images (CPIs). Average apparent diffusion coefficient (ADC) values and fractional anisotropy (FA) values were calculated based on DTI data.

Results

MrD showed negative correlation for LIC with aging, with the highest HIC (left/right 2149.3 ± 19.6/2155.9 ± 17.9) and LIC (left/right 1996.6 ± 18.2/1999.6 ± 20.7), the lowest LIC ratio (left/right 21.5% ± 7.9%/19.4% ± 8.0%), and the highest AIC (left/right 2116.4 ± 21.4/2124.7 ± 21.0). The width (Head: left/right 2.01 ± 0.41 mm/1.86 ± 0.36 mm; Body: left/right 1.84 ± 0.38 mm/1.49 ± 0.29 mm; Tail: left/right 1.17 ± 0.36 mm/1.05 ± 0.23 mm) and area (left/right 49.44 ± 9.71 mm2/42.75 ± 8.80 mm2) of MrD showed negative correlation with aging, presenting gradually narrower pattern based on CPIs. Average ADC value (left/right 0.69 ± 0.04 10‐3mm2/s / 0.71 ± 0.03 10‐3mm2/s) revealed negative correlation, while FA value (left/right 0.19 ± 0.03/0.22 ± 0.03) revealed positive correlation with aging.

Conclusion

The findings suggested that the structure measurements based on CPIs and DTI could provide a simple and effective tool for the evaluation of MrD in vivo in the human brain and for the assessment of the changes seen with aging.

Level of Evidence: 1

J. MAGN. RESON. IMAGING 2017;45:1343–1351
FTIR spectroscopy as a tool to detect contamination of rocket (Eruca sativa and Diplotaxis tenuifolia) salad with common groundsel (Senecio vulgaris) leaves
Authors: Kokalj Meta , Prikeržnik Marcel , Kreft Samo
Published: September 2016

BACKGROUND

Rocket is a popular salad vegetable used all over the world and it has many health benefits. However, like with all plant material, there exists a danger of contamination with toxic substances. In the case of rocket, contamination with groundsel has occurred. Groundsel is a common weed in rocket crops, and it contains very toxic pyrrolizidine alkaloids. In our study infrared spectroscopy was used to distinguish groundsel samples from rocket leaves. Infrared spectroscopy is a very simple analytical technique; however, some specific conditions are more easily implemented in industrial environment than others. Some of these conditions and parameters of infrared spectroscopy were explored in detail.

RESULTS

We tested for the influence of different parameters of attenuated total reflectance and transmission infrared method. Our results show that a 100 % correct classification can be obtained under conditions most suitable for industry: using fresh samples and parameters that enable fast spectral measurement.

CONCLUSION

Infrared spectroscopy is a fast and easy‐to‐use method that has been shown to be able to differentiate between rocket and groundsel leaves. Therefore, it could be further studied for implementation in the safety control of rocket salads. © 2016 Society of Chemical Industry