bluuebunny/crossref_metadata_2025_split huggingface dataset:
2 Cost effectiveness of formal methods in the development of avionics systems at AEROSPATIALE
Authors: PILARSKI François 
Published: November 2014

AbstractAEROSPATIALE has been using formal methods since the early 80's to develop part of the embedded systems, and more specifically most of the avionics systems. During the last two decades, such an approach has demonstrated significant cost savings. This paper presents some aspects of this approach and focuses more precisely on the way it has helped in reducing embedded system development and maintenance costs.This first section of this paper is devoted to a general description of the overall context and it gives some elements of history.The second section summarizes the benefits AEROSPATIALE has found in using SAO first, and now SCADE, and constitutes an attempt to synthesize the properties and characteristics that make a formal method efficient (at AEROSPATIALE).The third section summarizes some aspects of formal methods, which have not been extensively used yet but which are likely to induce extra cost reduction, namely proof techniques.
1 Collaborative Methods Applied to the Development And Certification of Complex Aircraft Systems
Authors: Langton Roy , O'Connor Steve , Jones George , DiBella Paul 
Published: November 2014

AbstractDescribed are new methods of procurement, development and certification for complex aircraft systems and how these new methods have evolved over the past 15 years.The traditional methods of system design and equipment procurement that were used in the 1980's by aircraft manufacturers and that had been in place for decades, have undergone major changes following the aerospace recession of the late 80's and early 90's. Almost all of today's primes are procuring equipment at the system level and are requiring a more direct involvement by the supplier community in the design, development, integration, testing and certification of the aircraft as part of the system procurement contract. Furthermore, suppliers are being made accountable for the performance of the system in the field in terms of maintenance cost, equipment removal rates, and dispatchability.This paper describes the evolution process and some of the different approaches used by the prime community in the procurement of major aircraft systems. Comparisons are made using specific examples of fuel system procurement adopted by different aircraft manufacturers.Issues and benefits of these new methodologies are discussed and opportunities for improvements for the future are suggested.
3 Developing a Simulator for the Aerospace Extended Enterprise Product Introduction Process
Authors: Mason‐Jones Rachel , Wingrove Stuart , Naim Mohamed , Alexander Ian 
Published: November 2014

ABSTRACTIndustries are keenly aware of the importance of speedy response in ensuring market share not only in the Product Delivery Process but also in the Product Introduction Process (PIP). Even those industries with traditionally long PIP's recognise the need to drive down time to market launch of new products in order to remain competitive. One such industry is aerospace which not only has a very competitive environment but also traditionally long PIP lead‐times. The sheer number of components, and hence companies, involved within the aerospace supply chain adds to complexity of the PIP and subsequent initiative to improve performance. While there is a recognised need to drive down current PIP lead‐times due to the time spans involved there is an increased risk when experimenting with new initiatives and approaches. It is in situations such as these where a business game can be an important supply chain redesign tool. So companies are free to experiment with a variety of new strategies while limiting online risks.This paper addresses the issue of business games as a media for raising awareness of the systems approach in Supply Chain Management and their subsequent use as design tools for Supply Chain strategies. The paper specifically focuses on the development of a Management Fight Simulator of an aerospace Product Introduction Process within an Extended Enterprise.
2 Lessons Learned in Transitioning to EIA/IS 731 from INCOSE SECAM
Authors: Barber Don E. 
Published: November 2014

AbstractIn 1995, Honeywell's Air Transport Systems division began using the INCOSE Systems Engineering Capability Assessment Model (SECAM) as a tool for facilitating Systems Engineering process improvement. The Key Focus Areas of the SECAM were used as a template for organizing the division's standard Systems Engineering process and Systems Engineering Capability Assessments were conducted to measure the completeness and effectiveness of this process. In 1998, the Electronic Industry Alliance released EIA/IS 731, the Systems Engineering Capability Model (SECM). Honeywell made the decision to transition to this new standard and conducted a Systems Engineering Capability Assessment using EIA/IS 731. This paper describes the similarities and differences between the two models from the perspective of the user, as well as, the lessons learned in executing the transition.
3 CMMI and Systems Engineering
Authors: Clouse Aaron , Schoening William W. , Graffius Joseph , Wells Curt 
Published: November 2014

