Atch 18_CITS Install Plan_NetOps SB.doc

Telecommunications System

Installation Plan (TSIP)

Template for

Yokota AFB

CONTRACT NUMBER:

DELIVERY ORDER NUMBER:

DATE OF PERFORMANCE:

753 ELSG/NE

U. S. AIR FORCE

HANSCOM AFB, MA

TABLE OF CONTENTS

INTRODUCTION

1.1 Purpose

1.2 Scope

1.2.1 TSIP Development

1.3 Building List

1.4 Topology

1.4.1 Cable Distribution Technology

1.4.2 Network Architecture

BASE DISTRIBUTION COORDINATION AND DOCUMENTATION

2.1 AF Form 332 Process

2.1.1 AF 332 Development Procedures

2.1.2 AF 332 Data Content

2.1.3 TSIP Submittal of AF 332

2.1.4 National Pollution Discharge Elimination System (NPDES)

2.2 CSIRS and CABLE DISTRIBUTION DESIGN

2.2.1 CSIRS and Cable Distribution Drawings

2.2.3 Digital Distribution Photos

2.3 FIBER TEST Data

2.3.1 GFE Fiber Being Reused

2.3.2 New Installed Fiber Testing

2.3.3 Fiber Data Test Records

2.4 List of Distribution Materials: Summary and by Run

2.5 Cable Tracing: Tone-Traceable Duct/Cable Runs for Locates and GIS

2.6 Communications Feature Location Data: Collection of Communications Feature Location

Data (CFLD) for GIS

2.7 Premise Wiring

2.7.1 Premise Wiring Decision Matrix and Evaluation Procedure

2.7.2 Premise Wire Test Data Format and Summary

2.8 Hazardous Material Handling (Under Netcents Contract)

2.8.1 Survey Procedures, Review Requirements and Documentation

2.8.2 Handling Process and Requirements

BASE AREA NETWORK (BAN) HARDWARE INFRASTRUCTURE

3.1 Current Network Equipment

3.2 Target Network Architecture

3.3 IP Addressing

3.4 ATM Addressing

3.5 Protocols

3.6 Virtual Local Area Networks (VLANS)

3.7 Emulated Local Area Networks (ELANS)

3.8 Network Management

3.9 Wide Area Network (WAN) and Classified Connections

3.10 Physical Environment

3.11 Miscellaneous

TARGET NETWORK DESIGN

4.1 High Level Design

4.2 IP Addressing

4.3 Protocols

4.4 Deleted

4.5

SONET

4.6

VLANS

4.7 Deleted

4.8 Network Management

4.9 Wide Area Network (WAN) and Classified Connections

4.10 Vendor Selection

4.11 Quality of Service

4.12 System Timing

4.13 Miscellaneous

NETWORK DESIGN DETAILS

5.1 Government Furnished Equipment

5.2 ITN Building Level Design Detail

5.2.1 Documented Elements

5.3 Document Element Presentation

5.3.1 Document Consolidation

5.4 Consolidated Network LOM

5.5 “As Built” (Installed) Network Documentation

INTEGRATED DETAILED SCHEDULE

LIFE CYCLE SUPPORTABILITY

RELIABILITY, MAINTAINABILITY, and AVAILABILITY

8.1 Modeling Technique and assumptions

8.2 Reliability and Maintainability Data

8.3 Detailed Results

8.4 Summary of Results

DEVIATIONS FROM CITS BASELINE ARCHITECTURE

MATERIAL SAFETY DATA SHEETS (MSDS)

Network Engineering Appendix

Part 1 – Example Network Figures

Part 2 – Network Data Tables

Distribution Engineering Appendix

Part 1 – Base Building List - Table D-1

Part 2 – Topology Drawing – Figure D-1A & D-1B

48-49

Part 3 – Base Civil Engineering Work Request Package (AF Form 332 and Supporting Documents) – Figures D-2 thru D-8

50-57

Part 4 – CSIRs Documentation Presentation Package – Figures D-9 thru D-45

58-95

Part 5 – Fiber Test Data – Tables D-2, D-3 & D-4

96-99

Part 6 – Distribution List of Materials (LOM) Table Package – Table D-5

Part 7 – Communication Feature Location Data (CFLD) Table Package

– Tables D-6 & D-7

101-103

Part 8 – CAT 6 Premise Wiring – “1st 400 Feet”, Figure D-46 & Table D-8

104-105 Integrated Schedule Appendix

List of Acronyms

107-108

LIST OF NETWORK FIGURES

Figure N-1 - Current Network Architecture Example

Figure N-1a – Current Architecture Example (Logical)

Figure N-2 - Rack Layout Example

Figure N-3 - Timing Diagram

Figure N-4 - High Level Design Example

Figure N-4a – Logical Direct and Patched Connections Example

Figure N-5 - Port Assignments

Figure N-5a – Box Level Architecture

Figure N-6 – Proposed CITS Network Architecture

Figure N-7 – WAN Connectivity

LIST OF NETWORK DATA TABLES

Table N-1 - Current Network Equipment List for each Building Example

Table N-2 - Base’s Existing IP Addressing

Table N-3 - Existing VLAN Structure

Table N-3A- Box-Level Collaborative Design Matrix

Table N-4 - As Delivered Device Configurations

Table N-5 - Final IP Addressing Configuration

Table N-6 - Deleted

Table N-7 - SONET Interfaces

Table N-8 - Deleted

Table N-9 - Deleted

Table N-10 - Deleted

Table N-11 - C&A Equipment Information Example

Table N-12 - GFE Example

