1

Inventory Mediation Solution

Proposal
Customer:

Understanding of the Project

Scope of the project aims at mediating the inventory feed from different source
systems to provide a normalised output to be used for Enrichment purpose. The
aim is to enable availability of relevant information by consolidating disparate
data points and providing a uniform format that can be consumed by concerned
systems/tools.

Proposed Solution: xFusion

The xFUSION- NOCOUT OSS platform designed by Teramatrix is a one stop
solution to revolutionize the offering delivered by the managed service providers.
The capability of the platform to capture the fast paced data in the real time and
presenting the data in an actionable format and notifications is one of the stand-
out features of the platform.
Teramatrixs xFUSION- NOCOUT OSS supports a powerful combination of Fault,
Configuration, Accounting, Performance, and Security functions, Service Level
Management, Ticketing, Provisioning, and Topology, with extensive customization
capabilities and extensibility across domains with multi-vendor and multi-
technology deployments. The solution integrates seamlessly with other OSS/BSS
systems, databases, and other management applications in the infrastructure.
The platform ensures the reliability, availability, and scalability of your critical
network elements by providing alerts and notifications based upon complex
escalation and workflow rules through its inbuilt rule processor.
For the current project, mediation capabilities spanning integration with multi-
vendor multi-technology touchpoints, rule engine, inventory module, scheduling
engine and authentication engine are to be used.

High Level Working

Considering the bottlenecks created due to huge inflow on information in any
Network and scarcity of adequate resources to convert this pileup of information
into a more usable knowledge base, experience shows that 30% or more time of
your valuable workforce is spent on managing data across multiple software and
manual interfaces deployed to visualize, analyse and optimize the enterprise
Network.
xFusion deploys a unique approach in network data collection. All filtering and
parsing is handled inside the network by xFusion Adapter (Integration with
EMS/OSS/Other Systems). By separating collection and parsing from post-
processing and analysis, xFusion improves the overall performance while
reducing management overhead and time to resolution.
2

Once the xFusion Adapter module receives or fetches data points from
EMS/OSS/Other systems or NE directly, TRANSLATOR, the smart filtering agent,
outlines the underlying structures hidden inside those unstructured streams. The
filtered and structured data then travels to the processing agent, over one-way,
secure channels. On the go, complex network data processing techniques results
in refined and actionable data points, that are relevant to the operational
context, and is provided for future accessibility.

Integration Capability
xFusions protocol stack comprises of most commonly used network protocols
used to make communication between the network devices as well as from EMS
or existing OSS tools.

Southbound and Northbound Integrations

The flexible protocol stack of xFusion is comprised of most commonly used
network protocols used to make communication between the Network Element/
Element Management System (EMS)/Devices/CPEs/Routers/etc. and xFusion.
Protocol stack would also provide out of the box support for integrating new
protocols as required. Some of the standard protocols used are:
SNMP: Simple Network Management Protocols (v1, v2, v3), responsible for
collecting the network device statistics and status as well as applying the
configuration on the network devices.
CORBA: The Common Object Request Broker Architecture (CORBA) is a
standard developed by the Object Management Group (OMG) to provide
interoperability among distributed objects. CORBA is the world's leading
middleware solution enabling the exchange of information, independent of
hardware platforms, programming languages, and operating systems.
CORBA is essentially a design specification for an Object Request Broker
(ORB), where an ORB provides the mechanism required for distributed
objects to communicate with one another, whether locally or on remote
devices, written in different languages, or at different locations on a
network.
ICMP: To monitor the heartbeat of a deployed host in the network or to
collect the RTT of the deployed host.
SSH/Telnet/TCP/IP: For configuration management of the device via console
HTTP/CGI: Accessing the web application server in the device
Syslog: System logs of the deployed network hosts
FTP: To transfer large files on the network, between Solution and the
deployed network devices.
OSI (Q3/CMIP): Q3 is an interface protocol for national telecommunication
management and CMIP defines services for accessing information about
network objects or devices
3

JMS: Communication between a JMS client and Server over TCP/IP

API: xFusion APIs provides a uniform interface and facilitates quick
interface development towards and from other 3rd party systems. xFusion
is equipped with customizable adapters that enable xFusion to seamlessly
integrate to different API formats, be it Restful API, XML, JSON, etc.
4

Proposed Solution Architecture

Project Schedule
Timeline

Baseline Start Date: Release of PO and Platform License Cost

Delivery Methodology, Dependencies and Assumptions

Project will follow an Agile Delivery methodology, with minimum Sprint
length of 2 weeks
ABCD to ensure availability of stakeholders for clarifications, as necessary
Single point of contact from ABCD will be available to TTPL team from the
start of the engagement. The contact will be responsible for overall
5

