Proposal to TPS delivery in 4 months?

Decreasing the often lengthy Test Program Set (TPS) development time is a high priority for both DoD and commercial industry. A protracted test development time for a commercial product can make or break its success. It can impact time-to-market goals for a product, which in turn, can result in a loss of market share. Though the DoD world has different objectives, they, too, are concerned with long test development times which can increase costs and jeopardize a weapon system's mission readiness. The case study for this paper is a test system developed by BAE Systems in less than four months to meet a commercial customer's stringent schedule requirements. The factors that contributed to the success of this project are examined, as is their relevance to the DoD world. The desire is to apply relevant lessons learned from the commercial industry to DoD programs, yielding a decrease in TPS development time     

A Survey of Software Quality Assurance

This summarizes the authors' research into the state-of-the-practice of software quality assurance (SQA) in software organizations throughout the Department of Defense (DoD). Information was obtained through personal visits to a limited number of software facilities and by utilizing a SQA questionnaire that was mailed to 27 DoD software organizations. Twenty questionnaires were returned from Army, Navy, Marine Corps, and Air Force organizations involved in the Life Cycle Software Support (LCSS) process. The survey developed information regarding such topics as: staffing; personnel qualifications; quality standards used; SQA responsibilities; error data collection; adequacy of existing documentation; staff composition; distribution of SQA effort; and workforce mix. In addition, a list of SQA ``Lessons Learned' was developed from comments made by DoD quality managers. The results of this study indicate a wide variance in the application of SQA within the DoD.     

Surveillance through walls and other opaque materials

The Department of Defense (DoD) has funded a dazzling array of “high tech” solutions for many of the problems facing our military forces. Many of these “solutions” have been effective for long range mass destruction but have not been applicable for the close-in hand-to-hand combat that is on our streets. Our goal at the Hughes AET Center has been to convert “high tech” DoD capabilities into cost effective tools to help law enforcement agencies do their jobs better. Surveillance systems presently used by law enforcement officers make extensive use of television, infrared and other Line-of-Sight (LOS) surveillance systems. However, these systems cannot tell what is happening on the other side of a wall, behind bushes, around the corner, in the dark or through a dense fog. A new sensor has been developed that uses technology developed by the DoD for missile warhead fuzing. This small, light weight, low power “Radar” is based upon the fact that radio waves can penetrate nonmetallic materials. This new surveillance capability can help provide information about what is in a wall, ceiling or floor or on the other side of a door or concrete wall. Real field scenarios are used in this paper to show how this radar works and how field users can tell if someone is moving inside a building, even from remote locations     

Software architecture requirements for DoD automatic test systems

The DoD has achieved success with recent automatic test equipment (ATE) families, as evidenced by the navy's consolidated automated support system (CASS) and the army's integrated family of test equipment (IFTE) programs. However, as these systems age, the increased requirements for technology insertion due to instrument obsolescence and the demands of advanced electronics are becoming evident. Recent advances in test technology promise to yield reduced total ownership costs (TOC) for ATE which can incorporate the new technology. The DoD automatic test system (ATS) executive agent office (EAO) objective is to significantly reduce total ownership cost. Several objectives have been identified including use of synthetic instruments, support for legacy test product sets (TPSs), and more efficient ways of developing TPSs. The NxTest software architecture will meet the objectives by providing an open systems approach to the system software. This will allow for the incorporation of commercial applications in the TPS development and execution environments and support current advances in test technology     

Bridging the gap between ATLAS and C: an open-systems approach toTPS re-host

As the DoD focuses on commercialization and open-architecture standards, the need to migrate existing TPSs from proprietary ATLAS-based platforms to an Open Systems platform becomes more critical. This paper will focus on a solution which leverages COTS software tools and emerging industry standards and technologies to implement object-oriented database tools which enable the conversion of an ATLAS TPS to an ANSI C environment     

我国大型民机复合材料产业的钻石模型分析

复合材料是确立我国大型民机产业竞争优势的重要因素之一。首先,梳理了大型民机复合材料产业上游、中游和下游的细分行业。随后,采用钻石模型,从六个维度对我国大型民机复合材料产业竞争力进行了分析,包括：1)资金、软硬件和人才队伍等生产要素的优势和不足;2)我国民航运输业、大型民机制造业的巨大市场需求;3)我国大型民机复合材料产业链的健全和快速发展;4)国内飞机主制造商的资源整合及国外主制造商的战略举措;5)国家和地方的政策支持;6)大型民机复合材料应用和产业发展的发展机遇等。最后,根据钻石理论,基于我国大型民机复合材料产业现状分析,从“政用产学研”五方面,提出提升我国大型民机复合材料产业竞争力的建议措施。钻石模型可以为我国大型民机复合材料产业规划制定和相关研发企业决策提供指导。     