Table N-13 - User Counts and Requirements Example

Table N-14 - Network List of Material Example

Table N-15 - Network Switch Slot and Port Assignments

LIST OF DISTRIBUTION FIGURES

Figure D-1A ITN Distribution System Connectivity Example

Figure D-1B ITN/EBN Distribution System Connectivity Example

Figure D-2 Base Civil Engineers Work Request AF Form 332

Figure D-3 Floor Plan Example

Figure D-4 Existing Equipment Room Plan Example

Figure D-5 New Equipment Room Plan Example

Figure D-6 Room and Floor Plan Symbol Sheet

55 Figure D-7 Text Notes for Floor and Room plans

Figure D-8 Example Photos of Room Areas

57 Figure D-9 ITN/EBN Distribution System Overlaid on a Base Map … (Horse Blanket)

Figure D-10 Sectional Drawing Example

Figure D-11 Typical Entry and Trenching Profiles Section Sheet

Figure D-12 Typical Sectional Symbols Sheet 1

Figure D-13 Typical Sectional Symbols Sheet 2

Figure D-14 Typical Sectional Symbols Sheet 3

Figure D-15 Cable Label Format

Figure D-16 Typical Manhole Butterfly Drawing

Figure D-17 Exploded View of CSIR Color/Level Legend to followed for all CSIRs Drawings 67 Figure D-18 Exploded Symbol View of Typical Trench Profile

Figure D-19 Exploded Symbol View of Concrete Pavement Trench Profile

69 Figure D-20 Exploded Symbol View of Asphalt Pavement Trench Profile

70 Figure D-21 Exploded Symbol View of Specialize Trench Protection Profile

Figure D-22 Exploded Symbol View of Riser Entry Profile

Figure D-23 Exploded Symbol View of Core Bore Entry Profile

73 Figure D-24 Exploded Symbol View of Road Trenching for Direct Buried

Figure D-25 Exploded Symbol View of Road Trenching for Conduit Install

Figure D-26 Exploded Symbol View of Road Boring for Direct Buried Install

Figure D-27 Exploded Symbol View of Conduit, Innerduct and Cable Install

Figure D-28 Exploded Symbol View of Direct Buried Trenching for Direct Buried Cable Install Figure D-29 Exploded Symbol View of Specialized Trench Protection

Figure D-30 Exploded Symbol View of Use of Existing Pathway Assets

Figure D-31 Exploded View of Cable Termination Label and Legend

Figure D-32 Exploded View of Reuse Cable Termination Label Styles

Figure D-33 Exploded View of Abandon In Place Cable Label Styles

Figure D-34 Exploded View of Reuse Cable Label Styles

Figure D-35 Exploded View of New Direct Buried Cable Label Styles

Figure D-36 Exploded View of Cable Splice Label Styles

Figure D-37 Exploded View of Generic Comm. Symbols – Telephone

Figure D-38 Exploded View of Generic Comm. Symbols – Existing Manhole and Duct System Figure D-39 Exploded View of Generic Comm. Symbols – Infrastructure Labels (1 of 3)

Figure D-40 Exploded View of Generic Comm. Symbols – Infrastructure Labels (2 of 3)

Figure D-41 Exploded View of Generic Comm. Symbols – Infrastructure Labels (3 of 3)

Figure D-42 Exploded View of Generic Comm. Symbols – Manhole and Duct System

Figure D-43 Exploded View of a Section of a Typical Manhole Butterfly Detail (1 of 3)

Figure D-44 Exploded View of a Section of a Typical Manhole Butterfly Detail (2 of 3)

Figure D-45 Exploded View of a Section of a Typical Manhole Butterfly Detail (3 of 3)

Figure D-46 Premise Wiring Evaluation/Decision Matrix

LIST OF DISTRIBUTION TABLES

TABLE D-1 – Building List Example

TABLE D-2 – Fiber Optic Cable Loss Test Data Sheet (Multi-Mode)

TABLE D-3 – Fiber Optic Cable Loss Test Data Sheet (Single Mode)

TABLE D-4 – CITS Fiber Reservation List

TABLE D-5 – Run # - Material Requirements Example

TABLE D-6 – Comm Feature Location Data Table Example

TABLE D-7 – Example SDS Names

TABLE D-8 – Sample Premise Wiring Test Data Sheet

1 INTRODUCTION

1.1 Purpose (Completed during site survey)

This document provides a detailed template that enables the contractor to develop a complete design package for the implementation of the CITS Information Transport System (ITS) at the base. It also defines the “as built” documentation requirement for the installation of ITS. Additional paragraphs can be added to this document if the contractor feels that the design cannot be adequately described within this template. The text, tables, figures, and tests are meant as examples of the type of information and documentation required and can be modified by the contractor to aid clarity or increase the scope of information portrayed. Since these examples were taken from several sources, the symbols and labeling are not consistent. The contractor shall use consistent symbols, coloring, and labeling in the site specific TSIP.

1.2 Scope (Completed during site survey)

This design shall include all the information needed to install ITS and shall support all user requirements at core and non-core locations.

1.2.1 TSIP Development

A draft TSIP, initially developed during the collaborative review on site, shall be updated and delivered by the contractor to the Government, including all vendor specific information, IAW the project schedule. Government will provide comments for incorporation at the final document writing/review meeting to be held at the contractor facility.

1.3 Building List (Completed during site survey)

An initial building list will be obtained by the PMO during the base Pre-site Survey. This table shall be reviewed at the start of the SS&IP (kickoff meeting) with any changes having to be approved by the MAJCOM. Insert the finalized building list (Table D-1) that was agreed to at the Topology Review.

