SAE GEIA-STD-0007-B-2013 Logistics Product Data (Formerly TechAmerica GEIA-STD-0007-B Includes Access to Additional Content).pdf

1、 Access to Additional Content for SAE GEIA-STD-0007-B, Dated: May 2013 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyright h

2、older of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. GEIA_STD_0007_B Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer distribution is unlimited. i TABLE OF CONTENTS

3、FOREWORD (INFORMATIVE) III 1 INTRODUCTION (INFORMATIVE) 1 1.1 Description of Model in Graphical Form . 1 1.2 Model Overview 2 2 FUNCTIONAL AREAS (NORMATIVE) . 5 2.1 Cross Functional Requirements (X Entities) 5 2.2 Operations failure modes, effects, and criticality analysis; and maintainability analy

4、sis The “B“ entities provide a description of the function of each item within the system; outline the maintenance concept to be utilized for design and support planning purposes; and identify any design conditions such as fail-safe requirements/environmental or nuclear hardness considerations impos

5、ed upon the system. The entities summarize the reliability, maintainability, and related availability characteristics of the item resulting from the failure modes and effects, criticality, and maintainability analyses, and accommodate a narrative description of any analysis related to the potential

6、redesign of an item. A separate information instance is prepared for the system, for each subsystem contained in the system, and for each level of breakdown for that subsystem until the lowest reparable item has been documented. The degree of breakdown shall be specified by the requiring authority.

7、Additional “B“ entities are designed to accommodate the Failure Modes and Effects Analysis (FMEA). These entities will also accommodate the Damage Mode and Effects Analysis, to be utilized for survivability and vulnerability assessments and accommodate the criticality and maintainability analyses. T

8、he purpose of the criticality analysis is to rank each identified failure according to the combined influence of severity classification and failure probability of occurrence. The relative ranking of the calculated item criticality numbers highlights system high risk items. The maintainability analy

9、sis serves as the starting point for maintenance task analysis. The FMEA documents the effects of an item failure upon system operations and is used to classify each potential failure according to the severity of those effects. The FMEA is initiated as an integral part of the early design process an

10、d is derived through a functional analysis. To provide concise information on the failure analysis, functional block diagrams should be provided. Subsequent to this effort, data is prepared to an indenture level, as specified by the requiring authority. The results are used as a guide in evaluating

11、design features and as a basis for initial quantitative predictions. The analysis identifies high risk items, facilitates the evaluation of design features, and provides the basis for criticality and maintainability analyses. The failure effects data are the basis for developing fault location and t

12、roubleshooting routines. These entities also document Reliability Centered Maintenance (RCM) logic results and accommodate a narrative description of any analysis related to the potential redesign of an item. These entities are completed to the same indenture level as the item Reliability and Mainta

13、inability (R one of the duties of a driver is emergency repair; a task within emergency repair is changing a flat tire). The task identification information in these entities is developed from the RCM analysis, maintainability analysis, and the maintenance task analysis. This information is complete

14、d to the same indenture level as the R Functional LCN Type must always be coded “F“. When a functional and physical LCN are mapped through this entity, all data contained against the functional LCN shall migrate to the physical LCN (physical LCN data shall take precedence if data duplication has occ

15、urred). After the data is migrated, data additions and updates for this item shall only occur against the physical LCN. Entity XG contains the following KEY elements: end_item_acronym_code 2040 physical_logistics_support_analysis_control_number 2970 physical_alternate_logistics_support_analysis_cont

16、rol_number_code 1200 physical_logistics_support_analysis_control_number_type 2980 Entity XG contains the following elements: functional_logistics_support_analysis_control_number 2970 functional_alternate_logistics_support_analysis_control_number_code 1200 functional_logistics_support_analysis_contro

17、l_number_type 2980 Entity XH_Commercial_and_Government_Entity_data. This entity contains all Commercial and Government Entity (CAGE) codes and the CAGE addresses. A CAGE street, city, state, nation, or postal zone cannot be included without a CAGE name. Entity XH contains the following KEY elements:

18、 commercial_and_government_entity_code 1520 Entity XH contains the following elements: commercial_and_government_entity_city 1510 commercial_and_government_entity_name 1530 commercial_and_government_entity_nation 1540 commercial_and_government_entity_postal_zone 1550 commercial_and_government_entity