engagement governance, managing communications with Business (and

other Stakeholders) and facilitating meetings with Business.
It is assumed that required environment and permission shall be made
available to TTPL project team for the development and testing by ABCD.
Readiness of corresponding environment required for each phase of the
project has to be ensured by ABCD
For all activities of integration with third party systems, ABCD will be
responsible to provide the required APIs/Touchpoint interfaces.
Connectivity, provisioning, configuration, porting, assignment of required
permissions, applications, interfaces, ports, servers, will be responsibility
of ABCD.
It is assumed that data from third-party system is responsibility of ABCD.
This is a mediation requirement, TTPL will not engage in correction of any
faulty data points. The required details about data and appropriate
mappings are to be provided as Business/IT inputs to TTPL. Mappings not
covered in Design will be treated as Change Requests.
The solution implementation would be considered as Accepted, when the
solution functions free of S-1, S-2 faults for a period of 4 weeks
Remote Access and permissions are to be extended to TTPL team for
development and production environment for configuration,
customisation, development, deployment and support activities.
All third party license components will be borne by ABCD. TTPL and ABCD
will jointly identify the applicable Third party components

Schedule of Payment

ABCD will make the payment to Vendor within 30 days of receipt of invoice
from Vendor.
All fees and expenses are payable in INR (Indian Currency). All fees
payable to Vendor are exclusive of any sales, use, value added tax or
service taxes measured by the Services, Deliverables or charges thereon,
imposed by any applicable taxing jurisdiction and where such taxes are
applicable, ABCD shall be responsible to pay or reimburse Vendor the
amount of such taxes. Where applicable, Vendor shall invoice such taxes
as a separate line item in applicable invoices and shall pay such amount of
tax to the appropriate taxing authority upon receipt of such amount from
ABCD.
This cost includes License AMC and remote Support,
Operational and On-Site Support will be over and above.
ABCD will bear the charge of any obligations for the usage of third party
systems/components
Payment Terms:
o Platform License Cost with PO
o Configuration Component: 10% on Design Sign-Off, 40% on
Integration Testing Report, 40% on UAT, 10% on Deploment
6

xFusion Advantage
xFusion Introduction
xFusion, allows data driven companies to analyse and correlate massive
data emanating from millions of sensors, devices and applications on their
networks resulting in greater Customer Satisfaction, Operational efficiency
and Revenues.
Awards for Excellent Innovative Telecom Service Assurance Solution
Won CMAI IoT Innovation Award
Indias Top 20 IoT Company CIO Review

Integration List
7

Platform Scalability
Scalability refers to the number of users, sessions, transactions, and operations
that can be accommodated by the entire system. Simply put, scalability is about
doing what you do in a bigger way: Scaling a Web application means allowing
more people to use the application by growing it to meet growing demand,
without changing the code or sacrificing the data affinity and service levels your
users demand. Why is scalability important? Because, in the end, you ideally
want to build an application that can serve millions of users with zero downtime.
Several organizations build a jumble of applications that dont conform to set
standards and dont share a cohesive deployment pattern. This reduces their
ability to iterate on product development and thereby creates a lag in business.
Adopting a scalable platform architecture that covers all applications is a way to
solve this problem.
The platform scalability will be facilitated by scaling the hardware and no
dependency would be on the core platform. The 3rd party software would also be
deployed with the new hardware and respective BOM would be provided as and
when required. xFUSION- NOCOUT OSS is highly scalable, so as the number of
devices being managed increases, so ISPs can scale up the xFUSION- NOCOUT
OSS. Teramatrixs xFUSION- NOCOUT OSS enables service providers to manage
from a very small number of devices through to many millions. xFUSION-
NOCOUT OSS is scalable for both, a comprehensive, distributed networking
solution and have flexibility to manage critical systems by providing rapid
solution.

Robustness of the Architecture

There is always an uncertainty of errors while working with a huge network with
many devices undergoing the processes like monitoring, data aggregation,
analytics and etc. The host system performing the above mentioned processes
should be robust enough to handle such load.
xFUSION- NOCOUT OSS has been developed keeping these important parameters
in mind, our platform is based on a robust architecture that can work efficiently
with huge device networks.
Some key highlight points defining robustness of the architecture that supports
the solution are:
Easily Build and deploy secure, scalable applications
Independent modules with dedicated communication bus
Supports open communication protocols for seamless integration to third
party systems
Latest UI/UX tech for rich and interactive interfaces customizable for web
and mobile
Develop powerful application controllers with URLs to ensure application
robustness
Produce a clean, maintainable code base using the MVC architecture
Design rich client and mobile user interfaces with Ajax and jQuery
Secure applications with latest encryption, authentication and role-based
authorization
Automated Testing controllers and views with load and performance
testing mechanism
Generating dynamic views and Grids, Interactive Charts and Graphs
8

Rapid development cycle with Agile Methodology

Regular feature updates, bug control and patch release
High performance, flexible and capabilities on distributed Architecture
Reliable, secure, Scalable support for all major industry standard Database
Possibility to store large volumes of data.
High performance on limited hardware resources
Support High Availability and Disaster Recovery Features
Continuous Integration (CI) practices for faster and robust future releases.