1.4 Topology (Drafted during site survey – Completed during collaboration)

Using the building list as a starting point, separate cable distribution topology and network hardware architecture efforts need to be documented.

1.4.1 Cable Distribution Topology

Physical connectivity of the distribution system shall also be provided in Figures D-1A & D-1B that identifies cable type (e.g., Multi-Mode (MM), Single-Mode (SM)) the total number of fiber strands, number of fiber strands available for ITS or new cable for CITS and the length of fiber runs.

1.4.2 Network Architecture

A diagram similar to the example depicted in Figure N-1, illustrating the Current Network Architecture should be used to document the initial network connectivity. During SS&IP develop and update a proposed CITS Network Architecture similar to the example, depicted in Figure N-6. This diagram should illustrate logical connectivity across the Information Transport Node (ITN) backbone and ITN to End Building Node (EBN) connectivity. This logical connectivity between network hardware elements should utilize the physical cable distribution topology documented above. Diagram(s) shall show logical connectivity of EBNs and ITNs and identify proposed interface types, e.g., Synchronous Optical Network (SONET), Fast Ethernet, Gigabit Ethernet (GbE) show EBN connectivity required; approximate user counts, and differentiate core building types. An initial, draft network architecture that uses generic hardware shall be developed during the survey and finalized during the Box Level meeting. A final proposed network architecture that is based on a selected vendor’s hardware shall be documented prior to HWIPR and then finalized prior to FDA.

2 Base Distribution Coordination and Documentation Packages

2.1 AF Form 332 Process 2.1.1 AF 332 Development Procedures:

The Base Civil Engineering Work Request, AF Form 332 (AF 332), contains information that Base Civil Engineering (BCE) uses to identify building modifications, track capital costs/improvements as well as a host of other items. During the Pre-Site Survey, the PMO will establish an acceptable processing procedure with the base for the submission, review and approval of the contractor developed AF 332’s along with the expectations for the review and processing time. The contractor shall follow this process and work with the BCE representative to submit and monitor status of these work requests throughout the survey and collaboration period.

The program office default position is that one AF 332 shall be prepared for each building identified on the building list, in which CITS provides any work. Including but not limited to if CITS installs new distribution fiber, places equipment racks/cabinets, installs dedicated electrical power and/or grounding to a communications equipment location, then a completed AF Form 332 will be required.

In addition to the individual bldg AF 332’s, a single overall AF Form 332 work request will be prepared covering the entire base exterior distribution excavation/installation plan. The hand drawn “Horseblanket” route diagram (see Figure D-9) shall be developed, as outlined in section 2.2.1, early in the stages of the survey and design. A working (but not necessarily complete) copy shall be available by the start of collaboration for the review by base civil engineering. A meeting with the Communication Squadron POC and Base Civil Engineering POC as well as the various utility and cable maintenance shop representatives shall be scheduled during the initial portion of the collaborative design cycle, to identify the likely routes being reviewed and request comments with regards to potential impacts. This meeting should be repeated, at least one additional time, 10 days prior to the HWIPR briefing, to assure approval of the planned routes. The final exterior route diagram work request shall be signed off at this last meeting and become part of the HWIPR design review package. The Detailed information on the route plans shall include the following:

- A single line showing the route of all new installed ducts.

- A small square indicating approximate locations of possible handhole and/or manholes.

- The approximate location of pavement (asphalt/concrete) cuts.

- The approximate location of all pavement bores.

Beginning at the earliest point possible during the SS&IP, AF 332 and accompanying details shall be turned in to the CE POC during the weekly Integrated Product Team (IPT) meeting. The contractor shall develop and maintain a status tracking sheet for the AF 332 work requests addressing at least the following:

1. Completed by the contractor and ready for base agency coordination (i.e., safety, fire depart, bio-environmental, etc)

2. Submitted for signature by base CS POC

3. Completed base agency coordination steps

4. Submitted to CE POC

5. Reviewed and signed off by CE

6. Completed and returned to the hands of the contractor.

This status shall be reported weekly during the IPT Meetings.

All AF Form 332’s shall be approved 10 days prior to the HWIPR and this fact documented in the HWIPR Briefing and TSIP. If circumstances exist making this not possible, the project managers for the contractor and the PMO, base communication and civil engineering squadrons shall discuss the issue(s), impact(s) and jointly develop a revised schedule for completion, preferably as early as possible in the remain SS&IP process. This information shall also be documented in the TSIP.

2.1.2 AF 332 Data Content:

The details of the information required in all building AF Form 332’s is as follows:

· The AF Form 332’s shall document all network equipment and distribution installations and all necessary support work.

· The 332’s shall include all drawings and photos necessary to clearly illustrate the work to be accomplished. This includes (but is not limited to) new/improved electrical power service to the equipment rack(s), communications grounding improvements, modifications to improve environmental control to the space occupied by the network equipment, and lead paint and/or asbestos abatement work and quantities, and any necessary access control changes.

· Specifically identify any work to be accomplished and whether it will be performed by the contractor or by the government.

· Digital photos of these areas shall be included to enhance the understanding of any issues as well as provide a record of what was present at the time of survey.

Drawings should be neatly sketched and convey all relevant information but not necessarily to scale.

The Detailed information on the OSP route plans shall include the following:

A single line showing the route of all new installed ducts.

A small square indicating approximate locations of possible handhole and/or manholes.

The approximate location of pavement (asphalt/concrete) cuts.

The approximate location of all pavement bores.

2.1.3 TSIP Submittal of AF 332

