REG NASA-LLIS-0831-2000 Lessons Learned Maintainability Program Management Considerations.pdf

《REG NASA-LLIS-0831-2000 Lessons Learned Maintainability Program Management Considerations.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0831-2000 Lessons Learned Maintainability Program Management Considerations.pdf（8页珍藏版）》请在麦多课文档分享上搜索。

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-04-19a71 Center Point of Contact: HQa71 Submitted by: Wil HarkinsSubject: Maintainability Program Management Considerations Practice: Identify program management considerations necessary when implementing maintainability prin

2、ciples for NASA space flight, atmospheric, or ground support programs.Programs that Certify Usage: This practice has been used on Hubble Space Telescope, SRBs, Shuttle GSE, and Space Acceleration Measurement System.Center to Contact for Information: HQImplementation Method: This Lesson Learned is ba

3、sed on Maintainability Technique number PM-2 from NASA Technical Memorandum 4628, Recommended Techniques for Effective Maintainability.Benefit:Early and effective planning and implementation of a maintainability program can significantly lower the risk of reduced system operational effectiveness res

4、ulting from maintainability design shortfalls. This reduces maintenance time/support, which directly relates to reduced operating costs and increased system operational time.Implementation Method:Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-This t

5、echnique outlines management considerations to observe when applying the principles of maintainability on a program at NASA. It also provides information on how to realize cost savings and reduced system downtime. This information complements PM-1, “Benefits of Implementing Maintainability on NASA P

6、rograms,“ by providing guidelines for establishing a maintainability program once the benefits have been understood.Program management is responsible for establishing proper integration of maintainability early in program development and ensuring adequate control of the application of the maintainab

7、ility discipline throughout the development program. Figure 1 provides flow diagram for an effective Maintainability program beginning with development of its goals and objectives , followed by development of the program/system maintenance concept and the Maintainability Program Plan, and establishm

8、ent of program control and evaluation during design, production (manufacturing) and operations. The order of these program development elements is important, as each affects the next step in the process.refer to D descriptionProvided by IHSNot for ResaleNo reproduction or networking permitted withou

9、t license from IHS-,-,-D Figure 1: Maintainability Program Development (1) ESTABLISH MAINTAINABILITY AS PART OF THE OVERALL SYSTEMS ENGINEERING AND OPERATION PLANNING PROCESS.Set Goals and ObjectivesOne of the missions of the maintainability program is to measure the ability of an item to be retaine

10、d or restored to a specified condition when maintenance is performed. The degree of maintainability designed into a system should reflect the function (mission) of the system/subsystem and the impact on operational objectives of the program if the system is non-operational for any length of time. Sy

11、stem availability (the ability of the system to operate whenever called upon to do so) is very important, and maximum availability should be a goal of the program. Program maintainability goals and objectives must be developed with cost and schedule in mind; however, careful consideration must also

12、be given to the technical and operational goals of the program. These qualitative goals and objectives are developed by analyzing the system operating cycle, the physical and maintenance support environments, and other equipment characteristics consistent with mission and cost objectives.Attention m

13、ust also be given to existing support programs to avoid needless duplication during development of new support systems. Development of the maintainability goals and objectives will lead to derivation of the maintenance concept, maintainability plan, and definition of maintainability requirements dis

14、cussed in the following paragraphs.Establish Interfaces with Other Engineering DisciplinesMaintainability engineering is a system engineering discipline that combines system analysis and equipment design with a knowledge of safety, reliability, human factors, and life-cycle costing to optimize the m

15、aintenance characteristics of system design and to provide an awareness of interface problems. Its goal is to optimize the combination of design features, repair policies, and maintenance resources to the desired level of maintainability at acceptable life-cycle costs. The many interfaces and feedba

16、ck paths between maintainability engineering and other product development and operational disciplines are shown in Figure 2.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-refer to D descriptionD Figure 2: System Reliability, Maintainability and Sup

17、port Relationships (typical) While maintainability personnel must be intimately involved in the product development process and provide inputs to design through design techniques and analysis, it is program managements responsibility to develop and support the relationship between maintainability an

18、d the rest of the system engineering disciplines. This support is key to establishment of a concurrent engineering process. These relationships must be mirrored in the Maintainability Program Plan.(2) DEVELOP MAINTENANCE AND LOGISTICS CONCEPTS EARLY IN THE CONCEPTUAL PHASE OF THE PROGRAM.The program

19、 maintenance concept provides the basis for establishing overall maintainability design requirements on the program, and contains detailed planning on maintenance policy.It defines overall repair policy, organizational and depot maintenance, system availability, repair vs. replacement policy, level

20、of replacement, skill level requirements, sparing philosophy, diagnostic/testing principles and concepts, contractor maintenance responsibilities, payload maintenance responsibilities, and crew time allocations for maintenance (Maintainability Technique PM-3 provides details on each of these element

21、s). Development of the maintenance concept is based on initial maintainability analysis and program inputs such as mission profile, system availability and Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-reliability requirements, system mass properti

22、es constraints, and personnel considerations. The maintenance concept may be developed from the ground up, or may come from a similar successful program, tailored to meet the needs of the new program. New technology may also dictate the maintenance concept, e.g. maintainable items may be scrapped in

23、stead of repaired because the cost of repair outweighs the replacement cost.Definition of logistics and support concepts is a function of the maintenance concept. The operational environment of the system, the level of support personnel defined by the maintenance concept, and cost and schedule are i

24、mportant drivers for the logistics/support programs.These elements are also important contributors to system maintainability in that logistics planning can define how much system down time is required during maintenance operations.For example, downtime can be held to a minimum if spares are co-locat

