Search Results

In this work we present a new procedure for customizing, in the desired format, requirements reports generated by a Requirements Engineering Environment. This environment includes tools for: 1- capturing textual and pictoric requirements; 2- templating requirements documents that can be adjustable to the formats required by the certification authorities or system engineering groups; 3- translating features from/to the main word processors used in the industry (Word, Excel, etc. formats); 4- managing requirements configuration. It provides gains of productivity, correctness, reusability, traceability, coverage, etc, improving the efficiency of the projects. The procedure emphasizes items 2 and 3, and is illustrated with some examples driven from the aerospace industry.

In this work we discuss some types of simulation architectures and standards, their characteristics and applications to the simulation and control of aerospace vehicles. This includes: the basic definitions, types and characteristics of simulators and simulations (physical, computational, hybrid, etc.; discrete events, discrete time, continuous time, etc; deterministic, stochastic, etc.) their basic compromise (simplicity x fidelity), their man-machine interfaces and interactions (virtual, constructive, live, etc.), their evolution law (time, events, mixed, etc.), their architectures (“stand-alone”, PIL, HIL, MIL, DIS, HLA, etc.), their standards (OMBA, SIMNET, ALSP, DIS, HLA 1.3, HLA 1516, ASIA, AP2633, etc.) and their applications to the simulation and control of aerospace vehicles. This is illustrated by some examples driven from the aerospace industry

Nowadays, given the shrinking budgets and deadlines of the aerospace and automotive industries, the importance and need of the requirements engineering is becoming more and more evident. This means that progressively more users face a difficult task on the different environments of project development: 1) to write better requirements; and 2) to do it faster than ever. It would be nice if they had some tools to help them and abbreviate such a difficult task. This work summarizes the development of a new tool that does exactly that. Its wizard guides the user through the steps necessary to create good requirements when writting a requirements document, depending on the kind of requirements document desired. For example: there are significant differences between user requirements and system requirements documents. The wizard script is composed by a serie of questions related to the parts of the scheme to build a complete and effective requirement.

This paper presents the preliminary results of an "a posteriori" exercise of application of a Requirements Traceability Automation Tool (RT tool) to a set of documents. The documents have been prepared according to established Space System Engineering methodologies and with attention to text quality, but without attention to requirements traceability because the processes and methodologies used during their preparation predates the emergence of the processes and methodologies developed by Requirements Engineering (RE). This study is intended to determine some of the benefits of using a RT tool when compared with the previously used processes and methodologies. The set of documents under scrutiny have been prepared in the frame of the development of the CBERS-3 satellite (China-Brazil Earth Resources Satellite) and is composed of system, subsystem and equipment specification and covering documents related to the Electrical Power Subsystem (EPS) of the satellite.

On several engineering applications high Reliability is one of the most wanted features. The aspects of Reliability play a key role in design projects of aircraft, spacecraft, automotive, medical, bank systems, and so, avoiding loss of life, property, or costly recalls. The highly reliable systems are designed to work continuously, even upon external threats and internal Failures. Very convenient is the fact that the term 'Failure' may have its meaning tailored to the context of interesting, as its general definition refers to it as "any deviation from the specified behavior of a system". The above-mentioned 'deviation' may refer to: performance degradation, operational misbehavior, deviation of environmental qualification levels, Safety hazards, etc. Nevertheless, Reliability is not the only requirement for a modern system. Other features as Availability, Integrity, Security and Safety are always part of the same technical specification, in a same level of importance.

In this work we discuss some types of simulators and simulations, their characteristics and applications to the simulation and control of aerospace vehicles. This includes: the basic definitions, types and characteristics of simulators and simulations (physical, computational, hybrid, etc.; discrete events, discrete time, continuous time, etc; deterministic, stochastic, etc.) their basic compromise (simplicity × fidelity), their man-machine interfaces and interactions (virtual, constructive, live, etc.), their evolution law (time, events, mixed, etc.), their architectures (“standalone”, PIL, HIL, MIL, DIS, HLA, etc.), their environments (discrete, continuous, hybrid, etc.) and their applications to the simulation and control of aerospace vehicles. This is illustrated by some examples driven from the aerospace industry

