SpatialInfo Redrafting PDF

Apex CoVantage, LLC
Conversion System Design Document

(CSDD)
Job 6301 – Redrafting
6301-SpatialInfo Redrafting CSDD (Rev 2.2).docx
Revision History
Rev Num Release Date Changes Author
1.0 April 19, 2011 Initial release Prakash Shinde
1. Fiber termination
2. Fiber WP allocation
3. Error Classifications &
Deductions
4. Re-organized Chapter 4
1.1 May 3, 2011 (workflow) for Manual Prakash Shinde
process; alternative
automated processes
for each Task are
included in blue font
within text boxes for
future use.
1. Modified
SNBatchProcess to
include Address with
“NOS”
2. Minor updates to
Chapter 2 Target
1.2 May 11, 2011 Prakash Shinde
specification
3. Fiber workpackage
creation updated
4. Appendix C added
1. Modified PIMCO
Inventory to include
“NoNode” workpackage
2. Target Specification -
Node Type
1.3 May 26, 2011 Placement Rules: RF Prakash Shinde
Segment and Footage
Conversion rules –
Fiber state and priority
5. Target Specifiction -
Patch Panel count @
i
Fiber sites
6. ProACT Integration –
Workpackage
dependency and
allocation
7. PIMCO – Source
discrepancy
identification
1. Updated section 3.3

2.0 May 28, 2011 and workpackage Prakash Shinde
dependency
1. Fiber workpackage
creation and Inline QC
2. Updated drawing in
2.1 July 24, 2011 Appendix C Prakash Shinde
3. Fiber Sites and Master
Circuit ID
4. Rotated Address offset
1. Updated Feature and

Attribute Matrix
2. 2.4.1.8 Drop Arrow
3. 2.8.1.3 Node annotation
at Node boundary and
Node inside MDU detail
4. 2.6.15 EOL for
Terminators
5. 2.4.16 Mount point with
device
6. 2.5.13 Hub stitch specs
2.2 Sep 2, 2011
defined
7. 2.4.13 Road Bore Tic
8. Power Supply
9. 2.6 Passive device
naming
10. Node placement rules
11. Terminator conversion
rule
12. Band Pass filter specs
13. Hub type should be ISP
ii
14. OCEF is mandatory
15. Added new section for
Term panel
16. Added new section for
Master Circuit and port
naming
17. Buss boundary is
mandatory
iii
iv
Contents
1.0 Project Overview ........................................................................ 1-1
1.1 Summary .................................................................................. 1-1
1.2 Scope ....................................................................................... 1-1
1.3 Project Documentation.............................................................. 1-2
1.3.1 Comcast ..................................................................... 1-2
1.3.2 SpatialNet................................................................... 1-2
1.3.3 Apex ........................................................................... 1-3
1.4 Batch and Work Package Definitions ........................................ 1-3
1.4.1 Node Workpackages .................................................. 1-3
1.4.2 Fiber WorkPackages .................................................. 1-3
1.4.3 No Production Lots ..................................................... 1-4
1.5 SpatialNet Information .............................................................. 1-4
1.5.1 JobID.......................................................................... 1-4
1.5.2 Job Status and Access ............................................... 1-4
1.5.3 SNet Job Posting Process .......................................... 1-5
1.6 Logistics.................................................................................... 1-5
1.7 Source Materials ....................................................................... 1-6
1.8 Deliverables .............................................................................. 1-7
1.9 Project Terminology .................................................................. 1-7
2.0 Target Specification ................................................................... 2-1
2.1 Cable Network Connectivity Model ........................................... 2-1
2.1.1 Introduction to Cable Networks ................................... 2-1
2.1.2 Hybrid Fiber Coax – HFC ........................................... 2-1
2.1.3 Connectivity ................................................................ 2-2
2.1.4 General Redrafting Rules ........................................... 2-2
2.1.5 Features and Attribute To be Captured ...................... 2-2
2.2 Source to Target Symbology Map ............................................. 2-3
2.3 Landbase Fabric ....................................................................... 2-3
2.3.1 Addresses .................................................................. 2-3
2.3.2 MDU Address ............................................................. 2-10
2.3.3 Street Centerline ........................................................ 2-10
2.3.4 Road Edge ................................................................. 2-11
2.3.5 Building Footprint ....................................................... 2-12
2.3.6 Building ...................................................................... 2-12
2.3.7 Pipeline ROW ............................................................. 2-12
2.3.8 Railroad ROW ............................................................ 2-13
2.4 Support Fabric .......................................................................... 2-13
2.4.1 Pole ............................................................................ 2-13
2.4.2 Support Attachment Point ........................................... 2-14
2.4.3 Lock Box .................................................................... 2-14
2.4.4 Strand Segment ......................................................... 2-15
2.4.5 Anchor ........................................................................ 2-16
2.4.6 Pedestal ..................................................................... 2-16
2.4.7 Handhole .................................................................... 2-16
2.4.8 Manhole ..................................................................... 2-17
2.4.9 Vault ........................................................................... 2-18
2.4.10 Trench Segment ......................................................... 2-18
v
2.4.11 Conduit Segment ........................................................ 2-19
2.4.12 UG Tic ........................................................................ 2-20
2.4.13 Road Bore Tic ............................................................ 2-20
2.4.14 Conduit Tic ................................................................. 2-20
2.4.15 Road Bore Conduit Tic ............................................... 2-21
2.4.16 Mount Point ................................................................ 2-21
2.4.17 Cell Tower .................................................................. 2-21
2.4.18 Drop Arrow ................................................................. 2-21
2.4.19 Guy Span ................................................................... 2-22
2.4.20 House Count .............................................................. 2-22
2.4.21 Footage ...................................................................... 2-23
2.5 Fiber Fabric .............................................................................. 2-23
2.5.1 Headend..................................................................... 2-23
2.5.2 Node .......................................................................... 2-24
2.5.3 Optical Cable Entrance Facility OCEF ........................ 2-27
2.5.4 Term Panel................................................................. 2-28
2.5.5 Hub ............................................................................ 2-29
2.5.6 Institutional Network Site (INET) ................................. 2-30
2.5.7 Fiber Customer Terminal Site (FCTS) ........................ 2-30
2.5.8 Cell Site ...................................................................... 2-31
2.5.9 Point of Presence (PoP) ............................................. 2-31
2.5.10 Fiber Segment ............................................................ 2-32
2.5.11 Master Circuit Naming ................................................ 2-33
2.5.12 Fiber Splice Case ....................................................... 2-36
2.5.13 Fiber Riser.................................................................. 2-38
2.5.14 Fiber Storage Loop (In SpatialNet - Storage Loop) ..... 2-39
2.5.15 Hub Stitch................................................................... 2-39
2.6 RF Fabric .................................................................................. 2-40
2.6.1 RF Segment ............................................................... 2-40
2.6.2 Power Supply ............................................................. 2-41
2.6.3 Power Inserter ............................................................ 2-41
2.6.4 Power Block ............................................................... 2-42
2.6.5 Tap ............................................................................. 2-42
2.6.6 Splitter ........................................................................ 2-43
2.6.7 Coupler (In SpatialNet – DC) ...................................... 2-43
2.6.8 Combiner.................................................................... 2-44
2.6.9 Terminator .................................................................. 2-44
2.6.10 Line Terminator (In SpatialNet – Self-Terminator) ...... 2-44
2.6.11 Amplifier ..................................................................... 2-45
2.6.12 High Leg DOT ............................................................ 2-46
2.6.13 Line Extender ............................................................. 2-46
2.6.14 Line Equalizer............................................................. 2-46
2.6.15 End of Line ................................................................. 2-47
2.6.16 RF Splice.................................................................... 2-47
2.6.17 Converter Box ............................................................ 2-48
2.6.18 Processor ................................................................... 2-48
2.6.19 Modulator ................................................................... 2-49
2.6.20 Inline Pad ................................................................... 2-49
2.6.21 Notch Filter ................................................................. 2-49
2.6.22 Source ........................................................................ 2-50
2.6.23 Generic Drop and Insert Network ............................... 2-50
vi
2.6.24 Band Pass Filter ......................................................... 2-50
2.6.25 Fiber Terminator ......................................................... 2-51
2.6.26 Power Cable ............................................................... 2-51
2.6.27 Status Monitor Cable .................................................. 2-52
2.7 Features in Comcast Legend not in Comcast Specs ................. 2-52
2.8 Boundaries ............................................................................... 2-52
2.8.1 Node Boundary .......................................................... 2-53
2.8.2 Buss Boundary ........................................................... 2-57
2.8.3 Power Supply Boundary ............................................. 2-57
2.9 MDU Detail ............................................................................... 2-57
2.9.1 Definition .................................................................... 2-57
2.9.2 Conversion Rules: ...................................................... 2-57
2.10 White Space Management ........................................................ 2-58
2.10.1 Permitted overstrikes .................................................. 2-58
2.10.2 Hierarchy of adjustment .............................................. 2-58
2.11 Source Error Icons .................................................................... 2-58
2.11.1 Support Route ............................................................ 2-58
2.11.2 Fiber OSP .................................................................. 2-59
2.12 Delivery Reports ....................................................................... 2-59
3.0 Production Work Flow & Instructions ...................................... 3-1
3.1 Task B1: Prep Source for Production ........................................ 3-1
3.2 Task W2: Place Addresses and Node Boundary....................... 3-1
3.3 Task W3: 100% In-Line QC: Address & Node Boundary ........... 3-3
3.4 Task W4: Create Support Network............................................ 3-4
3.5 Task W5: 100% In-line QC: Support Network ........................... 3-5
3.6 Task W6: Create Hub ............................................................... 3-6
3.7 Task W7: Create Fiber Network ................................................ 3-6
3.8 Task W8: 100% In-line QC: Fiber Network................................ 3-8
3.9 Task W9: Create RF Network ................................................... 3-8
3.10 Task W10: 100% In-line QC: RF Network ................................. 3-11
3.11 Task W11: Create MDU Detail View ......................................... 3-12
3.12 Task W12: 100% In-line QC: MDU Detail View ......................... 3-13
3.13 Task B14: Edge-Match All Boundaries ...................................... 3-15
3.14 Task B15: Run SNBatchProcess .............................................. 3-15
4.0 Appendix A: Target Placement Exhibits .................................. 4-1
5.0 Appendix B: Source and Target Symbols ................................ 5-1
6.0 Appendix C: Fiber Workpackage Definition............................. 5-7
vii
List of Figures
Figure 1: Typical HFC Network ...................................................................2-1
Figure 2: Feature and Attribute Source Matrix .............................................2-3
Figure 3: Address Placement Rules – Rear of Parcel, Parallel ....................2-6
Figure 4: Address Placement Rules – Front of Parcel, Parallel ...................2-7
Figure 5: Address Placement Rule – Front of Parcel, Perpendicular ...........2-8
Figure 6: Address Placement Rule – Rear of Parcel, Perpendicular............2-9
Figure 7: Example of a Donut.................................................................... 2-54
Figure 8: Example of an Island.................................................................. 2-55
viii
Proprietary & Confidential
1.0 Project Overview
1.1 Summary
This project is to create a GIS model of Comcast’s cable network. Comcast was founded
in 1963 as a single-system cable operation. It is now the leading provider of cable,
entertainment and communications products and services in the United States of
America. Comcast provides services in 39 states, including the District of Columbia, with
22.9 million video customers, 16.7 million high-speed internet customers and 8.4 million
digital voice customers.
Markets are the source-of-record for much of the company data. Outside plant engineering
drawings, Multiple dwelling units (MDU) details, various serviceability boundaries (i.e. Node,
Buss, Power, etc.) are maintained in a variety of formats. Data for some markets are already in a
GIS platform, others are in a CAD environment. The data are at various levels in terms of the
underlying data model and the reliability of the data.
Consequently, Comcast is utilizing two methods for bringing all of its outside plant (OSP) data
into a common, well-structured, SpatialNET GIS environment:
1. Re-drafting. This is for OSP data that is not currently well-structured and needs
human intervention to bring it into the target SpatialNET system
2. Migration. This is for OSP data that is well-structured enough to enable a
migration/transformation into the target SpatialNET system
In addition, Comcast is updating its landbase to a common TeleAtlas base, conflating
parcel data from a variety of sources onto the TeleAtlas street centerline data.
This document is for the re-drafting workflow.
1.2 Scope
The project scope is to move the following elements to a Comcast-provided landbase

within the SpatialNET environment:
1. Addresses,
2. Support network – Overhead and Underground (poles/pedestals and the
corresponding strands/trenches/conduits),
3. RF (Coaxial) Network, comprising the devices and cables, and
4. Fiber Network.
This is a multi-year project covering the entire Comcast service territory.
6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

