My WebLink
|
Help
|
About
|
Sign Out
Home
Search
04/11/2011 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2011
>
04/11/2011 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/29/2014 11:33:26 AM
Creation date
1/28/2014 11:55:59 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
04/11/2011
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• <br />• <br />• <br />Vi & <br />• Section VI, as revised, also empowers a municipality to require Zayo to remove its <br />equipment from a co- location site, upon request, if the municipality cancels connectivity <br />service at that site, within an agreed upon timeframe not to exceed 180 days. The <br />underlying right to use a co- location site would terminate with the removal of Zayo's <br />equipment. <br />• The County revised the insurance language in the connectivity service agreement to <br />comport with recommendations made by the League of Minnesota Cities Insurance Trust. <br />• Section XIV of the connectivity service agreement was revised to enable municipalities <br />to terminate connectivity service at a particular co- location site (and cease payment of <br />associated fees) without terminating the entire agreement, after providing 60 days' <br />written notice to the County and Zayo. <br />Notwithstanding the foregoing changes and improvements, the Final Agreement still contains <br />some major deficiencies, as a result of the County's unwillingness to address fundamental <br />problems in the MSA and other issues that apparently were not contemplated at the time the <br />Connect Anoka County project was initiated. For example: <br />• Zayo still is not a party to the Final Agreement, even though it remains responsible for <br />almost all performance under the Final Agreement (e.g., provision of service, repair and <br />maintenance of the network, responding to service problems, etc.). Because Zayo is not a <br />party to the Final Agreement, it is likely that enforcement issues will arise over time <br />because the municipalities will likely only have legal recourse against the County, which <br />may be ineffective in many cases (e.g., if there is a service deficiency, the County cannot <br />directly rectify it, because the County is not providing the connectivity service). <br />Moreover, the County's ability to require Zayo to perform is circumscribed by its flawed <br />MSA with Zayo, which further compounds potential enforcement problems and delays. <br />• The concept of "connectivity services" is still not well defined in the Final Agreement. <br />Accordingly, it is not clear precisely what services municipalities would be buying and <br />receiving, and what expectations they could have concerning connectivity services. <br />• Zayo and Anoka County are not guaranteeing service speeds or quality of service in the <br />Final Agreement. Consequently, municipalities could be paying for services they are not <br />actually getting, or receiving services that do not consistently meet their needs, <br />particularly for mission critical applications. That said, the Final Agreement now <br />contains language that permits a municipality to terminate service at a particular site after <br />providing 60 days' written notice to the County and Zayo. However, this early <br />termination option may not be helpful if a municipality has come to rely on the Zayo <br />system or if alternative services are too expensive. <br />• Anoka County's and Zayo's proposed service level standards would allow portions of the <br />Zayo system and certain connectivity services to be down for approximately 500 minutes <br />a year, which could lead to serious problems for mission critical applications and <br />
The URL can be used to link to this page
Your browser does not support the video tag.