GNS_RFP_Comment_Matrix_20150522.xlsx

Completed Questions

correctly in the PWS. Latency requirements will remain the same when diversity or avoidance requirements are specified.

116 45 and 46 Table 10.2 Table 10.2 makes reference to the following calculation for latency: Delay (One Way) = Lesser of 150msec or (.01 x D msec), where “D” is the SDP to SDP transmission distance, measured shortest great circle, in kilometers. The specification of a great circle distance for the calculation of delay does not take into account actual routes between locations. Fiber routes must take into account routing around rivers, mountains and other natural and manmade obstacles. A quick review of major fiber routes in the United States shows some backbone routes that exceed 2 times the direct route distance and would not comply. International routes connecting sites in Africa (where fiber crossing the center of the continent does not exist) will have pairs well in excess of this specification. Network solutions, by their nature offer multiple paths, and routing around failures with similar increases to delay. Latency can be “estimated” by using 2 ms of delay per 100 miles of driving distance. This takes into account deviations on carrier network’s paths and the latency injected by carrier transport equipment. Vendor proposes establishing a baseline latency for each location (back to vendor's PE router) once the circuit is installed. Only high level latency estimates can be provided in advance of circuit installation and these are not viable as acceptance criteria. Request the government NOT have a general formula for the PWS of GNS but rather the GNS task orders. This would establish latency requirements that are related to the specific sites in the task order. The Government's requirement is stated correctly in the PWS. Additional requirements may be detailed at the task order level.