1-1 July 13, 2012
1.3 Project Documentation
1.3.1 Comcast
The following documents are current versions of the applicable standards for
Comcast’s NGIP (Network GIS Integration Platform).
These documents are being maintained under strict version control by Comcast.
Updates will be identified by Issued Date and Version Number.
This CSDD will be updated as and when new versions of these standards are
relased to Apex by Comcast.
1. Outside Plant Design Standard
This document defines Comcast’s OSP feature naming conventions in
maps and SpatialNet dictionaries
2011.07.27_Comcast_HFC_OSP_Design_Name_Standard_v2.4.5b.do
cx
2. HFC Symbols Legend
This document defines Comcast’s symbology, layer, and AutoCAD
standards.
Comcast v1.1.04 Layers Standard.pdf
3. Acceptance Criteria and Use Cases
This document defines Comcast’s Quality Control and delivery
acceptance requirements.
Comcast_HFC_Acceptance_Criteria_Manual_v2.8.7.docx
4. Comcast HFC Drafting Practices Manual
This document defines Comcast’s specifications for the Project. It is
the equivalent of Chapter 2.0 “Target Specification” of this CSDD.
2011.03.29_Comcast_HFC_Drafting_Practices_Manual_v2.5.docx
5. NGIP Market Exceptions
Where a Market Area requires exceptions to the above NGIP standards
documents, these will be documented in a separate document. There
will be a separate chapter for each Market Area.
File Name: yymmdd_NGIP Market Exceptions_Version??
1.3.2 SpatialNet
SpatialNet software is being maintained under strict version control and

systematic release procedures by SpatialInfo. Redrafting will be done by Hub
using the then current version of the software. New releases may require re-work

1-2 July 13, 2012
of previously redrafted areas. Apex and SI will jointly evaluate the impact of the
new release on previously produced data and the handling of rework.
- SpatialNET User Guide 5.6.1 01-10-2011.pdf
1.3.3 Apex
1. Cable 101 Training and Certification Manual

2. Comcast Training and Certification Manual
3. Conversion System Design Document (CSDD)
4. Quality and Sampling Plan
1.4 Batch and Work Package Definitions
A Batch in this project is all of the geography served by a Hub. Hubs are assigned 4-digit
Batch numbers on receipt from Comcast.
There are two types of WorkPackages in this project.
1.4.1 Node Workpackages
Node WorkPackages comprise all of the geography served by a Node.

The naming convention for Node WorkPackages is:
bbbb-wwww, where
bbbb = 4-digit Batch Number
wwww = 4-digit serial ID assigned to each Node
wwww = 4-digit serial ID assigned to “NoNode” WorkPackages. The
workpackages should be numbered in reverse order, starting with 9999.
1.4.2 Fiber WorkPackages
The total Fiber Network for a Hub Service Area is to be divided into multiple
Fiber WorkPackages for redrafting. The goal is to create Fiber WorkPackages
that: (a) represent a work content of 4-8 hours and (b) minimizes potential conflict
from “locked” Node workpackage during production.
The naming convention for Fiber WorkPackages is:
bbbb-Frrss, where,
bbbb = 4-digit Batch number
F = Signifies that this is a Fiber WorkPackage
rr = Sequential Fiber Route number exiting the Hub or Headend
ss = Sequential Fiber Segment number within a Route
1-3 July 13, 2012
One Fiber WorkPackage will be created for the Hub or Headend and named as
follows:
bbbb-F0000
1.4.3 No Production Lots
Due to the interleaved and overlapping Fiber and Node WorkPackages, and
because the Fiber WorkPackages cannot be completed until all Node
WorkPackages are done, it is not possible to subdivide Batches into logically
consistent Production Lots.
Thus, no Production Lots are to be used in this project.
1.5 SpatialNet Information1
1.5.1 JobID
All work in SpatialNet (SNet) is done under a JobID. The SNeT JobID is created
by a user. The naming convention for SNet JobIDs is:
bbbb-wwww-ttt
where,
bbbb = Batch Number
wwww = WorkPackage Number
ttt = Task Number
For example, the SNet JobID for Task W3 for Node WorkPackage 0003 in
Batch 0102 would be: 0102-0003-W3.
The SNet JobID for Task W6 for Fiber WorkPackage F0103 in Batch
0102 would be: 0102-F0103-W6.
Jobs are to be created and assigned through ProACT.
1.5.2 Job Status and Access
The status of SNet Jobs are:

1. Private – In this state, only the user who created the Job can access it.
Other users cannot view it. However, the SNet Administrator can re-assign
a Private Job to another user.
2. Published – NOT TO BE USED under any circumstances; it causes
irrecoverable database contamination.
1
In this section of the CSDD, high level summaries of some of the key features affecting the
management of production are presented. For details see Section 1.3.2.
1-4 July 13, 2012
3. Posted – Once a task on a Job is completed, it can be posted. A Posted

Snet Job can be viewed and edited by another user.
4. Cancelled – If Snet Job has been cancelled prior to posting. Once
cancelled the work cannot be recovered.
1.5.3 SNet Job Posting Process
1.5.3.1 Posting Queue
1. When a Task is designated as “completed” in ProACT, the

corresponding SNet Job is added to the SpatialNet posting queue by
ProACT.
2. Posting is started at pre-scheduled times.
3. ProACT notifies users to log off prior to scheduled posting time. Once
all users are logged off, ProACT starts the posting process.
4. The Posting log generated by SpatialNet is used by ProACT to re-
allocate to the original operator any SNet Job that failed to post.
1.5.3.2 Posting Schedule
Posting will be performed

1.5.3.2.1 Single Shift:
1. During the lunch break
2. During the night.
1.5.3.2.2 Multiple Shifts
1. During every long break
2. During the night.
1.6 Logistics
The Client will send data for complete Hubs via FTP with a notification to Apex Project
Manager via email.
a. Initially, files will be exchanged manually via FTP
b. Once ProWEB is released, the entire logistic process will be automated
Apex will return completed Hubs via FTP.
Source files and converted data are to be archived for a period of 6-months after delivery.

1-5 July 13, 2012
1.7 Source Materials
Source Format Description
Systems Maps contain the network for a set of Nodes.

There are several System Maps for each Hub, and are
1. System Maps DWG
the definitive source of the data to be moved to
SpatialNET.
Node Maps are used as a reference to clean up the

2. Node Maps DWG
Node Boundaries in the System Maps.
These are detail drawings of Multiple Dwelling Units

such as apartment complexes, hotels, etc. where
3. MDU Drawings DWG
multiple CATV service drops are associated with a
single parcel.
4. Fiber Key Map DWG High level route map for the Fiber Network for a Hub
5. Fiber Interconnect MS Excel Fiber network across Hubs.
Comcast maintains the detailed splicing information

for its Fiber cables in the form of spreadsheets. This
6. Fiber Splice Detail MS Excel
information is used to model the Fiber Splicing in
SpatialNET
SpatialNET
This provides the starting database for each Hub. It
7. Oracle Dump file Database
includes the read-only landbase data, new blocks, and
for the Hub Oracle
commands.
“Dump”
8. Old-to-New Node This file maps the current Node names to the new
MS Excel
Names Node names.

1-6 July 13, 2012
1.8 Deliverables
Deliverables for Comcast NGIP Redraft project as follows:

1. Oracle Spatial Dump file for each Batch (HUB)
2. Delivery Reports
a. Source Error Icon Log
b. Exception Log
c. Quality Acceptance Certificate
d. Billing Quantities Report
1.9 Project Terminology
Term Description
Address
The house number(s) of a parcel
Text
This is a temporary object created to place objects at the required offset

Block
from the parcel boundary automatically. It traces the back and front of
PLine
contiguous parcels. (Under development)
Buss A single RF circuit starting from a Node
Cable RF (Coaxial) and Fiber cables
CATV
The active network carrying the CATV signal
Network
Device Network devices such as Taps, Splitters, and Amplifiers
Route A single Fiber circuit starting from a Hub

1-7 July 13, 2012
Linear feature between two point features:

1. CATV Segment:
• Fiber Segment
• RF Segment
Segment
2. Support Segment:
• Strand Segment
• Trench Segment
• Conduit Segment
Support Segments fall into the following three (3) categories, each
containing two (2) sub-types
• Overhead Routes (OH):
(a) Strand
(b) Slack-Span.
Support
Segment • Underground Routes (UG):
(a) Trench (direct-buried cable)
(b) Conduit (cable in pipe)
• Vertical Routes:
(a) Riser (OH to UG transitions at poles)
(b) Vertical Plant (found in high rise buildings)

1-8 July 13, 2012
2.0 Target Specification
2.1 Cable Network Connectivity Model
2.1.1 Introduction to Cable Networks
Refer to the companion document, “Cable 101 Training Manual” for a description of how a
cable network is engineered in the field. It provides a very useful overview of the critical
concepts on this project like signal strength, cable footage, signal loss, etc.
In addition it explains the functionality of every feature as a component of the connected
CATV network.
2.1.2 Hybrid Fiber Coax – HFC
The hybrid fiber coax (HFC) system is an advanced CATV transmission system that uses
fiber optic cable for the head end and feeder distribution system and coax for the customers
end connections. HFC offer high-speed backbone data interconnection lines (the fiber
portion) to interconnect end user video and data equipment. Many cable system operators
anticipating deregulation and in preparation for competition began to upgrade their systems
to Hybrid Fiber Coax (HFC) systems in the early 1990’s.
Figure 1: Typical HFC Network
Figure 1: Typical HFC Network shows a typical cable distribution system that uses a
combination of fiber optic cable for the core distribution and RF cable for the local

2-1 July 13, 2012
connection. This diagram shows the satellite signals received at the Headend facility. These
signals are converted to allow distribution through a terrestrial network. From the Headend,
the signals are carried on high-speed fiber cable. The fiber cable is connected in a loop
around the cable television service area so that if a break in the cable occurs, the signal will
automatically be available from the other part of the loop. The loop is connected (tapped) at
regular points by a fiber hub that can distribute the optical signals on fiber spurs. The fiber
spurs end at Nodes that convert the optical signals into RF television signals that are
distributed on the local RF cable network.
2.1.3 Connectivity
1. Connectivity requires that Fiber and RF Networks be drafted in strict downstream

connectivity order from the Hub or Node all the way to the Service Drops or
Terminators.
2. Connectivity is required to be traceable upstream and downstream from any point in
the network. Exception: INET connected to another INET. Connectivity between
INET sites needs to be checked separately.
3. In addition, some features associations need to be made manually.
2.1.4 General Redrafting Rules
1. Inside-plant entities are out of scope for this project.

2. Every feature must be connected at the “snap points” for graphic connectivity.
3. If a feature on the Source Map does not exist in SpatialNet, raise an IMS ticket.
4. Flipping objects is not allowed within the SpatialNET during redrafting due to the
potential for introducing discrepancies between the logical and physical connectivity
of the plant. Left and Right versions of symbols should be used.
5. Errors in the source data are to be identified by Source Error Icons. The Source Error
Icons will be taken into account by SpatialNET quality software tools when checking
connectivity or other conversion rules.
2.1.5 Features and Attribute To be Captured
The Features and Attribute data to be captured during redrafting are enumerated in the below
file, which contains the following information that is pertinent to the redrafting project:
Column B: Feature Name
Column C: Sub-features
Column D: Attribute
Column E: Attribute data status (mandatory/optional)
Column F: Source for the attribute data.
For re-drafting, data is to be captured from the following sources:
2-2 July 13, 2012
1. System Maps
2. Fiber Splice Spread Sheets
3. MDU Detail Drawings
4. Node Name Spreadsheets
Figure 2: Feature and Attribute Source Matrix
6301-SpatialInfo
Feature and Attribute Source Matrix (Rev 2.0).xlsx
2.2 Source to Target Symbology Map
Appendix B contains the map for source and target symbology.
2.3 Landbase Fabric
The Target landbase is in AutoCAD 3D map and has been built by conflating parcel data from a
variety of sources with street centerline data from TeleAtlas.
Currently the NGIP HFC engineering plant data is stored in a Albers projection system within
Oracle. It is important to designate the correct UTM Zone for every Market.
2.3.1 Addresses
2.3.1.1 Definition
The house number(s) of a parcel. House numbers are part of the full Street Address
for a parcel. House numbers are to be distinguished from unit or apartment numbers
shown on the source to recognize multiple cable services being provided within a
parcel.
2.3.1.2 Conversion Rules
1. Addresses must be taken from the source; addresses in the target maps are not
reliable.
2. Select Single Dwelling Unit (SDU) or Multiple Dwelling Unit (MDU) based
on whether or not there are multiple units for an Address.
3. For parcels marked with “VL” on the source (indicating Vacant), the Address
is to be captured as VL.
4. For parcels marked with “NA” on the source (indicating No Address) the
Address is to be captured as VL.

