We are using extended version of TeleManagement (TM Forum)’s Shared Information/Data Model called as CSM (Common-Service-Model) in our design architecture, which provides a unified set of terms for business objects used in telecommunications.
With the Shared Information/Data (SID) model, the TM Forum has developed a common language for enterprise operations in the telecommunications industry. The TM Forum added XML Schema Definition (XSD) representations to the original Unified Modeling Language (UML) definitions for the SID model. The SID XSDs are an important advance, providing the basis for developing reusable data models for integrated business applications.
CSM provides key support for building robust integrations that gain the value of the SID as a common data model to promote speed, agility, reuse, and data quality in integration projects for operational and business support systems (OSS/BSS).
5 things you can do with our model which is based on extended version of TM Forum’s Information Framework:
- Reduce integration costs by adopting standards-based information models and using them in applications and interfaces
- Save hundreds of design hours by starting with a mature framework and 1500 entities developed and vetted by subject matter experts
- Speed time to market by using well-understood integration interfaces based on the Information Framework, eliminating the need for data translation between systems
- Avoid wasting precious development time on debates with your team, partners, or vendors by adopting a widely proven, industry accepted, rich and extensible information model
- Mandate conformance to the Information Framework and save time and money during vendor evaluation and procurement
FAQs about our architecture
- What is the purpose of Common Service Model?
- What is the Common Information Model?
- What are the benefits of Common Service Model?
- What are the capabilities of CSM services?
- How can WodenSoft support your integration project?
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.
CSM is realised using service-oriented architecture (SOA) principles and methodology.
CSM is informed by foundation architectures and reference models, including:
- Common Information Model (CIM)
- Shared Information/Data Model (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 Common Service Model?
- The benefits of adopting CSM 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 CSM benefit through accelerated delivery, simplified architecture and reduced costs.
What are the capabilities of 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.**
- The operations exposed by each service depend upon the business context.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.