s pro- cesses defined in the eTOM. A combination of SID and eTOM provides the requi- site materials that will help an enterprise to achieve its business goals. The SID framework organizes information in a business view using business entities. The definitions using SID are made as generic as possible to promote reuse. The layered framework in SID helps to logically partition data relating to specific domains. The use of business oriented UML class models makes it easy to work with SID. The domains of SID align with the business framework of eTOM. Creation of domains enables segmentation of the total business problem and allows TMF teams to be focused on a particular domain of interest. When the resultant busi- ness entity definitions within each domain are used in conjunction with the eTOM business process framework, it will provide a business view of the shared informa- tion and data. Aggregate business entities allow further partitioning of the informa- tion within each domain. The business entities, attributes, and relationships are detailed with textual descriptions in each SID addendum. SID provides a consolidated Rational Rose UML based model that characterizes the entities to a model that can be easily understood for implementation of business applications. Information Models The ABEs are organized using a categorization pattern. This ensures consis- tency of the ABE content and structure within each domain. The managed entity categories include: Strategy and plan specification: This is a description of the managed entity that is used to build the entity. Interaction: Any business communication with the managed entity is termed an interaction. Price: This signifies the cost of a managed entity. Configuration: The internal structure of a managed entity is its configuration. Test: This is the operation performed to identify the state of the managed entity. Trouble: Any problem like faults and alarms associated with the managed entity is referred to as trouble. Usage: This is the period of time during which a