The TSIP format of the AF Form 332 and accompanying documentation shall be as below with the content provided by the examples in Parts 2 and 3 of the Distribution Appendix, Figures D-2 through D-8.

All AF Form 332s and accompanying documentation shall be placed in the ordered outlined below

- ITN (lowest building # 1st)

AF 332

Digital Photos – Before CITS work

Building Floor Plan – Including Bldg POC(s) and phone # contacted at time of survey Communication(s) Room Plan(s)

· EBN(s) attached to this ITN (lowest building # 1st)

· AF 332

· Digital Photos

· Building Floor Plan

· Communication(s) Room Plan(s)

This order shall be repeated for each sequential ITN for the entire project. This order should also be utilized when developing the soft copies for submittal.

2.1.4 National Pollution Discharge Elimination System (NPDES)

Development of a NPDES permit takes various shapes according to the state in which the subject base is located. The contractor is responsible for contacting the appropriate state agency responsible for management/oversight of this federally mandated program. Based on information from the responsible state agency, prepare the necessary documentation to maintain compliance within state guidelines. During the design phase of the project update the IPT on development status and document both requirements and decision involving this process. A copy of this documentation shall be included as part of the TSIP submission and provided under separate cover as part of the FDA TSIP documentation. Updates shall be provided as necessary during the site installation process. A final clearance of responsibilities document from the state agency shall be included as part of the TSIP Final As Built documentation package

2.2 CSIRS AND CABLE DISTRIBUTION DESIGN

The distribution system design shall be a composite of both found infrastructure and newly designed distribution. Found infrastructure shall consist of any existing manholes, ducts, and fiber cabling that the contractor plans to reuse in the design. This information will be obtained by document review and site survey to develop the most complete package possible.

All reused infrastructure shall meet current installation criteria, along with all other current requirements of the ITS program or shall be brought into compliance as a part of developing the ITS.

Of critical importance in using found infrastructure is the network Backbone and its diversity. The contractor shall physically verify diversity to ensure clear cable separation between ITNs in accordance with the guidelines of the Baseline Program Directive (BPD). The contractor shall use all documentation available from government sources, as well as physical inspection, to verify all backbone diversity. The contractor shall submit the process of verification steps, as part of HWIPR, at the end of collaboration on site. During the contractor’s physical inspections all identified backbone cables shall be marked, as “CITS Backbone Cable” at all manholes inspected and building entry points.

2.2.1 CSIRs and Cable Distribution Drawings (Draft during collaborative design - Final by FDA or as described in section below)

a. HORSEBLANKET - Develop an overall (Horseblanket) drawing (Figure D-9), overlaid on an “E size” copy of the government furnished record drawing base map that shows the reuse and new distribution system components and demonstrates the backbone route and diversity. This drawing shall be colored and coded to identify ITNs and associated EBNs, existing and new conduit and direct bury routes. During collaboration, this drawing may be in hand drawn form and shall be used to identify design routes and highlight areas of concern. After the HWIPR, this drawing shall be developed into a color CAD. This drawing shall be updated as necessary throughout the design, installation process and be part of the as-built package.

b. SECTIONAL DRAWINGS - Develop a set of “D” sized, sectionalized drawings based on Air Force supplied Communications and Information Systems Installation Records (CSIR) (Figure D-10) using the record drawings and IAW instructions in section d below, showing the details of the reuse, found Infrastructure, and newly installed components.

REDLINES DRAWINGS - During the onsite survey, the field copies of these drawings shall show redlined design plans containing all the information discussed below.

CAD DRAWINGS - After the HWIPR, these drawings shall be rendered in color CAD form. These drawings shall be colored and coded to differentiate reuse from new, as well as conduits from direct bury cable, and support systems. Drawing packages shall contain a Title cover sheet identifying the Base, the date and the reason for the package (i.e., Pre-FDA, Post-FDA, As-Builts), table of contents as well as a standard symbol legend sheet at the beginning of each package. This symbol sheet shall show all of the CITS Standard Symbols, shown in Figures D-11 through D-14, as well as any special symbols developed because of unique base requirements. The CSIRs will be developed according the requirements outlined below in paragraphs e, f, and g.

- Update existing and/or develop new butterfly drawings as outlined in Figure D-16 for each manhole, hand-hole and pull box and key these butterfly drawings to the cable drawings in which they are used.

c. CABLE LABELING - Develop cable labeling according to the example in Figure D-15. There are two acceptable methods for labeling the cable. The choice shall be coordinated with the base and the CITS PMO DS prior to the development of the HWIPR documentation. The PMO shall be informed of the labeling choice and/or any issues involving the development of the labeling scheme during the regular IPT meetings. The final TSIP shall show only the decided cable label scheme.

d. Update existing and/or develop new butterfly drawings as outlined in Figure D-16 for each manhole, hand-hole and pull box and key these butterfly drawings to the cable drawings in which they are used. .

e. Color CAD sectionalized cable drawings shall be developed using the government furnished record drawings (normally the “g Folder” portion of the CSIRs) to produce updated drawings. Files received from the government shall normally include a folder labeled xxxx (where xxxx is the coded identifier for a particular base) and subfolders with the following labeling:

i. A Key sheet contained in the file labeled xxxxKS01.000 found in a sub-folder labeled RFRNK. Key sheets contain all of the base road and building information.

ii. Grid Sectional sheet contained in files labeled yyyyydd01.000 (where yyyyy represents the grid location of the sectional when overlaid on the base Key sheet) found in a sub-folder labeled “g”. These files contain only cable path and manhole information.

iii. Manhole butterfly sheets contained in files labeled yyyyyod01.000 (where yyyyy represents the grid location of the sectional when overlaid on the base Key sheet) found in a sub-folder labeled “g”. These files contain only cable path and manhole information

iv. Drawing sheet layouts with the appropriately sized (C, D, or E sized page) government border and title box maybe found in a sub-folder labeled RFRNB.

f. Updates to the record drawings shall be in Microstation J format. Updated information (i.e., cable and manhole) data shall be placed on the appropriate grid sectional drawing and saved to a copy of that file with the file extension name “.DGN”. Alternate or other drawing sources shall be identified at Pre-site Survey and at kickoff and resulting issues resolved at this time with the PMO Lead DS Engineer.

g. All existing drawing elements shall be turned to a light (but visible) color GRAY without modifying any level attributes. The Contractor shall not combine grids that are sub-gridded in the government record drawings. The contractor may sub-grid or sub-sub-grid sections to allow for the necessary level of detail. These actions shall be noted on Level 52 in BLUE (see below)

The following specific colors and levels shall be used to define /identify work: (see example and symbol details)

Existing Assets

Reused cables shall remain GRAY in the record drawing if for Reuse -there are no changes to its use. However, a bold note shall be added to Level 54 in BOLD BROWN, above the applicable cable tag, which shall read “CITS REUSE”

New/Reworked

New cables, or direct bury.

Level 50, New infrastructure such as manholes, hand holes, etc.

BOLD RED -

Existing duct with new cable shall get a BOLD RED cable tag. Distance between (center to center) manholes, hand holes, pull boxes and to the edge of buildings at entry point.

Repairs to existing exterior infrastructure and/or cabling (i.e., outside of bldgs) that is performed by the Contractor.

Removed Items

Any removed cabling and/or infrastructure.

Level 51, ORANGE -

Notes to Drafter

Any notes to drafter (such as sub-grid changes).

Level 52, BOLD BLUE -

Found Existing

Existing Infrastructure not on the record drawing that is

Infrastructure discovered and reused during CITS shall be added to the

Level 53, record drawing.

GREEN -

CITS Construction Construction tasks/actions numbers, cut/replace pavement

Information trench lines. Installation of new conduits, rollpipe, rigid

Level 54, and/or flexible geotextile fabric innerduct with and/or without BOLD BROWN -tracer wires.

For Cable Reused The type identifier shall remain unchanged. However, the with Fiber assignment removed count shall be placed in parenthesis on Level 51 in

(count) changes - ORANGE. The new count shall be placed on Level 50 in BOLD RED, directly above the removed count.

For Cables

Cables abandoned in place shall have counts annotated on

Abandoned

Level 51 in ORANGE, enclosed in parentheses and the letters in Place (AIP)

“AIP” shall be placed directly above the cable identifier on

Level 50 in BOLD RED.

For Tracer Wires

A note shall be added on level 54 in Bold Brown of the new installed with new install on the CSIR drawings indicating the type of cable when no other tracer wire used in a particular run and how long.

infrastructure is added

(override)

2.2.3 Digital Distribution Photos

At completion of the OSP work, take digital pictures of the interior of each new and/or re-used manhole/handhole and all above ground building entry boxes showing the cable paths, installed maintenance & splice loops, splice cases & mounting, labeling and trace wire installation.

2.3 Fiber Test Data

2.3.1 GFE Fiber Being Reused (Draft during collaborative design

· Final by FDA or as described in the section below)

For all existing cables, when recent (per BPD) test data is not available, that are planned for reuse shall be tested (ALL unused fibers in the cable) with both Optical Time Domain Reflectometer (OTDR) and power meter before they are integrated into the design. If fibers in use must be considered in order to meet the minimum fiber count requirement, these fibers (the ones currently in use) must be tested and determined to be good before the cable is considered viable for reuse. By the time of Box Level collaboration, test data (see 2.3.3 for sheet/data requirements) will be available, documenting suspected faults and possible repairs (i.e. replace connector, clean feed through). Large Fiber Count Cables, especially Hybrid cables, and un-terminated fibers, should be identified for discussion as outlined in the BPD. OTDR data shall be used to determine if bad fiber can be economically repaired or if it will require replacement. Testing of fibers, which have not been terminated, but ultimately are planned for reuse, is required

Calibrated power source shall be used to measure the light loss (in dB) for each fiber proposed for reuse, from both ends and both wavelengths, and measurements recorded, in soft copy, on the data sheet, see Tables D-2 and D-3). In addition, include a soft copy of the OTDR plots for multi-mode at 1300nm and single mode at 1550nm from one end of each fiber being reused, along with a soft copy of the appropriate reader software to display and examine the traces.

The purpose of the OTDR test is to identify any bad splices, fibers, connectors, and to use the length measurement to determine an expected maximum loss figure for the fiber. For fiber showing bad connectors or splices, repair shall be considered as a viable alternative to replacement. Such actions shall be documented on the CITS Fiber Reservation List (table D-4) and with the test data sheets in the TSIP, along with any design decisions resulting from fiber discussions during IPTs.

The fiber should be considered valid for reuse when; the age of the cable is not considered a factor, the OTDR results show no anomalies, unexpected reflections or losses and the fiber attenuation is less than the maximum allowable attenuation value as calculated below including measurement error.

The attenuation of a fiber is a function of the length of the cable, the number of splices in the cable, and the number of connectors in the cable. Refer to Tables D-2 and D-3.

Single Mode at both 1310 and 1550 nm Max Attenuation (in dB) = (0.50 x Length) + (0.3 x Number of Splices) +

(0.8 x Number of Connectors) + 0.5 dB (Measurement Error).

Multimode at 1300 nm

Max Attenuation (in dB) = (1.5 x Length) + (0.3 x Number of Splices) +

(0.8 x Number of Connectors) + 0.5 dB (Measurement Error).

Multimode at 850 nm Max Attenuation (in dB) = (3.75 x Length) + (0.3 x Number of Splices) +

(0.8 x Number of Connectors) + 0.5 dB (Measurement Error).

NOTE: Length is measured in kilometers, and is determined using an OTDR.

To verify fiber valid for reuse, inspect all cable loss data sheets and OTDR traces to verify the following:

• The OTDR measured cable length is within 10% of expected value (only required for backbone fibers that are used to meet the diverse routing requirement and new fibers, for all other reused fibers this is N/A)

• The OTDR trace does not show signs of problems due to installation, damage, or splicing

• The attenuation of each fiber does not exceed the “Max Attenuation” derived using the OTDR length and verified by a calibrated power meter measurement.

2.3.2 New Installed or Repaired Fiber Testing

All newly installed and/or repaired fiber optic cable shall be tested in accordance with the requirements set forth in paragraph 2.3.1. The cables shall be identified as new installed fiber on the Fiber Data Sheets, in Appendix C-2 of the Cutover and Test (COT) Plan. New installed fiber tests shall be delivered according to Block 13.a, CDRL A009 requirements.

2.3.3 Fiber Data Test Records During collaborative design, a soft copy of all fiber test data shall be maintained on site.

In addition, develop the CITS Fiber Reservation and reuse Conduit Reservation lists, in Excel spreadsheet format as shown in Table D-4, which summarizes GFE Fiber and Conduit to be used in the ITS installation, including initial conditions and actions to be taken to repair unsatisfactory items. Existing Fibers and Conduits identified for re-use shall be reported during the weekly IPT meeting and updated weekly using this format as an attachment to each IPT minutes submitted.

The pre HWIPR read ahead’s shall include the completed Table D-4 with fiber and conduit data for review.

During the HWIPR the final Table D-4; fiber, and conduits identified for reuse shall reviewed and accepted by the IPT.

For the TSIP delivery (FDA), submit the completed CITS Fiber Reservation List (both hard and soft copies) as well as soft copies of reused fiber power meter test data, Tables D-2 and D-3 as well as a soft copy of the existing OTDR test data.

This information will be updated at the completion of the distribution installation phase with soft copies of the new and re-terminated fiber power meter test data and a soft copy of the new and re-terminated fiber OTDR test data. This updated data shall be delivered in the COT documentation package and referenced from this paragraph of the TSIP

All soft copy submissions shall be delivered on CD along with a soft copy of the appropriate reader software to display and examine the traces. The soft copy of the reader software shall be license free and include instruction on installation and use.

2.4 List of Distribution Materials: Summary and by Run (Final for major items by HWIPR - Complete by FDA)

Summarize DS materials for the project, in total and by runs, in a format similar to that depicted Table D-5. The list of material (LOM) elements should match the elements of the contractors installation cost model and be easily equitable to each other. The LOM shall be organized by runs with appropriate ITN subtotals provided. Summary and sub-section totals shall have math formulas totaling up the individual quantities and shall not be hard coded entries.

2.5 Cable Tracing: Tone-Traceable Duct/Cable Runs for Locates and GIS

The following requirements exist and shall be met to allow the after installation location of all CITS cable pathways, both new and existing:

a. The CITS Distribution design shall include the ability to tone-trace the installation of new duct and cabling. This toning capability will allow the initial location for GIS purposes and extend to the base the ability to locate the new runs post the CITS installation effort.

b. Tone-trace capability will utilize any existing conductive pathway, the metallic jacket of armored cable or will have newly installed tracer wire systems such as the following:

1) 14 AWG wire with THHN two part insulation jacket.