19、_state 1560 commercial_and_government_entity_street 1570 GEIA-STD-0007-B 11 Entity XI_Technical_Manual_Code_and_Number_Index_data. This entity contains a cross-reference of Technical Manual (TM) code to TM number(s). Entity XI contains the following Key element: technical_manual_code 5250 Entity XI

20、contains the following element: technical_manual_number 5280 Entity XT_Digital_File_data. This entity contains elements to describe a file,document, image, or other electronic medium. The document_id can contain an Information Control Number or digital file identifier. In the latter case the origina

21、tor_code must be the associated commercial_and_government_entity_code. Drawing and Document File Extension must either both be blank, or both have entries. Entity XT contains the following Key element: document_id 1940 originator_code 1520 issue_number 2715 security_classification 4655 Entity XT con

22、tains the following elements: caption 1480 document_file_extension 1930 drawing 1980 Entity XZ_Logistics_Support_Analysis_Control_Number_Digital_File_data. This entity contains elements to associate or map a document, image, or other electronic medium to a particular logistics_support_analysis_contr

23、ol_number. Entity XZ contains the following Key elements: document_id 1940 originator_code 1520 issue_number 2715 security_classification 4655 end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logistics_support_analysis_control_number_code 1200 logistics_support_ana

24、lysis_control_number_type 2980 GEIA-STD-0007-B 12 2.2 Operations & Maintenance (A Entities) 2.2.1 Description Data entities beginning with “A“ in the first position of the entity name are structured to consolidate information related to the anticipated operation of the system, environment in which t

25、he system will be operated and maintained, and maintenance requirements of the system that must be met. This information is prepared for the system and for each subsystem for which maintenance requirements are to be imposed. 2.2.2 Graphical Representation See Figure 2 for the graphical description o

26、f the Operations and Maintenance (O/M) functional area. GEIA-STD-0007-B 13 Figure 2 - Operations and Maintenance GEIA-STD-0007-B 14 2.2.3 Entity Descriptions Entity AA_Operations_and_Maintenance_Requirements_data. This entity identifies operations, maintenance, and reliability requirements for the n

27、ew system/equipment by the service designator code. For a given entity instance of information, Required Percentile is not allowed without a Maximum Time to Repair. Entity AA contains the following Key elements: end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logi

28、stics_support_analysis_control_number_code 1200 logistics_support_analysis_control_number_type 2980 service_designator_code 4710 Entity AA contains the following elements: crew_size 1720 number_operation_locations 3660 operational_mean_active_maintenance_downtime 3200 reliability_centered_maintenanc

29、e_logic_utilized 4460 required_achieved_availiability 1010 required_inherent_availiability 2560 required_maximum_time_to_repair 3170 required_operational_mean_time_to_repair 3360 required_percentile 3880 required_technical_mean_time_to_repair 3360 technical_mean_active_maintenance_downtime 3200 tota

30、l_systems_supported 5420 Entity AB_War_Peace_Operations_and_Maintenance_Requirement_data. This entity identifies O/M requirements for the new system/equipment based on its projected wartime and peacetime missions for a given service designator code. For a given entity instance, Mean Mission Duration

31、 and Mean Mission Duration Measurement Base must either both be blank, or both have entries. Entity AB contains the following Key elements: end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logistics_support_analysis_control_number_code 1200 logistics_support_analys

32、is_control_number_type 2980 service_designator_code 4710 operational_requirement_indicator 3710 GEIA-STD-0007-B 15 Entity AB contains the following elements: additional_requirements 1080 annual_number_of_missions 1220 annual_operating_days 1230 annual_operating_time 1250 mean_mission_duration 3250 m

33、ean_mission_duration_measurement_base 3380 required_administrative_and_logistics_delay_time 1090 required_operational_availability 3700 required_standby_time 4950 Entity AC_Maintenance_Level_Requirement_data. This entity identifies O/M requirements for the new system/equipment by O/M level, wartime/

34、peacetime scenario, and service designator code. For a given entity instance, Maintenance Level Percentile is not allowed without a Maintenance Level Maximum Time to Repair. Entity AC contains the following Key elements: end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alter

