A Four-Way Interaction Model: A Holistic Approach to the Group Decision Support Systems

This study adopts the general systems theory and proposes a four-way interaction model which uses nth logic function to represent interactions of a Group Decision Support System (GDSS) to examine the interaction issues when designing a GDSS. Task type and decision guidance are used to illustrate the application of the proposed model

Development of approach control system requirements with applications to a jet transport

The development of requirements for an approach control system and example applications to a jet transport aircraft are presented. The material is divided into a general discussion of approach control requirements, and a specific application resulting in the design of three alternative longitudinal controllers. The point of view taken is that the essential features of the system structure are the feedbacks themselves, their equalization, and their combinations to create control commands. Use is made of the fact that for sucessful systems the possible feedback structures are very limited. They derive primarily from guidance, control, and regulation demands; and secondarily from dynamic response characteristics desired by the pilot. From the systems view it is the satisfaction of these requirements that is important rather than the means automatic, manual, or hygrid manual/automatic approach systems

Combined automotive safety and security pattern engineering approach

Automotive systems will exhibit increased levels of automation as well as ever tighter integration with other vehicles, traffic infrastructure, and cloud services. From safety perspective, this can be perceived as boon or bane - it greatly increases complexity and uncertainty, but at the same time opens up new opportunities for realizing innovative safety functions. Moreover, cybersecurity becomes important as additional concern because attacks are now much more likely and severe. However, there is a lack of experience with security concerns in context of safety engineering in general and in automotive safety departments in particular. To address this problem, we propose a systematic pattern-based approach that interlinks safety and security patterns and provides guidance with respect to selection and combination of both types of patterns in context of system engineering. A combined safety and security pattern engineering workflow is proposed to provide systematic guidance to support non-expert engineers based on best practices. The application of the approach is shown and demonstrated by an automotive case study and different use case scenarios.EC/H2020/692474/EU/Architecture-driven, Multi-concern and Seamless Assurance and Certification of Cyber-Physical Systems/AMASSEC/H2020/737422/EU/Secure COnnected Trustable Things/SCOTTEC/H2020/732242/EU/Dependability Engineering Innovation for CPS - DEIS/DEISBMBF, 01IS16043, Collaborative Embedded Systems (CrESt

Penerapan Sistem Akuntansi Dasar pada Usaha Kecil Menengah di Kota Banjarmasin

The following research was conducted to gain an overview of the application of accounting systems in small andmedium enterprises engaged in trading business built Jakarta Cooperative Micro Small and Medium Enterprisesin Banjarmasin. The research uses descriptive method with a sample of 60 respondents. With the scale ofcumulative or Guttman scale is known that the application of accounting systems in small and mediumenterprises engaged in trading business built offices Cooperative Banjarmasin city is on a scale of 0,064 or areon the no association or low association (weak association) which shows that the application of the accountingsystem base on small and medium enterprises in the field of trade business Banjarmasin city is still relativelylow. Guidance and cooperation of the parties involved, especially the service cooperatives, small and mediummicro Banjarmasin city, is expected to continue to provide guidance and more intensive training with regard tothe application of the accounting system to a group of small and medium enterprises in general, especially forsmall and medium enterprises engaged in the trading business in the city of Banjarmasin

Анализ основных свойств траекторий и влияния ветра на точность наведения БпЛА при применении разных методов самонаведения

Проведено аналіз спрощених кінематичних рівнянь руху по траєкторії наведення, що враховують вітер. Досліджено аналітичний розв’язок цих рівнянь та проаналізовано основні властивості траєкторій при самонаведенні методом прямого наведення, методом погоні та методом пропорційного наведення. При порівнянні траєкторій наведення аналізується характер зміни таких параметрів руху, як кути орієнтації вектора швидкості – кут нахилу траєкторії та курс, кут атаки, циліндричні і прямокутні координати. Окремо проаналізовано вплив вітру на характер зміни цих параметрів при застосуванні різних методів самонаведення. Показано, що найбільші викривлення траєкторії і промах від дії вітру мають місце при застосуванні методу прямого наведення, в той час як при пропорційному наведенні вплив вітру практично відсутній. Для підтвердження зроблених висновків приведено результати моделювання із застосуванням моделі, яка описана у попередніх роботах авторів.Generally unmanned aerial vehicles (UAV) flight control system may be divided into guidance system and stabilization system. Guidance system function lies in guidance commands forming and providing center of mass motion according to built guidance law. Stabilization system function lies in providing of UAV specified attitude or stable angular motion in order to assure a stable center of mass motion along the guidance trajectory. Today the most general guidance systems classification divides them into four main groups: autonomous systems, homing systems, teleguidance systems and combined guidance systems. These groups are separated by the way and place of guidance signal forming. Homing of UAV is such method of UAV guidance, when guidance commands are produced onboard a UAV by means of energy illuminated by the target or reflected from it. Each guidance method possesses its own advantages and disadvantage which must be considered during UAV design subject to its specification requirements. One of such requirements may be providing of specified accuracy under any weather conditions, including wind availability with given wind velocity. That is why wind effect and trajectory features for various methods of self-guidance are investigated in this article. Three guidance methods are chosen for this analysis: direct homing, pursuit-course guidance and proportional guidance. Within the investigation, simplified kinematic equations of motion along the guidance trajectory, allowing for wind, are analyzed. Analytic solutions of these equations are investigated and main trajectory features are compared for three guidance methods above. During trajectory comparison such motion parameters as velocity vector orientation angles – flight-path angle and course angle, attack angle, cylindrical and rectangular coordinates are considered. Special attention is paid on wind effect on these parameters behavior with application of various homing methods. It is displayed that the greatest trajectory curvature and miss due to wind influence take place on application of direct homing, while on application of proportional homing wind effect is almost absent. To confirm the drawn conclusions, simulation results, obtained by means of described in authors’ previous publications model, are presented.Произведен анализ упрощенных уравнений движения по траектории наведения, которые учитывают ветер. Исследовано аналитическое решение этих уравнений и проанализированы основные свойства траекторий при самонаведении методом прямого наведения, методом погони и методом пропорционального наведения. При сравнении траекторий наведения анализируется характер изменения таких параметров движения, как углы ориентации вектора скорости – угол наклона траектории и курс, угол атаки, цилиндрические и прямоугольные координаты. Отдельно проанализировано влияние ветра на характер изменения этих параметров при применении различных методов самонаведения. Показано, что наибольшие искривления траектории и промах от действия ветра имеют место при применении метода прямого наведения, в то время как при пропорциональном наведении влияние ветра практически отсутствует. Для подтверждения сделанных выводов приведены результаты моделирования с применением модели, описанной в предыдущих работах авторов

Programmable Electronic Mining Systems: Best Practice Recommendations (In Nine Parts) - Part 6: 5.1 System Safety Guidance

This report (System Safety Guidance 5.1) is the sixth in a nine-part series of recommendations and guidance addressing the functional safety of processor-controlled mining equipment. It is part of a risk-based system safety process encompassing hardware, software, humans, and the operating environment for the equipment s life cycle. Figure 1 shows a safety framework containing these recommendations. The reports in this series address the various lifecycle stages of inception, design, approval and certification, commissioning, operation, maintenance, and decommissioning. These recommendations were developed as a joint project between the National Institute for Occupational Safety and Health and the Mine Safety and Health Administration. They are intended for use by mining companies, original equipment manufacturers, and aftermarket suppliers to these mining companies. Users of these reports are expected to consider the set in total during the design cycle. 1.0 Safety Introduction (Part 1). This is an introductory report for the general mining industry. It provides basic system/software safety concepts, discusses the need for mining to address the functional safety of programmable electronics (PE), and includes the benefits of implementing system/software safety program. 2.1 System Safety (Part 2) and 2.2 Software Safety (Part 3). These reports draw heavily from International Electrotechnical Commission (IEC) standard IEC 61508 [IEC 1998a,b,c,d,e,f,g]and other standards. The scope is surface and underground safety-related mining systems employing embedded, networked, and nonnetworked programmable electronics. System safety seeks to design safety into all phases of the entire system. Software is a subsystem; thus, software safety is a part of the system s safety. 3.0 Safety File (Part 4). This report contains the documentation that demonstrates the level of safety built into the system and identifies limitations for the system s use and operation. In essence, it is a proof of safety that the system and its operation meet the appropriate level of safety for the intended application. It starts from the beginning of the design, is maintained during the full life cycle of the system, and provides administrative support for the safety program of the full system. 4.0 Safety Assessment (Part 5). The independent assessment of the safety file is addressed. It establishes consistent methods to determine the completeness and suitability of safety evidence and justifications. This assessment could be conducted by an independent third party. Safety Framework Guidance. It is intended to supplement the safety framework reports with guidance providing users with additional information. The purpose is to assist users in applying the concepts presented. In other words, the safety framework is what needs to be done and the guidance is how it can be done. The guidance information reinforces the concepts, describes various methodologies that can be used, and gives examples and references. It also gives information on the benefits and drawbacks of various methodologies. The guidance reports are not intended to promote a single methodology or to be an exhaustive treatment of the subject material. They provide information and references so that the user can more intelligently choose and implement the appropriate methodologies given the user s application and capabilities. The guidance reports comprise parts 6 through 9 of the series and are listed below: [< 5.1 System Safety Guidance (Part 6). This guidance supplements 2.1 System Safety. < 5.2 Software Safety Guidance (Part 7). This guidance supplements 2.2 Software Safety. < 6.0 Safety File Guidance (Part 8). This guidance supplements 3.0 Safety File. < 7.0 Independent Functional Safety Assessment Guidance (Part 9). This guidance supplements 4.0 Independent Functional Safety Assessment.] [

Programmable Electronic Mining Systems: Best Practice Recommendations (In Nine Parts) - Part 9: 7.0 Independent Functional Safety Assessment Guidance

This report (Independent Functional Safety Assessment Guidance 7.0) is the last in a nine-part series of recommendations and guidance addressing the functional safety of processor-controlled mining equipment. It is part of a risk-based system safety process encompassing hardware, software, humans, and the operating environment for the equipment s life cycle. Figure1 shows a safety framework containing these recommendations. The reports in this series address the various life cycle stages of inception, design, approval and certification, commissioning, operation, maintenance, and decommissioning. These recommendations were developed as a joint project between the National Institute for Occupational Safety and Health and the Mine Safety and Health Administration. They are intended for use by mining companies, original equipment manufacturers, and after-market suppliers to these mining companies. Users of these reports are expected to consider the set in total during the design cycle. 1.0 Safety Introduction (Part 1). This is an introductory report for the general mining industry. It provides basic system/software safety concepts, discusses the need for mining to address the functional safety of programmable electronics (PE), and includes the benefits of implementing a system/software safety program. 2.1 System Safety (Part 2) and 2.2 Software Safety (Part 3). These reports draw heavily from International Electrotechnical Commission (IEC) standard IEC 61508 [IEC 1998a,b,c,d,e,f,g]and other standards. The scope is surface and underground safety-related mining systems employing embedded, networked, and nonnetworked programmable electronics. System safety seeks to design safety into all phases of the entire system. Software is a subsystem; thus, software safety is a part of the system s safety. 3.0 Safety File (Part 4). This report contains the documentation that demonstrates the level of safety built into the system and identifies limitations for the system s use and operation. In essence, it is a proof of safety that the system and its operation meet the appropriate level of safety for the intended application. It starts from the beginning of the design, is maintained during the full life cycle of the system, and provides administrative support for the safety program of the full system. 4.0 Safety Assessment (Part 5). The independent assessment of the safety file is addressed. It establishes consistent methods to determine the completeness and suitability of safety evidence and justifications. This assessment could be conducted by an independent third party. Safety Framework Guidance. It is intended to supplement the safety framework reports with guidance providing users with additional information. The purpose is to assist users in applying the concepts presented. In other words, the safety framework is what needs to be done and the guidance is how it can be done. The guidance information reinforces the concepts, describes various methodologies that can be used, and gives examples and references. It also gives information on the benefits and drawbacks of various methodologies. The guidance reports are not intended to promote a single methodology or to be an exhaustive treatment of the subject material. They provide information and references so that the user can more intelligently choose and implement the appropriate methodologies given the user s application and capabilities. The guidance reports comprise parts 6 through 9 of the series and are listed below: [< 5.1 System Safety Guidance (Part 6). This guidance supplements 2.1 System Safety. < 5.2 Software Safety Guidance (Part 7). This guidance supplements 2.2 Software Safety. < 6.0 Safety File Guidance (Part 8). This guidance supplements 3.0 Safety File. < 7.0 Independent Functional Safety Assessment Guidance (Part 9). This guidance supplements 4.0 Independent Functional Safety Assessment.] [

Programmable Electronic Mining Systems: Best Practice Recommendations (In Nine Parts) - Part 8: 6.0 Safety File Guidance

This report (Safety File Guidance 6.0) is the eighth in a nine-part series of recommendations and guidance addressing the functional safety of processor-controlled mining equipment. It is part of a risk-based system safety process encompassing hardware, software, humans, and the operating environment for the equipment s life cycle. Figure 1 shows a safety framework containing these recommendations. The reports in this series address the various life cycle stages of inception, design, approval and certification, commissioning, operation, maintenance, and decommissioning. These recommendations were developed as a joint project between the National Institute for Occupational Safety and Health and the Mine Safety and Health Administration. They are intended for use by mining companies, original equipment manufacturers, and aftermarket suppliers to these mining companies. Users of these reports are expected to consider the set in total during the design cycle. 1.0 Safety Introduction (Part 1). This is an introductory report for the general mining industry. It provides basic system/software safety concepts, discusses the need for mining to address the functional safety of programmable electronics (PE), and includes the benefits of implementing a system/software safety program. 2.1 System Safety (Part 2) and 2.2 Software Safety (Part 3). These reports draw heavily from International Electrotechnical Commission (IEC) standard IEC 61508 [IEC 1998a,b,c,d,e,f,g]and other standards. The scope is surface and underground safety-related mining systems employing embedded, networked, and nonnetworked programmable electronics. System safety seeks to design safety into all phases of the entire system. Software is a subsystem; thus, software safety is a part of the system s safety. 3.0 Safety File (Part 4). This report contains the documentation that demonstrates the level of safety built into the system and identifies limitations for the system s use and operation. In essence, it is a proof of safety that the system and its operation meet the appropriate level of safety for the intended application. It starts from the beginning of the design, is maintained during the full life cycle of the system, and provides administrative support for the safety program of the full system. 4.0 Safety Assessment (Part 5). The independent assessment of the safety file is addressed. It establishes consistent methods to determine the completeness and suitability of safety evidence and justifications. This assessment could be conducted by an independent third party. Safety Framework Guidance. It is intended to supplement the safety framework reports with guidance providing users with additional information. The purpose is to assist users in applying the concepts presented. In other words, the safety framework is what needs to be done and the guidance is how it can be done. The guidance information reinforces the concepts, describes various methodologies that can be used, and gives examples and references. It also gives information on the benefits and drawbacks of various methodologies. The guidance reports are not intended to promote a single methodology or to be an exhaustive treatment of the subject material. They provide information and references so that the user can more intelligently choose and implement the appropriate methodologies given the user s application and capabilities. The guidance reports comprise parts 6 through 9 of the series and are listed below: [5.1System Safety Guidance (Part 6). This guidance supplements 2.1 System Safety. < 5.2 Software Safety Guidance (Part 7). This guidance supplements 2.2 Software Safety. < 6.0 Safety File Guidance (Part 8). This guidance supplements 3.0 Safety File. < 7.0 Independent Functional Safety Assessment Guidance (Part 9). This guidance supplements 4.0 Independent Functional Safety Assessment.] [

Human Factors Flight Testing of an ADS-B Based Traffic Alerting System for General Aviation

Mid-air collisions are a concern for general aviation. Current traffic alerting systems have limited usability in the airport environment where a majority of mid-air collisions occur. A Traffic Situation Awareness with Alerting Application (TSAA) has been developed which uses Automatic Dependent Surveillance – Broadcast (ADS-B), a Global Positioning System (GPS) based surveillance system, to provide reliable alerts in a condensed environment. TSAA was designed to be compatible with general aviation operations. It was specifically designed to enhance traffic situation awareness and provide traffic alerting. The system does not include guidance or resolution advisories. In addition, the design was consistent with established standards, previous traffic alerting system precedents, as well as air traffic control precedent. Taking into account the potential financial burden associated with installation of a multi-function display (MFD), an audio based TSAA system was also designed to account for constrained cockpit space and the added cost of a MFD.This project was funded by the U.S. Department of Transportation - Federal Aviation Administration through the University of Maryland (NEXTOR II) Contract #Z988401