| Business DEX (LOGSA004):— operations_and_maintenance | Date: 2010/12/29 16:18:09 Revision: 1.14 |
Customer operations and maintenance “design to” requirements can be exchanged via this data exchange set.
Operations and Maintenance specification information is summarized in Figure 14 below.
The product in scope and its component assemblies and parts. Can be either a part, or an element in a logical breakdown structure of a defined end item. This is normally defined by an End Item Acronym Code.
The product in focus can have different versions of the product, each of which, has a different breakdown. Models are normally identified by a Usable on Code.
The product in focus and its product model breakdowns can be represented via a physical breakdown (e.g. follows the design drawing structure) or a functional breakdown (e.g. represents functions of the product, propulsion, fuel, communications, etc). Breakdowns may also be hybrid or zonal.
The identifier assigned to each physical or functional element in the breakdown of the product. An Logistics Support Analysis Control Number is normally used for the breakdown element.
Defines the intended operation of the product in focus and its models (e.g. annual operating requirements, annual number of missions, number of maintenance shops and locations, crew size, total products to be fielded, etc.) and the environment it will be operated in (e.g. desert, arctic, etc).
Captures specific design requirements from a logistics standpoint (e.g. mean time between failure, mean time to repair, skill limitations, etc.) for the product in focus and breakdown elements that require specific design to requirements.
© OASIS 2010 — All rights reserved