Laserfiche WebLink
Metadata
Document management portal powered by Laserfiche WebLink 9 © 1998-2015 Laserfiche. All rights reserved.
items or Owner facility, structure, and/or property which become damaged by the <br />Contractor's installation activity. <br />Any and all equipment, material, components, cable, etc., provided, installed and <br />operationally activated by the Contractor that is deemed unacceptable by the Owner or <br />does not comply with the specifications herein and rules, regulations, codes, ordinances, <br />or standards as indicated in other sections of this document, shall be replaced with <br />appropriate and compliant products by the Contractor, prior to system acceptance, at no <br />cost whatsoever to the Owner. <br />3.1.12 All installed backbone fiber cabling shall be end to end tested. Fiber links shall meet the <br />EIA/TIA requirements for connector mated pair reflection loss and splice loss as applicable. <br />3.1.13 Consumables — Items used for the installation of fiber infrastructure that are expended to <br />complete an installation process are the sole responsibility of the Contractor. Examples of <br />these items are: jet line, electrical tape, label tape, solvents, cleaners, cable lube, polishing <br />paper, etc. <br />3.2 Manuals and Documentation <br />3.2.1 It shall be the responsibility of the Contractor to provide the as -built documentation. As - <br />built information should be understood to be part of the work units authorized by Owner. <br />Because as-builts are part of the scope of work for each project, final payment will not be <br />made to the Contractor until the drawings are received and approved by the Owner. <br />The requirements contained below address some of the data collection processes and <br />methodologies for the outside plant (OSP) as -built documentation. <br />a) All OSP infrastructures shall be documented utilizing GPS instruments as <br />construction occurs. <br />b) Provide positioning data for trench deployment. Documentation shall include <br />conduit support infrastructure description, when installation is different than the <br />standard 2" conduit or when more than a single conduit is laced underground, as <br />well as placement. GPS coordinates shall be taken at 150 foot intervals and/or at <br />any running line changes, infrastructure changes (manhole, hand holes, pull <br />boxes, cabinets, and terminations) or other points, as necessary. <br />c) Provide positioning data for directional bores. Documentation shall include GPS <br />coordinates for each rod length with its corresponding depth. Other points shall <br />be documented as necessary. <br />d) Provide positioning data of aerial infrastructure by taking GPS coordinates of <br />each pole. Documentation shall include attachment details such as pole type, <br />pole class, riser conduit, height of attachment (HOA), etc., as well as any aerial <br />slacks and aerial splices between poles. <br />e) Provide positioning data of service loops with slack length, as well as the <br />sequential cable length markings at each splice vault, pull box, terminations or <br />other points. <br />f) All GPS datasets ported to GIS features classes shall be projected in the NAD 1983 <br />HARN State Plan Florida East FIPZONE 0901 coordinate system, with the unit of <br />measure being U.S. Foot. <br />g) All GPS points shall have sub foot (< 12 inch) accuracy for horizontal (X, Y) and <br />vertical (Z) axis, unless otherwise specified. <br />h) Submit as -built data as ESRI file geodatabase. Line and point attributes shall be <br />appropriately formatted and accurately recorded. <br />4.0 Service Requirements <br />4.1 Customer Service <br />19 <br />