2) Geo-Textile Multiple Cell inner duct with built in tracer wirer

3) Roll Pipe with an attached external surface tracer wire

c. Tracer wires will be installed between manholes (new or existing) with new duct bank runs or new cables when installed in existing assets. The tracer wire shall be left exposed, hanging approximately 12 inches free from the conduit where installed. The ends of the tracer wire shall be capped (insulated), secured to the manhole wall and tagged with a label so indicating it as a “Duct Tracer Wire to xxx – Do Not Remove (where xxx is the other end of the wire).” Normally these wires will not be connected to any grounding system.

d. Tracer wire installations shall be documented on Cable Sectional and Butterfly drawings as outlined in paragraph 2.2.1 and the example figures of the TSIP.

e. The contractor will have on site tone-tracer capabilities that are compatible with all the tracer methods utilized in the installation.

2.6 Communications Feature Location Data: Collection of Communications Feature Location Data (CFLD) for GIS

Utilizing the capabilities outlined in Section 2.5 above and the requirements outlined in the CFLD section of the BPD, the contractor will collect the following CITS installed CFLD data in a MS Excel spreadsheet format as depicted in Table D-6.

a. At a minimum, data shall be collected for the following:

(1) The centerline position of:

(i) Direct buried cable.

(ii) The duct bank runs.

