CSM : Common Service Model

What is the purpose of Common Service Model?

The purpose of Common Service Model (CSM) is to establish, realise, maintain and facilitate the adoption and reuse of integration assets, namely the development of a modular architecture underpinned by strong API integration.

CSM is an API integration reference model.
It is realised using service-oriented architecture (SOA) principles and methodology.
And it is informed by foundation architectures and reference models, including:

  • Common Information Model (CIM)
  • Shared Information/Data Model (SID)
CSM is informed by foundation architectures and reference models, including Information Framework (SID).

CSM is informed by foundation architectures and reference models, including Information Framework (SID).

  • Business Process Framework (eTOM)
  • Common OSS/BSS Reference Architecture (COBRA)
  • Business Capability Architecture (BCA)
  • Telecom Application Map (TAM)

These reference artefacts describe the business, information and technology architectures in general.

CSM identifies the ‘landscape’ of APIs, or services, used to integrate companies business capabilities, applications and platforms, to support the enterprise’s objectives.

  • What is the Common Information Model?

  • The Common Information Model (CIM) is the key reference model underpinning our model. Our information model consisting of business concepts, their characteristics and relationships, described in an implementation independent manner. It acts as a language for different stakeholders to communicate effectively and precisely and provides a single common definition of important entities.*
  • Our information model is the standard used for developing our services (interfaces) between applications (IT systems). It extends TM Forum’s Shared Information/Data Model (SID), which provides a unified set of terms for business objects used in telecommunications.
  • What are the benefits of CSM?

  • The benefits of adopting Common Service Model for systems integration include:
  • Service reusability – services are designed with reuse in mind, so they can be positioned in many solutions without further modification
  • Standardised service contracts/interfaces – creating a catalogue of service specifications allows us to build up solutions from a list of pre-packaged functional modules
  • Service abstraction – the interfaces only contain the essential information required to invoke the service, hiding implementation specifics, allowing ‘wrapping’ of legacy applications
  • Loose coupling – systems are connected without intimate knowledge of how each other work, so they are decoupled from their surrounding environment
  • Integration projects adopting Common Service Model benefit through accelerated delivery, simplified architecture and reduced costs.
  • What are the capabilities of our CSM services?

  • CSM provides capabilities associated with entities, tasks and utilities modelled in our Information Model. CSM addresses ‘coarse-grained’ business scenarios in order to maximise applicability and reuse.**
  • Examples of CSM includes’Customer Bill’ (an entity service),’Bank Account’ (a utility service),’Check Customer Credit Rating’ (a task service).Standard of CSM provides ‘Create’, ‘Update’, ‘Delete’, ‘Get’, ‘Synchronise’ and ‘Notify’ operations. The operations exposed by each service depend upon the business context. Services identified in CSM landscape are realised in the form of a specifications set or ‘package’. Each service package includes ;
      • a business service specification (BSS),
      • technical service specification(s) (TSS),
      • a message blue-print (MBP),

    which may include mappings to providing platform(s), and a release note, together with the technical artefacts specifying the implementation(s) of the service.

    CSM supports Simple Object Access Protocol (SOAP) and representational state transfer (REST) implementations.

    WodenSoft is working to complete the CSM service catalogue in response to demand from integration projects adopting our model.

  • How can WodenSoft support your integration project?

  • The first step towards adopting CSM is to review and agree the proposed target integration architecture, with reference to the business and technical objectives of your project. We can help you to develop your target integration architecture and map the appropriate services to the interfaces in scope for your project. If a service contract needs to be mapped to a producing or consuming platform, WodenSoft can support this activity. Please contact us.
  • Ref:TM Forum’s Shared Information/Data Model