25、ed with the system during operations. It is important that Program management closely monitor all logistics development to ensure inclusion of maintenance and logistics concepts early in the program. Both concepts drive the development of lower-level requirements.Assess Existing ResourcesAnother imp

26、ortant aspect of planning for a new program is assessment of the existing logistic and support infrastructure. As an example, the infrastructure of the NSTS system at KSC comprises the launch pad, numerous assembly and support buildings, and support personnel and equipment. These are important facto

27、rs to consider when planning for new programs that will use KSC as the central operations base. If some of the existing structures and equipment can be used by the new program, then the developmental and operational costs of the program will be reduced. During early planning stages, management shoul

28、d also look at how the new program can adapt to the existing support infrastructure, and what equipment and personnel may be used to eliminate unnecessary costs.Establish a Maintainability Program PlanThe maintainability program plan is the master planning and control document for the maintainabilit

29、y program. It provides detailed activities and resources necessary to attain the goals and objectives of the maintainability program. It must be developed with the program contractor(s) if they exist, or if the program is in-house, all developmental and operational disciplines must be represented. T

30、he plan must be consistent with the type and complexity of the system or equipment and must be integrated with the systems engineering process. It identifies how the contractor/program office will tailor the maintainability program to meet requirements throughout the three major program phases: Deve

31、lopment, Production, and Operations/ Support. Typically it contains the following elements shown in Table 1:Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Duties of each organizational element involved in the accomplishment of the maintainabilit

32、y tasks cited in the product specification or statement of work.a71 Interfaces between maintainability and other project organizations, such as design engineering, software, reliability, safety, maintenance, and logistics.a71 Identification of each maintainability task, narrative task descriptions,

33、schedules, and supporting documentation of plans for task exectuation and management.a71 Description of the nature and extent that the maintainability function participates in formal and informal design reviews, and authority of maintainability personnel in approval for drawing release.Table 1. Elem

34、ents of the Maintainability Program Plan (3) PROVIDE UNIFORM QUALITATIVE AND QUANTITATIVE MAINTAINABILITY REQUIREMENTS.Maintainability design requirements are established from the Maintainability Program Plan and the derived maintenance concept.These requirements are intended as rules system designe

35、rs follow to meet overall program goals and objectives. They include mission, operational environment, and system concepts. They must be baselined early and not changed unless absolutely necessary.The requirements can include both quantitative and qualitative values of maintainability parameters. Qu

36、antitative maintainability requirements are usually the result of maintainability allocations based on system availability and operational timing requirements, with allocations made at each level down to the replaceable module, assembly or component level as needed. Examples of quantitative requirem

37、ents are shown in Table 2:Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Maintenance manhours per operating hour (MMH/OH)a71 Mean-Time-To-Repair (MTTR)a71 Mean-Time-To-Restore-System (MTTRS)a71 Fault detection and isolation of sub-systems task t

38、imesa71 End item change out timea71 Unit removal/installation timesa71 AvailabilityTable 2. Examples of Quantitative Requirements They may be established at any, or all, levels of maintenance and can help define maintenance criticalities and reduction of necessary system components. Qualitative requ

39、irements are used to accomplish two purposes. First, they address maintainability design features which are vital in achieving the maintainability goals, but cannot be measured. For example, elimination of safetywire/lockwire, standardization of fasteners, use of captive fasteners, and color-coding

40、of electrical wiring are some basic qualitative maintainability requirements used on orbital programs. Second, qualitative requirements are used to meet customer/program requirements and enhance the maintainability characteristics of the system. Examples include specification of common handtools onl

41、y for organizational and intermediate levels of maintenance, and designing so that only one skill level is required for all organizational level maintenance personnel.(4) EXERCISE PROGRAM CONTROL AND EVALUATION.The maintainability program must be an integral part of the systems engineering process a

42、nd all design and development activities. Activities include design reviews, development and implementation of methods for assessing maintainability effectiveness, dissemination of maintainability data, and proper implementation of program test and evaluation. Subcontractor/supplier control is also

43、a key area for program evaluation and monitoring.SummaryProgram managements participation in the development and implementation of sound maintainability practices on NASA programs is extremely important. Whether the program contains ground based systems, or is orbital and beyond, maintainability pla

44、ys a key role in system operations, providing for increased system effectiveness and availability, and lower life cycle costs. The steps outlined above are guidelines towards success, and can be tailored depending on the type of program. However, the importance of a concurrent engineering approach a

45、nd the existence of intimate professional relationships between maintainability personnel and other systems engineering disciplines can not be overstated, and existence of these examples will enhance the chance of program success (based on historical experience).Provided by IHSNot for ResaleNo repro

46、duction or networking permitted without license from IHS-,-,-References:1. NASA Handbook 5300.4(1E), “Maintainability Program Requirements for Space Systems,“ March 10, 1987, NASA Headquarters.2. Air Force Design Handbook 1-9, “Maintainability (for Ground Electronic Systems),“ Second Edition, Revisi

47、on 7, February 25, 1988, United States Air Force Aeronautical Systems Division.3. “Maintainability Engineering Design and Cost of Maintainability,“ Revision II, January, 1975, Rome Air Development Center.4. Reliability, Maintainability, and Supportability (RMS) Guidebook, Second Edition, 1992, Socie

48、ty of Automotive Engineers G-11 International RMS Committee.5. Maintainability Technique PM-1, “Benefits of Implementing Maintainability on NASA Programs“6. Maintainability Technique PM-3: “Maintenance Concept for Space Systems.“Impact of Non-Practice: Decisions by program management to establish ma

49、intainability requirements early in the program will provide design impetus towards a system with higher operational availability at lower operational costs. Lower downtime and less complicated maintenance actions will be needed when maintenance is required.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-04-19a71 Approval