 documents can be downloaded from the Web site GB922 and GB926: SID Solution Suite GB932 and GB933: CIM-SID Suite 2. John P. Reilly. Getting Started with the SID: A Data Modeler's Guide. Morristown, NJ: TeleManagement Forum, 2009. 3. Distributed Management Task Force (DMTF) CIM Tutorial at: www.wbemsolutions com/tutorials/CIM/ 4. Chris Hobbs. A Practical Approach to WBEM/CIM Management. Boca Raton, FL: CRC Press, 2004. 5. John W. Sweitzer, Patrick Thompson, Andrea R. Westerinen, Raymond C. Williams, and Winston Bumpus. Common Information Model: Implementing the Object Model for Enterprise Management. New York: John Wiley & Sons, 1999. Chapter 25 Standard Interfaces This chapter is about OSS interfaces for interaction. Two of the most popular information models in telecom domain, Multi-Technology Operations System Interface (MTOSI) and OSS through Java Initiative (OSS/J) are discussed in this chapter. How these two standards can complement each other is also covered in this chapter. 25.1 Introduction There are multiple operation support systems currently available in the telecom market. In a service provider space, multiple OSS solutions need to interoperate seamlessly to reduce operational costs and improve operational efficiency. To make this possible the interfaces for interaction need to be standardized. Most OSS solu- tion developers are making their products compliant to MTOSI or OSS/J interface standards. In current industry, compliancy to standards is more a necessity. Let us take a simple example of a simple fault management module. Now the network provision- ing module might request active fault alarms using the interface call "getAlarm- List ()," the inventory management module might request active fault alarms using the interface call "getActiveAlarms ()," and the event management module might request active fault alarms using the interface call "getFaultLogs ()." On the other end, the fault management module might be exposing the interface getActiveFault () for other modules to query and get the activ