2-3 July 13, 2012
5. For parcels with no address and marked with “UNC” on the source (indicating
Under Construction), the Address is to be captured as VL.
a. If the Address is an MDU, refer to Section 2.3.2 for Conversion
Rules, etc.
6. For all remaining parcels with no address, the Address is to be captured as
“NOS”. Note: This requirement was included to ensure all Addresses have
been transposed from the source and also use as quality check. If the address
redraft quality is good then stop creating “NOS” Addresses
7. Select Commercial, Residential based on prefix of House count on the source
(R or C).
8. (Mandatory) Every Address on the Source must be captured in the Target
Landbase.
9. The Location Address block is required for parcels where:
a. the Support Structure is located in the rear of a parcel,
b. there is no alley, and
c. accessing the Support Structure would require going on the
customer’s property.
10. Special Conditions:
a. Multiple Address entities are to be created for parcels containing
multiple addresses on the source.
b. If there is an extra parcel on the source that does not exist in the
target landbase, an extra Address entity is to be created on the
target parcel, maintaining the sequence.
c. If there is an extra parcel on the target landbase that doesn’t exist
on the source, a Source Error Icon is to be added.
d. If a Address is over 250’ from the Tap, a Source Error Icon is to be
placed near the address (done by AssociationCheck software)
2.3.1.3 Placement Rules
1. If the Support Route is on the street side, Address Text should be in the back
of the parcel.
2. Parcel Address Block is to appear parallel to the Street Lot Line, orientated
based on the quadrant in which it is located (Insert example), at the following
offsets:
a. 20’ from the SLL to Address Text insertion point
b. If the Address text overstrikes the side parcel lines, the address
must be rotated (90 degrees) to be perpendicular to the SLL line.

2-4 July 13, 2012
Offset is to be 12’ from the SLL to the first/last character of the

Address Text depending on the Quadrant.
The overstrike rule does not apply to the rectangular box around
the address text for Parcels with Taps
3. Multiple Address Texts should be placed close to the 1st without any overlap.

2-5 July 13, 2012
Figure 3: Address Placement Rules – Rear of Parcel, Parallel
'
20
IV I
Quadrant Quadrant
12
34
34
12
20
'
C
l
l
C
34
12
C
l
20
'
'
20
l
C
12
34
III
II
Quadrant
Quadrant

2-6 July 13, 2012
Figure 4: Address Placement Rules – Front of Parcel, Parallel
IV I
Quadrant Quadrant
'
20
12
34
34
12
C
l
l
C
20
'
'
20
C
l
12
34
34
12
l
C
20
'
III
II
Quadrant
Quadrant

2-7 July 13, 2012
Figure 5: Address Placement Rule – Front of Parcel, Perpendicular
IV
Quadrant I
Quadrant
'
12
34
12
12
34
l
C
C
l
12
'
'
12 C
l
12
34
34
12
l
C
12
'
II
Quadrant
III
Quadrant

2-8 July 13, 2012
Figure 6: Address Placement Rule – Rear of Parcel, Perpendicular
IV
Quadrant I
Quadrant
'
12
12
34
34
12
12
'
l
C
C
l
12
C
l
34
12
34
'
12
l
C
'
12
II
Quadrant
III
Quadrant

2-9 July 13, 2012
2.3.1.4 Manual Associations
1. Addresses should be associated to the Street Centerline.
2.3.2 MDU Address
2.3.2.1 Definition
An MDU Address is:

a. Any building with 5 or more Units.
b. Clustered complexes, even if containing fewer than 5 units
1. If the MDU contains a mix of Residential and Commercial Units, separate

MDU Addresses must be created
2. If an Apartment Office, Clubhouse or Pool House is fed from a Tap capture it
as an Commercial MDU Address
3. Unit numbers should have prefix “UNIT”
4. Unit numbers should be captured if shown on System map, except for
Condominiums and Townhouses
2.3.3 Street Centerline
2.3.3.1 Definition
Street segments between two intersections are identified by a Street Centerline

feature. The Street Centerline feature includes all the address attributes like City,
State and Zip code, except for the house number.
1. Street Centerline features are to be created in service areas that either do not
have Street Centerlines or do not have Parcel Data.
2. Street Type should be as per source
3. Directional prefix should be as per source
4. Prefix should be as per source
5. Street name (Mandatory) should be as per source
6. Directional Suffix should be as per source
7. State (Mandatory) should be as per source

2-10 July 13, 2012
Case 1: Parcels exist; No Centerline

Street Centerline should appear approximately in the center of the street, as defined
by the Street Lot Lines of the parcels.
Case 2: No Centerline; No parcels
New Street Centerline should be snapped to the existing centerline and follow the
path per source map
Add Street Name for the new Street Centerline once per Street centerline segment
1. Street Centerlines need to be associated with Addresses
2.3.4 Road Edge
2.3.4.1 Definition
The target landbase does not have any Road Edges. The edge of road is inferred from
the street-facing parcel lot line of the parcel polygon.
1. Road Edge features are to be created in service areas with no Parcel Data.
Case 1: Centerline exists; No Parcels

Road edge features need to be created. The following standard widths will be
maintained in SpatialNet
- Primary Roads: 65’
- Secondary Roads: 50’
Case 2: No Centerline; No parcels
Road edge features need to be created. The following standard widths will be
maintained in SpatialNet
- Primary Roads: 65’
- Secondary Roads: 50’

2-11 July 13, 2012
2.3.5 Building Footprint
2.3.5.1 Definition
Footprints of large buildings such as office buildings, apartment buildings, hospitals,

etc. are sometimes shown on the source.
2.3.5.2 Conversion Rules:
1. Create a building footprint only if shown on the source.

2. DO NOT populate boundary attributes.
3. A Building Type feature is required inside the Building Footprint (see below)
1. The building footprint should be positioned, oriented, and shaped like it

appears on the source.
2.3.6 Building
2.3.6.1 Definition
A Symbol placed within every Building Footprint, whether or not building type is
indicated on the source.
1. The Building Type – To be set as “Building”.

2. Building Name – To be captured only if available on the source. Otherwise
left blank.
3. Building Use Type – To be captured only if obvious from the source.
Otherwise, the field is to be set to “Blank”.
1. Placed within the Building Footprint without any overstrikes.
2.3.7 Pipeline ROW
2.3.7.1 Definition
Pipeline ROW is the right of way for buried pipes.
1. Capture as per source

2-12 July 13, 2012
2.3.8 Railroad ROW
2.3.8.1 Definition
Railroad ROW is the right of way for railway lines.
1. Railroad Name – To be captured if available on source
2.4 Support Fabric
The Support fabric must be drafted in strict order of connectivity, starting from the Headend to the
Node/Site and from each Hub to the end of line.
2.4.1 Pole
2.4.1.1 Definition
Poles are OH support structures. A pole is used to support overhead lines such as
Strand Segment, RF Cable, Fiber Optic cable, and related equipment. Based on Pole
owner it will be referred to as a Telephone pole, Power pole and Hydro pole. Poles
are made of wood, metal, concrete, or composites like fiberglass.
The Support Route is the representation of the Overhead and Underground/Trench
Strand that will provide the support and the attachment database links with distances
and house counts/addresses for RF and Fiber Design.
1. Pole Type – Set to “Steel” or “Concrete” per source.

2. Pole Number – Capture per source. If multiple Pole Numbers are given,
capture them as a single string separated by commas. Standardize Pole
Ownership to “PWR-“ (power company) and “TEL-“ (telecom).
Example:
Source: P12345 T9999
Capture As: PWR-12345, TEL-9999
3. Riser Length – If the cable transitions without a break from a OH to UG (or
vice-versa) a Riser Footage must be entered (default 25’).
4. Guy Poles – Do not associate House Counts or Addresses with Guy Poles. Do
not associate with any network feature.
2-13 July 13, 2012
5. Do not capture
a. Push Poles
b. Extension arms
1. If Support Fabric is on the street side, then Pole should appear inside the
parcel at 10’ offset from the SLL
2. If Support Fabric is in the back of the Parcel then Pole should appear at 10’
offset from back of the Parcel line. The Pole location should match as per
source
1. Poles should be associated (Mandatory) to the Address.
2.4.2 Support Attachment Point
2.4.2.1 Definition
Support Attachment Points are OH/UG Support structures. These structures will not
be shown on Source map.
1. If no Support Structure is shown on the source where a Strand attaches to a

building, add a Support Attachment Point.
2. Aerial Support Attachment Point should be used on Strand Segment
3. Underground Support Attachment Point should be used on Trench Segment
2.4.3 Lock Box
2.4.3.1 Definition
Is a Support Structure that is made of metal box that is mounted internally or

externally on a wall.
1. Aerial Lock Box should be used on RF Network in OH environment

2. UG Lock Box should be used on RF Network in Underground environment
1. Should be placed per Source

2-14 July 13, 2012
2.4.4 Strand Segment
2.4.4.1 Definition
A segment of Strand between two poles or a pole and a Support Attachment
1. Each Strand Segment must be a single polyline between:

a. two Support Structures
a. Support Structure and a Support Attachment.
2. For slack span, select the mid-point of the Strand Segment and stretch the arc
to below the Footage.
1. If Support Fabric is on the street side, then Strand should appear inside the
2. If Support Fabric is in the back of the Parcel Strand should appear at 10’
offset from back of the Parcel line. The Strand location should match as per
source
3. In open areas without parcels, Strand Segments should not be
disproportionate. For example, a 200’ Strand Segment should not be longer
than a 300’ Strand Segment.
4. Multiple Strand Segments, if present, should appear on the parcel side as
shown in Exhibit
1. Strand Segment is to be associated with a Fiber or RF Segment

2-15 July 13, 2012
2.4.5 Anchor
2.4.5.1 Definition
Anchor is a tensioned line designed to add stability to Structures. One end of the line
is attached to the structure and the other is anchored to the ground at a distance from
the structure's base.
1. Capture only if shown on shown on source.
1. Anchors angle of rotation should be as per source.
2.4.6 Pedestal
2.4.6.1 Definition
Pedestal is a cable enclosure cabinet that provides suitable housing to mount taps,
splitters, line extenders, filters and splicing.
1. Should appear as per source
1. If Support Fabric is on the street side, then Pedestal should appear inside the
2. If Support Fabric is in the back of the Parcel then Pedestal should appear at
10’ offset from back of the Parcel line. The Pole location should match as per
source
1. Pedestal is to be associated with the Address

2. Pedestal is to be associated with the Tap
2.4.7 Handhole
2.4.7.1 Definition
Handhole is an underground support structure/enclosure shaped like a box made out

of non-metallic, non-conductive materials. This is used to house splices and conduit
connections.
2-16 July 13, 2012
1. If Support Fabric is on the street side, then Handhole should appear inside the
2. If Support Fabric is in the back of the Parcel then Handhole should appear at
10’ offset from back of the Parcel line. The Handhole location should match
as per source
1. Handhole is to be associated with the Address

2. Handhole is to be associated with the Tap
2.4.8 Manhole
2.4.8.1 Definition
Manhole is an underground support structure. It is made of concrete and houses

underground Cables and Equipments. Field technician can climb down and can add
new Network/Equipments.

2. Additional ID (optional) should be the Manhole owner
1. If Support Fabric is on the street side, then Manhole should appear inside the
2. If Support Fabric is in the back of the Parcel then Manhole should appear at
10’ offset from back of the Parcel line. The Manhole location should match as
per source
1. Manhole is to be associated with the Address

2. Manhole is to be associated with the Tap

2-17 July 13, 2012
2.4.9 Vault
2.4.9.1 Definition
A Vault is an underground room providing access to the network and equipments in a

controlled environment. Vault commonly exist inside a building like Headend
however there can Control Equipment Vault (CEV) located offsite.
1. If Support Fabric is on the street side, then Vault should appear inside the
2. If Support Fabric is in the back of the Parcel then Vault should appear at 10’
offset from back of the Parcel line. The Vault location should match as per
source
1. Vault is to be associated with the Address

2. Vault is to be associated with the Tap
2.4.10 Trench Segment
2.4.10.1 Definition
The Trench route that consists of the strand connection between Pedestals and other
trench support features with a dashed trench line and a distance text.
1. Each Trench must be a single polyline between:

b. Support Structure and a Bore Tic Trench (UG).
2. If no trench is shown between a pedestal and a cell tower, add a Trench
feature with footage of 1’.
3. Place a Trench between Pedestal and Riser, with footage of 1’.
4. Capture multiple Trench Segments with the same start and end Structures, as a
single Trench Segment.