(iii) Above ground terminations.

(2) The geometric center of the lids/hatches/covers of any manhole/handhole used in the CITS design.

(3) The center of exterior riser(s), at ground level, on building entries used in the CITS design.

(4) The center line of contractor installed underground conduit entries at the edge of building foundations.

(5) The beginning and ending points of CITS designed:

(i) Steel casing and/or other sleeve transition points.

(ii) Concrete encasement. The contractor shall mark these points during backfill operations with a temporary marker and maintain these markers until the CFLD data is collected. This does not apply to concrete encased road crossing.

(6) Any other surface/above ground contractor installed special features.

b. All vertical position data shall be taken at surface level. All CITS installations are required to have a minimum of 36” top cover above the top of any duct system.

c. Each CFLD in Table D-6 shall also be named using CADD/GIS Technology Center’s Spatial Data Standards (SDS) release 2.0 (or the most current version available) naming conventions. Examples are provided in Table D-7. The contractor shall not deviate from the SDS without prior written approval from the Government.

2.7 Premise Wiring

The following paragraphs outline the review process and decision tree to be used to determine what premise wiring shall be considered

2.7.1 Premise Wiring Decision Matrix and Evaluation Procedure

As part of the Pre-Site Survey the PMO will obtain existing and new user drop information, which will be provided to the contractor. At the Kickoff meeting this information will be further reviewed and adjust as necessary. This will become the basis for the scope of work on premise wire (i.e., establishes the range from large scale effort down to only small number of new drops). The contractor will survey the buildings identified on the list to include reviewing the premise wiring as outlined in the Decision Matrix shown in Figure D-46. Sample testing is to be employed for actual evaluation in any building to determine the requirements of a specific building. This data, in combination with other information and NACA results, shall be tallied for review during the time frame of the Box Level Collaboration. At his time a final premise wire design will be discussed by the entire IPT and the conclusions presented at HWIPR and in the FDA package.

