ServiceNow Telco Suite consists of SOMT, TSM, FSMT, TSOM, SPMT and TNI. Most of the APIs exposed by these functions are currently covered and the few that are not covered like 651, 699, 652 etc. will be covered in the coming releases.
API exposure is by a function. If the function exposing the API (or even consuming) is not part of the ServiceNow suite, for e..g Usage management, Product rating etc. and their corresponding APIs ,will not be covered for the simple reason that ServiceNow is not a charging and billing platform. These APIs are exposed by a Charging and rating engine and not a CRM, Service Assurance, Field Service Management etc.
The list of APIs certified currently are
| TMF API # and name |
Application |
Comments |
| TMF632 Party Management |
CRM - Customer Foundation |
Used to create, manage and delete the customer Account and Account. The same API Is used since this is Party |
| TMF620 Product Catalog |
CRM - Customer Foundation |
Used to ingest products from other catalogs, partner catalogs asd the SOMT catalog will be master masrketplace catalog. Currently with SOMT. Needs to be moved to Foundation |
| TMF633 Service Catalog Management |
CRM - Customer Foundation |
API to create and manage the Service Catalog for the Service Specs. Currently with SOMT. Needs to be Foundational as the RFSS , RS etc., get modelled as CI classes to maintian the relationship between PI-Sold Product-Install Base Item with the CI classes |
| TMF637 Product Inventory Management |
CRM - Customer Foundation |
API to manage and get the Product Inventory Instance of the customer with a root - child relationship. Currently with SOMT. Needs ot be moved to Foundation |
| TMF688 Event Management |
CRM - Customer Foundation |
|
| TMF697 Work Order |
CRM -FSMT |
Exposed by FSMT and used by SOMT and TSM to trigger the work order either part of a Order task or Case task |
| TMF622 Product Ordering |
CRM - SOMT |
Exposed by SOMT to receive the Sales / Product Order from external CPQ/CRM |
| TMF641 Service Ordering |
CRM -SOMT |
In cases where offnet or partner orders are submitted as Service orders OMT can consume both PO and SO as the relevant Catalog entities like PS and CFSS are modelled in the PSR catalog |
| TMF645 Service Qualification |
CRM - SOMT |
Needs to be discussed. Exposure and instantiation of this API, and also location and site management |
| TMF648 Quote Management |
CRM -SOMT |
Exposed by SOMT to create and manage the Quote in a headless manne to enable an Omni Channel experince |
| TMF642 Alarm Management |
TSOM |
|
| TMF653 Service Test Management |
CRM - TSM |
TSM triggers and stores the result (Against the case?). Pls refer to comments on Site on the next worksheet. Exposure should be by the back end Assurance - Diagnostics. |
| TMF646 Appointment Management |
CRM - FSMT |
FSMT exposes the Appointment management for scheduling appointment during Order capture or Case management processes |
| TMF 621 Case Management |
CRM - TSM |
Case of type Case or TT can be created in TSM via this API. |
| TMF688 Event Management |
TSOM |
TSOM uses this for events |
| TMF639 Resource Inventory |
TNI |
For Network Resource instances i.e. the Allocatied resoures for a party (role = Customer, Business partner, Retail CSP) of both Physical and Logical resources managed inside TNI |