2-18 July 13, 2012
1. If Support Fabric is on the street side, then Trench should appear inside the
2. If Support Fabric is in the back of the Parcel Trench should appear at 10’
offset from back of the Parcel line. The Trench location should match as per
source
3. In open areas without parcels, Trench Segments should not be
disproportionate. For example, a 200’ Trench Segment should not be longer
than a 300’ Trench Segment.
1. Trench Segment is to be associated with a Fiber or RF Segment
2.4.11 Conduit Segment
2.4.11.1 Definition
Conduit is a piping system used for protection and routing of cables in the
Underground environment. Conduit may be made of metal, plastic, fiber, or fired
clay.
1. Conduit Segment is a single polyline between:

b. Support Structure and a Road Bore Tic Conduit (UG)
2. Capture multiple Conduit Segments with the same start and end Structures, as
a single Conduit Segment, with the number of Conduit Segments captured as
Conduit Count
3. Do not enter Conduit count for single Conduit Segments
4. Conduit size should be captured if shown on source
1. If Support Fabric is on the street side, then Conduit should appear inside the
parcel at 10’ offset from the SLL.
2. If Support Fabric is in the back of the Parcel the offset should appear at 10’
offset from back of the Parcel line. The Trench location should match as per
source
3. Conduit Count feature (for multiple Conduit Segments only) should appear at
0⁰ rotation and should be associated with one of the Support Structures.
2-19 July 13, 2012
1. Conduit Segment is to be associated with a Fiber or RF Segment
2.4.12 UG Tic
2.4.12.1 Definition
Used to represent a change in direction of a Trench
1. Placed on the Trench Segment at the point where the direction changes
2.4.13 Road Bore Tic
2.4.13.1 Definition
Indicates the point at which a Trench crosses a road edge.
1. Add a Road Bore Tic Trench feature if shown on source when a Trench
crosses from a parcel to a street and vice-versa.
1. Placed on the Trench Segment at both sides of the road
2.4.14 Conduit Tic
2.4.14.1 Definition
Used to represent a change in direction of a Conduit
1. Placed on the Conduit Segment at the point where the direction changes

2-20 July 13, 2012
2.4.15 Road Bore Conduit Tic
2.4.15.1 Definition
Indicates the point at which a Conduit crosses a road edge.
1. Add a Road Bore Tic Conduit feature wherever a Conduit crosses from a
parcel to a street and vice-versa.
2.4.16 Mount Point
2.4.16.1 Definition
This is a Support Structure. A piece of plywood mounted on a wall allowing the

Comcast network to then mount equipment to the plywood.
1. Aerial Mount Point should be placed if shown on Source connected to OH

environment
2. Underground Mount Point if shown on Source connected to UG environment
3. Mount point should be created for RF/Fiber network with devices but no
supporting structure.
2.4.17 Cell Tower
It is a structure housing a Cell Site. Antennas are mounted on to the Cell Tower.
2.4.18 Drop Arrow
2.4.18.1 Definition
A drop arrow identifies the customer service from a Tap.
1. Use Drop Arrows to associate the Support Structure with the Addresses
served.
2. Create Drop Arrows per source.

2-21 July 13, 2012
3. Use the appropriate OH/UG Drop Arrow based on the associated Support
Structure.
4. Drop arrow Type should be “Unknown” if it is not shown on Source
1. Drop Arrow is to be associated with the Support Structure and the Address
2.4.19 Guy Span
2.4.19.1 Definition
The Overhead Guy Span that has no associated RF Network.
1. Last Strand segment without any RF network
1. Guy span should be placed at the midpoint
2.4.20 House Count
2.4.20.1 Definition
The number of Service connections from a Tap. House Count is an attribute of

Structure and Tap. However, because of its criticality, it has been treated separately in
the CSDD
1. House count should be shown per Source

2. Missing House count on source will be captured as “Zero” 0 Residential count
1. House Count should appear on the parcel side of the Support Route, parallel to
the Support Route, centered on the Structure.
2. If both residential and commercial House Counts are present, the residential
House Count is to remain centered on the Structure. The commercial House
Count is to appear as close as possible to the Structure, parallel to the Support
Route

2-22 July 13, 2012
1. House Count is associated with the Support Structure on which the serving
Tap is located.
2.4.21 Footage
2.4.21.1 Definition
It is the length of a Support Segment.

Footage is an attribute of Support Segment. However, because of its criticality, it has
been treated separately in the CSDD
1. Every Support Segment must have a footage. If not given on source, place a
Source Error Icon.
2. Footage show with asterisk ‘*’ should be captured without asterisk(*)
1. Footage should appear on the parcel side of the Support Route, parallel and
centered on the Route Segment, at an offset of 10’ between the Route
Segment and the insertion point of the Footage.
2. Footage should be shown opposing side of RF segment.
3. Footage for a slack span should appear above the arc.
2.5 Fiber Fabric
The Fiber Network must be drafted in strict order of connectivity, starting from the Headend to the
Node/Site for each Fiber Route.
Inactive entity notes should be captured from Source Maps. Example: Dead Cable and Dead
Equipment notes.
2.5.1 Headend
2.5.1.1 Definition
All CATV services originate at the Headend facility. It is in this building that the
satellite receivers are located and the CATV signal is transferred to the terrestrial
cable system. In the normal case, there would be one Headend per Market Area.
However, due to consolidation of different providers (such as Time Warner, Charter,
etc.), multiple Headend may be inherited by a Market Area.

2-23 July 13, 2012
1. Site Type – should be ISP

1. Site Name (Mandatory ) - to be taken from the Batch inventory: 2-char State
Code + 2-char Headend Code
2. Type – (Mandatory) Master, Standalone, or Backup, based on the symbol
shown on the source
3. Location – Name of the nearest cross street
4. A Term panle - (Mandatory) entity needs to be added to the Headend.
2.5.2 Node
2.5.2.1 Optical Node Definition
An Optical receiver that splits the signal from the fiber source into RF busses (see RF
Node). There are a maximum of 6 RF busses.
Mini Node: Is an Optical Node that is non-segmentable and is fed via a conventional
HFC fiber optic cable and architecture.
Mux Mini Node: A non-segmentable Optical Node that is fed via unconventional
muxing fiber architecture. In these architectures the fiber cable with muxing feeds a
"Mux Node", which is the primary or master node. The Mux Node then separates the
muxed wavelengths and then sends them out multiple fiber cable to feed up to 16
"Mux Mini Nodes", which are secondary or slave nodes.
2.5.2.2 RF Node Definition
The RF Node is the coaxial transmission device placed inside the Optical Node.
1. Node type
a. If the source map shows a Node with “MN” then redraft this as 1
output Mini-Node symbol (F_MINI1).
b. If the source map shows a Node with “SF” (Single Fiber) then redraft
this as 1X1 Node symbol (F_NODE1X1).
c. If the source map shows a Node anything else other than “MN” or
“SF” then use the 4X1 Node symbol (F_NODE4X1).
2. Designation (Mandatory) – Enter New Node Name from the “Old to new
Node Name List.xls” for the current Hub
3. Street Address – Enter if shown on source
4. Town – Enter if shown on source

2-24 July 13, 2012
5. Zip Code – Enter if shown on source

6. State – Enter if shown on source
7. Location – Name of the closest cross street
8. Legacy Node Number - Enter from the “Old to new Node Name List.xls” for
the current Hub.
9. Segmented Node should have appropriate Legacy Node names
10. Power Supply ID (Mandatory) – Enter from Source
11. Data Block (Mandatory) – Add Data Block feature
12. Unused ports must contain terminators
13. Circuit Construction Status – default ‘none’ unless shown different on source
14. Determining Buss IDs Missing on Source Maps – Many of the source maps
do not have named buss legs. To determine the buss names, orient the new
Comcast node the same as the source map node. Then match the original node
outputs straight across to the Comcast node buss ports
15. Segmented Node will have the appropriate Legacy node ID populated on the
connected devices.
16. Node inside MDU
• Should be an exception not a rule
• Node boundary should enclose the connected RF network in the MDU
detail view. If multiple Node exists in a MDU detail create Node
boundaries as needed

2-25 July 13, 2012
1. The Node is to be oriented in a manner that avoids RF cable crossing over

fiber cable and Support Segments
2. Node configuration based the cable output:
a. 2 Cable output: Port A and B
b. 3 Cable output: Port A, B and C
c. 4 Cable output: Port A, B, C and D
1. The following associations must be made for every Node:

a. Interface
b. Ports
c. Power Supply
d. Power Block
e. Power Inserter
f. Power Cable
g. Fiber Cable
h. RF Cable
i. Support Structure
2.5.2.6 Port Mapping Requirements
1. Interface should be created for port Mapping

2. Interface mapping type should be Instance based mapping
3. Forward port mapping should be from Optical Node side to the RF Node side
with the Direction set to “=>”
4. Return port mapping should be added from Optical Node side to the RF Node
side with the Direction set to “<=”

2-26 July 13, 2012
2.5.3 Optical Cable Entrance Facility OCEF
2.5.3.1 Definition
Optical Cable Entrance Facility is a cabinet in which Fiber Cable from the outside is
spliced. The OCEF is connected to the Term panel using Pigtail jumper within the
Headend or Hub. The pigtail jumper cable is a logical connectivity defined in
SpatialNET. The OSP fiber sheaths originate from OCEF to feed the Fiber network.
1. OCEF should be created, If an OCEF is shown on the source, the Standard

OCEF symbol is to be used. Otherwise, the False OCEF symbol is to be used.
2. If the source shows multiple Fiber Sheaths exiting the Head end/Hub then
place one OCEF for each direction.
1. Place the OCEF along the Head-End or Hub

2-27 July 13, 2012
1. If the Hub Termination details as provided the fiber splice matrix then connect
the Fiber cables to the Term panel using Pigtail Jumper.
2. Do not connect if there is no Termination detail.
2.5.4 Term Panel
2.5.4.1 Definition
Term or Patch Panels are not mapped in the Comcast network maps, but they do exist
logically within the engineering software sites for connection purposes. The Term
Panel is the connection point between Inside & outside Plant within a site.
Sites can be Head-Ends/Hubs, Cell Sites, INET Sites, or any other Fiber End Site
location. While some sites may contain many Term Panels, others may only contain
one (1). Additionally Term Panels can have varying Port Counts on them which need
to be accounted for when naming circuits.
1. If the Hub Termination details as provided the fiber splice matrix then connect
the Fiber cables to the Term panel using Pigtail Jumper inside the
Headend/Hub.
2. If the source shows multiple Fiber Sheaths from Fiber sites with the exception
of Node, multiple Term panels should be placed to accommodate the Fiber
sheaths.
3. Term panel at the Headend/Hub is different from other Fiber sites as per the
OSP Design Name Standard below shows the breakdown for Head-End/Hub
Term Panel naming, the final full name, and the total length of the name.

2-28 July 13, 2012
Hub/Site Equipment Name

Floor Isle Rack Chassis Port Full Name
Name Designator Length
TXEG TP 01 07 04 04 TXEG.TP.01.07.04.04 19
TXEG TP 01 07 04 04 0017 TXEG.TP.01.07.04.04.0017 24
4. Term panel naming for Fiber Sites is shown below
Equipment Term Name

Hub/Site Name Port Full Name
Designator Panel Length
CT.TXEG.0034 TP 0001 CT.TXEG.0034.TP.0001 20

CT.TXEG.0034 TP 0001 0002 CT.TXEG.0034.TP.0001.0002 25
Note: the port ID should be used when Master circuit ID is populated.
1. The fiber cables need to be connected to the Term panel using Fiber Splice
connections.
2.5.5 Hub
2.5.5.1 Definition
A Hub is the facility in which the Fiber Cable coming from a Headend is distributed
to Nodes within the Hub Area.
2. Site Type – should be ISP

3. Site Type (Mandatory) – Select Primary, Secondary or Hybrid from drop
down list, based on the symbol on the source.
4. Site Name (Mandatory) – Per Naming Standard.
5. Contact – Enter if shown on source
6. If the source shows multiple Fiber Sheaths from a Headend, multiple Term
panel should be placed.
7. Location (Mandatory) – Enter Hub name from Source

2-29 July 13, 2012
1. The fiber cables need to be connected to the Term panel using Fiber Splice
connections.
2.5.6 Institutional Network Site (INET)
2.5.6.1 Definition
Institutional facility that is served by Fiber cable, such as schools, universities,

government buildings, hospitals, etc.
1. The Fiber End Site symbol is to be used to depict INET sites.

2. Site Name (Mandatory) – Per Naming Standard
3. Location: capture if shown on source
4. Owner: capture if shown on source
5. Working Footage – 50’
6. Construction Status – default ‘none’ unless shown different on source
7. Site Type – should be OSP
8. Patch Panel (Mandatory) – A 12-count patch panel needs to be added
2.5.7 Fiber Customer Terminal Site (FCTS)
2.5.7.1 Definition
Commercial customer served by Fiber cable, such as offices.
1. Site Name – Per Naming Standard