2.7.2 Premise Wire Test Data Format and Summary

Premise wire test data shall be collected for all sample drops tested during the SS&IP as well as for all new drops installed as a result of the finalized design. The format for the test data shall follow that shown in Table D-8

2.8 Hazardous Material

Hazardous material handling is a new aspect of the ITS program and this efforts are meant to address small wall and/or floor spaces within specific areas of a comm. room (literally a square foot or two at a time), when it is absolutely required because there is no practical alternative to utilizing a given area where this material may be present. It is not meant to be a wholesale remediation effort for a comm. room or a conduit pathway. Areas deemed too large for ITS to handle will be referred back to the base for accomplishment.

2.8.1 Survey Procedures, Review Requirements and Documentation

Determination of impacted areas shall be documented on AF Form 332 – Work Request, identifying the materials to be removed, location and an estimated quantity as outlined in section 2.1.2 above.

A summary of the buildings impacted shall reviewed in a collaboration meeting with PMO, contractor and base personnel at or before the completion of the Box Level Network Review. The conclusion from the meeting shall be documented in the HWIPR briefing and documented in this section of the TSIP to be reviewed again at development of the PSA and at the FDA.

2.8.2 Handling Process and Requirements

In this section document the handling procedures for hazmat materials to be removed, stored and disposed of as part of the ITS effort. Outline the necessary State and/or Federal regulations governing such procedures. Update final quantities at the completion of the project.

For liquid handling, ITS will process contaminated liquids only if contaminate levels are below the following conditions: Oxygen concentration less than 19.5 percent; flammable gas or vapor at 10 percent or more of the lower flammable limit; or hydrogen sulfide or carbon monoxide at or above 10 ppm or 35 ppm, respectively, measured as an 8-hour time-weighted average.

3 Base Area Network (BAN) Hardware INFRASTRUCTURE (Completed during site survey)

This section shall include a summary depiction of the current legacy LAN configuration that exists at the site prior to the ITS upgrade. With this as a starting point, and the target design summary in the next section, the planning and discussions necessary for a smooth transition to a totally compliant ITS can be made.

3.1 Current Network Equipment (Completed during site survey)

A diagram(s) describing the current network architecture (Figures N-1, N-1a), at a box level showing network connectivity, shall be used to provide the high-level design of the existing network. This diagram shall include all ITNs, EBNs, core and non-core that are currently connected to the network. This shall include connectivity details within each building.

Provide a complete list of current network equipment, suitable for reuse or relocation, for each building. This list shall include hardware revision level and software revision level for each component, e.g., IOS version level, etc. Table N-1 shows one possible format for portraying this information.

3.2 Target Network Architecture

A diagram(s) describing the target network architecture to be discussed at a box level meeting and to be used as the requirements basis for the Vendor Selection process will be presented by the Prime. The diagram(s) showing network connectivity shall be used to provide the high-level description of the proposed network architecture. This diagram(s) (Figure N-6) shall include all ITNs, EBNs, core and non-core that are planned to be connected to the network. This shall include connectivity details within each building.

3.3 IP Addressing (Completed during site survey)

This section shall show and discuss current IP addressing at the site. Tables and text shall be used to describe the current situation. Table N-2 depicts one possible format of the information to be provided.

3.4 Deleted

3.5 Protocols (Completed during site survey)

This section shall show and discuss the routing and non-routing protocols in use at the site prior to the implementation of ITS. Tables, diagrams, and text shall be used in this section as necessary to describe the current situation.

3.6 Virtual Local Area Networks (VLANS) (Completed during site survey)

This section shall show and discuss the current VLAN environment at the site prior to ITS implementation. Tables, diagrams, and text shall be used in this section as necessary to describe the current situation. One possible depiction of the information is shown in Table N-3.

3.7 Deleted

3.8 Network Management (Completed during site survey)

This section shall show and discuss the current status of network management at the site. Tables, diagrams, and text shall be used in this section as necessary to describe the current situation.

