Atch 17_CITS BPD_NetOps SB.doc

COMBAT INFORMATION TRANSPORT SYSTEM (CITS)

INFORMATION TRANSPORT SYSTEM (ITS)

BASELINE PROGRAM DIRECTIVE (BPD)

For FY09 Projects Introduction: The purpose of this document is to define what the CITS program management office (PMO) will provide to meet a base’s ITS program requirements. This document is based upon the 15 January 1998 final Operational Requirements Document (ORD), the 20 September 2004 ITS Architecture, and the DOD Unified Capabilities Requirements 2008 (UCR 2008). The Assured Services Local Area Network (ASLAN) performance requirements provided in UCR 2008 Section 5.3 "IP-Based Capabilities and Features" shall be incorporated as needed to achieve the mandated level of voice quality, delay, jitter, reliability, availability, and recovery from failure, etc. Reliability, availability and backup power / UPS requirements are dependent on the type of C2 user being served. User types and requirements are identified in the last table of the BPD. The BPD provides a baseline for the program which applies to all aspects of the ITS. Specific technical and installation/implementation direction is separated into three parts, the distribution system, premises wiring, and the network system. The distribution system entails all outside plant (OSP) for ITS up to the first fiber optic patch panel upon building entry, as well as inside plant (ISP) distribution between communications closets and “1st 400 feet” user drops. The portion from the communications closets to the end user equipment is currently outside the scope of the ITS program’s funding except as highlighted below. The network system portion is made up of all active components necessary for the ITS within a building. An ITS project includes the outside fiber plant, all distribution patch panels between connections and the electronics, all connections to any LAN distribution closets or other distribution points within the building, and all network electronics including the end user ports that connect the premise wiring to end user equipment. Additionally, ITS projects will provide the necessary system support requirements such as dedicated electrical power, grounding of the comm. equipment and equipment operating climate needs.

Deviation process: As with any guidance document applicable to many different situations, optimization for a specific location may require deviations from the baseline. Each deviation from the baseline must be documented in the final base specific Telecommunication System Integration Plan (TSIP). If the implementation team’s PMO representative determines that a deviation is against an ORD requirement, additional guidance will be provided as to how the deviation should be handled.

General Definition: ITS is a high speed, broadband, robust digital information transport system The Air Force direction to CITS to implement a “One Base--One Network” concept will be met by integrating all existing base data systems and providing the capability to integrate all existing and planned voice, video, imagery, and sensor systems including classified systems. The program does not include funding to repair problems or provide solutions beyond the requirements for the program. This eliminates the following items from most ITS solutions without PMO pre-approval:

Encryption devices for classified transmission

Video equipment such as transmitters, receivers, splitters, amplifiers, etc

Major facility upgrades to communications closets

Manhole and duct system implementations beyond those required to support the proposed ITS solution

User end equipment such as computers, cameras, speakers, software, and applications

Voice end equipment such as multiplexers, trunking devices, telephones, etc.

The CITS program will provide full network interconnection to existing core buildings and backbone capacity for future support of non-core buildings. Buildings are classified as either End Building Nodes (EBNs) or Information Transfer Nodes (ITNs). The backbone consists of all ITNs and associated interconnections between adjacent ITNs. The backbone must be designed to support the total requirement for all buildings (Core & Non-Core) that are planned for connection by CITS even if they are not funded or implemented immediately. This allows the program to provide a backbone capable of meeting present and future requirements without forklift upgrades.

The ORD contains requirements to support IP traffic, Quality of Service (QOS) capabilities, and circuit transport on each base. A minimum of an Ethernet backbone will be provided at all bases. If a base does not have significant circuit requirements, an Ethernet only solution will be provided. If significant circuit requirements are documented, a SONET backbone may be provided to support them. The SONET will not be used for transport of IP traffic unless specific requirements are identified by the IPT and approved by the PMO. Proposed SONET solutions may not span the entire base, and need only be provided at those Core buildings where circuit requirements exist. The program office will make a technology recommendation prior to issuance of a request for proposal from Integration Contractors. CITS ITS does not provide for WDM/DWDM solutions. The CITS program provides sufficient fiber for all base requirements and consideration will be given for WDM/DWDM only when requirements and cost justify.

