Definition: The definition of a Transport or Equipment type is that all items or parts with the same Form, Fit, Function and Maintenance plan must be the same Transport or Equipment type. Depending on the industry the classification of Transport or Equipment types can be quite different.
In some instance the Transport or Equipment type will be the same as item numbers used within the organisation. In general the Transport or Equipment type will be a grouping of item numbers and part numbers.
Before Transport or Equipment types are defined, the user should have decided on an implementation strategy regarding the grouping and identification of Transport or Equipment. The following must have been considered:
- Configuration items - Which items must be controlled. This will be the maintenance significant items, high cost items and any other item that needs to be controlled. Spare parts needed for maintenance or operational tasks must be included.
- Facilities - All facilities that need to be controlled such as workshops, wash bays etc.
- Special Tools and Support Equipment - All tools and support equipment needed for operation and maintenance purposes.
- Documentation - All documentation needed for the maintenance and operation of the equipment such as workshop repair manual, illustrated parts breakdown, setting to work manual, etc.
Transport or Equipment types are used in the ALM module to group the Transport or Equipment with the same characteristics or parameters, together. This means that multiple items with the same characteristics may have the same Transport or Equipment type. Transport or Equipment types are used throughout ALM. Transport or Equipment type must be registered for each generic configuration item which has the same parameters such as documentation, modification states, performance criteria, etc.
Fleet: Create, Setup and Configure Transport or Equipment Structures
How to build the structure of your transport or equipment may be the most important decision your organisation will take regarding the use of the Fleet solution. It is therefore necessary to evaluate your transport or equipment structure thoroughly before registering it and start using Fleet solution. The structure you choose will have effect on the use of all other functionalities in the application. It is possible to change a badly designed structure but it will require thorough investigation and the impact of a change may affect many support resources.
This process generates the baseline structures that are applicable to the transport or equipment types used by your organisation to conduct business. It also supports the function of status control to ensure that the transport/equipment owner can plan the utilisation of the transport/equipment properly. These configuration structures are representations of the physical assemblies of the transport/equipment. Structures are necessary for effective:
- Identification of a specific serialized component.
- Tracking the history of serialized components.
- Management of component exchanges.
- Management of implementing modifications for serialized components.
- Monitoring of material consumption of positions in a structure.
- Identification of the position where scheduled and adhoc work is done on the equipment.
Fleet solution uses the concept of a configuration structure, to build relationships between transport/equipment and define how these interrelate. This configuration structure is however not a Bill of Material (BOM), it has got a maintenance focus and is driven by how maintenance is performed, how history is to be gathered and transport/equipment tracking to be managed. To this extend it is also referred to as an “As Maintained Structure”.
The process is initiated when an instruction to create a new, or maintain a current configuration structure is received. The maintenance of a configuration structure may result from an engineering change or transport/equipment update. The same process is followed to create or maintain the transport/equipment structure and the first step is to define (open graphic display of structure) the top level description of the new structure.
Fleet: Hierarchical breakdown of transport/equipment structure
The hierarchical breakdown of transport/equipment structure follows the following decomposition pattern: (A vehicle is taken as an example)
The various sub structures are linked from "top-down" or “bottom-up” to construct the end object i.e. Vehicle.
The user can maintain a current object structure by either adding previous missing information or change existing information on the transport/equipment structure.
Part of the creation and maintenance process is to determine if the changes were accurate, complete and reasonable. The process includes format checks, completeness checks and reasonableness checks. The checking of configuration structures for correctness or compliance with applicable standards, rules and conventions is usually performed by an independent person.
A structure report can be drawn to view the new equipment composition to verify if the update or change is acceptable. The necessary corrections can be incorporated and re-submitted for validation purposes. Once the updates are acceptable, the status of the structure can be changed from Draft to Active.
This structure can be used as a "building block" to complete the current object structure. These "blocks" are re-usable within one or more object structures and the newly created or updated structure can be copied and added to another transport/equipment structure.
Description of Functionalities
Transport definition and structure (Object definition and Object Structure : For example : End-use vehicle)
- AND/OR -
Equipment definition and structure (Object definition and Object Structure : For example : Engine of vehicle)
Transport Object: Top level of object type and parent of the component e.g. Vehicle. This defines the create/maintain of transport definition (End use) and the top structure of the vehicle.
Transport/Equipment structure (Object structure)
Component: Child of transport/equipment but parent of sub component e.g. Engine. This defines the create/maintain of the child equipment structure position from the parent level.
Equipment structure (Object structure)
Sub Component: Child of component e.g. Starter. This defines the create/maintain of the child equipment structure position from the equipment component level.