TMF ODA Support and Compliance

Intro

This section describes how the IMS platform aligns with the TM Forum Open Digital Architecture (ODA) model. It outlines the direct correspondence between IMS components and specific TMF ODA Building Blocks, and evaluates compliance with the relevant TM Forum Open APIs.

• Product Inventory component corresponds to the TMF ODA Building Block C005, effectively supporting comprehensive product management capabilities in line with the TMF637 API standard.
• Service Inventory component corresponds to the TMF ODA Building Block C008, enabling complete lifecycle handling of service instances while ensuring compliance with the TMF638 API specification.

This mapping ensures that the IMS platform delivers the expected inventory management functionalities defined by TM Forum, while maintaining alignment with industry-standard Open APIs. Our objective is to guarantee modularity, interoperability, and telecom-grade readiness, fully aligned with TM Forum best practices.

ODA Concepts in IMS

The IMS architecture is highly modular and naturally aligns with the ODA paradigm. Each major domain is implemented as an independent microservice, mapped to a well-defined business capability. The platform extensively leverages TMF Open APIs to ensure integration readiness with external systems.

ODA Mapping Table

Highlights

Product Inventory

Three components: ims-tmf-pi-model, ims-tmf-pi-gateway and inventory-service provide comprehensive TMF637 functionality, except for the following event-listener and partial-update endpoints: POST /listener/productAttributeValueChangeEvent, POST /listener/productProductBatchEvent, PATCH /product/{id}.

Service Inventory

Three components: ims-tmf-si-model, ims-tmf-si-gateway and inventory-service provide comprehensive TMF638 functionality, except for the following event-listener and partial-update endpoints: POST /listener/serviceAttributeValueChangeEvent , POST /listener/serviceOperatingStatusChangeEvent, PATCH /service/{id}.

Modular Deployment

Both the Product Inventory and Service Inventory modules are designed as independent, hot-deployable services. This modularity enables selective scaling, rolling updates of individual building blocks, and incremental introduction of event-driven listeners without disrupting core TMF API operations.

Summary

The IMS architecture demonstrates strong alignment with the ODA model:

• Core building blocks are fully supported through dedicated components that ensure broad TMF Open API compliance.

• Product Inventory and Service Inventory building blocks leverage TMF APIs effectively, ensuring interoperability, integration readiness, and flexibility in adapting to specific business needs. Although the platform is capable of supporting the full scope of TMF standard fields, such comprehensive implementation is adjusted based on practical business requirements.

• Custom components within IMS, such as internal orchestration layers and service models, follow modular and ODA-compliant design principles, utilizing APIs and messaging to ensure scalability, autonomy, and ease of maintenance.