General System Considerations: At a minimum, the system design shall consider the location of classified enclaves, server farms and consolidation plans, Network Management/Network Defense (NM/ND), high-density user populations, mission critical facilities, existing voice switching equipment, and existing/projected VoIP needs. . If a base does not have current requirements for VoIP, a backbone capable of supporting VoIP with upgrade but without fork lift upgrade will be implemented as required. These factors may lead to an additional links between ITNs or to an EBN, larger switches, higher speed interfaces, and backup power / UPS. Prior to the start of the site survey, a starting topology shall be determined which takes into consideration geography, the number of buildings serviced, the number of users in the buildings, the missions supported, the ASCLAN requirements, and cable access.

ITS is considered to be a weapons system made up of existing and new components configured as a consolidated network. The system shall be based on a one-base, one-network methodology and topology with the goal of integrating all base network services under management of the NM/ND. The system design shall address all base information transport requirements and not be a design to some real or perceived budget estimate. Also, the system integrator shall fully integrate all new and existing network components, insure that all components meet the full requirements, and cutover all current users before the system is accepted by the government.

Main Medical Enclave (MME) and AFMSA support: The use of a medical facility, or non-combatant facility with respect to the Law of Armed Conflict (LoAC), as an ITN for ITS is not allowed. However, we will work with AFMSA to support the use of a medical enclave as the hub for medical traffic. AFMSA will support the IPT in determining which buildings apply to the LoAC, how these buildings will be attached to the network (either to the closest ITN or back to the MME), and how any secondary communications closets within a building are attached. If the architecture agreed to by the IPT exceeds the cost of a standard ITS implementation (all EBNs are attached to the most cost effective ITN), the contractor shall track the delta in cost and AFMSA will fund the differential. If connections are required from the MME to two different ITNs, AFMSA and the PMO will work together to get the required waivers to the LoAC. Under no circumstances will the MME or any medical building be used to transport or support core buildings other than medical buildings. All allied support funded by ITS must be in support of ITS requirements. The following rules govern what the CITS ITS program will provide for the MME.

a. Switches: The only switch that ITS will acquire and install is for the 1st comm closet at the Main Medical Facility (MMF). Additional switches at the MMF and all other medical facilities are the responsibility of AFMSA.

b. Fiber: If the MMF does not have adequate reusable fiber, ITS will install fiber to the nearest ITN. If medical buildings are currently connected to the MMF with adequate (per the BPD) reusable SM or MM fiber, we will install no new fiber. If a medical EBN is connected to another ITN (not the MMF) with adequate reusable fiber ITS will provide a VLAN solution back to the MMF. ITS will install fiber back to the MMF only if AFMSA provides all required funds. When a core medical EBN has inadequate fiber, ITS will install fiber to the nearest ITN (with a VLAN solution to the MMF) or the MMF, whichever is most cost effective.

OSP Distribution System Specifics

- All existing cables, when worthwhile test data is not available as determined by the IPT, planned for reuse shall be tested (ALL unused fibers in the cable) with both 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 fiber is considered viable for reuse. Large Fiber Count Cables, especially Hybrid cables, and un-terminated fibers identified for possible reuse shall be called to the attention of the IPT (specifically the PMO DS) for discussion and possible testing modifications. Any decisions resulting from these discussions shall be documented in section 2.3 of the TSIP. 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.

- Between an ITN and a Core 3 EBN, existing 62.5 multi-mode fiber can be used if it will support Gigabit Ethernet. This reuse would typically limit distances to a maximum 550 meters.

- The minimum existing fiber count acceptable for reuse is 6 between ITN and EBN and 18 between ITNs. In all cases where larger, more than 6 or 18 respectively, numbers of fibers are planned for use, the number of fibers used in the design, plus 4, is the minimum acceptable. In all cases the fiber is considered reusable when it is tested-good, unused, and available for ITS.

- At no time shall non-building rated fiber optic cables entering a building exceed 50 feet in cable length without prior approval of the PMO distribution engineer.

- Building rated cable shall be spliced, in equal counts, to the non-building rated cabling at the building entry point where 50 feet of non-building rated cable length will not reach the first communications closet/FODP, unless another design method is approved by the PMO distribution engineer.

