The description of an FIS template is split into modules. Each module has: a. Module name: This uniquely identifies each module. b. Datatypes: The attributes associated with the module are listed in a table with attribute name in the first column in the table. The other columns are "Set By" describing whether EMS, NMS, or both can set the attribute, when and how the attribute was set, the format of the attribute that could be a fixed format or a list of values and a final column called "Clarification Needed" for specifying the length requirements of the attribute. Attribute Set By Set When and Format Clarification Needed Interfaces: The operations associated with the module are listed in a table with the name of the operation in the first column of the table. The other columns include status to check if the operation is mandatory or optional, if any additional support is required in the operation, the exception or error codes that can occur in the operation, and the final column is to add any additional comments on the operation. Operation Status Support Exception/Error Reason Comments Notifications: Notifications can be of different types and each of them are discussed separately in TMF 814A. It starts with the alarm probable cause. The requirements of probable cause can be defined in a table with fields that even gives information on the severity of the alarm. Threshold crossing alert is another notification in which thresholds are set on the values of configuration and performance attributes. Crossing of the threshold value generates notifications of the requirements that can be defined in a specific way that both system vendor and service provider can understand. Some of the other notifications for which TMF 814A gives guideline to define specifications are attribute value change (AVC) for change in the value of an attribute, object creation in information tree, object deletion from the tree, and a generic discussion for any other form of notifications. 2. Nonfunctional implementation statements (NIS): As the