Presently,
BottomLine Data Solutions (BDS) offers Carriers three Solutions
that involve the movement of data to/from a foreign data environment
(i.e.: provisioning system, leased line database, fixed asset
record, billing system, etc.). These Solutions are Net
Sync, Net Load, and Net
Trak™.
Understanding
how the system (OSS - Operations Support Systems) data flows through
the respective BDS Solution is critical to comprehending the ultimate
reconciliation process. This page provides both a visual, and
brief narrative explanation of the data flow process attributed
to each Solution.
Figure
1: Net Sync™
NET
SYNC DATA FLOW
Data
enters the Net Sync environment (Step 1A above) through API import
(i.e.: MetaSolv), and/or mapping via the WiseExtract module of
the BottomLine CircuitWise software. Auto-poll equipment and cross-connect
data (Step 1B) is also received by WiseExtract, with all data
then being stored in the NetSync Database (Step 2). In Step 3,
Network Facility equipment and circuit audit files and equipment
catalog files are produced in support of field equipment and circuit
validation activities. During Step 4, the field validation activities
are completed, with the post-audit data (Step 5) then being electronically
transmitted back to the Net Sync Database for reconciliation purposes
(Step 6). In Step 7, the WiseAnalyze Reconciliation Engine analyzes
the OSS data (pre-audit) in relation to the post-audit data to
arrive at the exceptions (Step 8). In Steps 9A/9B, exceptions
are validated by a qualified Data Administrator
who then either pushes corrections back into the OSS (assuming
no conflict) and/or makes corrections directly from the WiseAnalyze
exception reports.
_________________________________________________________________________
Figure
2: Net Load™
NET
LOAD DATA FLOW
Although
the data flow within Net Load may appear quite similar to that
of Net Sync, Net Load has been designed with a very different
purpose. With Net Load, the ultimate repository of the validated
equipment and/or circuit data may be completely or largely empty.
Net Load is intended to support:
1.
Greenfield system implementation
2. Targeted data update or introduction
3. System conversion
4. System upgrade
5. Load of acquired network properties
6. Load of individual network locations
That
being said, here network equipment and circuit configurations
are produced essentially "from scratch". Therefore equipment
specification/parts catalog data only (Step 1 above) enters
the Net Load environment either through API import (i.e.: MetaSolv),
and/or mapping via the WiseExtract module of the BottomLine CircuitWise
software. Auto-poll equipment and cross-connect data (Step 1B)
is also received by WiseExtract, with all data then being stored
in the NetSync Database (Step 2). In Step 3, Network Facility
and equipment catalog files are produced in support of field equipment
and circuit data gathering activities. During Step 4, the field
validation activities are completed, with the post-audit data
(Step 5) then being electronically transmitted back to the Net
Load Database for processing (Step 6). In Step 7, the WiseAnalyze
Reconciliation Engine processes the audit data and prepares it
for OSS data load (Step 8). In Steps 9A/9B, reports are validated
by a qualified Data Administrator who then either
pushes the now complete site equipment and circuit configuration
data into the OSS (assuming no conflict) and/or makes corrections
directly from the WiseAnalyze exception reports.
Figure
3: Net Trak™
NET
TRAK DATA FLOW
The
Net Trak data flow process includes four sequential categories
(or "clusters") of activity:
A.
OSS Import: here all salient data sources are identified
that contain equipment and other material requiring asset management.
In the early stages of Net Trak implementation, asset/material
data can originate from a variety of OTS (Off-the-Shelf) and custom
systems - Fixed Asset Systems (ex: Oracle Financials), Excel Spreadsheets,
Home Grown Systems (i.e.: Access databases), Provisioning Systems
(MetaSolv, TIRKS, etc.) and so forth. The goal is to get
all of this disparate data in a single, manageable location
- the Net Trak Environment.
The
WiseExtract module of the Net Trak Solution serves as the primary
system interface for mapping OSS data into the Net Trak Database.
Should the client be a MetaSolv customer, equipment data can be
automatically transferred via API integration (specifically, the
Inventory Capacity Management API).
B.
Net Trak Environment: Net Trak's primary objective
is to monitor the location and status of each asset as it moves
throughout the Asset Life Cycle. Net Trak also seeks to
serve as a single data repository for storing and managing asset
activity. The Solution includes a mobile computing module, MobileMap,
which leverages scanning technology. Net Trak includes the WiseAnalyze
reconciliation engine that produces highly valuable, intuitive
asset management reports.
C.
Remote Equipment Locations: the MobileMap application is
designed to reside on a Technician's laptop, that is used in the
field to rapidly capture changes in asset status and movement
electronically. The MobileMap user relies upon a common decoding
scanner (or low cost wand) that is used to rapidly introduce and/or
validate asset tags, serials numbers, CLEI heci bar codes, and
so forth. It is also possible to implement the mobile platform
in a PDA environment.
D.
Database Update: optionally, a variety of
OSS' can interface with Net Trak to serve as the primary asset
management database - with Net Trak serving as the conduit between
the field and the back office. For instance, it is possible to
use MSS and a variety of other systems (i.e.: Remedy) to serve
as the asset management hub. Here, BDS can either produce the
Oracle output files for handoff or assist in direct integration.