- Cabling between communications equipment locations shall have a minimum of 4 strands or if requirements dictate more connections at least 2 more than connection requirements.

- New ITN-to-ITN fiber optic cabling shall contain 36 fibers (all single mode), or the number of fibers needed to meet the architectural requirements mandated for the ASLAN plus 18 spares, if this number is greater.

- New ITN-to-EBN fiber optic cabling shall contain 12 fibers (all single mode), or the number of fibers needed to meet the architectural requirements mandated for the ASLAN plus 6 spares, if this number is greater.

- Direct bury cable shall be metallic armored. Alternatively, standard external grade fiber optic cable shall be placed in a high-density polyethylene (HDPE) SIDR 11 roll pipe having a nominal inside diameter of 1.25 inches. Only one cable shall be installed in each HDPE pipe. One roll pipe in each run shall have a tracer wiring on the exterior surface of the pipe.

- All runs shall use continuous fibers, with no intermediate patches, cross connects, and a minimum utilization of splices. Any splices that must be used shall be fusion splices. No mechanical splices are to be used.

- Provide 50 feet of maintenance loops coiled in every third manhole, starting/ending in the first manhole exiting each building (i.e. the first manhole outside of each building will contain 50 feet of maintenance loop). If manhole spacing and/or congestion presences issues with the loop size or placement in the first manhole outside of a building or along the run, alternatives can be implemented with concurrence of the PMO distribution engineer.

- A coil of 25 feet of cable shall be installed on all cables entering and leaving a man hole splice case For an interior splice sufficient cable shall be left to enable repairs and changes. Adjustments can be made with PMO distribution engineer concurrence. Adjustments for design purposes shall be made and agreed to prior to FDA submission and adjustments during installation shall be made and agreed to prior the install effort and reflected on as-built CSIRs as needed.

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

- ITS installed cable shall not contain factory fiber splices.

- The single mode fiber shall comply with industry standards with regard to mode field diameter, core-cladding concentricity, attenuation, and dispersion characteristics at 1300 nm and 1550 nm.

- The multi-mode optical fiber shall comply with industry standards for 62.5-µm fiber with regard to core-cladding concentricity, attenuation and modal bandwidth at 850 nm and 1300 nm.

- Cable plant shall be tested and proven to perform within expected tolerances.

- Each ITN shall be connected to at least two other ITNs. Additional connections may be used between ITNs if requirements justify the expense. In addition (for ITNs only), two of these connections must be physically diverse (separated by a minimum of 40 feet) cable routes. Physical diversity starts at the end of the entry conduit when direct buried or at the first manhole after leaving a building if the manhole is within 50 feet of the building. If the manhole is more than 50’ from the building, a new entryway must be provided or another method of physically protecting the cable may be used, with PMO approval. Changes to cable entries made during previous phases of ITS can only be reworked with approval of the PMO.

- Of critical importance in using found infrastructure is the network Backbone and its diversity. This diversity must be verified to ensure true physical separation in cable paths between at least two connecting ITNs. The contractor will use all documentation available from government sources as well as physical cable identification to clearly identify cable separation along the entire length of all ITN backbone routes.

- In all cases the contractor shall physically verify and mark the routes of backbone cables at the entry point(s) of each ITN and along the route until diversity is clearly demonstrated through manhole inspection. Cables used in the backbone cable shall be marked as a CITS backbone cable where ever the cable is inspected.

- Where insufficient duct capacity exists to support the new ITS, direct bury (preferred) or additional duct capacity shall be considered.

- Overbuilding of manholes and ducts requires coordination and approval of the PMO

- Repairing manholes and duct systems shall be considered when economically feasible. Repairs shall only be done when necessitated by the ITS installation and with coordination with the CITS PMO.

- All new manholes and handholds shall be fully enclosed pre-cast concrete in construction, have round cast iron cover/ring or shall be full sized, galvanized hinged lids and shall be rated for roadway traffic, and sized to accommodate the full build-out of the duct system.

- New manholes/handholes shall be capable of being secured to prevent direct opening/access. However, this is not meant to be an elaborate system nor capable of meeting the requirements of a protect distribution system (PDS).

