1 Scope
1.1 Functionality
1.2 Field of application
1.3 Document structure
2
Normative References
2.1 Identical Recommendations | International Standards
2.2 Paired Recommendations | International Standards equivalent in
technical content
2.3 Additional References
3
Definitions
4
Abbreviations
5
Conventions
5.1 Use of graphic string syntax
5.2 Use of list in attribute labels
5.3 Labelling conditional packages
5.4 Describing parameters in primitives
6
Requirements
6.1 Trouble management report creation
6.2 Tracking trouble management reports
6.3 Management of trouble management reports
6.4 Trouble management report clearing and closure
7
Model description
7.1 Introduction
7.1.1 Instantiation of troubles reports
7.1.2 An overview of the trouble management
objects model
7.1.3 Trouble report states and status
7.2 Model components generic definitions
7.2.1 Object class definitions
7.2.2 Attribute type definitions
7.2.3 Error messages
8
Service description
8.1 Introduction
8.2 Kernel functional unit
8.2.1 Enter Trouble Report
8.2.2 Request Trouble Report Status
8.3 Request Trouble
Report Format Functional Unit
8.4 Trouble History Event Notification Functional Unit
8.4.1 Trouble History Event Notification
8.4.2 Parameters
8.5 Review Trouble History Functional Unit
8.6 Add Trouble Information Functional Unit
8.7 Trouble Report Status/Commitment Time Update Notification
Functional Unit
8.7.1 Trouble Report Status/Commitment Time
Update Notification
8.8 Verify Repair Completion Functional Unit
8.9 Modify Trouble Administration Information Functional Unit
8.10 Trouble Administration Configuration Event Notification
Functional Unit
8.10.1 Attribute Value Change Notification
8.10.2 Object CreationNotification
8.10.3 Object Deletion Notification
8.11 Trouble Report Progress Notification Functional Unit
8.11.1 Trouble Report Progress Notification
8.11.2 Parameters
8.12 Cancel Trouble Report Functional Unit
8.13 Extended Modify Trouble Administration Information Functional
Unit
8.14 Delete Telecommunications Trouble Report functional unit
8.15 Refer Telecommunications Trouble Report functional unit
8.16 Transfer Telecommunications Trouble Report functional unit
8.17 Update State and Status functional unit
8.18 Repair Activity Object Functional Unit
8.19 Provider Trouble Report Control Functional Unit
8.20 Summary of functional units
9
Service mapping to Protocol
9.1 Element of procedure
9.1.1 Trouble History Event Notification
Service procedures
9.1.2 Trouble Report Progress Notification
Service procedures
9.2 List of items having templates in Annex A and Recommendation
X.721
9.2.1 Objects
9.2.2 Attributes
9.2.3 Notifications
9.2.4 Actions
9.3 Negotiation of functional units
10 Relationship with other Standards
11 Conformance
11.1 Static conformance
11.2 Dynamic conformance
11.3 Management implementation conformance statement requirements
11.4 Conformance to the general purpose platform profile for CCITT
Rec. X.733 | ISO/IEC 10164-4
11.5 Conformance to support managed object definition
Annex A – Managed objects
A.1 Managed object class and package definitions
A.1.1 Account
A.1.2 cnmService
A.1.3 contact
A.1.4 providerTroubleReport
A.1.5
repairActivity
A.1.6 service
A.1.7 telecommunicationsTroubleReport
A.1.8 troubleHistoryRecord
A.1.9 troubleReport
A.1.10 troubleReportFormatDefn
A.2 Attribute definitions
A.2.1 Account contact list
A.2.2 Account name
A.2.3 Activity code
A.2.4 Activity duration
A.2.5 Activity info
A.2.6 Activity person
A.2.7 Additional text
A.2.8 Additional trouble info list
A.2.9 Additional trouble status info
A.2.10 After hrs repair auth
A.2.11 Agent contact person
A.2.12 Agent contact object ptr
A.2.13 Alarm record ptr list
A.2.14 Alternate manager contact person
A.2.15 Alternate manager contact object ptr
A.2.16 Applicable managed object class list
A.2.17 Applicable managed object instance list
A.2.18 Authorization list
A.2.19 Begin time
A.2.20 Call back info list
A.2.21 Called number
A.2.22 Cancel requested by manager
A.2.23 Close out narr
A.2.24 Commitment time
A.2.25 Commitment time request
A.2.26 Contact company
A.2.27 Contact details
A.2.28 Contact function
A.2.29 Contact id
A.2.30 Contact names
A.2.31 Contact
object ptr list
A.2.32 Contact type
A.2.33 Close out verification
A.2.34 Cust trouble tick num
A.2.35 Customer work center
A.2.36 Dialog
A.2.37 Electronic mail address
A.2.38 End time
A.2.39 Entry time
A.2.40 Escalation list
A.2.41 Facsimile telephone number list
A.2.42 Hand off
center
A.2.43 Hand off location
A.2.45 Hand off person name
A.2.46 Hand off person ptr
A.2.47 Hand off time
A.2.48 Initiating mode
A.2.49 Last update time
A.2.50 A location access address
A.2.51 Z location access address
A.2.52 A location access hours
A.2.53 Z location access hours
A.2.54 A location access person
A.2.55 Z location access person
A.2.56 Maintenance org contact name
A.2.57 Maintenance org contact ptr
A.2.58 Maintenance org contact time
A.2.59 Maint service charge
A.2.60 Managed object access from time
A.2.61 Managed object access hours
A.2.62 Managed object access to time
A.2.63
Managed object instance
A.2.64 Managed object instance alias list
A.2.65 Manager contact person
A.2.66 Manager contact object ptr
A.2.67 Manager search key1
A.2.68 Manager search key2
A.2.69 Manager search key3
A.2.70 Manager search key list
A.2.71 Outage duration
A.2.72 perceived trouble severity
A.2.73
Preferred priority
A.2.74 Received time
A.2.75 Related trouble report list
A.2.76 Repair activity
A.2.77 Repair activity list
A.2.78 Repeat report
A.2.79 Responsible person name
A.2.80 Responsible person ptr
A.2.81 Restored time
A.2.82 Service alias list
A.2.83 Service description
A.2.84 Service location list
A.2.85 Service Id
A.2.86 Service type
A.2.87 Supported service name list
A.2.88 Suspect object list
A.2.89
Telephone number list
A.2.90 Trouble clearance person
A.2.91 Trouble detection time
A.2.92 Trouble found
A.2.93 Trouble location
A.2.94 Tr constrained to single value attr id
list
A.2.95 Trouble report format object ptr
A.2.96 Tr format id
A.2.97 Trouble report id
A.2.98 Tr must be present attr id list
A.2.99 Tr may
be present attr id list
A.2.100 Trouble report number list
A.2.101 Trouble report state
A.2.102 Trouble report status
A.2.103 Trouble report status time
A.2.104 Trouble report status window
A.2.105 Trouble type
A.2.106 Tsp priority
A.2.107 Type text
A.2.108 Unavailable service ptr
A.3 Error messages
A.3.1 Trouble Report Already Exists
A.3.2 Fallback Reporting
A.3.3 Can Not close
A.3.4 Trouble Report Must Be Present Attribute
Missing
A.3.5 Cannot Verify or Deny at This Time
A.3.6 Trouble Report Change Denied
A.4 Events
A.5 Name Bindings
A.6 Abstract syntax
A.6.1
A.7 Rules of extensibility
Appendix I – Scenarios
I.1 Introduction
I.1.1 Trouble management environment
I.1.2 Trouble management roles
I.2 Creation of a trouble report
I.3 Processing and tracking of the trouble report
I.3.1 Clearing of the trouble report
I.3.2 Closure of the trouble report
I.3.3 Cancelling of the trouble report
I.4 History notification
Appendix II – Further work
II.1 Additional
requirements not met in this Recommendation
II.2 Future work
Appendix III – Overview of the service model
Appendix IV – Trouble report format examples
Appendix V