AbstractIn late 1999 the systems engineering community will be presented with a new process maturity model produced by the Capability Maturity Model Integration (CMMI) project. The immediate significance to systems engineers is that the new model offers, for the first time, strong integration and consistency with the Software CMM (SW‐CMM v2). Organizations can choose to use one or more of several highly integrated models – a Systems Engineering CMM, a Software CMM and a Systems + Software CMM.Organizations can further choose to use a continuous or a staged version of each model and be assured of equivalent content. This paper describes the relationship of the new CMMI models to the recently completed EIA/IS 731, Systems Engineering Capability Model, and the potential impacts to systems engineering process appraisal and improvement. An overview of the CMMI models and terminology is provided as a basis for describing the relation to the EIA/IS 731
2 Introducing and Maintaining Systems Engineering in a Medium Sized Company
Authors: Hamann Robbert J. , van Leeuwen Wim 
Published: November 2014

AbstractThis paper describes the introduction of Systems Engineering at a medium sized company and the organisation set up to maintain this capability afterwards. The paper explains the context leading to the introduction and describes the steps taken to formally introduce Systems Engineering. It shows the relation between the organisation of the company and the way elements of the Systems Engineering process are formalised. The paper stresses the necessity that any change in the engineering practices should be shown to fit into the engineering process that is in place and to improve it, and needs a firm backing from senior engineers to be applied. Also, continuous training and review is necessary to keep application of the processes alive.
1 RAMSAAT – Systems Engineering Modeling and Simulation Aid
Authors: Newland Ronald K. , Conroy Joseph L. 
Published: November 2014

AbstractRAMSAAT (Rapid Airspace Management Siting and Analysis Tool) is a systems engineering design and analysis tool for air space management systems (AMS). It provides a highly mobile, laptop based means for AMS Systems Engineers to work with customers (acquirers) to evolve system specific requirements and characteristics. The Systems Engineer can work with any customer and Program Managers to geographically site the AMS system per customer description. This enables analysis of the customers up front requirements for the sensors and associated communications. Within this paper insight is provided into the use of RAMSAAT to enhance the engineering process in regards to requirements analysis and validation. It is also shown how RAMSAAT assists with meeting the standards for requirements definition as outlined in EIA 632, “Process for Engineering a System”.
3 Team Efficiencies Within a Model‐Driven Design Process
Authors: Koenig Lynda J. , Smith David B. , Wall Stephen D. 
Published: November 2014

Abstract(Smith & Koenig 1998) formulated a model‐based design process describing a triad of people, process, and technology (PPT) within an aerospace culture. It suggested that the time required for an organization to change to a new approach is a function of a minimum development time and powerful forces acting in tension (Lewin 1951).(Wall et al. 1999) described the object model‐based system, addressed the team dynamics involved in developing the products of the process, and proposed metrics to assess productivity of each team.This paper examines the PPT triad at the lowest level, the minimum product cycle time. It shows that team interventions, above and beyond team productivity considerations, can produce even lower product cycle times.A model shows the effect of the three components of the triad acting together. The lower cycle times possible are a product of team effects and technology advances in producing an individual object.
2 System Issues Related to Implementing on the Internet
Authors: Mackey William , Bagg Thomas C. 
Published: November 2014

ABSTRACTImplementing capabilities on the World Wide Web should never be taken lightly. A good systems engineer is able to examine such implementations from all points of view, including political, legal, security, access, technical deployment, and quality.The evaluation discussed in this paper was conducted to ensure that the National Aeronautics and Space Administration (NASA) was proceeding in a correct direction by implementing RECALL a Lessons Learned System on the Web and, subsequently, did so successfully. The systems approach extended well beyond technical implementation to several issues that are not often addressed by an implementation team. The resulting evaluation increased the team's sensitivity to such issues and, in fact, the authors believe that the evaluation provided as much benefit as the system itself.
1 Process Assessment Framework – An Integral Part of Safety Assessment
Authors: Burke M. 
Published: November 2014

AbstractThis paper examines the importance of the processes used to produce engineered artifacts for safety critical computing systems.The integration of direct evidence about the system with supporting process related evidence is the basis of all safety cases. The process of assessing the acceptability of such cases is based on Engineering Judgement. Engineering Judgement is inherently conservative and appeals to precedent systems or analogous systems where possible. Faced with genuinely new technology or new uses of existing technology the Engineering Judgement can appear to be totally subjective.This paper examines the underlying approaches taken by Engineers to define exactly what level of risk is “tolerable” in the absence of historical precedent.A general approach is common across a wide range of engineering disciplines. The adaptation of lessons learnt from mature disciplines (e.g. mechanical engineering) to relatively new and immature disciplines (e.g. Computing Systems Engineering) are of particular interest.This paper considers how general engineering principles can be applied to support the integration of Commercial Off The Shelf (COTS) components and systems for modern aerospace related products
3 Software Engineering and Systems Engineering in DoD
Authors: Zettervall Brenda T. 
Published: November 2014

