This is the root element of the information required by management when a system requires maintenance. Choice allows for two different maintenance scenarios. If General Maintenance is selected, no anomaly should occur. If their is an anomaly, then an action must be taken. Scheduled or unscheduled maintenance not related to an operational anomaly. These commnets include technician actions and observations that would be required for historical information. The status of the action should also be mentioned. A description of the perceived failure. Description of the anomaly that either came from the system or the operator. Multiple anomalies can occur for a single action. System generated anomaly received from a bit error or the Data Transfer Module (DTM). Operator generated anomaly sent to maintenance control by the operator or maintenance crew. Action(s) taken as a result of the discovered failure(s). Work required to restore the unit in an operational state. Authorized/approved repair effort for given UUT initiated. These commnets include technician actions and observations that would be required for historical information. The status of the action should also be mentioned. Reason(s) for failure is determined during repair of items exhibiting trouble symptoms. The removal of a component required to initiate a repair. Manufacturer support program. Repair facility/capability documented. These commnets include technician actions and observations that would be required for historical information. The status of the action should also be mentioned. Installation of a component required to complete a repair. Manufacturer support program. Repair facility/capability documented. These commnets include technician actions and observations that would be required for historical information. The status of the action should also be mentioned. All necessary info (tech manuals, equipment data, personnel, training needs, etc) used during the maintenance action. May be a pointer to a Test Configuration document, or some other equipment-specific documentation. All relevant data required to support maintenance action transaction. Lists all the latest and approved tech manuals that support maintenance. Comments that are relevant to the maintenance process. Document unique maintenance action. Summary of repair actions taken and part involved. Cause encompasses a debriefing session or during system operation or during maintenance activity or inspection. Symptoms for removal: Reason for removal group: removal of malfunctionitems for repair. Occurance duritng system operation Conditional group: When a nondefective item is removed or when the malfunction is not the fault of the item in question. The reason for not being able to perform the required maintenance on the unit. Reason for repair delay Identifies the failed Items parent system, subsystem, major component, subassembly or part of the end item.