2. Street Address – If shown on source
4. Whole Design Name (Mandatory) – Per naming Standard
5. Short Design Name (Mandatory) – Per Naming Standard
6. Job ID – Per source. If not available, place a Source Error Icon
7. Terminal ID – Per source
8. Legacy Name – populate with FCTS Owners ID ( Legacy ID shown at the
Commercial site)

2-30 July 13, 2012
9. Terminal Owner Name – Per source, if available

2.5.8 Cell Site
2.5.8.1 Definitions
Cell Site from which mobile services are back-hauled to the Hub.
1. The Cell Site Hub symbol is to be used to depict Cell sites.

2. Site Type – Name of Operating Customer as shown on source
4. Owner – the name of the carrier that owns the cell tower as per source
5. Working Footage (Mandatory) – 50’
6. Project ID – populate with Comcast Legacy ID
7. Legacy Hub - Name of the Hub
8. Static Frequency – Auto populated based on Carrier ID
9. Legacy Name – populate with Cell Owners ID: Example AT&T ID ( Legacy
ID shown at the Cell Tower)
12. Patch Panel (Mandatory) – A patch panel needs to be added, with the number
of patch counts as per source or, if not given, 12.
2.5.9 Point of Presence (PoP)
2.5.9.1 Definitions
Is a Fiber site where Comcast provides a fiber connection and then Comcast has no
idea how the customer uses it after that. This is usually for security reasons. Examples
of PoP are Government locations, Airports, etc…
1. Convert if shown on Source map


2-31 July 13, 2012

4. Street Address – If shown on source
5. Whole Design Name (Mandatory) – Per naming Standard
6. Short Design Name (Mandatory) – Per Naming Standard
7. Job ID – Per source. If not available, place a Source Error Icon
8. Terminal ID – Per source
9. Legacy Name – populate with PoP Owners ID ( Legacy ID shown at the PoP
site)
10. Terminal Owner Name – Per source, if available
2.5.10 Fiber Segment
2.5.10.1 Definition
A segment of Fiber Cable containing multiple Optic Fibers enclosed in a sheath

between two fiber devices.
1. Should be placed as single polyline between two Fiber devices

2. Fiber Segment Name – Per naming Standard; cannot be duplicated
3. Fiber Segment Length, Count and Cross-section – captured from the Fiber
Splice Detail spreadsheet
4. Fiber Segment Slack – to be set to 1.03 (3%)
5. If the Fiber Segment is shown as a Pigtail on the source, Working Footage
must not be populated. Instead, the length shown on the source should be
entered in the Fiber Cable Length attribute (default 100’)
6. Fiber Segment should be connected to Term panel starting at Port 1.
1. Fiber Interconnect if present should be drafted farthest from support route

2. If the support route is on the street side of the parcel Fiber cables should be
placed in the Parcel at the following offsets
a. 1st Fiber cable at 25’ offset from the support route
b. Subsequent Fiber cables at 10’ from the previous cable
2-32 July 13, 2012
3. Fiber counts should be placed before and after every Fiber Equipment. For
Fiber Segments exceeding 1,500’, multiple Fiber counts should be placed.
4. If the support route is in back of the parcel, Fiber cables should be placed on
the opposing side relative to the RF cable (if present) at the following offsets:
a. 1st Fiber cable at 25' offset from the support route
b. Subsequent Fiber cables at 10’ from the previous cable
1. Fiber Master Circuit ID should be auto-populated for the complete Fiber

Route
2. Fiber Segment should be associated to all Support Segments between the end
points of the Fiber Segment
2.5.11 Master Circuit Naming
2.5.11.1 Definition
A Master Circuit ID is a way of identifying the End-to-End (A-to-Z) path of an

individual service between a Head-End/Hub and a Fiber End Site. Master Circuits
ID's can be applied at the individual Fiber Strand level or to an individual wavelength
on a fiber strand when multiplexing (mux'ing) is present.
1. All Fiber End Sites get a Master Circuit except Nodes that have single
wavelength (no muxing).
2. Fiber Owner – Always should be ‘Comcast’ unless shown different on source
3. Fiber Usage Type code and priority should be as per OSP Design Naming
Standard.
a) If the entire forward path from the Head-End to Node or Fiber Site has no
mux'ing involved then that path is considered to be "Single-Wavelength",
therefore the Fiber State Code for the Node or Fiber Site port would also
be "Single-Wavelength" and the Fiber State Code is applied at the
individual fiber strand level.
b) If mux'ing is involved in any portion of the forward path from the Head-
End to the Node or Fiber Site then that path is considered to be
"Multiplexed" or "Mux’ed". The Node or Fiber Site port would also be
considered "Multiplexed" or "Mux'ed" and the Fiber State Code is applied
at the wavelength level.

2-33 July 13, 2012
c) These same considerations, points b & c, are to be applied to the entire

return path from the node or fiber site back to the head-end for
determining the return node port state.
4. Circuit Owner – should be populated with Cell service provider like T-

Mobile, AT&T or Verizon…etc. All other Fiber sites should be ‘Comcast’
5. Circuit Type – should be set to ‘Unknown’ unless shown different on source
6. Circuit ID – should be blank
7. Usage Description – should be updated with <Fiber site>. <Port ID>
8. Circuit Construction Status – should be ‘Constructed’ unless shown different
on source
7. Account Code – should be customers internal ID this should be same as
project ID
8. Master Circuit Type – valid types include Cell Tower, Fiber Customer, INET,
Node or Point of Presence
9. Master Circuit Owner – should be Comcast, AT&T, Cricket, Metro PCS,
Sprint, T-Mobile or Verizon.
• If the owner or customer name is not known then the master circuit ID
should have “Unknown” (minus the “ ”) for this attribute
10. Master Circuit Name - should be populated without spaces and separated with
“Dot” (.) <OwnerName>.<SiteID>.<Term panel Port ID> as per the OSP
Design Name Standard.
Note: for Node designation there is no ‘.’ (dot) separation in the site name
Owner/Customer
Name Unique Term Panel Port ID Master Circuit Name
TMobile CT.TXGP.0029.TP.0001.0021 TMobile.CT.TXGP.0029.TP.0001.0021
HomeFinder CS.TXEG.0058.TP.0002.0034 HomeFinder.CS.TXEG.0058.TP.0002.0034
Unknown CS.TXEG.0065.TP.0003.0022 Unknown.CS.TXEG.0065.TP.0003.0022
MDKR ND KIRK025.FWD01 MDKR.ND.KIRK025.FWD01
AustinCounty IN.TXHU.0041.TP.003.0045 AustinCounty.IN.TXHU.0041.TP.003.0045
GeorgeBushAirport PP.TXDA.0001.TP.0004.0056 GeorgeBushAirport.PP.TXDA.0001.TP.0004.0056
Hub-to-Hub Master Circuit Naming
Site #1 ID Separator Site #2 ID Site-to-Site Master Circuit Name
TXEG.TP.01.07.04.04.0017 - TXDA.TP.01.02.05.12.0042 TXEG.TP.01.07.04.04.0017-TXDA.TP.01.02.05.12.0042

2-34 July 13, 2012

2-35 July 13, 2012
2.5.11.3 Port Naming
1. Term Panels: All ports will be named using four (4) numeric digits, except in
Optical Nodes. All four (4) fields will be used starting with 0001 and continue
in sequential order.
2. Optical Node Receiving Ports: The port will be named using the three (3)
UPPER CASE alpha characters of "FWD" followed by two (2) numeric digits.
The two (2) numeric digits will start with 01 and continue in sequential order.
Example: FWD01.
3. Optical Node Transmit Ports: The port will be named using the three (3)
UPPER CASE alpha characters of "RTN" followed by two (2) numeric digits.
The two (2) numeric digits will start with 01 and continue in sequential order.
Example: RTN01.
2.5.12 Fiber Splice Case
2.5.12.1 Definition
Is a Fiber device used to join fiber cables. The primary source for Fiber splicing is
Fiber Splice Detail spreadsheet.
1. Mid Span Fusion should be captured if shown on source

2. Splice designation – Per Naming standard
2-36 July 13, 2012
3. The following attributes are to be populated from the Fiber Splice Detail
spreadsheet:
a. Type (Mandatory) (default: Fusion)
b. Legacy Splice ID – if available
c. Street Address – if available
d. Location – Name of the cross street
e. Working Footage (Mandatory) (default 50’)
f. Muxing – identified by ‘M’ in the Fiber Splice spreadsheet
1. Fiber Splice symbol should be aligned with the Fiber Segment
2.5.12.4 Fiber Splicing Requirements
1. Fiber Splice Spreadsheet should be used as the Primary source for Splicing
2. The Fiber color coded of the Field side Fiber Segment will be connected to the
specific sheath color and fiber on the Headend side Fiber Segment.
3. The Fiber segment at in a Splice case may be connected to multiple Fiber
segments on the field side. The color code and order of Fibers should be
connected as per Fiber Splice Spreadsheet.

2-37 July 13, 2012
1. Fiber Splice should be associated to Support Structure

2. The Fiber Splice Detail spreadsheet shows color coded connections between
fiber “bundles” contained in a Fiber Cable. This connectivity must be
maintained.
2.5.13 Fiber Riser
2.5.13.1 Definition
Fiber Riser is used to indicate a change in environment from OH to UG or vice versa
1. To be placed at every transition from OH/UG and UG/OH

2-38 July 13, 2012
2. Fiber Riser Length – Per source (default 25’)
1. Riser should be associated to the Support Structure
2.5.14 Fiber Storage Loop (In SpatialNet - Storage Loop)
2.5.14.1 Definition
Extra length of fiber cable at various points in the network.
1. Fiber Loop Symbol should be placed on the Fiber Cable at the location shown
on the source
2. Fiber Loop Length – Per source (default 150’)
1. Fiber Loop should be aligned with the Fiber Segment
1. Fiber Loop should associate to the Support Structure
2.5.15 Hub Stitch
2.5.15.1 Definition
Device used as a place holder on Interconnect fiber cable segments at the current Hub
boundary.
1. Hub stitch Symbol should be placed on the Fiber Interconnect Cable at the
Hub service area boundary
2. Place name should be captured from source map
1. Hub stitch should be aligned with the Fiber Segment
1. Hub stitch should associate to the Support Structure

2-39 July 13, 2012
2.6 RF Fabric
The RF Network must be drafted in strict order of connectivity, starting from each Node to the end
of line for each RF Buss.
Note: Passive Device Equipment name should be captured as per the OSP Design name standard.
2.6.1 RF Segment
2.6.1.1 Definition
A segment of RF Cable between two devices.
1. Each RF Segment must be a single polyline.

2. When Cables cross, use the Cable Jump feature.
3. Draft RF Segments with sag factor of 1 (no sag).
4. Construction Status – should be set to ‘Constructed’
1. If the support route is on the street side the RF cables should be placed in the
street at the following offsets:

2-40 July 13, 2012
a. 1st RF cable at 28’ offset from the Support Segment

b. Subsequent RF cables at 18’ from the previous cable
2. If the support route is in the back of the Parcel, RF cables should be placed on
the same side as shown on source following the offset rules.
1. RF Segment must be associated to all the Trench/Span Segments between the

end points of the RF Segment
2.6.2 Power Supply
2.6.2.1 Definition
The device that feeds power into a Power Inserter.
1. Number (Mandatory) – Per Naming Standard.

2. Status Monitor Type (Optional) – Capture per source
3. Legacy PS Number – Enter if shown on source
1. Power Supplies must appear in parcels, at a rotation of 0⁰.
1. Power Supply needs to be associated with the correct Support structure
2.6.3 Power Inserter
2.6.3.1 Definition
Is a device that allows power to be inserted into RF network from Power supply.
1. Power Cable should be connected in between Power Inserter and Power

Supply
2. Input/Output ports should be connected with RF Network
3. Unused ports should have Terminators
4. Power Inserter should be at the opposite end of Power Supply

2-41 July 13, 2012
1. Power Inserter should be associated with its Support structure
2.6.4 Power Block
2.6.4.1 Definition
Power block prevents the power from inserting into the RF Network
1. Should be connected to RF network

2.6.5 Tap
2.6.5.1 Definition
A Tap is a device that divides incoming signal so that separate properties can be fed.
The tap might be on a pole or in a pedestal on the ground.
From the tap the service drop runs to customer locations, either overhead or
underground.
1. Capture as per Source

3. EOL should be placed on the last Tap of the RF Cable Segment
1. Tap symbol should be centered and parallel to its Support Structure.