AbstractAs the Department of Defense (DoD) moves toward acquisition without rigid DoD standards, acquisition is becoming less an issue of hardware vs. software or software engineering vs. systems engineering – it is becoming an integrated whole. New DoD directives, an integrated Capability Maturity Model, highly trained acquisition personnel, and a partnership with industry to manage risk will help us meet the challenges of acquisition in the next century.
1 Enterprise‐wide Requirements & Decision Management
Authors: DeGregorio Gary 
Published: November 2014

AbstractDecision‐making is one of the most fundamental processes contributing to a corporation's success, yet in many companies, decisions are often characterized as ad‐hoc events without a clear linkage to supporting information, tradeoff studies, or clearly stated rationale. Furthermore, the “information” used to support these decisions is often in the form of complex, unstructured documents which lack clear linkages between their content. As a result, future decision‐makers are often not able to benefit from the collective experiences of their predecessors. Consequently, there are no cycles of learning and the same mistakes are often repeated each time that a similar decision is made. It is clear that the most successful companies in the future will be those who can effectively manage and leverage the “intellectual capital” generated by the decision making process (the thinking engine of systems engineering) and the linkage of that process to essential supporting information. This paper describes an approach to address the deficiencies in the prevailing methods for requirements and decision management by proposing an enterprise‐wide approach which provides for a true “learning organization” capability in the form of reusable decisions frameworks.
2 Effective Decision Making in the Product Introduction Process: A Supply Chain View
Authors: Naylor Ben , Naim Mohamed 
Published: November 2014

AbstractMany enterprises are currently considering the total supply chain in their product delivery process. If an enterprise is to view the product delivery process as part of a supply chain then it must also consider the product introduction process (PIP). The PIP can account for a considerable proportion of an enterprise's total costs. This paper presents the development of a supply chain view of a steel industry PIP so as to establish a framework for a software based Decision Support System (DSS) via a systems engineering approach. The systems engineering approach is used to ensure optimisation of the whole. The paper shows that there is limited evidence of a framework for considering the PIP from a supply chain perspective using IT or otherwise.
3 A Proven Approach to Requirements Baseline Management
Authors: Kennedy Larry M. , Thomas Donna , Weber Marie D. 
Published: November 2014

ABSTRACTRequirements baseline management can be the single most effective method used to guide system development and test. This paper presents a proven approach to requirements baseline management, requirements traceability, and processes for major system development programs. Effective baseline management can be achieved by providing: effective team leadership to guide and monitor development efforts; efficient processes to define what tasks needs to be done and how to accomplish them; and adequate tools to implement and support selected processes.As in any but the smallest organization, effective engineering leadership is essential to provide a framework within which the rest of the program's engineering staff can function to manage the requirements baseline. Once a leadership team is in place, the next task is to establish processes that cover the scope of establishing and maintaining the requirements baseline. These processes will form the basis for consistent execution across the engineering staff. Finally, given an appropriate leadership model with a forward plan, and a collection of processes that correctly identify what steps to take and how to accomplish them, consideration must be given to selecting a tool set appropriate to the program's needs.
3 The Future Systems Engineering Data Exchange Standard STEP AP‐233: Sharing the results of the SEDRES Project
Authors: Johnson Julian , Loeuillet Jean‐Louis , Inderst Manfred , Nilsson Benny , Torne Anders , Candy Linda , Harris David , Alenia Federica Luise 
Published: November 2014

ABSTRACTSharing design information during the systems engineering activities on large international projects within virtual enterprises faces many challenges, amongst them is working with heterogeneous sets of systems engineering tools. The adoption of neutral data exchange standards is one appropriate approach now well advanced in areas such as structural design (Computer Aided Design or CAD).ESPRIT project 20496, ‘SEDRES’, has made significant progress in producing a neutral data exchange standard based on STEP (ISO‐10303), embracing systems engineering design data. SEDRES stands for Systems Engineering Data Representation and Exchange Standardisation. Co‐funded by the European Commission and running 1996–1999, SEDRES was initiated by Aerospatiale, Alenia, British Aerospace, DASA and Saab. Also contributing are the Universities of Loughborough, Linkoping, and the Australian Centre for Test & Evaluation.This paper reports on the development and prototyping of the Capability/2 data model, on early exchange experiences, and on the related ISO STEP AP‐233 standardisation activity. Two companion papers describe the data model content and data exchange evaluation in detail.
4 The Design, Implementation and Management of A Systems Engineering Database
Authors: Collins Rob , North Lee 
Published: November 2014