Open system concepts for modular avionics

Advanced communications, guidance and navigation systems play key roles in determining superiority of one combat aircraft over another. The use of advanced technology is essential to meeting the mission requirements of present as well as future aircraft. Modular avionics are being used in next generation aircraft, such as the Air Force F-22 fighter and the Army Comanche helicopter, as the means of achieving higher levels of performance, including reduced volume and improved adaptability, maintainability, and expandability. New system acquisitions such as Joint Strike Fighter will attempt to achieve these same performance levels but at dramatically reduced life cycle cost. Retrofit applications will also take on increasing roles in meeting this affordability need as the Department of Defense (DoD) struggles to maintain readiness in the face of the shrinking defense budget. The government is encouraging the use of open standards practices as a means of addressing the affordability issue. The Open Systems Joint Task Force (OS-JTF), formed in September 1994, is chartered to “sponsor and accelerate the adoption of open systems in weapons systems and subsystem electronics to reduce life-cycle costs and facilitate effective weapon system intra- and interoperability”. The purpose of this paper is to relate the concept of open systems to modular avionics. It discusses the key attributes of an open systems approach and identifies key technologies necessary for its success     

Sole means navigation in US Navy aircraft

The current edition of the US Federal Radionavigation Plan, issued in 1984, presents a consolidated federal plane on the management of those radionavigation systems which are used by both the civilian and military sectors. It states the US Dept. of Defense (DoD) goal to phase out the use of TACAN, VOR/DME, OMEGA, LORAN C, and TRANSIT in military platforms and for Global Positioning System (GPS) to become the standard radionavigation system for DoD. This would eliminate all the current sole-means air navigation systems (TACAN and VOR/DME) aboard military aircraft. Instrument Flight Rule (IFR) operations within controlled airspace requires an operating sole-means air navigation system to be aboard the aircraft. The authors investigate the requirements for GPS certification as a sole means air navigation system in the US National Airspace System (NAS); discuss the implication for GPS user equipment (UE) hardware and software; describe the actual UE implementation; and discuss approaches for UE integration with flight instruments on US Navy aircraft     

Selecting a programming language for your project

Since the mandate was dropped that the Ada language had to be used in all DoD projects, software managers have had more freedom to choose which programming language to use on their DoD projects. For most new DoD software projects that need a general purpose high-level language, Ada, C, or C++ are the main contenders, with increasing attention paid to the new language celebrity, Java. Furthermore, multilanguage systems seems to be getting increasingly popular. As a result, companies offer integrated multilanguage programming environments. Although each programming language has its own strengths and weaknesses, the reason for choosing a particular language may ultimately be based on factors having nothing to do with the technical merits of the language itself. Such factors may include the availability of compilers for the host/target, the maturity and efficiency of available compilers, the availability of programmers who already know the language, whether the language can easily interface with existing systems such as graphical user interfaces or data bases, the existence of legacy software written in a specific language, or how well the language fits in with adopted COTS products. A few common misconceptions that may affect the choice of a programming language are listed     

Shared technologies: a new roadmap

The long-term goal of the USAF Shared Technologies Program is to facilitate the development of a roadmap for technology insertion on the wide variety of legacy Automatic Test Equipment (ATE) accumulated by the USAF over the past 30 years. A successful roadmap will provide for Operation & Support (O&S) cost reduction, preserve Test Program Set (TPS) development investments, and evolve in concert with the DoD Executive Agent for Automatic Test Systems (ATS) initiatives and commercial industry, and (e.g., NxTest) changes. The near-term objective of this phase of the USAF Shared Technologies Program is to demonstrate the feasibility of incorporating available commercial technology into the Radio Frequency (RF) Mobile Electronic Test Set (RFMETS). The RFMETS was originally delivered to the USAF during the early 1990s and is used to support a variety of C-130 avionics including the APQ-170 and APQ-180 Radar Systems.     

Technical trends in the future

On the day that Raytheon bought Hughes Electronics, A.N. Chester described how aerospace executives evaluate options for research programs. Their objective is to develop products that have value after the planned work is completed. Big changes are taking place in the environment in which a new commercial product must succeed. By “environment” means the official and unofficial rules created by social pressures, government decisions, industrial activity, and financial activity     

In-flight entertainment-getting from wishlist to reality

