My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2011-094
San-Marcos
>
City Clerk
>
03 Resolutions
>
2010's
>
2011
>
Res 2011-094
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/28/2016 1:56:43 PM
Creation date
8/8/2011 4:45:46 PM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Approving
Number
2011-94
Date
8/2/2011
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
274
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).
Show annotations
View images
View plain text
The Contractor will provide the City with hourly status updates until the <br />failure is corrected. <br />C) Repair Documentation: Upon notice from the City of any system failure, generate <br />a trouble ticket detailing the problem, estimated costs, if any, and schedule for <br />completion. The Contractor will provide and maintain repair documentation for <br />each trouble ticket generated. Repair documentation may be emailed to the City <br />for City access to ongoing service documentation and history log in accordance <br />with the Contractor's procedure established in Attachment B. <br />D) Reporting Procedures: All Contractor technicians who require access to City <br />premises for any reason will be required to report to the City's representative or <br />its designee. Upon arrival on City property, prior to commencement of repair and <br />when the repair is complete /prior to departure, the technician will report to the <br />City representative. Reporting to any other City employee is not acceptable. If <br />the repair cannot be completed in one day, the technician will advise the City's <br />representative of that fact before leaving City premises, will state the reason for <br />the delay, and will schedule repair completion. <br />1.1.9 Disaster Recoverv: Implement a disaster recovery plan for force majeure events in <br />accordance with Disaster Recovery Institute International's ( "DRII ") professional practices <br />which includes risk identification and assessment, risk reduction strategies, business resumption <br />planning, disaster recovery planning and incident management as more specifically detailed in <br />Section G of Attachment B. The Contractor's disaster recovery plan includes procedures for use <br />in the event the Contractor's telecommunication switching equipment is rendered inoperable. <br />1.1.10 Remote Monitoring Capabilities: Provide remote monitoring capabilities of the T1 <br />services installed at City sites(s) seven (7) days a week, 24 hours a day, 365 days a year utilizing <br />its Network Support Center Surveillance Group. Alarms generated are routed to the Contractor's <br />local technicians who will be on site, if necessary, within two (2) hours of the alarm. Remote <br />monitoring of the City's services will include notification of failures, as they occur and monthly <br />reporting of such failures. <br />1.1.11 Monthlv Traffic Analvsis Report: Provide monthly traffic analysis reports of installed <br />services to the City for the first year after acceptance. Traffic analysis reports will include the <br />current grade of service along with any recommendations to improve the City's response to the <br />public. The City expects these reports to show its usage of services including bandwidth/channel <br />usage, busy signals, or blockage. <br />1.1.12 Inspections And Cleanup: Take every precaution against damage to property, buildings, <br />apparatus, materials, supplies, and equipment in an orderly fashion at the work site so as not to <br />interfere with work progress of any other City contractors; and will frequently remove all refuse, <br />Telecommunications Services Agreement 2011 <br />10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.