 (TSG). While the project coordination group handles management activi- ties in 3GPP, the technical specification group develops standards and creates work groups (WG) for focused work on developing the standard in a specific area. To have "individual membership" with 3GPP, the individual must have membership with one of the organizational partners of 3GPP. The 3GPP has many standards defined on OAM&P (network management) including detailed implementation guidelines on FCAPS. For example, consider the 1999 release of "3GPP TS 32.111-2 version 3.4.0" on the alarm integration reference point. It specifies that an alarm needs to have two parts, the notification Header and alarmInformationBody. The parameters in the notification Header are: managedObjectClass: Class specific to managed object (an element or com- ponent of the element being managed) managedObjectInstance: Instance of the managed object notificationId: Unique id that can differentiate this alarm notification from another notification on same problem scenario of the managed object eventTime: The time at which the event occurred eventType and extendedEventType: Details of the type of event systemDN: The domain name of the system Some of the parameters in the alarmInformationBody are: probableCause: It provides information that supplements the eventType perceivedSeverity: The severity of the alarm Standardizing Bodies proposedRepairActions: How to fix the problem specified in the alarm additionalInformation: Information like the time the alarm was acknowledged The depth of defining the standard goes even further to the set of values that can be taken by some of these parameters, like perceivedSeverity, which can have values critical, major, minor, warning, indeterminate, and cleared. Another example of 3GPP specifications on FCAPS for a specific technology is "3GPP TS 32.409 version 7.1.0 Release 7," which gives information on the per- formance parameters for specific network elements in an IP multimedia subsystem (IMS). 3GPP is one of the leading organiz