TNS Private Inter-Building Networks Policy
In order to support telecommunications needs during the past decade, situations arose which argued for the use of dedicated point-to-point links between separate buildings to create private networks. Although these situations were often focused upon data communications, there are also cases of private networks supporting video, voice or other types of communication needs which needed some form of private link.
The reasons for using private links vary. They have often been used to meet specified requirements that could not yet be met by the evolving--but standard--IP backbone protocol. Frequently, private links were used to meet specific needs, often with little or no regard for ongoing support needs, nor for their current or future relationship to other, standard, services. This policy is intended to establish a basis upon which to recover the overall costs to the University to support private links, in order that centrally funded physical and human infrastructure consumed by this service can be adequately replenished.
Definition
Links that do not have one end directly attached to the public, shared (beyond the conduit or sheath level), and TNS-managed Penn State network which supports university-wide telecommunications services, are considered private. Of special note is that, even though a signal may transit a private link and eventually reach one of the TNS-managed networks, the link is still considered private unless there is a direct connection to a TNS-designated interface.
One example of a private link is a connection of a departmental LAN in one building, and to another departmental LAN in another building. Another example is a baseband video feed that connects departmental equipment in one building with departmental equipment in another. A third example is a broadband cable television (CATV) feed between two departmental CATV systems.
Perspective
Penn State's common backbone network is a critical University resource intended to support all inter-building network needs. The perspective developed by those developing University strategies for telecommunications is that "private network" links are generally undesirable, and not in concert with the University's long-term strategic networking direction. Telecommunications and Networking Services is charged with managing the University's backbone networking services, and therefore has an obligation to assure that the use of the infrastructure consumed by private links does not undermine the broader needs by the University of that infrastructure. It is critical that a fair value of the resources consumed by these types of links--ideally sufficient to replenish those resources when necessary--is recovered from those individual departments, colleges, or administrative organizations which create the need for them.
In addition to the physical infrastructure consumed by private links, recognition is given that personnel in buildings connected via private links tend to consume common backbone networking resources at levels similar to those in buildings having direct backbone network connections. It is unfair to those who shoulder the one-time and monthly service costs associated with direct backbone connections, to not spread those costs as evenly as feasibly possible among all who use them. In essence, establishing the true cost of private links needs to account for provision of a fair portion of the cost of all resources consumed, not just those of a physical nature.
Therefore, regardless of whether services are provided to a building by direct backbone connection, or by extension of a private network via a private link, one-time and monthly network connection rates will be applied, to pay the costs of network service to each building.
In addition, there is also a need to recover the specific physical infrastructure costs. First, there is a set of one-time flat costs associated with project initiation and start-up. Second are the costs of the physical infrastructure associated with the length of the link, both one-time and recurring.
Exception
Over the 10 years this policy has been in effect, the networking landscape has changed significantly. The use of network resources is now seen as a key component of efficient academic, research and administrative tasks. The technical capability of the independent academic and administrative units has increased, and common networking standards and strategies are widely accepted and used. In addition, the cost to deploy fiber has decreased over the years, central funding for fiber resources has increased, and fiber resources are now more plentiful than in the past.
Due to these factors, TNS will offer a rate exception, as follows:
Provide the use of point-to-point fiber links to the University community at a rate of $1000.00 one time cost, with a $20.00 monthly fee. Fiber will only be provided under the following guidelines and limitations.
- Fiber will be provided point-to-point. TNS will retain full responsibility for providing and maintaining the fiber circuit. Fiber circuits may be either 62.5 micron MM or SM. (50 micron MM fiber is not currently supported, and is not planned on being supported).
- Fiber will be provided on an as-available basis [TNS will reserve 1 pair of each type for maintenance uses]. If no fiber is available for a request, ITS/TNS will fund the deployment of additional fiber. However, TNS will add the request to the already established funding and deployment schedule; the request will not be escalated in priority over other previously established projects.
- Point-to-point fiber circuits will be limited to the current fiber distribution hubs. All hub-to-hub fiber connections will fall under the existing rate schedule.
Rates
Exemptions
All exemptions must be approved by the Vice Provost of Information Technology and the Senior Director of TNS.
