TIP Service Management ABE

The TMF Interface Program introduced in the Multi-Technology Operations System Interface (MTOSI) 2.0, Service Management interfaces based upon extensions to the SID service model in this ABE. The resulting solution set introduced two new service management activation interfaces, and a service inventory interface.<br/> <font color="#e0121d"><b>Introduction</b></font><br/><ul>
<li><font color="#29313b"><i>Note: TMF Interface Program (aka TIP) is legacy stuff to define interfaces and interfaces are now defined by the Open API Program.</i></font></li></ul>
<font color="#29313b"><br/></font><font color="#29313b">The TMF Interface Program (aka TIP) introduced in the Multi-Technology Operations System Interface (MTOSI) 2.0, Service Management interfaces based upon extensions to the SID service model. The resulting solution set introduced two new service management activation interfaces, and a service inventory interface:</font><br/><ul>
<li><font color="#29313b">The Service Activation interface (SAI) between the Customer Relationship Management (CRM) and Service Management and Operations (SM&O) layers allows for the activation of Customer Facings Services (CFS)</font></li><li><font color="#29313b">Interactive Service Activation </font></li><li><font color="#29313b"><i>Best-effort Transaction interface </i>Service requests entailing multi-task transaction execution. In this type of interface, the entire transaction execution is completed despite single task failures. </font></li><li><font color="#29313b"><i>Atomic Transaction interface </i>This interface has the same operations as the previous one; however, the failure of any single task will incur the termination of the transaction execution and will invoke a roll-back of the preceding task.</font></li><li><font color="#29313b"><i>Service Order Management interface   </i>Add-on interface to both the Best-effort Transaction or Atomic Transaction interfaces. Provides full exposure and control of the service order associated with the service request over the interface. It depends on the functions provided by the previous interfaces.</font></li><li><font color="#29313b">The Service Component Activation interface (SCAI) is an internal SM&O layer interface. It allows for the activation of Service Components, also known as Resource Facing Services (RFSs), given specific service related information defined in a Service Template. The SCAI, contrary to the SAI, has no knowledge of the product domain.  </font></li><li><font color="#29313b">The Service Inventory interface supports the retrieval of service related entities from a Service Inventory repository. </font></li></ul>
<font color="#29313b">The TIP Service Management ABE provides the extensions made to the SID model in support of the new Service Management interfaces introduced. The basic <i>service </i>and <i>service specification</i> concepts as defined in this addendum remain unchanged, and are merely enhanced to support the TIP Service Management interfaces.</font><br/><br/>