- New duct/conduit building entries shall have a manhole/handhold or access point installed within 50’ of the building entrance.

- All new direct buried armored cable or roll-pipe alternative, shall be installed with at least 36” of top cover depth.

- All new manhole and duct systems shall use 4” schedule 40 PVC pipe and be installed below the normal frost line or with a minimum top cover depth of 36”. The one exception is when utilizing a 3’ X 5’ X 4’ full lid manhole with a 4-4” duct system (in 2 over 2 configuration), at which time it is permissible for the top duct to enter the manhole at a depth of not less than 30” from the surface. However, ducts shall transition to the minimal 36” top cover depth before extending more than 6’ from the side of the manhole.

- In OCONUS designs an equal or better product can be utilized if identified and specified during the design collaboration and agreed to by the PMO prior to FDA.

- Boring will be the preferred method of road and parking lot crossings.

- New duct installed under roadways shall be encased in 900 psi concrete slurry filling the entire trench depth less pavement surface requirements. Coordination with the PMO distribution engineer and base CE will be required and shall be documented in the TSIP for any variations to this requirement.

- Sleeveless or uncased boring shall not be used.

- Ducts installed under runways, taxiways, railroad tracks, or other special conditions require coordination with the base civil engineer and the PMO.

- On backbone runs, alternative methods of protecting the ducts (i.e., capping) are permitted only with coordination with the CITS PMO and if it is shown to be more cost effective than diverse routing.

- Standard 1” Innerduct and/or flexible geotextile multiple cell innerduct shall be used to maximize capacity of the duct system.

- All work with the fiber optic cables shall be done by qualified and experienced fiber optic technicians.

- All CITS duct/fiber optic cable runs shall be capable of being tone-traced. Tone-tracing shall be accomplished by utilizing any one of several methods (see TSIP for additional details) to allow a tone signal to be sent along the duct/cable run. Tracing methods will be developed during collaboration and presented for PMO distribution engineer for review prior to Hardware Implementation Plan Review (HWIPR).

- All above ground entries shall consist of an exterior rated NEMA pull box mounted on the buildings exterior wall, connected by UV rated schedule 80 PVC external riser(s) and shall have a 4” wall core thru to the interior wall surface sealed at least on the exterior side depending on the wall thickness, compliant with fire codes.

- All cables,FODPs panels, and connectors, both new and reused, shall be clearly labeled, adequately supported, and neatly dressed.

- No mechanical, butt-splice type connectors will be used.

- SC or MTRJ connectors are preferred. Any other connector will be agreed to in collaboration.

- The Vertical (Z) axis, data shall be taken at ground level.

- CFLD data will be in an excel spread sheet format.

- Leased circuits or other techniques, with bulk encryption, shall be considered, as alternatives, when they have cost or performance advantages when compared to dedicated fiber. Equipment, which is used for transmission, shall be FIPS 140-2 (FIPS 140-1) Level 1 or Level 2 certified.

Level 2 is employed for more sensitive information.

- Before the contractor may use any product that has an associated material safety data sheet (MSDS) a copy for the MSDS must be supplied to the PMO.

- CITS will return distributed areas of the base to similar conditions of those existing prior to ITS installation within a reasonable period of time. Seeding or hydro-seeding shall be used to restore grassy areas.

ISP Distribution System Specifics

- Any newly installed user drops shall use CAT 6 materials, be installed to CAT 6 standards, and certified to meet ANSI/EIA/TIA CAT 6 performance requirements.

- All new user drops will be installed according to BICSI Telecommunications Distribution methods manual.

- Existing Multi-mode fiber optic drops can be employed in special situations where distances, environmental conditions, or situations make it the cost-effective solution for meeting the minimum requirement of Fast Ethernet to the end users.

- Meets CITS Equipment Enclosures or Communications Closet Requirements (CEECR):

- All existing user drops shall be used and assumed to be in good operating condition unless specific 1st 400’ work is authorized.

- If work is authorized to service/improve the existing user drops shall be tested to demonstrate 10/100/1000 Capability as described in the decision flow chart in the TSIP Part 8 of Distribution Appendix (figure D 46), the information will be recorded in the format shown in Table D 8

