Arrow comes preloaded with a number of reports that provide plan outputs in a variety of formats and granularity levels. Here are the most commonly-used ones:
- Financial Model details (by service area),
- Summary of Network and Equipment Capex (counts/mileage and cost by service area for each element),
- Itemized list of Routed Locations, with corresponding lat-longs,
- Complete list of Network Equipment elements, with corresponding lat-longs
Additionally, kml/kmz/shp files including Planned Fiber network and its Equipment are also available.
“Routed Locations List” report contains exact drop cable length information for every locations connected in a plan.
If you enter plan edit mode (pencil) and click a service boundary and select a terminal. The drop cables connected to that terminal will be visible as a green line connected from the terminal to the locations.
Arrow Customer Success team can also create a custom report to that will allow you to download the drop cables as a KML or SHP.
Overlap distance is the length of fiber that planned distribution network shares with planned feeder network, i.e. both feeder and distribution network are placed along the same conduit path.
Users can choose whether the tool treats the two fiber cables independently, and effectively applies cable costs twice for the section where distribution overlaps feeder (legacy functionality), or whether it identifies overlapping segments, and uses estimated cable cost for the Feeder segment cost, and a separate cost for the overlapping Distribution fiber ($0 per meter by default).
To enable fiber overlap accounting select Fiber Planning ->”Pricebook Defined Overlap Cost” checkbox in Planning Constraints Manager. “Install Conduit – Planned Overlap” under Fiber Construction in Price Book defines the cost of the overlapping distribution fiber (defaulted to $0).
Please contact Arrow Customer Success to discuss your exact need and feasibility of creating such report.
Arrow divides Total CapEx (upfront expense, without success-based expenditures) by total number of premises connected in the plan.
There is no standard report for exporting Near-Net locations. Please contact Arrow Customer Success team to discuss your options.
Sometimes the shortest (or only) path to connect location that is near the edge of a service area runs outside of it. In those situations, Arrow runs the fiber network outside of the target area, to eventually reenter and connect the target.
The exact distance (buffer) of how far the network is allowed to exit the target service area is set in Planning Constraints Manager under “Edge buffer distance (m)” setting. The setting is in meters.
Customer Penetration is derived by dividing Customers by Premises, i.e. a view of penetration from the perspective of locations.
Penetration, on the other hand, is a revenue-based view. We divide Revenue by TAM (Total Addressable Market) to calculate it.
In most cases Penetration and Customer Penetration are pretty much identical, but Arrow keeps track of them separately for situations where, for example, there is a large difference in the pace with which HHs and Businesses ramp up to their fair shares. If there is a corresponding large gap in estimated revenues from each location type, we could see those two penetration measures diverge during the ramp up period.
In practice, when looking at PLANNED_NETWORK category, we want to be looking at Customer Penetration, but when you are in any other section of ROIC report you can use whichever definition of penetration you prefer.