The document discusses the importance of accurately mapping telecommunications networks. It notes that mapping is needed to reduce truck rolls, better utilize existing network infrastructure, and provide accurate records to other utilities. However, network data often deteriorates over time. The document then recommends improving data quality by ensuring data captured from network builds is accurate, providing resource orientation and standardized tools/processes, and implementing ongoing data maintenance to address increasing network complexity and churn.

1. Mapping Your Network
Observations & Trends
Kevin Challen
Practice Head – Infotech

2. So what's mapping your Telco network for:
• Next Generation Network (NGN), such as
FTTx / Cable / Backhaul / Core…
• Need accurate records to accurately plan the network
• The three C’s is our mantra
Concurrency
Completeness
Consistency

3. So Why do we need to do this
• Why – well we need to:
• Reduce Truck Roll – Anecdotal evidence indicates the many
Service Providers will perform some type of physical survey.
• Better understand the existing network topology, so as to
better utilize as much of the existing network
as possible.
• Be able to visualize the location of
key network elements to better plan
the new network
• Provide accurate records to
other Utilities and relevant organisations..

4. But we already have a great network data set !
• Well that’s excellent news, but ask some questions:
• When was it originally captured ?
• What was the quality at the point/time of
capture ?
• What’s happened since ?
• How is the on-going quality of the data
managed and measured ?
• The evidence is that the data in these models will
deteriorate over time…
the question is by how much ?

5. Some Evidence
• In a number of cases we have seen
a systemic problem with the network records.
• Poor source Data
• Validation of the network build out – 40/50% error
• On-going quality measurement
• Bottle neck in Recording
• Some other issues:
• Often focus is on functionality rather than quality tools, and
while PNI is an excellent tool there is still a chance of poor
data being recorded.
• As the network complexity increases; can the workforce
keep up with the technology changes…. People

6. Yes but it’s the best we have:
• Is it supporting the business ?
• Where else can we go for additional information ?
• How can we ensure that what we put into PNI is CCC ?
• The rate of change is going to be
exponential in terms of network churn.
• Need to follow the Process…… and
the data..

7. What else can we do:
• Well we can ensure that the data being fed into PNI is
accurate.
• Data from the “Build Out” needs to be better.
• Often the resources use different technology to record field data
• Resource Orientation, Tools and Standards.
• Need to ensure that the engineering and recording standards are
well defined, and reflect the business requirements
• Build Better Data.
• Alternative data sources – what additional
data can be added…..
• Maintain the Data
• On-going maintenance

8. OK lets get a plan together
But lets look at some Trends:
• Inventory management is going to be a combination of
both logical and physical networks – Discuss….
• GIS WILL play a critical role in this model, in fact its
role will/is expanding.
• Data is and always has been key and the real value of
spatial data is being recognised by businesses and
any short comings are being addressed.

9. A Plan
• Realise that Inventory data is about the logical and
physical network,
• Need to establish some
“Common Language”
• There are TMF standards for this.
• With the increase in Network
churn, we must rationalise
our existing processes to drive efficiency.
• Need to look at the end to end process not the technology.
• People
• We have often underestimated the training and orientation
required to ensure we maximise the potential of PNI.