2. If a Tap is associated to the same Support Structure as another piece of
equipment, the snap point between the equipments should be centered on the
Support Structure.
3. End of Line (EOL) Datablocks, if applicable, are to appear close to the
Equipment so that the association is clear, at a rotation of 0⁰.
1. Tap is to be associated with its Support Structure

2-42 July 13, 2012
2. SpatialNet auto-associates Tap to Addresses. The number of Addresses

associated with a Tap cannot exceed the number of Ports. SpatialNet manages
this by dropping the “extra” Addresses.
2.6.6 Splitter
2.6.6.1 Definition
Splitter is a device that splits power equally to all downstream lines.
2.6.6.2 Conversion Rule
1. Capture if shown on Source

3. 3 Way Splitter should have Hileg dot
1. Should be placed with connected features in the RF Network
1. Splitter is to be associated with its Support Structure
2.6.7 Coupler (In SpatialNet – DC)
2.6.7.1 Definition
Coupler is a device that splits power flow unequally to downstream lines.
1. Leg Configuration – Match the source

1. Coupler is to be associated with its Support Structure

2-43 July 13, 2012
2.6.8 Combiner
2.6.8.1 Definition
Combiner is a Splitter/Coupler used in reverse. This allows the RF signal on 2 or

more cables to be combined onto 1 cable.

2.6.9 Terminator
2.6.9.1 Definition
A Terminator is required at every unused port and at the end of the last Segment of
every RF Route, to maintain the electronic integrity of the network.
2.6.9.2 Conversion Rule
1. Every unused Port on a device must have a Terminator with the exception of
Power supply unused port
2. Terminator EOL should not be placed at end of RF Cable segment
1. Terminators should be aligned with the cable.

2. If there is insufficient space (such as at 3-way splitters), the symbol can be
rotated as required.
1. Terminator is to be associated to its Support structure
2.6.10 Line Terminator (In SpatialNet – Self-Terminator)
2.6.10.1 Definition
Line Terminator is used at the end of RF Cable segment when no additional

customers can be serviced

2-44 July 13, 2012
1. Add a Line Terminator at the end of the last RF Segment in the following
cases:
a. 2 port Tap has value 4
b. 4 port Tap has a value 8
c. 8 port Tap has a value 11
1. The Line Terminator should be aligned with the RF Cable Segment
1. Line Terminator is to be associated to its Support structure
2.6.11 Amplifier
2.6.11.1 Definition
Amplifiers boost the cable signal to extend the length of the RF Network.
1. Device ID – Per Naming Standard. There cannot be duplicates.

2. Mode – Enter per source (A=Automatic, T=Thermal, M=Manual)
3. Capture Output Signal Strength (43db-49db)
4. Capture Component Type (None, Splitter, DC)
5. Capture DC, Signal Loss at Hileg Dot (-8 or -12)
6. Capture Through Port Number (Hileg Dot) and Tap Port Number
7. Data Block (Mandatory) – Add Data Block feature
8. Device ID Label (Mandatory) – Add Device ID Label feature
1. Amplifier should be aligned to the connected RF Network

2. Hileg Dot should be placed on the Leg with the Lowest signal loss
3. Data Block and Amplifier ID should be placed near the Amplifier

2-45 July 13, 2012
2.6.12 High Leg DOT
2.6.12.1 Definition
Notional symbol attached to either a Coupler or an Amplifier to indicate the leg with
the lowest signal loss.
1. Capture High leg Dot on the leg with the lowest signal loss “thru leg”.
1. High Leg Dot should be placed on the “thru leg” an Amplifier or Coupler
2.6.13 Line Extender
2.6.13.1 Definition
This is a small Amplifier. Most do not accept internal couplers (DA_LE1), but some
do (DA_LE2). Line Extenders (a.k.a. LE) require higher inputs than Mini-Bridgers
(amplifiers) and are distortion limited where as Mini-Bridgers are Noise limited and
typically have multiple output ports.
1. Capture as if shown on Source

1. should be placed and aligned to RF Network
2.6.14 Line Equalizer
2.6.14.1 Definition
Device used to attenuate the lower frequencies more than the higher frequencies to
offset cable line loss, thus flattening out the RF signal on all frequencies. "In- Line
Equalizer" can be used both "In-Line" and "Internally" in a devices.


2-46 July 13, 2012
1. should be placed and aligned to RF Network
1. Line Equalizer is to be associated to its Support structure
2.6.15 End of Line
2.6.15.1 Definition
End of Line is an annotation block placed at the last tap on RF Network branch. The
calculated RF signal levels out of the Tap Ports are populated into these blocks.
1. All End of Line (EOL) taps get EOL block placed.

3. EOL should be placed for all Terminators except for Terminators are the end
of RF segment with a Tap.
2. EOL block should be placed near the last Tap on RF Network branch
2.6.16 RF Splice
2.6.16.1 Definition
Is an equipment used to join 2 RF cables. There are 3 types. Straight splices can only
join 2 identical cable types (Identical Cable Type means same Size, Generation, and
Manufacturer). Block and Tap Housing splices are used to join 2 different cable
types, but can also be used in place of a Straight splice.

2. Capture the appropriate Splice Type of Straight - "S", Block - "B", or PBA -
"T" per source
3. Source Error Icon should be placed when Source map violates the Identical
Cable Type rule.
Example:
CommScope P3-500; Size = 0.500", Gen. = P3, Manf. = CommScope.

2-47 July 13, 2012
Trilogy MC2-500; Size = 0.500", Gen. = MC2, Manf. = Trilogy.

The above 2 example RF Cables are 500 cables, but are not Identical Cable
Types.
1. Should be aligned with connected features in the RF Network
2.6.17 Converter Box
2.6.17.1 Definition
Set Top Box that goes on top of a customer’s TV. These are used in some Drop and
Insert Networks.
1. Should be placed with connected features in the RF Network (Drop and

Insert).
2.6.18 Processor
2.6.18.1 Definition
Device that takes a RF modulated frequency/channel and heterodynes it to a desired

frequency/channel. These are used in some Drop and Insert Networks as well as in
Inside Plant
1. Should be placed with connected features in the RF Network (Drop and

Insert).

2-48 July 13, 2012
2.6.19 Modulator
2.6.19.1 Definition
Is a device that takes base-band video and adds it to a carrier wave at a desired
frequency/channel. This is known as "Modulation". These are used in some Drop and
Insert Networks as well as in Inside Plant.
1. Should be aligned with the connected RF Network (Drop and Insert).
2.6.20 Inline Pad
2.6.20.1 Definition
In-Line Pad, device is used to attenuate all RF signal by the same, defined amount.
These are used in some Drop and Insert Networks.
2.6.21 Notch Filter
2.6.21.1 Definition
Device used to remove or strip out 1 or more defined adjacent frequencies/channels

from the RF signal spectrum. These are used in some Drop and Insert Networks as
well as in Inside Plant. Notch filter is also called Trap.

2-49 July 13, 2012
2.6.22 Source
2.6.22.1 Definition
Alternate video source used in a Drop and Insert Network. Source can be a VCR,
Camera etc. It is called as Other Source
2.6.23 Generic Drop and Insert Network
2.6.23.1 Definition
Is used to show Channel Drop & Insertion at a location, but the details of how that is
being done has not been captured.

2. When Drop & Insert configurations are found in source map or data that do
not contain details of the equipment or devices
2.6.24 Band Pass Filter

2. When Drop & Insert configurations are found in source map or data that do
not contain details of the equipment or devices

2-50 July 13, 2012
2.6.25 Fiber Terminator
2.6.25.1 Definition
A device used on Fiber Network similar to RF Terminator
1. Should be captured at the end of a Fiber cable segment or output port of a

Fiber device.
1. Should be aligned with the connected Fiber Cable segment or Equipment.
2.6.26 Power Cable
2.6.26.1 Definition
Is a cable that is used to connect Power Inserter with the Power Supply.
1. Use RF Cable feature, with the correct Power Cable Type “PC-xxx”.
2. Footage – When the power supply (PS) and power inserter (PI) are co-located
on the same support structure, enter footage as 15’.
3. If the power supply and power inserter are mounted on separate support
structures, enter footage as 15’ plus the Trench/Strand/Conduit length.
1. If the support route is on the street side the RF cables should be placed in the
street at the following offsets:
c. 1st RF cable at 28’ offset from the Support Segment
d. Subsequent RF cables at 18’ from the previous cable
2. If the support route is in the back of the Parcel, RF cables should be placed
inside the parcel at the same offsets
1. RF Segment must be associated to all the Trench/Span Segments between the

end points of the RF Segment

2-51 July 13, 2012
2.6.27 Status Monitor Cable
2.6.27.1 Definition
Input cable or drop to a RF network equipment typically inside a power supply. These
devices monitor the network performance and then communicate that data back to the
main office.

2. Status Monitor Drop is not part of the RF Network
3. Status Monitor on source should be converted as DC coupler with a value of
– 12
1. SM Drops from a tap should be a polyline from the Tap to the Status Monitor
port on the power supply.
2. Status Monitoring Cable should be connected to Power supply output port.
2.7 Features in Comcast Legend not in Comcast Specs
1. Node Extender
2. Mini Bridger
3. Network Interface Unit
4. In-line Equalizer
5. Digital Loop Carrier
6. Direct Connect Start Point
7. RF Wireless Device
8. Step-down Transformer
9. Make Ready Note
10. New Build Boundary
11. VMDU Cable Transition
12. Walkout
2.8 Boundaries
1. Boundaries shared with adjacent service areas must have coincident vertices.

2-52 July 13, 2012
2. Boundaries must follow Parcel Lot lines or Street Centerlines.

3. If a Support Network is shared by two Node service areas, the Node Boundaries must be
drawn so as to include the Support Network in one of them.
4. Water features must be fully included in one of the adjacent Boundaries
5. The Buss boundaries must fill all the space within a Node Boundary
6. The Power Supply boundaries must fill all the space within a Node Boundary
7. A Boundary must fully enclose every feature of the Support and RF Network in the Node,
Buss, or Power Supply service area.
2.8.1 Node Boundary
2.8.1.1 Definition
The Node Boundary defines the service area for a Node.
1. The Node Boundary does not include the Fiber Cable serving the Node or
connecting two Nodes.
2. Donut Node Boundary. A Node Boundary contained entirely within another
Node
Figure 7 shows an example of a Donut. Blue shaded area is a Node contained
entirely within the Node Boundary shaded in green. In this situation, the
Donut Node is to be created as shown, with a small “passage” for the Fiber
feed.

2-53 July 13, 2012
Figure 7: Example of a Donut

2-54 July 13, 2012
3. Island. An Island is an area within one Node Boundary that is fed by RF

Cable from another Node.
Figure 8: Example of an Island

2-55 July 13, 2012
The current version of SpatialNet has no way to model Islands. In this

situation, do not convert facilities in the Island. Instead, place a closed
polygon and add a Source Error Icon.
1. Node annotation should be placed along the Node boundary

2-56 July 13, 2012
2.8.2 Buss Boundary
2.8.2.1 Definition
The Buss Boundary defines the service area of every RF Buss, and includes every
features of the RF Network that is served from a single port of the Node.
1. Service Area Type – To be set to ‘2’

2. Buss Boundary should be drafted even if it is NOT shown on source map.
2.8.3 Power Supply Boundary
2.8.3.1 Definition
Power Supply boundaries are placed on the network to identify the area feed by a
particular power supply. This method is used to avoid having to place individual
power block at every location where the power supply stops feeding the RF network
1. Power Supply Boundary should contain all parcels and/or addresses that may
lose service if there is a power supply failure.
2. Dual or Quad output power supplies systems, Power Supply Boundary should
be drafted for each power supply output port.
3. Create a Power Supply Boundary only if shown on the Source
2.9 MDU Detail
2.9.1 Definition
An MDU Detail is required for Addresses for which a separate MDU detail AutoCAD
drawing has been provided for conversion.
2.9.2 Conversion Rules:
1. Source MDU Detail drawings are separate AutoCAD files, named by the Job Number
shown on the System Map . These are to be imported into the MDU Detail View per
the following rules.
2. The orientation of the MDU Detail View must be the same as the System View.
3. MDU Detail Source should fit within the Node boundary
4. Remove Support, RF and Fiber Network from the imported AutoCAD MDU Detail
Source
2-57 July 13, 2012
5. Save the MDU Detail View