3.9 Wide Area Network (WAN) and Classified Connections (Completed during site survey)

This section shall show and discuss the current WAN connections to the network existing at the site prior to ITS implementation. For classified networks to be integrated into the network, detailed information about classified architecture shall be included. Tables, diagrams, and text shall be used in this section as necessary to describe the current situation.

3.10 Physical Environment (Completed during site survey)

This section describes current power, grounding, air conditioning, suitability and apparent constraints of building space, patch cords and their compatibility with existing wiring. It should identify the requirements for improvements to support the new and/or modification to the existing network gear.

3.11 Miscellaneous (Completed during site survey)

This section shall be used to document and discuss any other aspects of the current network environment or performance data that existed at the site prior to ITS implementation. It shall show and discuss items such as LOS radio, leased circuits, or other transmission media that forms part of the ITS. It shall also discuss the condition of the electrical grounds for each element in the current network and how they were measured. Tables, diagrams, and text shall be used in this section as necessary to describe the current situation. Actions taken to address any performance issues shall be discussed.

4 TARGET NETWORK DESIGN (Draft during collaborative design – final by HWIPR)

This section shall describe the network’s total configuration. This shall include closet level, card level, and port level details for the network design. It shall discuss any local factors that influence the proposed design. For example, local factors can include legacy data equipment infrastructure, heavy processing locations such as server farms, organizational based addressing needs, large concentrations of users in a facility, network synchronization services including timing sources and distribution, classified enclaves, and support for voice infrastructure. This section of the TSIP captures the high level design, the detailed design, and operational configuration once implementation is complete. (Note that “as built operational configurations” are captured in Table N-4.) The following sub-sections are meant to capture these details.

4.1 High Level Design (Draft during collaborative design – final by HWIPR)

Provide top-level system diagram(s) similar to Figure N-4. The diagram(s) shall expand on the topology, as shown in Figures N-1 and N-6, and incorporate any changes required due to site survey data and discussions during the collaborative design phase. After VSD is approved, provide a detailed set of drawings (Figure N-5a) for HWIPR that correlate with Box Level spreadsheet requirements and include the selected vendor components for each building / facility and communications closet to be serviced by the target network architecture. This set of drawings shall be finalized (Figure 5) by conclusion of FDA. This logical network architecture shall describe top level switching and routing for all technologies used. Both direct and patched connections shall be included (see Figure N-4a). At a minimum, the following areas shall be addressed: redundancy measures including routers, component redundancy, interconnection links for SONET, Fast Ethernet and Gigabit Ethernet; a timing analysis to support SONET design; external WAN connections to gateways, e.g., NIPRNET, Secret IP Router Network (SIPRNET), Defense Research Engineering Network (DREN) and Internet Service Providers (ISPs); IP voice and data requirements including Command and Control Voice Grade LAN (C2VGLAN), voice and data circuit requirements; and miscellaneous items such as locations of routers, transport rates, security architectures, and line protocols.

4.2 IP Addressing (Draft during collaborative design – final by FDA)

Describe the IP addressing plan,. e.g., IPv4 and/or IPv6, and the philosophy behind any changes to the IP addressing. In developing the IP addressing plan, the contractor shall work with the site and collaborative IPT to determine the most beneficial long-term IP addressing scheme. This plan will include IP addressing for systems (such as GATES) for which advance notification of any IP address changes are critical to ensure continuity of operation. Sub-netting of the addressing scheme shall consider the following: addresses provided by the base users, identify the number of sub-nets that the organization needs today and estimates for next three years, and identify the number of hosts on the organization’s largest sub-net today and estimates for the next three years. Consider the AF goal of regional management, in selection of the addressing scheme for management of VLANs. Identify the general sub-netting philosophy; i.e., based on buildings or users. This IP addressing subnet scheme shall also take into account any mission required static and dynamic addressing subnet requirements either in place or planned. The goal of this section is to document the ultimate final IP addressing configuration for the site. Table N-5 shall describe the final recommended configuration. Provide any dual stack router and network address translation schemes as necessary to meet addressing needs. This plan may require changes to be made to existing equipment and configurations, addition of new equipment and configurations, and in general a requirement to change the existing methodology that the site uses to manage IP addresses. Some of these changes may be too aggressive for implementation during the ITS deployment schedule. The Cutover and Test Plan shall provide transition planning with respect to IP addressing including what the delivered configuration will be from the contractor to the Government.

4.3 Protocols (Draft during collaborative design – final by FDA)

Describe general philosophy and provide details on what routing protocols were selected for the design and where they will be implemented. Provide rationale for changes to the site’s existing use of protocols. This section shall consider, but not be limited to the following items: network size, available bandwidth, inter-network delay, reliability, and load. Provide also the general philosophy and detailed design for non-routed and IP multicast protocols selected for the design. The contractor shall document all protocols, both routed and non-routed, that are used or supported in the ITS design. This section shall document the protocols in use after the system is fully implemented and cutover. The contractor shall use whatever combination of text, tables, and figures are necessary to describe the protocol implementation. The cutover and test plan shall contain specific information involving the transition process and changes required to the protocols during ITS implementation.

This shall include eliminating any protocols currently in use which are no longer needed, the addition of new protocols such as network time protocol (ntp), the implementation of an IP multicast protocol so that the capability to support IP multicast can be demonstrated, or any changes in how protocols are used.

4.4 Deleted

4.5 SONET

If a SONET transport is employed in the ITS network, the design in this section shall address the following:

1. Describe how the layer 3 is engineered with SONET or Next Gen SONET.

2. Discuss why either Bidirectional…