| Business DEX (NOLITO003):— Gripen_task_spec | Date: 2008/12/08 19:49:15 Revision: 1.13 |
The Product variant is identified, e.g. "39ENoK1". There are no revisions of product variants, revisioning is managed on the configuration baseline.
The Product Configuration Baseline is identified (e.g. "AC39ENoK1_CIN_breakdown"), and has a revision (e.g. "8830.04-44.0;1"). It also has a relationship to the Product Variant.
A Configuration Item Node is identified (e.g. "JS-CI-00057") and has a revision ("1"). It is related to the Product Configuration Baseline version.
An Equipment has an identifier, e.g. "9307009-601", and a revision ("B").
A Maintenance Object has an identifier (e.g. "A37-10-00-00A"), a revision ("20"), a name ("Tank, fuel"), and is of a certain type:
The Maintenance Object has a relation to either a Configuration Item Node or an Equipment (or Subequipment), although this relation is instantiated via an external, hand-made mapping table since there is no information in the Saab systems for this relationship.
A Maintenance Action has an identifier (built up by concatenating the Maintenance Object ID and revision with the Maintenance Action's "action code", e.g. "A37-00-00-00A,20,320B"), and a name (e.g. "Fuel system check"). It is classified as either a corrective or preventive maintenance action, and if there is some environmental risk in performing the action, it is described and assigned to the maintenance action.
The maintenance action is designed to be performed at a specific Maintenance Level (e.g. "O", "I", or "D", each corresponding to a certain Base, Hangar or Supplier workshop), and has always a relation to the Maintenance Object it describes. It is possible to relate documents to the maintenance action, e.g. for reference. A document is identified and has a description.
The maintenance object is described in a series of Subtasks, or steps. They are ordered sequentially, and each Subtask is identified (e.g. "356889", "356890", etc). A subtask contains a description of the step, and is classified as one of the following:
A Subtask may also have an estimated duration, or carry out time. It is a time estimate given in hours, minutes, or seconds.
A Subtask defines a number of resources that are required for the performance of the subtask. Required resources can be many different type of things, such as a facility, infra structure, or environment that is required, spare parts and consumables that are needed, and tools (support equipment) that are required to perform the activity.
Resources are classified as one of:
Sometimes in ILS-DB, it is impossible to know what type of resource it is. Those resources are classifed as "Required material resource".
A requirement for a facility, infra structure, or environment is assigned to the Subtask, and is defined in a document (publication) specifying the actual requirements. Such a document is identified and has a description.
A spare part, a consumable, or a tool that is required for the performance of a Subtask are identified as a resource for the Subtask. This resource may be identified using a NATO stock number and NATO stock name. In the assignment of the resource to a specific Subtask, the required resource may be quantified, e.g. "4 pieces", or "0.25 litres". It is realized as a Part, identified by a Saab part number and with a part name. The Part may be classifed regarding Maintenance Start :
A Maintenance Action may have a scheduled or even-based intervals in the relation to the Maintenance Object it describes. There are two basic types of intervals given, the in-service interval and the in-storage interval. Additionally, the Total Interval is regardless of if the product in focous is in-operation or in-storage. Sometimes, the interval is described in a text string that cannot be interpreted as the above, and it is then called "other maintenance action interval".
A Maintenance Interval should be classifed as either scheduled or even-based interval. if it is a scheduled interval, the value of the interval is given as a numerical maximum value. For an even-based interval, the state or event (e.g. fault mode) is defined rather than an interval maximum value.
The end item context for the maintenance action (task) is simply a classification of wether the activity is to be performed on the aircraft ("ON"), or off of it ("OFF"). The class "on aircraft" implies that the end item cannot be used or operated as long as the maintenance task is performed.
The task administrative information is basically the ILS-DB Configuration Edition. The Configuration Edition is identified much like the Configuration Item Baseline, using the Saab "seriestatus" as the key, and it has a revision.
The Configuration Edition is related to the Configuration Item Baseline, and to the Maintenance Objects that is part of the Configuration Edition.
The actual message, the exchange file definition or envelope, has an identifier so it can be distinguished from other messages. It defines the sending and receiving organizations (Saab Aerotech and 'Norwegian Defence Logistics Organization' respectively), and the date and time of data extraction. It also identifies the contract under which the data exchange takes place. For the NOLITO project, the contract is identified as "NOLITO".
© Saab AB 2010 — All rights reserved