6. Create Support, RF and Fiber Network using SpatialNET in MDU Detail View
7. A Support Attachment Point must be placed at the end of the last Support Segment in
the System View. A corresponding Support Attachment Point must be placed in the
MDU Detail View. A zero length strand must be placed form the Support Attachment
Point to the next Support Structure in the MDU Detail View.
8. A Fiber or RF DMark must be placed at the end of the last Cable Segment in the
System View. A corresponding DMark feature must be created in the MDU Detail
View.
9. Only MDU-size symbols are to be used in the MDU Detail View
10. For a high-rise MDU, the “Vertical Detail Storey” feature is to be used.
11. MDU Detail should be contained within its Node boundary
12. The Support, RF and Fiber Network are to be captured as per the Source MDU Detail
Drawing.
2.10 White Space Management
2.10.1 Permitted overstrikes
1. Drop Arrows may overstrike Structure symbol

2. Address LOC Block may overstrike parcel boundaries
3. Features may overstrike Street Centerlines
4. Support, RF, and Fiber segments may overstrike parcel boundaries
2.10.2 Hierarchy of adjustment
1. Place Bridges at every cable cross-over

2. Ensure that cables Segments are parallel or perpendicular as per Device type
specifications
3. Resolve overstrikes in the following order:
a. Address (move first)
b. House Count
c. Strand Segment Length
d. Cable Segment (move last)
2.11 Source Error Icons
2.11.1 Support Route
1. Place Source Error Icons in areas where Support Route is missing

2-58 July 13, 2012
2.11.2 Fiber OSP
1. Place Source Error Icons in areas where Fiber Sheath is missing

2. Place Source Error Icons when Fiber Cable type switch within a span
3. Place Source Error Icons if the Fiber Trace does not terminate at HUB
2.12 Delivery Reports
1. Source Error Icon Log

2. Exception Log
3. Quality Acceptance Certificate
4. Billing Quantities Report

2-59 July 13, 2012
3.0 Production Work Flow & Instructions
General Rule:
Every Task starts with the following login activity:
Step 1: Log into ProACT. ProACT serves up all required source files.
Step 2: Log into SpatialNet. Enter the SpatialNet JobID per the naming convention in
Section 1.5.1.
Step 3: Launch AutoCAD, attach all System Maps for the WorkPackage
3.1 Task B1: Prep Source for Production
Step 1: Download source files from ProWEB (including file manifest).

Step 2: In ProACT, define WorkPackages for each Node, using the naming convention
defined in Section 1.4.
Step 3: Create a database schema for the new Hub & import the database dump
provided in to SpatialNet Server.
3.2 Task W2: Place Addresses and Node Boundary
Step 1: Find Node on System Map. Identify a parcel number near the Node feature.
Step 2: In SpatialNet, search for this parcel number
a. Search for this parcel number.
b. Select the correct record based on street name
c. If no match (rare case when parcel number is missing in Landbase), try
adjacent parcel number
Step 3: Select a parcel polygon. Offset 20’ inside the parcel to create a temporary
polygon.
Repeat for all parcels.
Step 4: Select the street centerline and create the Address Text according to offset rules.
Step 5: Chose Address LOC block for parcels containing a Structure in the System map
Step 6: Clean up for:
Overlaps (rotate to perpendicular, or move)
Incorrect alignment/placement
Repeat for all Streets
Step 7: Delete the temporary offset buffer.

3-1 July 13, 2012
Automated Process (future):