Much of what we see in the consumer electronics stores will eventually find its way into airplanes in the form of In-Flight Entertainment (IFE). This consumer electronic equipment is often referred to as “the leading edge of technology”. Unfortunately, that same equipment that is the “leading edge” of consumer electronics, often stalls to feel like the “bleeding edge” when you try to integrate it into IFE systems for today's modern aircraft. Unlike Avionics Systems, the technologies behind IFE equipment are not usually mature before they are integrated into the aircraft. What may work well in a home environment, may not work well at all in the aircraft environment. Often this problem results in last minute redesign in an effort to make the equipment function as intended on the aircraft. Both the FAA and the aircraft manufacturer impose many requirements on the suppliers and products of IFE. Systems need to be designed for the aircraft environment. Many variations on IFE Systems have forced the creation of new standards for integration into commercial aircraft. Power, cooling, and EMC issues are becoming more of a concern as we move to fill aircraft implementations. Beyond the technical evaluations and lab/aircraft testing, one key component is customer satisfaction. This paper will cover some of the methods and tools we use to get IFE from wishlist to reality     

Multifunctional structures technology experiment on Deep Space 1Mission

Lockheed Martin Astronautics has developed the Multifunctional Structure (MFS) concept as a new system for spacecraft design that eliminates chassis, cables, connectors and folds the electronics into the walls of the spacecraft. Concurrent engineering will be essential to integrate the electronic, structure, and thermal design. Design methodologies are in work to manage all power, grounding and shielding concerns. The MFS approach offers significant savings in mass and volume and supports the “faster-better-cheaper” philosophy in new spacecraft programs. The technology will be demonstrated as an experiment on the New Millenium Program Deep Space 1 (DS 1) mission     

Military Products From Commercial Lines

“Military Products From Commercial Lines” is a pilot program within the Air Force Manufacturing Technology Directorate's Industrial Base Pilots Office. TRW's Avionics and Surveillance Group (ASG) is leading the program. This pilot program will demonstrate commercial-military integration by producing F-22 military avionics modules on an automotive electronics production line operated by TRW's Automotive Electronics Group (AEG). To accomplish this requires a redesign of the modules so that they are producible using commercial automotive electronics processes. Dual use manufacturing also dictates establishing compatible business practices, manufacturing infrastructures and process technologies. Business practices that must be changed involve accounting procedures, contracting requirements, audit requirements and quality control. Manufacturing infrastructure improvements include incorporation of advanced concurrent engineering tools and process control software to allow economic production of small lot sizes. Process technology changes involve designing for production lines that are highly automated and compatibility with commercial practices     

Advances in DoD's ATS Framework

The Automatic Test System (ATS) Executive Directorate (ED) is charged with developing objectives for the Department of Defense (DoD) ATS modernization. The DoD ATS Framework Working Group (FWG) was established by the ATS ED to create a Framework addressing these objectives. The FWG consists of two sub-groups: Management, that includes members from all of the DoD Services, and Technical. The Framework is made up of key elements and associated specifications and standards that form the open system architecture approach for DoD ATSs. In addition to creating and updating key element definitions, the FWG focuses on identifying commercial ATS related specifications that might satisfy the elements in the Framework. The standards specified in the DoD ATS Framework are documented in the DoD's Information Technology Standards Repository (DISR) and thereby become a mandatory requirement for all DoD ATS acquisitions. The Framework is also being specifically called out in DoD ATS requirements documents so that its standards are incorporated in future DoD ATS acquisitions, such as the Navy's eCASS.     

COTS based open systems for military avionics

The DoD has many acquisition programs that are aggressively implementing open architecture principles in new avionics systems. Since “open” is an unclear attribute, projects eventually give in to a point solution that has no flexibility to cost effectively keep up with rapid changes in technology. The Open Systems Development Initiative (OSDI) project utilized COTS products to study the feasibility of building an open system that has plug-and-play capabilities. Lessons learned from the AV-8B Open Systems Core Avionics Requirements (OSCAR) and the F/A-18 Advanced Mission Computers and Displays (AMC&D) programs clearly indicated that understanding the underlying interfaces is crucial to keeping the system as open as possible to take advantage of the rapid changes in technology. A matrix of Key Open Standard Interfaces (KOSI), called the KOSI matrix, was developed and an applicable standard was identified for each interface. A list of non-conforming interfaces was also identified and the use of extensions or wrappers was investigated in an attempt to comply with standards. Standardization, rather than optimization of such interfaces, was considered more beneficial. It became evident that, with the exception of ruggedization, there is no difference in the use of COTS products for either commercial or military systems. Performing a KOSI analysis helped identify the key interfaces and standards, thus enabling the OSDI system to be scalable, portable and interoperable. A good KOSI matrix provides a vehicle for clear communication and helps systems integration and technology insertion to be less painful than what it is today. It helps reduce time-to-market and provides guidance to systems engineers and vendors to keep the system open     