- If the existing patch cables are not compatible with the premises wiring and patch panels, new patch cords shall be installed.

- Does not meet CEECR and a new location is selected, the contractor shall consider relocating the patch panels, using longer patch cords, or coordinating with the site the rework of the premises wiring while an interim solution is employed. Since the ITS program is not currently funded for the first 400 feet, our goal is to maintain all existing user connections without repairing or replacing premises wiring.

- In cases where the location meets CEECR requirements but it makes technical and economical sense to consolidate closets, CITS will consider doing the “last 400 feet wiring” affected by comm. closet consolidation.

- All electrical work will be labeled at the circuit Panel with room and rack identification and at the equipment end with panel and circuit information.

- EBNs shall be on a minimum of a single dedicated power circuit (sufficient to support the entire suite of equipment). If the EBN supports VoIP to one or more C2 or Special C2 Users, backup power / UPS must be provided.

- A new circuit of an equivalent OCONUS rating shall be used where applicable.

- The contractor is not to install any new facility grounds.

- All existing building grounds that the contractor plans to use in the design shall be tested and presented to the PMO at the HWDR. Readings found during testing of grounding at main electrical service panels that are at or above 25 ohms or no building ground is found shall be reported to the PMO and base Civil Engineering during the next regular IPT and resolutions discussed during collaboration.

- All new ground connections shall be tested for compliance.

- All armored cable shall be grounded according to the manufacturers’ specification and NEC when entering or leaving a building.

- Ground points shall follow the applicable local standards in OCONUS locations.

CITS Equipment enclosures or communications closets

- ITS equipment shall be placed in existing communications closets whenever possible.

- If an adequate closet is not available, a cabinet capable of providing the necessary environmental controls shall be provided. The cabinet shall provide physical protection for the equipment and electrical service and environmental support when none is available at a location. If the location is to serve C2 Users requiring equipment redundancy and UPS for future deployment of VoIP, then sufficient space shall be allocated for this equipment. If a closet or room can be modified to support the equipment for approximately the same cost, this option may be used with PMO approval.

- All ITS equipment shall be located in a physically controlled area (i.e. kept under lock and key where control is maintained by the NCC including, when possible, the power for the rack and end user patch panels). This area shall have sufficient heating, ventilation, air conditioning, cable access, and space to allow for maintenance and operation of the equipment.

If a grounding stud or clearly marked threaded grounding hole is provided the equipment must be grounded to the rack. If there is a question the installer should look to the manufacturer's specifications. An e-mail or written correspondence should be acquired from the manufacturer if any proof of this statement is needed

- CITS will extend ductwork and/or install louvers to address ventilation problems within CITS equipment locations. If new HVAC is needed this will be discussed during the normal IPT meeting. Normally new HVAC is the responsibility of the base.

- CITS will not re-label user drop cables.

Network System Specifics

All new Ethernet backbone equipment shall be upgradeable to 10 Gig Ethernet and capable of supporting a semi-meshed design (>two 10 Gig uplinks)

- Where SONET is required, OC-48 (2.4 Gbps) SONET shall be employed for the backbone. Higher speed connections can be used if requirements justify their use. SONET will only be deployed at ITNs where sufficient circuit requirements exist.

- All new SONET backbone equipment shall be upgradeable to support OC-192 and WDM either internal or external to the box.

- Connections between ITNs and EBNs shall use a minimum of Fast Ethernet (100Mbps) with a target of Gigabit Ethernet (1000Mbps). Multiple Ethernet links can be used when justified by requirements. Usage of SONET equipment and connections to EBNs can be made only when circuit and bandwidth requirements exist in sufficient quantity to make this a best value solution for the Air Force.

- Each item delivered under this contract shall accurately transmit, receive, process, and function correctly using either the Internet Protocol Version 4 or Internet Protocol Version 6 (IPv6). For equipment to be deemed IPv6 Capable, the network equipment vendor must warrant that:

1) each item delivered complies with the current DISR* (was Joint Technical Architecture (JTA)) developed IPv6 standards profile;

2) each item delivered maintains interoperability with IPv4 (specifically, is able to operate on/coexist on a network supporting IPv4 only, IPv6 only, or dual stack (i.e., a hybrid of IPv4 and IPv6)) and

