Browse Topic: Maintainability and supportability

Items (69)
As the U.S. Army endeavors to maintain overmatch capability in the global arena, Future Vertical Lift has become a high priority. In a climate that demands a more efficient and affordable acquisition process, it is imperative that structural integrity requirements are maintained as a priority to ensure initial quality, supportability, and maintainability considerations. Therefore, it is paramount that a standard practice be utilized so that structural integrity requirements are clearly understood by the Product Office, the Airworthiness Authority, and the Original Equipment Manufacturer(s). This paper highlights how the MIL-STD-3063 U.S. Army Standard Practice for Rotorcraft Structural Integrity Programs can meet these demands by laying out interrelated functional tasks in a concise manner to allow for decision makers to make sound choices with regards to structural integrity for any new developmental aircraft. The paper also details how the standard practice is being utilized to assist and guide Future Vertical Lift efforts.
Kiser, Michael
ABSTRACT Operations and support cost constitutes nearly 70% of rotorcraft lifecycle cost. When considering new rotorcraft concepts and technology infusion for current concepts, quantitative performance evaluation is undertaken during conceptual design. However, the effect of design decisions on operations and support metrics are typically evaluated qualitatively. Since operation and support costs constitute an overwhelming majority of rotorcraft lifecycle cost, quantitative evaluation of these metrics is required to fully capture the design trade space. To this end, an integrated discrete-event simulation environment is developed to quantify the impact of architectural decisions and subsystem technology infusion on key metrics including the operational availability, system mean time between failures, Maintenance Free Operating Period, repair cost, and maintenance man-hours needed for a given period of operation. Since data needs are immense, it is appropriate to use data from existing platforms to populate unknown fields. An example is presented in this paper for a notional helicopter to demonstrate the use of the discrete-event simulation environment as a tradeoff environment for operations and supportability metrics.
Price, JoshuaAshok, SylvesterArmstrong, RyanCollins, KyleMavris, DimitriSchrage, Daniel
Due to its subjective nature, the concept of value is not one that is easily defined. Marketers often refer to a product's 'value proposition' as an explanation to why an operator should buy a product or use a service. This statement should convince a potential operator that one particular product or service will add more value or better solve a problem than other similar offerings. In the rotorcraft market, this value proposition is often tied to capabilities of the helicopter and is typically defined as a composite metric. This metric is then compared to the acquisition cost to get a sense of helicopter value. Helicopter manufacturer's marketing and sales departments then go to the market and sell the benefits, either in range, take-off weight, reliability, operating cost, etc… One major difference in the value stream of rotorcraft products as compared to typical consumer products is that it is standard for a second-level supplier, in this case the engine manufacturer, to offer its own services and support. This creates an environment where both the helicopter and engine manufacturer have direct contact with the end operator and can influence their perception of value. A method for an engine manufacturer to define value can aid the helicopter manufacturer, and ultimately, the operator, to make an informed decision regarding the right product for their mission objectives. In order to derive a metric for the concept of value for a helicopter engine, one must understand the important aspects from an operational perspective, as opposed to the technical focus typically associated to this type of product. This paper focuses on the derivation of such a composite metric by using terms that represent a product's reliability, maintainability, and capability as compared to its direct operating cost as the acquisition cost of the engine is transparent to the end operator. Looking at the helicopter engine competitive environment in such a way serves two purposes: one for the engine manufacturer to be able to gauge the competitiveness of their product, and one for the operators to understand an engine's value proposition and how it fits into the helicopter capabilities. The details of how the metric of engine productivity were derived will not be elaborated as they are considered intellectual property to Pratt and Whitney Canada, but the benefits and concepts of viewing helicopter engines in such a way can be discussed.
Carpentier, Pierre
Logistics Product Data Reports HandbookTAHB0007_1 (Current)5/1/2013
This document describes a set of standardized reports that can be generated using the logistics product data elements contained in GEIA-STD-0007-B. Each report is defined by selection options, processing, format, report sequence, and data sources. The selection options paragraph identifies recommended mandatory and optional selections that can be made by the user to tailor the report content. The processing paragraph identifies qualifying criteria for report data, report calculations, and specific instructions regarding how the data should be presented on the report. Each report has a sample report showing its format. Report sequences specify the sort criteria for a given report, and each Part/Section within a report. There is an attached listing of data sources for the elements that are on a report. The listing provides the report header for each element; and its GEIA-STD-0007-B data element/attribute along with the appropriate entity. The data source listings were developed by viewing each report in a left-to-right, top-to-bottom sequence. If an element shows up more than once on a report and each subsequent occurrence is pulled from the same GEIA-STD-0007-B Entity as the previous one, then that element is only listed once in the data source listing. However, if an element is listed more than once and each occurrence is pulled from different GEIA-STD-0007-B Entities, then that element will be listed for each report occurrence. Report development can be accomplished via a manual process or via software. The latter approach is recommended since software is available on the market that meets the requirements for each of the reports in this handbook.
LCLS Life Cycle Logistics Supportability
G-11R, Reliability Committee
G-11R, Reliability Committee
G-11R, Reliability Committee
G-11M, Maintainability, Supportability and Logistics
G-11R, Reliability Committee
G-11M, Maintainability, Supportability and Logistics
G-11R, Reliability Committee
G-11R, Reliability Committee
Items per page:
1 – 50 of 69