Adaptive inverse control for helicopter vibration reduction

The reduction or alleviation of helicopter vibration will reduce maintenance requirements while at the same time increase ride quality and helicopter reliability. In forward flight, the helicopter's fuselage vibration spectrum tends to be dominated by multiples of the N/REV component. A way to use the method of adaptive inverse control to identify, in real-time, a controller capable of generating N/REV vibration of opposite phase to cancel the uncontrolled N/REV component is presented. Multicyclic feathering of blade pitch is the control considered

Closing the Certification Gaps in Adaptive Flight Control Software

Over the last five decades, extensive research has been performed to design and develop adaptive control systems for aerospace systems and other applications where the capability to change controller behavior at different operating conditions is highly desirable. Although adaptive flight control has been partially implemented through the use of gain-scheduled control, truly adaptive control systems using learning algorithms and on-line system identification methods have not seen commercial deployment. The reason is that the certification process for adaptive flight control software for use in national air space has not yet been decided. The purpose of this paper is to examine the gaps between the state-of-the-art methodologies used to certify conventional (i.e., non-adaptive) flight control system software and what will likely to be needed to satisfy FAA airworthiness requirements. These gaps include the lack of a certification plan or process guide, the need to develop verification and validation tools and methodologies to analyze adaptive controller stability and convergence, as well as the development of metrics to evaluate adaptive controller performance at off-nominal flight conditions. This paper presents the major certification gap areas, a description of the current state of the verification methodologies, and what further research efforts will likely be needed to close the gaps remaining in current certification practices. It is envisioned that closing the gap will require certain advances in simulation methods, comprehensive methods to determine learning algorithm stability and convergence rates, the development of performance metrics for adaptive controllers, the application of formal software assurance methods, the application of on-line software monitoring tools for adaptive controller health assessment, and the development of a certification case for adaptive system safety of flight

Certification of Safety-Critical Software Under DO-178C and DO-278A

The RTCA has recently released DO-178C and DO-278A as new certification guidance for the production of airborne and ground-based air traffic management software, respectively. Additionally, RTCA special committee SC-205 has also produced, at the same time, five other companion documents. These documents are RTCA DO-248C, DO-330, DO-331, DO- 332, and DO-333. These supplements address frequently asked questions about software certification, provide guidance on tool qualification requirements, and illustrate the modifications recommended to DO-178C when using model-based software design, object oriented programming, and formal methods. The objective of this paper is to first explain the relationship of DO-178C to the former DO-178B in order to give those familiar with DO- 178B an indication of what has been changed and what has not been changed. With this background, the relationship of DO-178C and DO-278 to the new DO-278A document for ground-based software development is shown. Last, an overview of the new guidance contained in the tool qualification document and the three new supplements to DO-178C and DO-278A is presented. For those unfamiliar with DO-178B, this paper serves to provide an entry point to this new certification guidance for airborne and ground-based CNS/ATM software certification

Survey of Verification and Validation Techniques for Small Satellite Software Development

The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation

Small-Satellite Mission Failure Rates

The purpose of this report is to determine the failure rate of small-satellite missions launched between the years 2000 and 2016. This analysis considers the rates of both partial and total mission failure, as well as the failures attributable to failure of the launch vehicle. This study observed that between the years of 2000 to 2016, 41.3% of all small satellites launched failed or partially failed. Of these small satellite missions, 24.2% were total mission failures, another 11% were partial mission failures, and 6.1% were launch vehicle failures. The small satellite failure data reveals an increase in the failure rate as the yearly launch rate has increased. The period 2000 to 2008 averaged 15 launches per year, during which 28.6% of the small satellite missions failed or partially failed. The period from 2009 to 2016 averaged 48 launches per year, during which 42.6% of the small satellite missions failed or partially failed. The launch vehicle failure rate for both periods was the same at around 6.1%. The implication is that for modern small satellite missions, almost one out of every two small satellite missions will result in either a total or a partial mission failure. Counting the partial mission successes as successful missions reduces the failure rate, but only to 38.2% for the period 2009 to 2016

The costs of accessible quality assured syphilis diagnostics: informing quality systems for rapid syphilis tests in a Tanzanian setting.

OBJECTIVES: To determine the costs of Rapid Syphilis Test (RSTs) as compared with rapid plasma reagin (RPR) when implemented in a Tanzanian setting, and to determine the relative impact of a quality assurance (QA) system on the cost of RST implementation. METHODS: The incremental costs for RPR and RST screening programmes in existing antenatal care settings in Geita District, Tanzania were collected for 9 months in subsequent years from nine health facilities that varied in size, remoteness and scope of antenatal services. The costs per woman tested and treated were estimated for each facility. A sensitivity analysis was constructed to determine the impact of parameter and model uncertainty. FINDINGS: In surveyed facilities, a total of 6362 women were tested with RSTs compared with 224 tested with RPR. The range of unit costs was $1.76-$3.13 per woman screened and $12.88-$32.67 per woman treated. Unit costs for the QA system came to $0.51 per woman tested, of which 50% were attributed to salaries and transport for project personnel. CONCLUSIONS: Our results suggest that rapid syphilis diagnostics are very inexpensive in this setting and can overcome some critical barriers to ensuring universal access to syphilis testing and treatment. The additional costs for implementation of a quality system were found to be relatively small, and could be reduced through alterations to the programme design. Given the potential for a quality system to improve quality of diagnosis and care, we recommend that QA activities be incorporated into RST roll-out

Electronic prescribing - how does it affect the ward pharmacist?

It is likely that electronic prescribing will be a common feature in tomorrow’s hospitals. However, we do not yet know how its introduction will affect the practice of hospital pharmacists. We are evaluating a closed-loop electronic prescribing, automated dispensing, bar-coded administration system (ServeRx) on one surgical ward. As part of this evaluation, we wanted to explore its impact on the ward pharmacist. Our objectives were to assess the impact of ServeRx on the time spent providing a ward pharmacy service, and on the activities undertaken

Design and performance of a multicentre, randomized controlled trial of teleconsulting.

We have designed and performed a multicentre, randomized controlled trial of teleconsulting. The trial investigated the effectiveness and cost implications in rural and inner-city settings of using videoconferencing as an alternative to general practitioner referral to a hospital specialist. The participating general practitioners referred a total of 3170 patients who satisfied the entry criteria. Of these, 1040 (33%) failed to provide consent or otherwise refused to participate in the trial. Of the patients recruited to the trial, a total of 1902 (91%) completed and returned the baseline questionnaire. Although the trial was successful in recruiting sufficient patients and in obtaining high questionnaire response rates, the findings will require careful interpretation to take account of the limits which the protocol placed on the ability of general practitioners to select patients for referral