35、nate_logistics_support_analysis_control_number_code 1200 logistics_support_analysis_control_number_type 2980 service_designator_code 4710 operational_requirement_indicator 3710 operations_and_maintenance_level_code 3750 Entity AC contains the following elements: maintenance_level_maximum_time_to_rep

36、air 3170 maintenance_level_percentile 3880 maintenance_level_scheduled_annual_man_hours 1210 maintenance_level_unscheduled_annual_man_hours 1210 number_of_systems_supported 3650 scheduled_man_hour_per_operating_hour 3120 unscheduled_maintenance_mean_elapsed_time 3210 unscheduled_maintenance_mean_man

37、_hours 3220 unscheduled_man_hour_per_operating_hour 3120 Entity AD_Organizational_Level_Requirement_data. This entity identifies organizational level O/M requirements for the new system/equipment by wartime/peacetime scenario, O/M level, and service designator code. For a given entity instance, only

38、 “C“ and “O“ for the O/M Level Code are allowed for this entity. GEIA-STD-0007-B 16 Entity AD contains the following Key elements: end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logistics_support_analysis_control_number_code 1200 logistics_support_analysis_contro

39、l_number_type 2980 service_designator_code 4710 operational_requirement_indicator 3710 operations_and_maintenance_level_code 3750 Entity AD contains the following elements: daily_inspection_mean_elapsed_time 3210 daily_inspection_mean_man_hours 3220 mission_profile_change_mean_elapsed_time 3210 miss

40、ion_profile_change_mean_man_hours 3220 periodic_inspection_mean_elapsed_time 3210 periodic_inspection_mean_man_hours 3220 postoperative_inspection_mean_elapsed_time 3210 postoperative_inspection_mean_man_hours 3220 preoperative_inspection_mean_elapsed_time 3210 preoperative_inspection_mean_man_hours

41、 3220 turnaround_inspection_mean_elapsed_time 3210 turnaround_inspection_mean_man_hours 3220 Entity AE_Skill_Operations_and_Maintenance_Requirement_data. This entity identifies operational maintenance manpower constraints by Skill Specialty Code (SSC) at specific O/M levels given a wartime/peacetime

42、 scenario and service designator code. Entity AE contains the following Key elements: end_item_acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logistics_support_analysis_control_number_code 1200 logistics_support_analysis_control_number_type 2980 service_designator_code 47

43、10 operational_requirement_indicator 3710 operations_and_maintenance_level_code 3750 skill_specialty_code 4810 Entity AE contains the following elements: available_man_hour 1320 available_quantity 1330 utilization_ratio 5810 GEIA-STD-0007-B 17 Entity AG_Reliability_Requirement_data. This entity iden

44、tifies reliability requirement parameters for the new system/equipment that are dependent on measurement base (MB). There can be multiple entities depending upon the annual operating requirements MB. For a given entity instance of information, the following cross-element edits apply to entity AG: a)

45、 AOR and AOR MB must either both be blank, or both have entries. b) Reliability Operational Requirements Indicator must match Operational Requirements Indicator in Entity AB for the given keys. The keys consist of EIAC, LCN, ALC, and LCN Type. Entity AG contains the following Key elements: end_item_

46、acronym_code 2040 logistics_support_analysis_control_number 2970 alternate_logistics_support_analysis_control_number_code 1200 logistics_support_analysis_control_number_type 2980 annual_operating_requirement_measurement_base 3380 Entity AG contains the following elements: annual_operating_requiremen

47、t 1240 reliability_operational_requirements_indicator 3710 required_mean_time_between_removals 3340 required_mean_time_between_effective_function_failures 3260 required_mean_time_between_noneffective_function_failures 3320 required_mean_time_between_system_aborts 3350 required_operational_mean_time_

48、between_failures 3270 required_operational_mean_time_between_maintenance_actions 3280 required_technical_mean_time_between_failures 3270 required_technical_mean_time_between_maintenance_actions 3280 Entity AH_Interoperability_Requirement_data. This entity identifies item name, National Stock Number (NSN), and the TM of the system/equipment with which the new system/equipment must be able to be t