AbstractThe work reported in this paper has been completed over the last 18 months on the Bowman project. The Bowman project will encompass the design, development, manufacture, conversion (rollout) and support of the new communications systems for the British Army. The Bowman contract will be valued in excess of £3 Billion and be delivered and installed over a period of 6 years.This paper describes the design, implementation and management of a Systems Engineering Database (SED) for the project. The SED contains all of the Engineering data for the project. Each item of data is maintained with a full audit‐trail of change information. All information is cross‐referenced and controlled against all other dependent information.Replication of data is eliminated and thus consistency and integrity are assured. Metrics collected on the database provide managers with a high degree of visibility of progress.Experience of developing and using the SED is reported and advantages and problem areas are detailed.
1 Information Security Risk Management for Systems Engineers
Authors: Gauvain Tony 
Published: November 2014

AbstractDesigning security in at the start of system definition and design, rather than adding it later, has long been accepted wisdom. Sadly system security has often been found to be deficient, and attempts to add improvements later have often proved to be disastrous.Systems engineers see security as a contribution to a system's value to be managed throughout the system's life‐cycle. Increasingly networked systems produce increased benefit, but also increased risk. Standards such as BS7799 are emerging as a necessary way of promoting trust between networked and inter‐dependent systems.Information Security Risk Management is an essential part of the good health of a system's life‐cycle. Managing Risk requires its measurement. This paper shows how the complexity and urgency of the relationship between Assets, Threats and Vulnerabilities in order to calculate Risk and then determine Safeguards, can only be met by sophisticated computer aided algorithmic software applications.
2 Systems Engineering Applied to Integrated Safety Management for High Consequence Facilities
Authors: Barter Robert H. , Morais Bernard G. 
Published: November 2014

AbstractIntegrated Safety Management is a concept that is being actively promoted by the U.S. Department of Energy as a means of assuring safe operation of its facilities. The concept involves the integration of safety precepts into work planning rather than adjusting for safe operations after work activities have already been defined. The system engineering techniques used to design an integrated safety management system for a high consequence research facility are described. An example is given to show how the system design evolved over time.
1 Creating a Collaborative Systems Engineering Environment: …the need for collaboration in Systems Engineering and the technologies to support it
Authors: Sampson Mark E. 
Published: November 2014

AbstractWe have often heard that everyone on a project needs to be a systems engineer—or at least have a systems perspective. This paper suggests using emerging technologies to capture the complex interrelationships that are the essence of systems engineering and presenting them to the right people at the right time in a context they understand through the web…creating virtual systems engineers in the process.
4 Simulation Based (Systems) Engineering or Collaborative Based Acquisition
Authors: Zittel Randy C. 
Published: November 2014

AbstractSimulation tools have been applied to an increasing range of ongoing product development programs and have significantly reduced development time, life cycle costs and improved system quality. Some improvements have reportedly reduced the overall development time by half and some individual activities by 30 fold as described below.The computer revolution and age of information technology is creating more realistic, more capable and more diversified simulation tools. Because of the opportunities to benefit business processes, the natural market forces are driving all industries to find better ways to couple information technology, and simulation tools are a large part of this evolution. Beyond simply networking more and more computers and software together in ever‐increasing capability, an entirely new approach is emerging where product development and management tools are accessible as needed via internet‐like convenience. This new approach is staggering in its potential to further advance operations and design capabilities; and it's capturing more elements of industry everyday. It has the potential to revolutionize product design all over again.
2 “Simple Simon met a System” – bridging the gap to the rest of the organisation
Authors: Sillitto H.G. 
Published: November 2014

AbstractPilkington Optronics uses many elements of Systems Engineering and product development best practice. The company is now tailoring a very competent, but complex, Systems Engineering methodology to provide a “smart but simple” core method, useable at all levels of our business from complex sensor systems to individual components; and by managers and marketeers as well as engineers.The core method provides a consistent framework for communication between Systems Engineering and the rest of the company. It is compatible with the Thomson “MIST” Systems Engineering methodology, and consistent with both “Systems Engineering” and “world class product development” paradigms. These two paradigms are closely related. A business such as ours operating across the system/technology interface has to be able to operate seamlessly between the two.This paper reviews recent experience, discusses some of the problems encountered, and outlines the approach to a more integrated cross‐project cross‐discipline method.