Cyber-physical systems are joint instances of growing complexity and high integration of elements in the information and physical domains reaching high levels of difficulty to engineer an operate them. This happens with satellites, aircraft, automobiles, smart grids and others. Current technologies as computation, communication and control integrate those domains to communicate, synchronize and operate together. However, the integration of different domains brings new challenges and adds new issues, mainly in real time distributed control systems, beginning with time synchronization. In this paper, we present a discussion on time synchronization and their effects in distributed cyber-physical control systems. To do that, we review the literature, discuss some time synchronization techniques used in cyber-physical systems, and illustrate them via model and simulation of a system representative of the aerospace area.

Switching controls are those that can switch between control or plant modes to perform their functions. They have the advantage of being simpler to design than an equivalent control system with a single mode. However, the transients between those modes can introduce steps or overshootings in the state variables, and this can degrade the performance or even damage the control or the plant. So, the smoothing of such transients is vital for their reliability and mantainability. This is can be of extreme importance in the aerospace and automotive fields, plenty of switchings between manual and autopilot modes via relays, or among gears via clutches, for example. In this work, we present a first strategy for smoothing transients in switching controls of aerospace and automotive systems.

In this work we discuss current trends driving the aerospace and automotive systems architectures. This includes trends as: 1) pos-globalization and regionalization; 2) the formation of knowledge oligopolies; 3) commonality, standardization and even synergy (of components, tools, development process, certification agents, standards); 4) reuse and scalability; 5) synergy of knowledge and tools convergence; 6) time, cost and quality pressures and innovation speed; 7) environmental and safety issues; and 8) abundance of new technologies versus scarcity of skilled manpower to apply them.

Many control systems switch between control modes according to necessity. That is often simpler than designing a full control to all situations. However, this creates new problems, as determining the composed system stability and the transient during switching. The latter, while temporary, may introduce overshooting that degrade performance and damage the plant. This is particularly true for the MultiMission Platform (MMP), a generic service module currently under design at INPE. Its control system can be switched among nine main Modes of Operation and other submodes, according to ground command or information coming from the control system, mainly alarms. It can acquire one and three axis stabilization in generic attitudes, with actuators including magnetotorquers, thrusters and reaction wheels.

Systems are becoming increasingly more complex. To follow this increasingly complexity, systems engineering must evolve rapidly with the introduction of new methodologies, processes, tools, etc. Due to this rapid evolution, little attention is dedicated to the study of the history of its evolution. Currently there is the initiative of installation of a chapter of INCOSE (International Council on Systems Engineering) in Brazil and from this initiative emerged the interest of recovering the history of systems engineering in the country. There are indications that the introduction of systems engineering into Brazil occurred in the late 1960's, directly from NASA and that its first applications in Brazil were in Space Systems Engineering. This paper recovers the origins of systems engineering, of its introduction into Brazil, and of its use in space systems engineering.

Current systems such as satellites, aircrafts, automobiles, turbines, wind power generators and traffic controls are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754 Standard. Such systems frequently require accurate generation, distribution and time or phase synchronization of signals with different frequencies that may be based on one reference signal and frequency. But the environment fluctuations or the non-linear dynamics of these operations cause uncertainties (skew and jitter) in the phase or time of the reference signal and its derived signals. So, techniques to reduce those causes or their effects are becoming important aspects to consider in the design of such systems. The PLL techniques are useful for establishing coherent phase or time references, jitter reduction, skew suppression, frequency synthesis, and clock recovery in numerous systems such as communication, wireless systems, digital circuits, rotors, and others.

In this work, the problem of fault detection, isolation, and reconfiguration (FDIR) for Networked-Control Systems (NCS) of aerospace vehicles is discussed. The concept of fault-tolerance is introduced from a generic structure, and a review on quantitative and qualitative methods (state estimation, parameter estimation, parity space, statistic testing, neural networks, etc.) for FDIR is then performed. Afterwards, the use of networks as loop-closing elements is introduced, followed by a discussion on advantages (flexibility, energy demand, etc.) and challenges (networks effects on performance, closed-loop fault-effects on safety, etc.) represented thereby. Finally, examples of applications on aerospace vehicles illustrate the importance of the discussion herein exposed.

Complex and/or highly integrated systems require the evaluation of Dependability (Reliability, Maintainability, Availability, etc.) throughout their life cycle. The designs of these systems have three main sets of activities: managerial, technical and quality. The recent literature suggests that: 1) the growth of the committed project cost is much greater than the cost spent in the initial stages; and also, the cost to eliminate the defects is smaller in the initial stages of project; and 2) the functions, responsibilities, and authorities of Project Management and Systems Engineering are strongly coupled. Thus, based on the recent literature and the INPE´s (National Institute for Space Research) experience, this paper will show a discussion on the interaction between Project Management and Systems Engineering to improve the Dependability of space and automotive projects.

