1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there
2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2013 SAE International All rights reserved. No part of this p
3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/TAHB0007_1 TECHNICAL REPORT TA-HB-0007-1 Issued 2013-05 Logistics Product Data Re
5、ports Handbook NOTICE This document has been taken directly from the original TechAmerica document and contains only minor editorial and format changes required to bring it into conformance with the publishing requirements of SAE Technical Standards. The release of this document is intended to repla
6、ce the original with the SAE International document. Any numbers established by the original document remain unchanged. The original document was adopted as an SAE publication under the provisions of the SAE Technical Standards Board (TSB) Rules and Regulations (TSB 001) pertaining to accelerated ad
7、option of specifications and standards. TSB rules provide for (a) the publication of portions of unrevised specifications and standards without consensus voting at the SAE committee level, and (b) the use of the existing specification or standard format. TechAmerica Engineering Bulletin Logistics Pr
8、oduct Data Reports Handbook TA-HB-0007-1 May 2013 TA-HB-0007-1 NOTICE TechAmerica Engineering Standards and Publications are designed to serve the public interest by eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and a
9、ssisting the purchasers in selecting and obtaining with minimum delay the proper product for their particular needs. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of TechAmerica from manufacturing or selling products not conforming to such Sta
10、ndards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TechAmerica members, whether the standard is to be used either domestically or internationally. Standards and Publications are adopted by TechAmerica in accordance wit
11、h the American National Standards Institute (ANSI) patent policy. By such action, TechAmerica does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. Technical Publications are distinguished from TechAmerica Stand
12、ards in that they contain a compilation of engineering data or information useful to the technical community and represent approaches to good engineering practices that are suggested by the formulating committee. This Bulletin is not intended to preclude or discourage other approaches that similarly
13、 represent good engineering practice, or that may be acceptable to, or have been accepted by, appropriate bodies. Parties who wish to bring other approaches to the attention of the formulating committee to be considered for inclusion in future revisions of this publication are encouraged to do so. I
14、t is the intention of the formulating committee to revise and update this publication from time to time as may be occasioned by changes in technology, industry practice, or government regulations, or for other appropriate reasons. (Formulated under the cognizance of the TechAmerica Systems Engineeri
15、ng Committee, G-47.) Published by 2013 TechAmerica Standards 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
16、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 elemen
17、t 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. 1.1 Common Selection Criteria 1
18、.1.1 For a majority of the reports there are 8 common selections. These common selections are end_item_acronym_code, logistics_support_analysis_control_number, alternate_logistics_support_ analysis_control_number_code, logistics_support_analysis_control_number_type, usable_on_code, service_designato
19、r_code, operations_and_maintenance_level_code, and item_category_code. 1.1.2 end_item_acronym_code. logistics_support_analysis_control_number selections must specify an end_item_acronym_code parameter. 1.1.3 logistics_support_analysis_control_number. logistics_support_analysis_control_number selecti
20、ons may have both a start and a stop logistics_support_analysis_control_number. If a start and stop logistics_support_analysis_control_number are selected then it will include all logistics_support_analysis_control_numbers that fall within that range of logistics_support_analysis_control_numbers sel
21、ected, unless start and stop are equal, in which case, just include the single logistics_support_analysis_control_number. If a start logistics_support_analysis_control_number is selected but not a stop logistics_support_analysis_control_number then only that logistics_support_analysis_control_number
22、 leg will be included. For selections from the “A“, “B“, “C“, “F“, “G“, and “J“ entities, which may have data under combinations of functional and physical logistics_support_analysis_control_numbers, the following rules apply: 1.1.3.1 If the report selection specifies a logistics_support_analysis_co
23、ntrol_number_type of “F“, an attempt to match each qualified logistics_support_analysis_control_number to the Entity XG_Functional_Physical_Logistics_Support_Analysis_Control_Number_Mapping_data functional/physical logistics_support_analysis_control_number mapping entity is first performed. If a mat
24、ch is found in this entity, then report data is extracted under the physical TA-HB-0007-1 2 logistics_support_analysis_control_number equivalent. The Functional logistics_support_analysis_control_number, however, is displayed on the report. If no match for a functional logistics_support_analysis_con
25、trol_number is found, then search for the report data for the non-matched logistics_support_analysis_control_number is conducted using the functional logistics_support_analysis_control_number value directly. 1.1.3.2 If the report selection specifies a “P“ logistics_support_analysis_control_number_ty
26、pe, the search for report data is conducted directly under the appropriate entities for report generation. It will not be necessary to search the Entity XG_Functional_Physical_Logistics_Support_Analysis_Control_Number_ Mapping_Data for functional equivalent logistics_support_analysis_control_numbers
27、. 1.1.4 alternate_logistics_support_ analysis_control_number_code. When a selection is made with a specific alternate_logistics_support_ analysis_control_number_code, only items matching the selected alternate_logistics_support_ analysis_control_number_code are displayed. If the alternate_logistics_
28、support_ analysis_control_number_code is left blank on a selection, then other report qualifiers are used. 1.1.5 usable_on_code. The usable_on_code is mandatory for most reports and is used to identify specific model(s) of the end item. It is used to identify the model/configuration relationship of
29、each logistics_support_analysis_control_number comprising a system/equipment and to control these relationships for report creation. In accordance with Entity XC, each configuration/model is assigned a unique usable_on_code at the system/end item level logistics_support_analysis_control_number. Each
30、 individual assembly/component/piece part is also “linked“ to the assigned usable_on_code of the model of which it is applicable through entities XF and HO. When an assembly/component/piece part is applicable to more than one configuration/model, then multiple usable_on_codes are “linked“ to the com
31、ponent for a single logistics_support_analysis_control_number and alternate_logistics_support_analysis_control_number via entities XF and HO. This eliminates the requirement of duplicating analysis and related data, merely because an item has application to multiple configurations/models. 1.1.6 serv
32、ice_designator_code. For selections, choosing a service_designator_code of A, F, N, or M results in the selection of the matched service_designator_codes and X and J codes. Choosing code T results in selection of T and J. Choosing X, J, S, or O results in only those codes being selected. service_des
33、ignator_codes are interpreted as follows: A ARMY T FAA N NAVY S National Security Agency F AIR FORCE Y COAST GRD M MARINES J FAA/All Military X ALL SERV O OTHER 1.1.7 operations_and_maintenance_level_code. The operations_and_maintenance_level_code will interpret the 3rd position of the task-code to
34、produce the requested report. See GEIA-STD-0007 for allowable codes. 1.1.8 item_category_code. The default value for selectable item_category_codes is all applicable item_category_codes. Each report description will denote allowable item_category_codes. If item_category_codes are selectable but not
35、denoted for the report, then all item_category_codes defined in GEIA-STD-0007, Appendix A are allowed. 1.2 Subordinate LCN/ALC Subordinate logistics_support_analysis_control_number/ alternate_logistics_support_ analysis_control_number_code selections can be of use when multiple configurations, or al
36、ternate design and maintenance concepts, have been included as part of the logistics product data for an equipment. The alternate_logistics_support_ analysis_control_number_code specified for the subordinate selection(s) for TA-HB-0007-1 3 any logistics_support_analysis_control_number within the log
37、istics_support_analysis_control_number range overrides the basic alternate_logistics_support_ analysis_control_number_code selection. The output report will include the alternate assembly(s) requested including its subordinate items, if applicable. Once the alternate assembly and their breakdown hav
38、e been selected, the process will revert back to the configuration and logistics_support_analysis_control_number range specified on the basic selection. For example, if the basic selection is logistics_support_analysis_control_number = A, alternate_logistics_support_ analysis_control_number_code = 0
39、0, no stop logistics_support_analysis_control_number (implies a stop logistics_support_analysis_control_number of B), with subordinate logistics_support_analysis_control_number/alternate_logistics_support_ analysis_control_number_code selections of A0102/01, A010207/02, and A04/01 yields the followi
40、ng alternate_logistics_support_ analysis_control_number_codes (LCN/ALCs) selected: LCN (From) LCN (To) ALC A A0101ZZZZZZZZZZZZZ 00 A0102 A010206ZZZZZZZZZZZ 01 A010207 A010207ZZZZZZZZZZZ 02 A010208 A0102ZZZZZZZZZZZZZ 01 A0103 A03ZZZZZZZZZZZZZZZ 00 A04 A04ZZZZZZZZZZZZZZZ 01 A05 AZZZZZZZZZZZZZZZZZ 00 1
41、.3 Task Referencing Or Subtask Referencing Entity CA_Task_Requirements_data in GEIA-STD-0007 allows for referencing of tasks and their related information. To reference a task, a user will input the “Referenced“ end_item_acronym_code, logistics_support_analysis_control_number, alternate_logistics_su
42、pport_ analysis_control_number_code, logistics_support_analysis_control_number_type and task_code following the Entity CA_Task_Requirements_data key set (or “Referencing“ keys). As paragraph 2.4.3.a) of GEIA-STD-0007 denotes, this task referencing capability should only be utilized when the data of
43、Entity CA_Task_Requirements and subordinate entities CB_Subtask_Requirements_Narrative_data to CI_ Task_Provisioned_Item_data are identical for the referenced and referencing tasks. All non-key attributes in Entity CA_Task_Requirements and all data in subordinate entities (CB_Subtask_Requirements_Na
44、rrative_data to CI_ Task_Provisioned_Item_data, CR_Subtask_Support_Equipment_data and optional alternate_logistics_support_ analysis_control_number_code, stop logistics_support_analysis_control_number, skill_specialty_code, number_of_systems_supported per operations/maintenance level (default=1) and
45、 Report Part (PARTS). 2.2 Processing. The same qualifying criteria is used for both parts I and II. Task_codes are qualified by matching on selected service_designator_code (task_code 4th position). Qualified tasks must have an entry in Entity CD_Subtask_Personnel_Requirements_data with a valid subt
46、ask_mean_man_minutes per subtask_person_identifier over the range of selected logistics_support_analysis_control_numbers. 2.2.1 It is possible to select only Part I of the report. If Part II is selected, Part I will also be displayed. If a selection is made by skill_specialty_code, then both parts I
47、 and II will be generated. 2.2.2 Report calculations: 2.2.2.1 Part II M-H PER PERSON ID is computed by summing all subtask_mean_man_minutes for each subtask entry matching an identical subtask_person_identifier and skill_specialty_code. This value is then divided by 60. 2.2.2.2 Part II ANL M-H/ITEM
48、is computed by multiplying the M-H PER PERSON ID (from 2.2.2.1) by the task_frequency. 2.2.2.3 Part II TOTAL ANL M-H is computed by multiplying the ANL M-H/ITEM (from 2.2.2.2) by the number_of_systems_supported by task_code operations/maintenance levels input through the report selection. 2.2.2.4 Part I Man Hour Summary MAN-HOURS is computed by summing all TOTAL ANL M-H for a given subtask_person_identifier, skill_specialty_code and Operations/Maintenance Level of the task_code, position 3. 2.2.2.5 PART I TOTAL NUMBER OF MAINTENANCE TASKS is computed by summing each qualified task_code hav
