My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt15 Packet Fusion
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2015
>
Agmt15 Packet Fusion
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/7/2015 4:35:42 PM
Creation date
10/7/2015 4:33:32 PM
Metadata
Fields
Template:
Agreement
Contractor Name
Packet Fusion
PROJECT NAME
New Telephone System
RMP File Number
304
Date
10/7/2015
MO Ref
15-160
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
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
EXHIBIT "A" SCOPE OF WORK <br /> 1.6. Installation will commence within 30 and 60 days from agreement <br /> execution. Packet Fusion will define a timeline specific to the project upon <br /> agreement execution. <br /> 1.7. A Systems Design Specialist, (SDS) will work with the Redwood City to <br /> gather the complete database. Every phone in the entire network will be <br /> visited and documented as to the current and future programming needs. <br /> A cut-sheet will then be created based on this information, which <br /> Redwood City will approve in writing. The cut-sheet must be approved at <br /> least two (2) weeks prior to cutover. <br /> 2. A Network Readiness Assessment shall be conducted by PFI to consist of the <br /> following: <br /> 2.1. Use of a standard testing tool such as Vivinet NetIQ, Viola NetAlly, <br /> Verint or equivalent. <br /> 2.2. The testing server shall be positioned on the core network switch <br /> expected to support the voice communications call server, with <br /> testing end-points strategically positioned in the voice VLAN of each <br /> and every IDF of every office. <br /> 2.3. VoIP Readiness Assessment shall test mesh connectivity from every IDF <br /> to every other IDF (not just closet to core). <br /> 2_4. An initial test shall be performed where call traffic is gradually "throttled <br /> up" to the limit set in Call Admission Control to ensure that the QoS <br /> bandwidth allocations are sufficient to prevent discarded packets. <br /> 2.5. Once voice capacity is established, PFI should generate data traffic, such <br /> that the uplink from an IDF to the MDF is saturated to nearly 100% <br /> utilization while generating test voice traffic. This ensures that QoS on the <br /> LAN is properly implemented to prioritize voice packets over data packets. <br /> This test will be repeated one time for each different access layer switch <br /> type to ensure that implemented QoS methodology is working correctly. <br /> 2.6. In order to test end-to-end QoS, PFI shall generate data traffic, such that <br /> the uplink from the Core Router to the Provider Edge (PE) Device is <br /> saturated, and the PE router is forced to shape traffic and drop excess <br /> data packets in favor of higher QoS voice packets, before putting traffic <br /> into the WAN link. Voice traffic will be generated and measured during the <br /> saturation test, and PFI will provide an MOS for the voice traffic under <br /> load. <br /> 2.7. In order to test QoS over WAN, PFI shall generate data tra�c from <br /> multiple remote locations, such that the uplink WAN link from the WAN <br /> REV:08-28-15 MLG <br /> Page 13 of 69 <br /> ATTY/AGR.2015.207/Packet Fusion New Telephone System <br />
The URL can be used to link to this page
Your browser does not support the video tag.