Replacement strategy for aging avionics computers

With decreasing defense dollars available to purchase new military aircraft, the inventory of existing aircraft will have to last many more years than originally anticipated. As the avionics computers on these aging aircraft get older, they become more expensive to maintain due to parts obsolescence. In addition, expanding missions and changing requirements lead to growth in the embedded software which, in turn, requires additional processing and memory capacity. Both factors, parts obsolescence and new processing capacity, result in the need to replace the old computer hardware with newer, more capable microprocessor technology. New microprocessors, however, are not compatible with the older computer instruction set architectures. This generally requires the embedded software in these computers to be rewritten. A significant savings-estimated in the billions of dollars-could be achieved in these upgrades if the new computers could execute the old embedded code along with any new code to be added. This paper describes a commercial-off-the-shelf (COTS)-based form, fit, function, and interface (F³I) replacement strategy for legacy avionics computers that can reuse existing avionics code “as is” while providing a flexible framework for incremental upgrades and managed change. It is based on a real-time embedded software technology that executes legacy binary code on the latest generation COTS microprocessors. This technology promises performance improvements of 5-10 times that of the legacy avionics computer that it replaces. It also promises a 4× decrease in cost and schedule over rewriting the code and provides a “known good” starting point for incremental upgrades of the embedded flight software. Code revalidation cost and risk are minimized since the structure of the embedded code is not changed, allowing the replacement computer to be retested at the “blackbox” level using existing qualification tests     

A methodology for evaluating, comparing, and selecting softwaresafety and reliability standards

The regulated industries, which in the FDA's (US Food and Drug Administration) case include the manufacturers of food, cosmetics, pharmaceuticals, and medical devices, are responsible for selecting and justifying the selection and use of appropriate national and/or international consensus standards. This paper documents the results of a scientific inquiry which was undertaken to develop a methodology to evaluate and select individual standards as well as compatible sets of standards. Initially the scope was limited to software safety and reliability standards. Since then it has been expanded to other areas. It was found that six categories of criteria are important when evaluating the potential use of software safety standards: General Factors, Product Characterization, Process Characterization, Personnel Characterization, Risk Management, and Overall Standards Framework. The criteria in each of the six categories must be addressed, How they are addressed is both a technical and a policy decision. The goal should not be to try to find the “ultimate” standard because there isn't any. Rather the goal should be to select a balanced “diet” of standards based on these six categories. The methodology provides a systematic framework from which to make an objective determination about the appropriateness of using a particular standard     

Implementing reusable, instrument independent test programs in thefactory

Development of computer programs that control test sequences on Automatic Test Equipment (ATE) is costly and time consuming. Test Programs are usually written by specifying the instruments to be used in the ATE and the sequence of the setup and measurement parameters for these instruments. Reuse of test program software on other ATE is usually not possible without rewriting, revalidating and re-releasing the programs. This paper describes an implementation of a test program software development system and a standard of software runtime architecture used in our factories. The object-oriented development environment and its associated class libraries allow test programs to be written without knowledge of the ATE on which they will be run. Two main principles guided the design: the software architecture was based on recognized formal and industry standards; and our implementation used commercial off-the-shelf software products when possible. Emerging standards such as the IEEE-1226 (ABBET) as well as defacto industry standards including VXI Plug and Play have made our implementation possible. The current draft of the ABBET and P&P standards do not promote this instrument independence, but it is hoped that this will be added as the standards mature. Three immediate benefits are: cost savings that result from reusing validated test programs; cycle time reductions that result from concurrently developing test program software and ATE; and software defect reductions that result from using proven software     

Software replacement of test module adapters for depot instrumentation due to obsolescence

Depot-level automatic test equipment has been used over the years by various facets of both the government and commercial industry. Over time, the instrumentation used in the depot will need to be repaired or replaced and, oftentimes, the older instruments are no longer serviceable or manufactured. This paper discusses how to replace the obsolete instrument and its associated hardware. Test module adapter with a software module and driver that allows compatibility between the original test executive and the modern instrument without re-hosting existing test program sets. Systems & Electronics, Inc. has implemented this procedure for a digitizer and precision DC power supply on a depot that utilizes the IEEE-488 general purpose interface bus (GPIB) for communication between the control computer and instrumentation.