Page
Summary:
A low cost proof-of-concept (POC) is a sensible, low risk approach
for deciding whether or not organizational time and resources
should be committed to an OSS reconciliation project. POC's typically
fund themselves and provide the Carrier with equipment and circuit
exception metrics relating to their unique network. The selected
sites are fully inventoried and reconciled, with BottomLine providing
the bulk of the labor.
Deciding
whether or not to move ahead with a comprehensive OSS (Operations
Support Systems) reconciliation is tough. Business cases need
to be developed and cost justified. Cross-functional teams must
"buy in" to the process. Daily production pressures cannot be
ignored, making it difficult to give the project any attention.
Many questions come to mind. Are things as bad as they seem? Would
the project actually make us money and make us more effective
- enough to make investing the time and money really worth it?
How can we measure whether or not the project is making money
or not? If we move forward with this project, will it just become
a cash drain to the organization? Are we biting off more than
we can chew here?
We at BottomLine Data Solutions (BDS) understand the anxiety that
accompanies the decision to commit an organization to a full-scale
OSS Network Reconciliation Initiative. The truth is, most
Management Teams will not sign-off on a project of this nature
unless the ROI (return-on-investment) is tangible and measurable.
We can provide you with the comfort that your business case projections
are sound.
BDS does not believe that you should commit to a project until
all parties understand the issues and the magnitude of a potential
problem. Some vendors say, "Give us the money and we will show
you later how much money you have made." In the days of shrinking
capital dollars this can lead to a lot of sleepless nights. Other
vendors present "Industry Statistics" or "Case Studies" from other
customers to justify moving forward with the greater project.
Unfortunately, the margin of error here is often high, and frequently
you are comparing "apples to oranges" - every Carrier is unique
and should be recognized as such.
That is why we recommend that all of our customers begin with
a low cost Proof-of-Concept (POC or beta study). A POC is targeted
in nature with BDS supplying virtually all of the labor. Two or
three mid-sized points of presence (POP's) are selected that "typify"
the network profile as a whole. All equipment and circuit information
relating to the POC Sites is audited via the BDS Solution, delivering
the following:
-
A
complete parent-child hierarchical profile of all equipment
at the site, including all related equipment data (CLEI, asset
tags, part numbers, etc.) and OSS Exception detail
-
A
complete cross-connect and circuit audit, including OSS Exception
detail
-
Comprehensive
Equipment and Circuit Impact and Error Analysis
Within
the confines of the POC, BDS still relies upon its tried and true,
proprietary '9 Step Equipment &
Circuit Reconciliation Process' (a process which has been
tested by completing full equipment and circuit audits and back
office corrections of literally hundreds of telecom facilities).
Moreover, the POC leverages BDS' proprietary software products.
However, the POC focuses its attention on the four stages (of
the nine) that precede the correction of the data in the OSS.
Those four steps are:
-
Determine
Project Scope: determination of what OSS/BSS will be in
scope, site/regional prioritization & scheduling, project
plan development, value schedule production, and metrics definition.
-
OSS
Data Mapped & Loaded: here, all relevant data sources
are identified, quality measures are developed and implemented,
and data mapping activities are initiated.
-
Field
Equipment & Circuit Validation: equipment polling
(if within scope) completed for all 'intelligent' devices,
retrieving equipment and cross-connect data. Non-intelligent
equipment and connections validated electronically in the
field via BDS mobile computing software platform.
-
Reconcile
OSS & Produce Reports: raw vs. audited equipment and
circuit data reconciled, and exceptions noted. Equipment,
circuit and financial exceptions measured and cataloged. Exceptions
further qualified as errors.
The
objective of a POC is not to make fixes in the OSS. The objective
of a POC is to obtain company-specific data to evaluate whether
or not the equipment and circuit discrepancies in the field, in
relation to the OSS, merit moving forward with a companywide effort.
Note: a POC does not typically include
billing and/or COGS reconciliation.
In
addition , a POC commonly pays for itself! Our clients are left
with the comfort they need to move forward with a full-scale implementation.
Our clients are also given the detailed information they require
(in the form of the BDS Solution Reports) to stamp the POC sites
"clean" from an equipment and circuit inventory perspective. Moving
forward with a POC just makes sense.
To discuss conducting a POC with
BottomLine, send an e-mail or call:
Steve_Adkins1@msn.com
360.607.4938