3) each item delivered is supported by the vendor’s IPv6 technical support.

4) and they are committed to providing a transition path that maintains compliance with evolving requirements in the DISR profile.

- Reused layer 2 equipment does not have to be IPv6 Capable. If available, new layer 2 equipment shall be purchased with support for assignment of an IPv6 management address.

- New devices must implement IPv6 functions through hardware solutions. Hardware implementations are expected to provide better IPv6 performance. The network equipment vendor must provide data on equipment performance in a dual stack configuration.

- Devices must provide IPv6 over all layer 2 protocols and methods supported by the proposed design.

* DoD Information Technologies Systems Registry (DISR)

- These service levels must be maintained from EBN to EBN and switch-to-switch across the ITS backbone.

- EBNs that have one or more C2 or Special C2 Users with IP phones shall have 2 or 8 hour UPS for switch and IP appliance. If the building is equipped with emergency backup generators, it will be equipped with a UPS capable of maintaining switch operation for a period of time sufficient to allow the Generator backup power to be brought on line. For all other EBNs surge protection at a minimum shall be provided.

- If site unique requirements for classified or mission critical systems require sustained power exceeding these standards, additional capability can be provided with PMO approval given that the system being supported meets the same standards.

- ITS shall maximize the use of existing network equipment which fully meets requirements. Tradeoffs shall be made to minimize the total number of vendors supported on a site.

- All SONET equipment must support the standard SONET framing.

- SONET equipment shall support DS-1, DS-3, Gigabit Ethernet, and SONET interfaces at a minimum. SONET equipment purchased for OCONUS installations may need to be capable of supporting alternative framing and circuit bandwidths required for that OCONUS location (i.e. E-1,E-3 etc.)

- All SONET equipment must be able to report status via SNMP to the NMS platform..

- Additional redundancy can be used if mission requirements justify the expense.

- When the reliability and availability analysis shows multiple interface cards are necessary, ports shall be assigned to allow a near even split of users between cards. Ports on the same interface card shall not be used to connect diverse paths between ITNs.

. Integration of these products into the NM/ND suite, if required, requires Configuration Control Board (CCB) approval, which the PMO will obtain prior to any changes being made to the NM/ND hardware and software..

- Hardware upgrades and/or additional servers are allowed if required for support of ITS element managers.

- Design of the IP subnet addressing for the management of the network devices will be coordinated with the base and MAJCOM.

- The ITS backbone shall be designed and sized to provide connectivity to all EBNs, core and non-core as identified by the overall base topology, plus 20 percent expansion without chassis replacement. However, only equipment required for current phase implementation shall be purchased.

Gigabit Ethernet, and/or SONET capable network analyzer(s) as required by the design and determined during collaboration.

- Network management traffic shall not share the same VLAN with user traffic.

- Circuits shall be provisioned on any SONET networks to support the circuits identified during the site survey and design.

External Interface External Connections

- All traffic entering or leaving a base shall traverse the base NM/ND system; no other interfaces are allowed.

- ITS shall provide connections to the NM/ND system consistent with the physical interfaces and maximum anticipated throughput of that system. Any Service Delivery Point (SDP), or SDPs if redundancy is provided in the future, shall be terminated at an ITN(s).

All connections external to the base (Data, TDM or SONET) which are part of the base domain (i.e. GSUs, connections between base areas, connections between bases within the same domain) shall be encrypted using as a minimum of FIPS-140 encryption devices. Purchase of these devices is not funded by CITS unless approved by the PMO.

Backup Power: 8 hours, any number of Users Network Availability: 99.999 & Dual Network Connectivity for > 96 Users

Backup Power: 2 hours, any number of Users Network Availability: 99.997 & Dual Network Connectivity for > 96 Users

C2(R) Users (i,e,, Routine C2 Users)

Originate: ROUTINE precedence sessions only. (Terminate Higher Precedence sessions) Backup Power: None required Network Availability: 99.9 & No requirement for Dual Connectivity

Backup Power: Not required Network Availability: 99.9 & No requirement for Dual Connectivity

Section J, Attachment 17

FA8771-09-R-0019