Step 8: Select 1st street centerline. (If necessary, create new Centerlines and/or Road-
edges as specified in Section 2.3.3.
Step 9: Place addresses in the parcels using “PlaceAddress” command per the
specifications in Section 2.3.1.
Exit PlaceAddress tool for the following:
1. Transitions between Residential, Commercial, or MDU building types
2. Change in the Address increment value
3. Break in Address number sequence (e.g., 101, 103, … to 2203, 2204)
4. New Street
Repeat this for all street blocks.
Step 10: For a parcel requiring an MDU Detail, create a placeholder for the MDU
Detail:
1. Place a Building Feature in the parcel.
2. In Address Details, Select “Owning Building”.
3. Select “Add/Drawing”
4. Enter building name from the System Map as the drawing name.
Step 11: Create Node Boundary based on the System Map.
If on mid-block parcel, snap to parcel boundary. If on last parcel in the block,
place in middle of the street.
Step 12: Adjust the Node Boundary for Islands and Donuts as described in Section 2.8.1.

3-2 July 13, 2012
Automation (future):
Step 13: Run the following SpatialNet scripts and correct all errors:
1. “AssociationCheck”
2. “PoleRiserCheck”
3. “SnapCheck”
4. “FootageCheck”
Step 14: To mark the Task as completed, the log files must contain no errors.
3.3 Task W3: 100% In-Line QC: Address & Node Boundary
Perform the following checks and make the required corrections.

Step 1: Check for the following and make necessary corrections:
a. incorrect associations between Street Centerline and Addresses.
b. missing addresses.
Step 2: Visually inspect Addresses to ensure that offset is roughly consistent across
parcels.
Step 3: Run “QA Network Analysis” tool and correct all errors listed in the log file.
3. “SnapCheck”
Step 5: Log errors in “6301-bbbb InLineQCReport” in ProACT.

Step 6: To mark the Task as completed, the log file created by “QA Network Analysis”
tool must contain no errors.

3-3 July 13, 2012
3.4 Task W4: Create Support Network
Step 1: Identify 1st Buss from the Node

Step 2: Select parcel polygon. Offset 10’ inside the parcel to create a temporary
polygon.
Repeat for all parcels.
Step 3: Select the Block PLine for the first city block.
Step 4: Use “CreateNetwork” tool to place Structures, House Counts, Support
Segments, and footage.
The tool will require the user to pick the Fiber Device on the System Map
before placing it in SpatialNET. Likewise, the tool requires the user to pick
the Cable Segment (or segments, if it is broken into multiple vectors)
before creating it in SpatialNET.
The user will also be required to pick the attribute value objects (if any) in
the System Map and these values are populated in SpatialNET, such as
House Count and Footage.
In addition, an inventory check is done on the System Map, ensuring that
no features were left without being redrafted in SpatialNET.
Step 5: Place starting Structure and capture House Count (if required for the structure
type)
Step 6: Select Support Segment type
Step 7: Enter Support Segment length
Step 8: Place Support Segment between two Support Structures. For OH the Support
Segment is a straight line. For UG, the Support Segment is created in rubber-
band mode so that the Pline can have multiple vertices.
Step 9: Enter House Count for next Structure
Step 10: Enter Riser length, if applicable (for OH only)
Step 11: Place end of Support Segment at next Structure location
Repeat for all Busses.
Step 12: Delete temporary parcel polygons

3-4 July 13, 2012
Step 14: Run “WhiteSpaceCheck” to identify overstrikes and:
a. Move Footage symbol if it overstrikes with the parcel boundary or
other features.
b. Note: Contrary to previous practice, do not move the House Count
symbol from its default placement
1. “Association Check”
3. “SnapCheck”
Step 13: If Support Segment extends beyond Node Boundary, refresh view
1. If adjacent Node features are visible, place end of Support Segment at
adjacent Node Structure
2. If adjacent Node features are not visible, do not capture the last Support
Step 17: Place Drop Arrows for all Structures with House Counts
1. Pick Structure
2. Select Drop Type
3. 3. Pick Addresses that are shown on the system map as connected to the Structure
Segment
Step 18: Perform White Space Management
1. Move Footage symbol if it overstrikes with the parcel boundary or other
features.
2. Note: Contrary to previous practice, do not move the House Count symbol
from its default placement
3.5 Task W5: 100% In-line QC: Support Network
Step 1: Verify Footage value for every Segment of the Support Network.
Step 2: Verify that the correct OH Structure symbol is used

3-5 July 13, 2012
3. “SnapCheck”
5. “WhiteSpaceCheck”
Step 3: Visually check that Span annotation does not overlap with the parcel or on the
support network
Step 5: Visually verify that Structure & Support Segment offsets are roughly consistent
with respect to parcel boundaries.
Step 6: Verify correct riser lengths placed at OH to UG transitions
Step 8: Log errors in “6301-bbbb InLineQCReport” in ProACT
Step 9: To mark the Task as completed, the log file created by “QA Network Analysis”
tool must contain no errors.
3.6 Task W6: Create Hub
The Hub WorkPackage must be performed first, prior to any of the other Fiber
WorkPackages.
Step 1: Create Hub Feature in Hub WorkPackage
Step 2: Capture the Headend/Hub name from the System Map
Step 3: Count the total fiber cables exiting from Headend/Hub as shown on the System
Map; add one or more OCEF (Use Patch panel until SpatialNET software is
updated) features to accommodate this fiber count.
3.7 Task W7: Create Fiber Network
This Task will be performed on all the Fiber WorkPackages. One Fiber WorkPackage
must be in production at all times.
Step 1: Create temporary offset lines from all Support Segments as per the offset rules
Step 2: Pick the Node Port as the starting Device
Step 3: Select correct Fiber Cable Type based on the count in the Fiber Splice Matrix

3-6 July 13, 2012
Step 4: Place Cable Segment from current Device to next Device overlaying the offset
line and picking every Strand Segment along the way.
Note: To properly model connectivity, Cable Segments must be created in strict
downstream connectivity order.
Step 5: Place Fiber Count entities using “Annotate Selected Entity” as per the
requirement in Section 2.5.10.
Step 6: Select correct Fiber Cable Type based on the count in the Fiber Splice Matrix
Step 7: Use “CreateNetwork” to place Fiber Splices and Cables, picking every
Support Segment along the way.
The tool will require the user to pick the Fiber Device on the System Map
before placing it in SpatialNET. Likewise, the tool requires the user to pick
the Cable Segment (or segments, if it is broken into multiple vectors) before
creating it in SpatialNET.
The user will also be required to pick the attribute value objects (if any) in the
System Map and these values are populated in SpatialNET.
In addition, an inventory check is done on the System Map, ensuring that no
features were left without being redrafted in SpatialNET.
Step 8: At each Splice add a Multiplexer or Coupler to the Splice if shown in the Fiber
Splice Matrix Spreadsheet.
Step 9: Connect each individual Fiber Cable per the “Fiber Splice Matrix” spreadsheet
Step 10: If Fiber Cable serves an MDU Detail, add a pair if DMark objects, one in the
System View near the MDU building object and the other in the MDU Detail
View.

3-7 July 13, 2012
Step 11: Run the following SpatialNet Scripts and correct errors:
1. “Network Trace”
2. “NameCheck”
Step 12: Connect the Fiber Cable to the optical side of the Node. If the Node has not yet
been created, place a Fiber Terminator at the end of the last Fiber Segment.
3.8 Task W8: 100% In-line QC: Fiber Network
Step 3: Verify that the Fiber Count matches the OCEF type.
Step 4: Verify that the Fiber Route placement matches the placement on the System
Map.
Step 5: Verify that “Custom Segment Annotation” is placed for each Fiber Segment.
Step 8: To mark the Task as completed, the log file created by the “QA Network
Step 1: Run the following SpatialNet Scripts and correct errors:
1. “Network Trace”
2. “NameCheck”
Analysis” tool must contain no errors.
3.9 Task W9: Create RF Network
Step 1: Construct Node Feature

1. Select correct Optical Node type and place perpendicular to Support
Segment (or parallel if necessary for white space consideration)
2. Assign name per new Node name convention from Node Name spreadsheet.
3. Select correct RF Node type

3-8 July 13, 2012
4. Create Interface
5. Map all Ports
6. Place Power Supply
7. Place Power Inserter
8. If the Fiber Route to the Node has already been created in Step 12 of Task
W7 and ends at a Fiber Terminator, delete the Terminator and connect the
Fiber Segment to the Optical Node.
9. Select correct Power Cable type
10. Connect Power Supply with Power Inserter
Step 2: Pick a Node Port as the starting point for the Buss.
Step 3: Create temporary offset lines from all Support Segment Segments per the offset
rules
Step 4: Select correct Cable Type
Note: To properly model connectivity, Cable Segments must be created in strict
downstream connectivity order from the Node, Splitters, Directional Couplers and
Amplifiers to the Terminators.
Step 5: Place Cable Segment from current Device to next Device overlaying the offset
line and picking every Support Segment along the way.
Step 6: Select Structure which terminates the Cable Segment
Step 7: Select correct Device type, enter attribute values, and place in correct location.
Step 8: Add a Source Error Icon if there is a break in the network.
Repeat for all Cable Segments on the Buss
Step 9: Create Buss and Power Boundaries if shown on the source.

3-9 July 13, 2012
Step 10: Pick the Node Port as the starting point for the Buss
Step 11: Select correct Cable Type
Step 12: Use “CreateNetwork” tool to place Cable Segment from current Device to
next Device, picking every Support Segment along the way.
The tool will require the user to pick the Device on the System Map before
placing it in SpatialNET. Likewise, the tool requires the user to pick the
Cable Segment (or segments, if it is broken into multiple vectors) before
creating it in SpatialNET.
The user will also be required to pick the attribute value objects (if any) in
the System Map and these values are populated in SpatialNET.
In addition, an inventory check is done on the System Map, ensuring that no
features were left without being redrafted in SpatialNET.
Step 13: If cable serves an MDU, add a DMark object near the MDU building object
(ensure no objects are selected except the Address)
1. Click “Add MDU Drawing DMark” button in the toolbar
2. Specify location of the DMark symbol in both the System View and the
MDU Detail View.
Step 14: Until SpatialInfo adds the logic to automatically associate Taps and Addresses,
perform the following steps, place Drop Arrows:
1. Pick Device
2. Select Drop Type
3. Pick Addresses as per House Count (up to the number of Ports)
Repeat for all Busses
Step 15: Run the following tools until the automated tools:
a. Service Area Manager
b. RF Level and RF Power Tool
c. RF Network Scripts.

3-10 July 13, 2012
2. “RFNetworkScripts”
3. “NetworkTrace”
4. “NameCheck”
5. “SnapCheck”
6. “NodeCheck”
7. “ServiceAreaManager”
3.10 Task W10: 100% In-line QC: RF Network
Step 1: Verify that Node feature construction is correct, including port mapping.
Step 2: Check all busses are originated from correct ports as per the source.
Step 3: Select a buss starting from the Node
Step 4: Check for the correct type of cable placed as per source
Step 5: Check RF cables are placed as per the offset rules
Step 6: Verify that Cable Segments are associated to the correct Support Segment.
Step 7: If the device is an Amplifier, perform the below steps:
1. Check correct type of amplifier is selected and correct components are
added into it.
2. Amplifier should be named according to standards.
Repeat for all Busses
Step 10: To mark the Task as completed, the log files created by the “QA Network

3-11 July 13, 2012
4. “NameCheck”
5. “SnapCheck”
6. “NodeCheck”
3.11 Task W11: Create MDU Detail View
Step 1: Select DMark symbol in the System View and open the MDU Detail View
Step 2: Add Building Footprint to the MDU Detail View
1. Select node boundary in the System View
2. Select Edit/Copy with base Point
3. Enter 0, 0 in the command prompt
4. Select the highlighted node boundary
5. In MDU Detail View, select “Edit/Paste to Original Coordinates”
6. Select Zoom extents command to view entire Node Boundary in the MDU
Detail View
7. Insert the Source MDU Drawing
8. Place the Source MDU Drawing inside the Node Boundary; scale as needed.
9. Delete the Title Block and all Structure, RF and Fiber Network objects in the
Source MDU Detail (use layer names where appropriate). This will leave
only the landbase and building objects required to create the MDU Detail
View.
10. Rotate Source MDU Detail Drawing to approximately the same orientation
as the System View
11. Delete the Node boundary in MDU Detail View
12. Save the MDU Detail View
Step 3: Starting from the DMark, create the Support and RF Networks in MDU
Detail View using the process specified in Sections

3-12 July 13, 2012
Task W4: Create Support Network and Section 3.7 Task W7: Create Fiber Network.
(Fiber will be done at the Hub level)
1. Open the Source MDU Detail Drawing
2. Place Unit Numbers in the MDU Detail View
5. “NameCheck”
6. “SnapCheck”
7. “MDUDetailCheck”
8. “ServiceAreaManager”
3. Place Support Attachment Point in the MDU Detail View

4. Add a Support Segment of 0 length from the Support Attachment Point to
the first Structure (A 0’ span length will not display).
Step 6: Run the following tools until the automated tools:
a. Service Area Manager
b. RF Level and RF Power Tool
c. RF Network Scripts.
3.12 Task W12: 100% In-line QC: MDU Detail View
Step 1: Check whether DMark symbol and SpatialNet MDU Detail drawing are
associated correctly to the proper Building address.
Step 2: Check for unwanted CAD Features.
Step 3: Verify Footage value for every Segment of the Support Network.
Step 4: Verify that the correct OH Structure symbol is used
3-13 July 13, 2012
Step 5: Visually check that Span annotation does not overlap with the parcel or on the
support network
Step 6: Check for the correct type of cable placed as per source
Step 7: Verify that Cable Segments are associated to the correct Support Segment.
Step 8: If the device is an Amplifier, perform the below steps:
1. Check correct type of amplifier is selected and correct components are
added into it.
2. Amplifier should be named according to standards.
Step 9: Verify correct riser lengths have been placed at the transition points from OH to
UG.
5. “NameCheck”
6. “SnapCheck”
Step 10: Check for the following and make necessary corrections:
a. incorrect associations between Street Centerline and Addresses.
b. missing addresses.
Step 15: To mark the Task as completed, the log file created by the “QA Network
Task B13: Perform White Space Management

3-14 July 13, 2012
Look for overstrikes and resolve conflicts according to the white space management rules
specified in Section 2.10
Run “WhiteSpaceCheck” and correct overstrikes as needed. Refer to Section 2.10 for
white space management rules.
3.13 Task B14: Edge-Match All Boundaries
Step 1: Ensure that Node Boundaries (and Buss and Power Boundaries, if present) are
well formed, as specified in Section 2.8.
Step 2: Run “BoundaryCheck” and correct as necessary.

3.14 Task B15: Run SNBatchProcess
Run “SNBatchProcess” to auto-populate place and location data (see Section Error!
Reference source not found. for details).

3-15 July 13, 2012
4.0 Appendix A: Target Placement Exhibits
Insert examples of features placed as per placement and offset rules.

4-1 July 13, 2012
5.0 Appendix B: Source and Target Symbols
Source Depiction Target SpatialNET

Source Source Feature Target
Sl No Category Source Symbol Target Symbol
Map Type Name Feature Name
System
1 Pole Joint Pole Joint Pole
Map
Joint
System Joint Transformer
2 Pole Transformer
Map Pole
Pole
System
3 Pole Power Pole Power Pole
Map
Power
System Power
4 Pole Transformer
Map Transformer Pole
Pole
System
5 Pole Telco Pole Telco Pole
Map
System
6 Pole CATV Pole CATV Pole
Map
System
7 Pole Riser Riser
Map
System Pole with

8 Pole Anchor
Map Anchor
System
9 Strand Strand Strand
Map
System
10 PED Pedestal Pedestal
Map

5-1 July 13, 2012
System
11 UG Tic UG Tic UG Tic
Map
System
12 UG Lock Box UG Lock Box UG Lock Box
Map
System
13 UG Trench UG Trench UG Trench
Map
System
14 UG Conduit UG Conduit UG Conduit
Map
System
15 RF Cable 500 RF Cable P3 500
Map
System
Map
System
Map
System
Map
System
Map
System
20 Tap 2 Port Tap 2 Port Tap
Map
System
Map
System
Map

5-2 July 13, 2012
System
23 Splitter 2 Way Splitter 2 Way Splitter
Map
System
24 Splitter 3 Way Splitter 3 Way Splitter
Map
System Directional Directional Directional

25
Map Coupler (DC) Coupler (DC) Coupler (DC)
System
26 Equalizer Equalizer Equalizer
Map
System Power
27 Power Inserter Power Inserter
Map Inserter
System
28 Power Block Power Block Power Block
Map
System
29 RF Splice Splice Block Splice Block
Map
System Hot leg

30 Hot leg Indicator Hot leg Indicator
Map Indicator
System
31 Terminator Terminator Terminator
Map
System
32 Line Extender Line Extender Line Extender
Map
System Single system Single system

33 Amplifier
Map Amplifier Amplifier
System Dual System Dual System

34 Amplifier
Map Amplifier Amplifier

5-3 July 13, 2012
Triple System
System Triple System Amplifier
35 Amplifier
Map Amplifier
System
36 Power Supply Power Supply Power Supply
Map
System Status
37 Status Monitor Status Monitor
Map Monitor
System
38 Fiber Splice Fiber Splice Fiber Splice
Map
System
39 Storage Loop Storage Loop Storage Loop
Map
System
40 Fiber Cable Fiber Cable Fiber Cable
Map
System Fiber and RF Fiber and RF Fiber and RF

41
Map NODE NODE NODE
System
42 Line Equalizer Line Equalizer Line Equalizer
Map
System Self
43 Terminator Self Terminator NA
Map Terminator
System Power supply

44 Power supply Power supply
Map Pedestal
System
45 Manhole Manhole Manhole
Map
System UG Mount
46 UG Mount Point UG Mount Point
Map Point

5-4 July 13, 2012
System
47 Cell Tower Cell Tower Cell Tower
Map
System
48 UG Vault UG Vault UG Vault
Map
System
49 Road Bore Tic Road Bore Tic Road Bore Tic
Map
Drop and
System Drop and Insert Drop and Insert
50 Insert
Map Network Network
Network
System
51 Splice Splice T Splice T
Map
System 2 Way
52 Splitter 2 Way Combiner
Map Combiner
System MDU Notch MDU Notch

53 MDU Notch Filter
Map Filter Filter
MDU
System Processor
54 MDU Processor MDU Processor
Map
System 3 Way
55 Splitter 3 Way Combiner
Map Combiner
System MDU
56 MDU Modulator MDU Modulator
Map Modulator
System MDU
57 MDU Convertor MDU Convertor
Map Convertor
System MDU Inline

58 MDU Inline Pad MDU Inline Pad
Map Pad

5-5 July 13, 2012
System
59 MDU Source MDU Source MDU Source
Map
System
60 Cell Site Cell Site Cell Site
Map
System Master Head

61 Head End Master Head End
Map End
Fiber
System Fiber Customer Fiber Customer
62 Customer
Map Terminal Site Terminal Site
Terminal Site

5-6 July 13, 2012
6.0 Appendix C: Fiber Workpackage Definition
End of End of
Line Line
End of
01
Line
F0
2
F0
01
2
01
End of
2
F0 Line
2
20
F020
F0
02
F0201
2
F0
201 F0
1 0
F02
2 0 2
F02
0 F02
End of
F0202 Line
F0201
F0
2 02 202
F0
1 0
F02
01 F0203
F01
01
F02 F0203
End of
F0
Line
20
3
F0000
F 02
03
F0
F0203
30
End of
F0203
1
Line
End of
Line
WorkPackages created should be:
1. 4-8 miles long
2. Crossing no more than 3-4
Node Workpackage

5-7 July 13, 2012

SpatialInfo Redrafting PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SpatialInfo Redrafting PDF

Uploaded by

Copyright:

Available Formats

Apex CoVantage, LLC

Conversion System Design Document

1.0 April 19, 2011 Initial release Prakash Shinde

1. Updated section 3.3

1. Updated Feature and

1.0 Project Overview

The project scope is to move the following elements to a Comcast-provided landbase

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

1.3 Project Documentation

SpatialNet software is being maintained under strict version control and

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

1. Cable 101 Training and Certification Manual

1.4 Batch and Work Package Definitions

1.4.1 Node Workpackages

Node WorkPackages comprise all of the geography served by a Node.

1.4.2 Fiber WorkPackages

1.4.3 No Production Lots

1.5 SpatialNet Information1

1.5.2 Job Status and Access

The status of SNet Jobs are:

3. Posted – Once a task on a Job is completed, it can be posted. A Posted

1.5.3 SNet Job Posting Process

1.5.3.1 Posting Queue

1. When a Task is designated as “completed” in ProACT, the

1.5.3.2 Posting Schedule

Posting will be performed

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

1.7 Source Materials

Source Format Description

Systems Maps contain the network for a set of Nodes.

Node Maps are used as a reference to clean up the

These are detail drawings of Multiple Dwelling Units

5. Fiber Interconnect MS Excel Fiber network across Hubs.

Comcast maintains the detailed splicing information

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

Deliverables for Comcast NGIP Redraft project as follows:

1.9 Project Terminology

This is a temporary object created to place objects at the required offset

Buss A single RF circuit starting from a Node

Cable RF (Coaxial) and Fiber cables

Device Network devices such as Taps, Splitters, and Amplifiers

Route A single Fiber circuit starting from a Hub

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

Linear feature between two point features:

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

2.0 Target Specification

2.1 Cable Network Connectivity Model

2.1.1 Introduction to Cable Networks

2.1.2 Hybrid Fiber Coax – HFC

Figure 1: Typical HFC Network

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

1. Connectivity requires that Fiber and RF Networks be drafted in strict downstream

2.1.4 General Redrafting Rules

1. Inside-plant entities are out of scope for this project.

2.1.5 Features and Attribute To be Captured

Figure 2: Feature and Attribute Source Matrix

2.2 Source to Target Symbology Map

Appendix B contains the map for source and target symbology.

2.3 Landbase Fabric

2.3.1.2 Conversion Rules

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]

2.3.1.3 Placement Rules

6301-SpatialInfo Redrafting CSDD (Rev 2.2) - To Subcontractor (2)[5754]