Internet of Things (IoT) for real-time applications are demanding more and more high performance, precision, accuracy, modularity, integration, dependability and other attributes in a complex and/or highly integrated environment. Such systems need to provide coordination among the integrated components (e.g. sensors, computer, controller and networks) for enabling the application to take real-time measurements and to translate into controllable, observable and smart actions with strict timing requirements. Therefore, coordination and synchronization are required to ensure the controllable, observable and smart actions of real-time IoT systems. This paper shows the design issues about the coordination and synchronization in the internet of things applied to real-time applications. We also show the current coordination and synchronization techniques and their design issues when applied to IoT systems.

Current systems such as satellites, aircrafts, automobiles, turbines, power controls and traffic controls are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754a Standard. Such systems operate in a real time distributed environment which frequently requires a common knowledge of time among different devices, levels and granularities. So, temporal correctness is mostly needed, besides logical correctness. It can be achieved by hardware clocks and devices, software clocks and algorithms, or both, to avoid or tolerate, within appropriate margins, the time faults or failures that may occur in aerospace and automotive systems. This paper presents an overview of clock synchronization algorithms and their uses in aerospace and automotive systems. It is based on a review of the literature, discussion and comparison of some clock synchronization algorithms with different policies.

The aerospace and automotive electronic systems are getting more complex and/or highly integrated, as defined by ARP 4754A, making extensive use of microelectronics and digital memories which, in turn, operates in higher frequencies and lower voltages. In addition, the aircraft are flying in higher altitudes, and polar routes are getting more frequent. These factors raise the probability of occurrence of hazardous effects like the Single Event Upsets in their embedded electronic systems. These must be designed in a way to tolerate and assure the immunity to the Single Event Upsets, based upon criteria such as reliability, availability and criticality. This paper proposes an overview of an assurance process of immunity of embedded electronic systems to Single Event Upsets caused by ionizing particles by means of a review of literature and an analysis of standards as ECSS-E-ST-10-1, NASA Single Event Effects Criticality Analysis and IEC TS 62396-1.

Currently, the use of Global Navigation Satellite Systems-GNSS has been widely disseminated for the most different applications, from the aeronautical navigation to the car traffic, being the Global Positioning System-GPS the most used system for such objectives. New applications have presented challenges in terms of the main requirements associated to such systems, namely: precision, reliability, availability, continuity and integrity. It is because proposed solutions, such as satellite or ground-based augmentation systems, depend on signals provided by the GNSS satellite constellation. It constitutes a limitation for using such systems for position and velocity estimations. On other hand, Inertial Navigation Systems-INS, being independent of external signals, have a big potential to be applied on these circumstances; furthermore, they present characteristics that may be considered complementary to the GNSS.

The realization of modern systems subjected to automatic control, such as aircraft, automobiles, satellites, rocket launchers, cargo and military ships, and so forth; increasingly assume, within its very set of requirements, the task of providing better dependability, i.e.: safety, reliability, and availability altogether. Towards this demand, fault-tolerant control greatly meets such growing demand of dependability, by its ability of recognizing the occurrence of potentially hazardous/hazardous faults within the overall (closed-loop) system, and by taking remedial action whenever necessary/mandatory. The process of fault tolerance can be segregated into two fundamental steps: (1) that of fault diagnosis, comprising fault detection-isolation-identification, and, (2) control adjustment/reconfiguration. This paper focuses on the second step, of control adjustment/reconfiguration.

Current systems such as: satellites, aircrafts, automobiles, turbines, power controls and traffic controls are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754 Standard. Such systems and their control systems use many modes of operation and many forms of redundancy to achieve high levels of performance and high levels of reliability under changing environments and phases of their lifecycle. The environment disturbances, environment variability, plant non-linear dynamics, plant wear, plant faults, or the non-symmetric plant operation may cause de-synchronization in phase or time among: 1) simultaneous units in the same normal mode of operation; 2) successive units in successive normal modes of operation; 3) main and spare units from normal to faulty modes of operation. So, techniques to reduce those causes or their effects are becoming important aspects to consider in the design of such systems.