Attachment 13 TSSx.pdf

United States Special Operations Command

Tactical Local Area Network (TACLAN)

System Specification (TSS)

Program Manager for Command, Control

(USSOCOM)

System Specification (TSS)

5 November 2010 United States Special Operations Command (USSOCOM)

Program Manager for Command, Control, Communications and Computers (PMC4

7701 Tampa Point Boulevard

MacDill AFB, FL 33621-5316

Computers (PMC4)

This Page Intentionally Left Blank

TACLAN System Specification (TSS) i

TABLE OF CONTENTS

1 SCOPE

1.1 BACKGROUND

1.2 SYSTEM OVERVIEW

1.2.1 TACLAN Full Suite

1.2.2 Mission Planning Kit

1.2.3 Field Computing Device

1.2.4 Video Distribution Hub -Lite

1.2.5 Coalition Local Area Network

1.2.6 Radio Over Internet Protocol Kit

2 APPLICABLE DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

2.1.1 Military Standards and Regulations

2.1.2 Other Guidelines and Publications

3 REQUIREMENTS

3.1 BOUNDARY

3.1.1 WAN Connection

3.1.2 Communications Security (COMSEC)

3.1.3 Firewall

3.1.4 Network Interoperability

3.2 INFORMATION ASSURANCE

3.2.1 DoD Information Assurance Certification and Accreditation Process Guidance

3.2.2 Network Protection and Security

3.2.3 System Recovery and Restoral

3.2.4 Disaster Recovery

3.3 SERVERS

3.3.1 Server Specification

3.3.2 Domain Services

3.3.3 KVM Switch (Monitor/Keyboard/Mouse)

3.4 STORAGE

3.4.1 Mass Storage and User Partitions

3.5 NETWORKING

3.5.1 Local Area Network

3.5.2 Network Capabilities

3.5.3 Protocol Support

3.6 COMPUTING

3.6.1 Laptops

3.6.2 Field Computing Device

3.7 POWER SUBSYSTEM

3.7.1 Primary power

3.7.2 Uninterruptible Power Supply

3.7.3 Grounding System

3.7.4 Protection Devices

3.8 ANCILLARY DEVICES

3.8.1 Printing

3.8.2 Projector

3.8.3 Web Camera

3.8.4 Scanner

3.8.5 Cabling

3.8.6 Fiber Optic Transceiver

3.8.7 Tool Kit

ii

3.9 PHYSICAL CHARACTERISTICS SUITE

3.9.1 Size

3.9.2 Weight

3.9.3 Set-Up/Teardown

3.10 QUALITY FACTORS

3.10.1 Reliability

3.10.2 Maintainability

3.11 LOGISTICS

3.12 ENVIRONMENTAL CONDITIONS

3.12.1 Non-Operating (Suites, MPKs, FCDs)

3.12.2 Operating (Suites, MPKs, FCDs)

3.13 PACKAGING AND TRANSPORTABILITY

3.14 ELECTROMAGNETIC ENVIRONMENT

3.15 HUMAN PERFORMANCE/HUMAN ENGINEERING

3.15.1 Safety

3.15.2 System Design

3.15.3 Manpower

3.15.4 Training

3.16 DESIGN AND CONSTRUCTION

3.16.1 Parts and Materials

3.16.2 Configuration Identification

3.16.3 Interchangeability

3.16.4 Electrostatic Discharge Control

3.16.5 Corrosion

3.16.6 Workmanship

3.17 SOFTWARE BASELINE

APPENDIX A: SOFTWARE BASELINE

APPENDIX B: ACRONYMS

APPENDIX C: VIDEO DISTRIBUTION HUB -LITE

iii

FIGURES AND TABLES

FIGURE 1-1 - TACLAN FUNCTIONAL COMPONENTS

FIGURE 1-2 - NOTIONAL TACLAN SIPR CONNECTION

FIGURE 1-3 - NOTIONAL MISSION PLANNING KIT

FIGURE 1-4 NOTIONAL VIDEO DISTRIBUTION HUB - LITE

FIGURE 1-5 NOTIONAL COALITION LOCAL AREA NETWORK

FIGURE 1-6 FIGURE NOTIONAL ROIP IMPLEMENTATION

FOUO//UNCLASSIFIED

1 SCOPE

The purpose of this document is to define the system specification for the United States Special Operations Command (USSOCOM) Tactical Local Area Network (TACLAN) family of systems, and to establish the technical and operational performance characteristics, fabrication, and hardware and software integration requirements.

1.1 BACKGROUND

TACLAN is the tactical equivalent of our Special Operations Forces (SOF) Command, Control, Communications, Computers and Intelligence Automation Systems (C4IAS) and Special Operations Command Research, Analysis, and Threat Evaluation System (SOCRATES) networks. It provides the automation infrastructure and common-user applications to interconnect deployed SOF headquarters, main operating locations, tactical teams, and liaison elements. Numerous joint, service, and SOF deployed automation programs/efforts leverage TACLAN to gain connectivity to SOF Information Environment (SIE) networks and subsequent SIE services. TACLAN consolidates numerous deployed SOF automation efforts into a single consolidated infrastructure program consisting of hardware and SOF validated software applications.

TACLAN systems shall be employed throughout the full spectrum of USSOCOM missions, globally and in all weather conditions.

1.2 SYSTEM OVERVIEW

TACLAN is a family of systems that extends SIE services to tactical SOF locations facilitating the timely exchange of information between deployed and garrison SOF headquarters and main operating locations, while enabling liaison and coordination with regional combat commands, Services, Department of Defense (DOD), and national agencies concerning SOF operational support. TACLAN shall scale to accommodate network resizing to meet mission requirements. TACLAN’s primary operational mission is to provide the tactical user with flexible interfaces to communications, databases, and mission applications that will collectively extend the equivalent fixed base garrison C4I Surveillance and Reconnaissance (C4ISR) architecture.

TACLAN’s families of systems are a modular and scalable suite of computer network equipment and workstations. The family of systems currently includes the Suite, Mission Planning Kit (MPK), Field Computing Devices (FCD), Video Distribution Hub -Lite (VDH-L), Coalition Local Area Network (C-LAN) and Radio Over Internet Protocol (ROIP) Kit.

TACLAN will consist primarily of Commercial Off-the-Shelf/Government Off-the-Shelf (COTS/GOTS) equipment and software applications that are compliant with industry and DOD standards. It will implement an open-system architecture in order to minimize interoperability issues.

TACLAN will interconnect all deployed SOF elements from the smallest team to a Joint Special Operations Task Force (JSOTF) headquarters with one seamless network to share information and facilitate responsive knowledge based decisions. It supports connectivity to interconnect liaison elements and tactical teams to the main network, including the fielding of FCDs for tactical teams. Figure 1-1 depicts the notional high level TACLAN functional components.

Figure 1-1 - TACLAN Functional Components

1.2.1 TACLAN FULL SUITE

The suite is the largest system in TACLAN. It currently includes the routers, hubs, switches, servers, network management and information assurance tools, printers, scanners, cabling, and workstations to interconnect deployed users at three (3) classification levels or segments (i.e., Unclassified Internet Protocol Router Network [NIPRNET], Secret Internet Protocol Router Network [SIPRNET], and Joint Worldwide Intelligence Communications System (JWICS).

TACLAN

Figure 1-2 - Notional TACLAN SIPR Connection

1.2.2 MISSION PLANNING KIT

The MPK is a standalone self contained LAN currently including laptops, switches, projectors, printers, scanners and cabling. The MPK may be used to connect to a TACLAN Suite or other networks. The MPK is packed in a transit case and includes;

four (4) laptops, switch, printer, scanner, video projector/screen, one (1) Universal Serial Bus (USB) Webcam and ancillary equipment to connect all devices.

Figure 1-3 - Notional Mission Planning Kit

1.2.3 FIELD COMPUTING DEVICE

An FCD is a semi or fully ruggedized laptop that is deployed with the SOF warrior.

FCDs are used by SOF warriors that are geographically separated from the wired network. The goal of a FCD is to be the lightest and smallest computing device that will still run the standard TACLAN suite of software. Each FCD includes the laptop computer, assault backpack and the following power connectors; five (5) bay battery charger, BA5590 Lithium Battery Connector, NATO slave connector, 240v up and down transfer, and vehicle power adapter.

1.2.4 VIDEO DISTRIBUTION HUB -LITE

The VDH-L is a specialized configuration of hardware and software that allows for the distribution of near real-time and recorded (Video on Demand [VoD]) Full Motion Video (FMV) to the deployed user. The VDH-L is a scaled down version of USSOCOM’s VDH. The VDH –L is utilizes the same video decoders, encoders and multicast distribution system that is included in the VDH but designed to be integrated into a deployed network that may include a TACLAN suite, another Services network or stand alone as its own network. The current encoder/decoders used in the VDH-L are by Optibase and are two (2) MGW 400 decoders, one (1) MGW decoder and the Fully Integrated Tactical IPTV System (FITIS) for VoD recording and web portal for user authentication. See Appendix C: Video Distribution Hub -lite for more detail.

Figure 1-4 Notional Video Distribution Hub - Lite

1.2.5 COALITION LOCAL AREA NETWORK

The C-LAN is specialized use of a TACLAN suite of equipment. The C-LAN currently includes the routers, hubs, switches, servers, network management and information assurance tools, printers, cabling, and workstations to connect users to any of the coalition networks in use today to include but not limited to; Battlefield Information Collection and Exploitation Systems (BICES), Combined Enterprise Regional Information Exchange (CENTRIX) - International Security Assistance Force (ISAF) or Afghanistan Mission Network (AMN).

Figure 1-5 Notional Coalition Local Area Network

1.2.6 RADIO OVER INTERNET PROTOCOL KIT

The ROIP Kit uses the USSOCOM standard approved ROIP software, as listed in Appendix B (currently WAVE), in a specialized arrangement of hardware and software to bridge communication devices (radios, soft phones, Voice over Internet Protocol (VoIP) phones, Personal Data Assistants [PDA]) that can not inherently transmit to each other. The ROIP Kit acts as the transition boundary for wireless communication (analog or digital) in the radio frequency spectrum (e.g., Very High Frequency [VHF], Ultra High Frequency [UHF], Satellite Communications [SATCOM]) to Internet Protocol (IP). The ROIP Kit will include hardware with serial ports to attach eight (8) radios that receive and transmit on a particular frequency (VHF, UHF,SATCOM) of interest. The ROIP Kit will provide network connectors (RJ45, fiber, etc.) that allow for the connection to a data network via an included switch or router. The ROIP kit will provide remote monitoring and operation of all integrated radios allowing user select ability for voice and/or data transmission.

Figure 1-6 Figure Notional ROIP Implementation

2 APPLICABLE DOCUMENTS

The following tables identify the documents that form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement.

2.1 GOVERNMENT DOCUMENTS

2.1.1 MILITARY STANDARDS AND REGULATIONS

DOCUMENT REVISION TITLE

MIL-STD-209 K

22 February 2005

Lifting and Tiedown Procedures

MIL-HDBK-470

A w/Notice 1

29 June 2007

Designing and Developing Maintainable Products and Systems, Volume 1

MIL-HDBK-781 A Reliability Test Methods, Plans and Environments for Engineering Developing, Qualification and Production

MIL-STD-810 G

31 October 2008

Environmental Engineering Considerations and Laboratory Test

MIL-STD-1472 F

w/Notice 1

Human Engineering Design Criteria for Military Systems, Equipment and Facilities

2.1.2 OTHER GUIDELINES AND PUBLICATIONS

CECOM Safety Office Technical Bulletin # 7

Guidelines for Equipment Using Sulfur Dioxide Batteries

CJCSI 6211.02 C

9 July 2008

Defense Information System Network (DISN): Policy and Responsibilities

CJCSI 6212.01 E

15 Dec 2008

Interoperability and Supportability of Information Technology and National Security Systems

DOD Directive 8000.1 19 February 2009 Management of the Department of Defense Information Enterprise

DOD Directive 4630.05 5 May 2004 Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS)

DOD Directive 8100.02 14 March 2004 Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense Global Information Grid

(GIG)

DOD Directive 8500.01 E

24 October 2002

Information Assurance (IA)

DOD Instruction 8510.01 28 November 2007 DoD Information Assurance Certification and Accreditation

Process (DIACAP)

DOD Instruction 8500.2 6 February 2003 Information Assurance (IA) Implementation

TACLAN 4 April 2004 TACLAN Capability Production Document (CPD)

TACLAN 29 May 2002 Reliability and Maintainability (R&M) Rationale report (RRR) for the TACLAN

All Appropriate Security Technical Implementation Guides (STIG) http://iase.disa.mil/stigs/stig/index.

html

USSOCOM Directive 25-1 3 June 2003 Special Operations Forces (SOF) Information Enterprise (SIE)

3 REQUIREMENTS

TACLAN shall be modular in design and permit for the addition/removal of users and devices with minimal impact to services. Components shall be packaged into transit-cases physically protecting the equipment and in such a way to enable operators the ability to deploy tailored network configurations. TACLAN Suite configurations shall be tailorable from 10 to 600 devices per segment with no degradation to the network services.

The following sections describe the specific functional, technical, physical, and design performance parameters required for the TACLAN system. Unless otherwise noted, the requirements listed below are applicable to all segments (i.e., NIPRNET, SIPRNET, JWICS) and all systems offered by the TACLAN program.

3.1 BOUNDARY

TACLAN’s boundary enables a reliable and secure connection to the Wide Area Network (WAN) for users and devices. The boundary shall be primarily designed to interface with SOCOM’s SOFTACs family of products but capable of interfacing with collocated military and commercial telecommunications transmission systems to establish connectivity with the SIE and other DOD tactical and strategic networks and services.

The major systems in the boundary include routers, firewalls and National Security Agency (NSA)-certified encryptors.

3.1.1 WAN CONNECTION

The WAN connection shall provide TACLAN users the interface to SOF tactical and strategic networks and data sources. WAN equipment shall include an IEEE 802.3-compliant routing device (e.g., router) to support wide area networking for each of the three segments (NIPR, SIPR, JWICS). The WAN shall support the port configurations and protocols listed in the subsections below.

3.1.1.1 PORT CONFIGURATION

The boundary shall provide interconnectivity between the WAN, LAN, Communications Security (COMSEC) equipment, and supporting telecommunications transmission equipment (for situations when COMSEC is not required). The following ports shall be provided:

a. Minimum of four (4) IEEE 802.3-2008 ports at one (1) gigabit/second (Gb/s) to interface with the LAN segments/access points (e.g., switches).

b. Minimum of four (4) serial ports. The serial ports shall be configurable either as host ports or as trunk ports and shall support the protocols in Paragraph 3.1.1.2.

The serial trunk ports shall interface and operate with the COMSEC equipment.

c. Maintain its configuration database in non-volatile memory during power interruptions.

3.1.1.2 PROTOCOL SUPPORT

The WAN gateway routing device shall support the following protocols (Threshold).

a. Software: Compliant with Industry and Government standards

b. Layer 1 WAN Protocols: EIA/TIA-232, EIA/TIA-449, V.35, EIA-530, X.21, HSSI, DS3/T3/E3, DS1/T1/E1

c. Layer 1 LAN Protocols: 10/100/1000Base-T,1000Base-SX

d. Layer 2 Protocols: IEEE 802.3i/j/u/z/ab/ac/ad/af, IEEE 802.1d d-2004/q-2005/x- 2004/ax-2008, Layer 2 Tunneling Protocol (L2TP), PPTP

e. Layer 3 Protocols: IPv4/6 unicast, multicast, routing and addressing, ICMP, IGMP, IGRP, IPSEC, OSPF, Border Gateway Protocol (BGP), RIP v2/ng

f. Layer 4 Protocols: GRE, MGRE, TCP, UDP

g. Layer 5 Protocols: Server Message Block

h. Layer 7 Protocols: BOOTP, DNS, DHCP, FTP, HTTP, IRC, LDAP, NetBios, NTP, POP3, RADIUS, RMON MIB, RTP, RSTP, SSH, SIP, SNMP v1,v2,v3, SOAP, TFTP

i. Access Control: L3/L4 ACL

j. QoS: Congestion avoidance, congestion management, traffic shaping and policing, link efficiency, DiffServ, RSVP/IntServ, classification/marking and remarking, queuing and scheduling, IP precedence, DSCP, policy filtering, COPS, CoS-based policing

The WAN gateway routing device shall support the following protocols (Objective).

a. Layer 1 LAN Protocols: 10GBase-T, 10GBase-LX4

b. Layer 2 Protocols: IEEE 802.3 ae/an/aq

3.1.2 COMMUNICATIONS SECURITY (COMSEC)

The boundary shall independently transport operations at three (3) security enclaves (NIPRNET, SIPRNET, JWICS) (Threshold). Cross-security Domain Systems (CDS) shall allow one boundary connection point to simultaneously process user data traffic at NIPRNET to SIPRNET or SIPRNET to JWICS (Objective).

TACLAN’s boundary shall utilize COMSEC equipment to encrypt/decrypt the WAN gateway interface. It shall have the capability to transport secure data utilizing NSA endorsed security protection mechanisms. The TACLAN COMSEC architecture shall be based on the equipment described in the subsection below.

3.1.2.1 INLINE NETWORK ENCRYPTION (INE)

The TACLAN system will be equipped with an approved HAIPE encryption device on each of the security enclaves. Users are responsible for all operational key material.

3.1.3 FIREWALL

A firewall shall be provided for protection on the NIPRNET and SIPRNET segments of the TACLAN Suite. The firewall shall be manageable through management software and provide the ability to correlate events for threat prevention and vulnerability analysis. The firewall shall comply with the following (Threshold):

a. Evaluation Assurance Level (EAL) 4 certified

b. Denial of service attack prevention

c. URL filtering

d. Mail Guard service

e. JAVA applet filtering

f. Support for up to 280,000 simultaneous connections

g. Protected logging

h. Cut-through proxy

i. Standards-based virtual private network (VPN)

j. Support for advanced Voice over IP (VoIP) standards including SIP, H.323 and

SCCP

k. Inbound/Outbound Access Control Lists (ACLs)

l. Layer 1 (WAN): RS232

m. Layer 1 (LAN) : 10/100/1000 Base-T

n. Layer2: IEE 802.1q

o. Layer 3: IPv4/IPv6

p. Layer 4: Network Address Translation (NAT)/ Port Address Translation (PAT)

q. Routing Protocols: OSPF

r. Network Management: SNMP, Syslog, CLI, Secure CLI, SSHv2, Telnet over IPsec, out-of-band console port, XML over HTTPS

s. Stateful failover

The firewall shall comply the following (Objective):

a. Support for advanced Voice over IP (VoIP) standards including Assured SIP

3.1.4 NETWORK INTEROPERABILITY

In accordance with CJCSI 6212.01E, TACLAN must support Net-Centric military operations. The system must be able to enter and be managed in the network, and exchange data in a secure manner to enhance mission effectiveness. The system must continuously provide survivable, interoperable, secure, and operationally effective information exchanges to enable a Net-Centric military.

3.2 INFORMATION ASSURANCE

Information Assurance (IA) is the process and procedures in place to manage the risks associated with storage and transmission of data. In addition to the IA measures employed on the boundary the following outlines the requirements of TACLAN’s IA process and procedures to ensure the integrity of the data that traverses TACLAN.

3.2.1 DOD INFORMATION ASSURANCE CERTIFICATION AND

ACCREDITATION PROCESS GUIDANCE

TACLAN systems shall be type accredited following the DoDI 8510.01 DIACAP process and in accordance with Defense Information Systems Agency (DISA) STIGs. TACLAN software shall be installed and configured in accordance with the DoD General Purpose STIG, Checklist, and Tool Compilation CD (also known as SRR Lite CD [RETINA, Gold Disk]).

3.2.2 NETWORK PROTECTION AND SECURITY

TACLAN hardware, hardware configuration, and overall system design shall ensure compliance with all Director of Central Intelligence Directive (DCID), DISA, Chairman Joint Chiefs of Staff Directives/Instructions, and USSOCOM security procedures and certification criteria.

3.2.2.1 NETWORK ACCESS

TACLAN shall prohibit unauthorized access to restricted network(s)/information, support continual security and system monitoring capabilities, determine database permissions, and provide for a user to logon anywhere within a network segment. TACLAN shall use approved security solutions to provide the system administrators with automated capabilities to monitor network activities, such as intrusion attempts, audit trails, and system backup status, and have the capability to affect defensive electronic responses (e.g., block IP address, disconnect attacker, notify system administrator, trace attack, etc.). The system shall require unique user identification and password per security level for logon.

3.2.2.2 NETWORK MANAGEMENT

TACLAN shall provide system administrators the current USSOCOM approved suite of management tools.

3.2.2.3 PATCHES & SOFTWARE UPDATES

TACLAN software to include operating systems, COTS/GOTS applications, network equipment operating systems shall be patched in accordance with SOCOM, DoD and DISA guidelines.

3.2.3 SYSTEM RECOVERY AND RESTORAL

TACLAN shall provide for network recovery from denial of service attacks and shall incorporate an automated means for malicious code detection and removal (e.g., computer virus) including an update capability at the user and server level.

3.2.4 DISASTER RECOVERY

A disaster recovery method shall be provided to facilitate a full system backup for each segment. The storage capacity shall be sufficient to backup and store the contents of all attached network servers and mass storage devices within a single TACLAN security segment/domain. Software and required agents shall be included to support a full and selective backup/restore requirement for all services. The backups shall be performed in a manner to minimize interference with the operation of a TACLAN system.

3.3 SERVERS

The systems referenced in this section cover the server component of the TACLAN architecture. TACLAN’s servers shall support the approved TACLAN software baseline and provide Directory Services, data and systems management, and common back-end services, such as electronic mail, intranet/Internet, streaming multimedia, C2, file, print, and access control. The items described in this section include Domain Controllers (DC), Back-End servers, and the Keyboard, Video and Mouse (KVM) switch.

In an effort to minimize space and weight all servers shall be run in a virtualized environment. A minimum of two (2) physical servers and minimum of ten (10) virtual machines shall be present. In the event of the loss of a single server, the reaming physical servers shall be able to run all virtual machines. Within each segment the virtual infrastructure shall:

a. Be centrally managed

b. Automatically move virtual machines from a failed machine

c. Provide a distributed resource scheduler

d. Provide consolidated backup

e. Provide distributed power management

3.3.1 SERVER SPECIFICATION

All servers shall be rack mountable in a standard TACLAN transit case. All the servers shall have the ability to slide into mounting brackets. Each of the servers shall be designed to comply with:

a. Size: Servers shall minimize size and weight and provide adequate space for all of the internal components to avoid external peripherals.

b. Hard Drives: Hard Drives shall be externally removable storage, compliant with security requirements associated with classified operations. Hard drives shall be configured in RAID for failover and redundancy. The drives shall be of sufficient size run all of TACLAN’s software applications.

c. Memory: Sufficient memory (RAM) shall be provided to support the server’s applications with acceptable performance while under full load conditions, including the loss of a single physical server. The memory shall be provided in at least two (2) units (modules, chips) for redundancy.

d. Processors and motherboards: Multi-processor servers are an acceptable method of fulfilling performance requirements. All processors and motherboards shall be certified by the manufacturer as server class processors and motherboards. Processors shall be compatible with any server software being used by TACLAN. (The vendor’s Web site may be referenced for the processors that are approved for server use.)

e. Server Peripherals: All servers shall have a DVD/CDROM drives (a combo is acceptable). Video, 10/100/1000 NIC cards shall be integrated or on separate cards.

Minimally the server shall have one (1) serial port, one (1) parallel port, four (4) USB ports and one (1) video connector.

f. Expansion Slots: All servers shall have a minimum of two (2) Peripheral Component Interconnect Express (PCI-E) slots.

3.3.2 DOMAIN SERVICES

3.3.2.1 DOMAIN CONTROLLERS

There shall be two (2) DC provided for each of the TACLAN segments. All DCs shall be on different physical machines. No other services shall be hosted on either DC.

3.3.2.2 OTHER SERVICES

Other services shall be hosted in accordance with vendor specifications. The services must be designed in compliance with the current TACLAN VDD.

3.3.3 KVM SWITCH (MONITOR/KEYBOARD/MOUSE)

A single KVM switch shall be included in any configuration that includes rack mountable servers. The KVM shall support three users with multiple security permissions. The KVM shall be chainable to allow for expansion. The KVM shall be a 1U mechanical (Threshold) or secure IP (Objective) KVM and mount in a transit case.

A secure IP device must meet the Federal Information Processing Standards (FIPS) 140 - 2 requirements. Secure IP KVM shall support FIPS 140-2 certified AES 256 bit encryption.

The KVM shall minimally comply with:

a. 17” monitor 1280x1024 resolution

b. 105-Key Keyboard

c. Touchpad Mouse

3.4 STORAGE

TACLAN shall provide additional storage externally to the servers. This storage will be used for backup and user data storage. For SIPRNET and JWICS, storage shall consist of two (2) separate storage devices; one for primary storage of user data and backup; the second for near-real time replication and redundancy. For NIPRNET, storage will consist of one (1) storage device for primary storage of user data and backup.

The storage device shall be capable of operating in the event of one (1) (Threshold) or two (2) (Objective) drive failures. The mass storage device shall be no larger than 2U (Threshold) or 1U (Objective) in height. The minimum drive RPM is 10K (Threshold) with a goal of 15K (Objective). User data shall be stored in its own logical partition separate from archival information.

3.4.1 MASS STORAGE AND USER PARTITIONS

The user storage data partition shall have a minimum capacity of five (5) terabyte (TB) (Threshold) ten (10) TB (Objective) of usable storage for NIPR and JWICS. The user storage data partition shall have a minimum capacity of ten (10) terabyte (TB) (Threshold) twenty (20) TB (Objective) of usable storage for SIPR, It shall be provided to support online data storage and archiving at all levels of classifications. This mass storage device shall support all file systems and protocols supported by the clients and servers. All storage media shall be removable.

3.5 NETWORKING

Network components shall provide the necessary interfaces for switching and routing to support the user’s operational requirement to rapidly and reliably exchange data/information.

3.5.1 LOCAL AREA NETWORK

TACLAN shall provide equipment to create a LAN segment for each TACLAN segment that supports network access. The LAN shall provide a minimum of Ethernet over twisted pair at 1 Gbit/s (IEEE 802.3ab) to transport large volumes of data among mission critical applications within a deployed SOF node. TACLAN user devices shall interface to the LAN through local network access points (e.g., switches, routers). TACLAN shall provide a capability to interconnect multiple LAN access points/switches to reduce physical points of presence and traffic on the boundary.

3.5.2 NETWORK CAPABILITIES

Network devices and access points shall:

a. Form a scalable networking architecture that provides access for up to 600 TACLAN devices.

b. Support LAN switching and, as a minimum, shall comply with IEEE 802.3i/j/u/z/ab/ad/af and support Multimode fiber optic and CAT5e copper interfaces.

c. Provide the capability to establish Virtual LAN (VLAN) architectures to segregate staff element (i.e., C2, VOIP, VIDEO etc.) traffic and to simplify moves, additions, and modifications of users within workgroups.

3.5.3 PROTOCOL SUPPORT

The LAN devices shall support the following protocols.

a. Layer 1 LAN Protocols: 10/100/1000Base-T,1000Base-SX

b. Layer 2 Protocols: IEEE 802.3i/j/u/z/ab/ac/ad/af, IEEE 802.1d d-2004/q-2005/x- 2010/ax-2008, Layer 2 Tunneling Protocol (L2TP), Point-to-Point Tunneling Protocol (PPTP)

c. Layer 3 Protocols: IPv4/6 unicast, multicast, routing and addressing, Internet Control Message Protocol (ICMP), Internet Group Management Protocol (IGMP), Interior Gateway Routing Protocol (IGRP), Internet Protocol Security (IPSEC), Open Shortest Path First (OSPF), Routing Information Protocol (RIP) v2/ng (next generation)

d. Layer 4 Protocols: Generic Routing Encapsulation (GRE), Multipoint Generic Routing Encapsulation (MGRE), Transmission Control Protocol (TCP), User Datagram Protocol (UDP)

e. Layer 5 Protocols: Server Message Block

f. Layer 7 Protocols: Bootstrap Protocol (BOOTP), Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), File Transfer Protocol (FTP), HyperText Transfer Protocol (HTTP), Internet Relay Chat (IRC), Lightweight Directory Access Protocol (LDAP), File Sharing and Name Resolution protocol (NetBios), Network Time Protocol (NTP), Post Office Protocol Version 3 (POP3), Remote Authentication Dial In User Service (RADIUS), Remote Network Monitoring 1&2 (RMON), Management Information Base (MIB), Real-time Transport Protocol (RTP), Real-time Transport Streaming Protocol (RSTP), Secure Shell (SSH), Session Initiation Protocol (SIP), Simple Network Management Protocol v1,v2,v3 (SNMP), Simple Object Access Protocol (SOAP), TELNET, Trivial File Transfer Protocol (TFTP)

g. Access Control: L3/L4 Access Control Lists (ACL)

h. Quality of Service (QoS): Congestion avoidance, congestion management, traffic shaping and policing, link efficiency, Differentiated Services (DiffServ), Resource Reservation Protocol (RSVP), Integrated Services (IntServ), Classification/marking and remarking, queuing and scheduling, IP precedence, Differentiated Services Code Point (DSCP), policy filtering, Common Open Policy Service (COPS), Class of Service (CoS)-based policing

The LAN devices shall support the following protocols (Objective).

a. Layer 1 LAN Protocols: 10GBase-T, 10GBase-LX4

b. Layer 2 Protocols: IEEE 802.3 ae/an/aq,

3.6 COMPUTING

TACLAN includes specific computing devices that may interface with all three (3) TACLAN segments to access network segments/services: laptops and FCDs. The performance parameters are described in the following paragraphs.

3.6.1 LAPTOPS

TACLAN shall have semi-ruggedized laptops for all three security segments (30 NIPRNET/ 30 SIPRNET/ 10 JWICS) and four (4) laptops on the MPK. The laptop shall be capable of running the client software baseline listed in APPENDIX A: SOFTWARE BASELINE . The laptop shall minimally comply with:

a. Display/Video: The display shall be a Color Liquid Crystal Display (LCD) measuring 15.4” on the diagonal. Resolution shall be user selectable up to 1920x1200. The video card shall have a minimum of 256 megabytes of memory.

b. Hard Drives: Hard Drives shall be removal and no smaller than 80 gigabytes in size.

c. Memory: Sufficient memory (RAM) shall be provided to run all of TACLAN’s approved software. Memory shall minimally be 2 GB.

d. Processors and motherboards: The processor shall be multi-core and capable of running all of TACLAN’s approved software. The minimum processor clock speed shall be 2.6 GHz with an 800 MHz Front Side Bus (FSB).

e. Peripherals: Laptops shall have an internal or external (USB) DVD/CDROM drives (a combo is acceptable). An integrated Video, 10/100 NIC, speakers and sound cards.

Minimally the laptop shall have one (1) serial port, four (4) USB ports and one (1) video connector.

f. Expansion Slots: The laptop shall have a minimum of two (2) Peripheral Component Interconnect Express (PCI-E) slots.

3.6.2 FIELD COMPUTING DEVICE

The FCD shall be a highly portable, visual computing and communications device that enhances the data collection and exchange capabilities for remotely deployed SOF operators. It shall enable the user to prepare, edit, and send and receive messages, data, and imagery to or from other SOF/C2 units and C4ISR systems.

The FCD shall be in two form factors; 1) semi-ruggedized (e.g. CF-19) and 2) fully-ruggedized (e.g. General Dynamics MR-1). Both models shall be able to operate of an internal rechargeable battery, US power outlets, International power outlets, BA5590 Lithium batteries and vehicle power outlets.

The FCD shall minimally comply with:

a. Size: The FCD shall minimally be 5 lbs.

b. Display/Video: The display shall minimally be a Color (LCD) touch screen measuring

10.4” on the diagonal. Resolution shall be user selectable. The video card shall have a minimum of 128 megabytes of memory.

c. Hard Drives: Hard Drives shall be removal and no smaller than 80 gigabytes in size.

d. Memory: Sufficient memory (RAM) shall be provided to run all of TACLAN’s approved software. Memory shall minimally be 2 GB.

e. Processors and motherboards: The processor shall be multi-core and capable of running all of TACLAN’s approved software. The minimum processor clock speed shall be 1.0 GHz with a 533 MHz FSB.

f. Peripherals: Laptops shall have an internal or external (USB) DVD/CDROM drives (a combo is acceptable). An integrated Video, 10/100 NIC, and sound cards. Minimally the FCD shall have one (1) serial port, two (2) USB ports and one (1) video connector.

g. Expansion Slots: The FCD shall have a minimum of two (2) Peripheral Component Interconnect Express (PCI-E) slots.

3.7 POWER SUBSYSTEM

The TACLAN system shall be designed to use available worldwide military or commercial power as its primary power. All TACLAN equipment shall be selectable to operate at either 110 or 220 volt. An uninterruptible power supply (UPS) shall be provided for each TACLAN Suite to power key components in the event of primary power loss. The UPS shall provide both visual and audio indications when primary power is lost.

3.7.1 PRIMARY POWER

TACLAN shall operate from externally supplied power sources within the following parameters:

a. Voltage: 90 - 250 VAC

b. Frequency: at 43 - 63 Hz

c. Phase: Single Phase

3.7.2 UNINTERRUPTIBLE POWER SUPPLY

Each TACLAN Suite domain shall include a UPS capability that provides back up power to switching devices, servers, storage subsystem, COMSEC equipment, KVM, routers, firewalls and other key components (Threshold) or full TACAN suite of equipment (Objective) for a minimum of fifteen (15) minutes (Threshold) or twenty four (24) hours (Objective) in the event of primary power loss. The fifteen (15) minute period shall be used to gracefully shutdown the key components. The UPS shall be capable of:

a. Over voltage protection

b. Lightening/surge protection

c. Power conditioning

d. Interoperable with domestic, international and field generator power sources/systems within the parameters described in Paragraph 3.7.1 above

e. Removable battery packs

f. User selectable output voltages

g. Input isolation transformer

h. Automatic by-pass

i. Rack mountable

j. Approved for civilian and military transport

k. Remotely manageable

l. Four (4) power receptacles

3.7.3 GROUNDING SYSTEM

The TACLAN system documentation shall identify the necessary steps to ground the system. Each segment must be grounded separately.

3.7.4 PROTECTION DEVICES

All power strips shall provide spike/surge suppression to protect system equipment.

3.8 ANCILLARY DEVICES

TACLAN provides a number of Ancillary Devices (AD) to assist the SOF user perform their mission. These AD include printers, projectors, scanners, cabling, fiber optic transceiver, video camera and tool kit. The following subsections outline TACLAN’s ancillary devices.

3.8.1 PRINTING

TACLAN shall provide a printer for use with the systems. The printer shall minimally comply with:

a. Two (2) connection interfaces 1) 10/100 network card and 2) USB

b. Resolution black and white 1200 x 1200

c. Resolution color 4800 x 1200

d. Print Speed black and white 18 pages per minute (ppm)

e. Print Speed color 14 ppm

f. Paper sizes including letter, legal, B5 and A4

Each TACLAN segment shall include two (2) printers accessed by subscribers through a printer server. The JWICS segment shall include an additional high speed, photo quality printer accessed by subscribers through a printer server.

The MPK shall include one (1) printer that is shared of off one of the included laptops.

3.8.2 PROJECTOR

TACLAN shall provide a projector that minimally compy with the specifications:

a. Video type LCD, resolution 1024x768

b. 2200 ANSI lumens (high brightness) and 1700 ANSI lumens (low brightness)

Each TACLAN segment shall inclulde one (1) projector and two (2) screens. One (1) screen shall be 80” in diagnol and one (1) shall be a table top.

The MPK shall include one (1) projector and one (1) table top screen.

3.8.3 WEB CAMERA

TACLAN shall provide video camera that minimally complies with:

a. Connector Type – USB

b. Built in Microphone

c. Resolution 960x720 @ 30 frames per second (FPS)

Each TACLAN segment shall include four (4) web cameras that are connected to already included laptops.

The MPK shall include one (1) web camera that is connected to an already included laptop.

3.8.4 SCANNER

TACLAN shall provide a scanner that minimally complies with:

a. Connector type – USB

b. Scan Color/Gray Scale and Black and White

c. Scan pages up to 8.5” x 11.7”

Each TACLAN segment shall include one (1) scanner that is connected to an already included laptop.

The MPK shall include one (1) scanner that is connected to an already included laptop.

3.8.5 CABLING

3.8.5.1 CAT 5E

One (1) 1000-foot spool of shielded twisted pair CAT 5e cable shall be provided with each TACLAN security segment.

3.8.5.2 FIBER OPTIC

One (1) 500-foot spool of tactical field fiber optic cable shall be provided with each TACLAN security segment.

3.8.6 FIBER OPTIC TRANSCEIVER

TACLAN shall provide six (6) fiber optic transceivers (FOTS) per segment to extend three (3) independent Gigabit links. These multi-mode fiber links will allow clusters of users to access the TACLAN domain(s) from remote areas within the local operating environment. Each FOTS shall provide full-duplex operation over multimode fiber optic cable. The data interface shall comply with ISO/IEC 802.3 (Gigabit); and the fiber interface shall comply with ANSI X3.237-1995. The FOTS shall operate with the same power sources as specified in Paragraph 3.7.1 above. The FOTS shall have the capability to be 19” rack-mountable.

3.8.7 TOOL KIT

A tool kit shall be provided with each TACLAN system that contains all specialized tools required to set-up and redeploy a TACLAN system. It shall include at a minimum:

a. T-stripper

b. LAN ProNavigator

c. Multimeter

d. 10/100/1000 BaseT toolkit

e. Fiber optic connectors ST

f. Fiber optic connectors SC

g. Fiber optic adapter set

3.9 PHYSICAL CHARACTERISTICS SUITE

3.9.1 SIZE

The TACLAN system (i.e., all three segments), including ancillary equipment when configured for transport in its transit cases, shall not exceed the maximum loading profile for one and one-half (1 1/2) (Threshold) or one (Objective) 463L pallet.

3.9.2 WEIGHT

All TACLAN equipment is mounted or packaged in multiple transit cases for flexible, tactical deployment. Each loaded transit case shall not exceed two (2) man (174 lbs) (Threshold) three (3) person (121 lbs) (Objective) lift to safely handle and maneuver as defined in MIL-STD-1472F.

3.9.3 SET-UP/TEARDOWN

TACLAN shall comply with the set-up and teardown requirements outlined below. Set-up/teardown times may be longer in extreme environmental conditions.

3.9.3.1 SET-UP

Two (2) operators shall be able to pass electronic mail (email) within one (1) hour (Threshold) or thirty (30) minutes (Objective) from a segment of a suite and ten (10) laptops that have been previously fully configured and packaged into transient cases.

3.9.3.2 REDEPLOY

Two operators shall be able to redeploy a ten (10) workstation one segment network, including full system disassembly and complete network degradation, within thirty (30) minutes (Threshold) or twenty (20) minutes (Objective).

3.10 QUALITY FACTORS

3.10.1 RELIABILITY

The Contractor shall ensure maintenance concerns are addressed during system design and integration to achieve a mean time between failure (MTBF) of 3500 hours (T) and 4000 hours (O). The Contractor must ensure the commercial transport contractual requirement is sufficient to meet the Network Mean Time to Repair (MTTR) of 30 min

(T) and 20 min (O).

3.10.2 MAINTAINABILITY

3.10.2.1 MAINTENANCE CONCEPT

The maintenance concept consists of two levels of maintenance: Organizational and Above Organizational (Contractor Support & Depot). Organizational Level maintenance is equivalent to Unit-level maintenance and will consist of unit personnel performing Preventive Maintenance, Checks and Services (PMCS), removal and replacement of major end-items or components, cable replacement, and minor hardware replacement (fuses, lamps, switches). Above Organizational Level entails all maintenance beyond the established capabilities of the Organizational Level, including Direct Support, General Support, and Depot Level maintenance.

Beyond the tools outline in section 3.8.7, no special tools shall be required to do routine maintenance. Decontamination procedures shall be addressed in appropriate technical manuals. The system shall include a diagnostic capability that will automatically notify system administration personnel by email, or other automated means, of system failures and malfunctions. The system will automatically generate a log for system usage and errors.

3.10.2.2 MEAN TIME TO REPAIR/MEAN DOWNTIME

TACLAN shall demonstrate the following:

a. Mean Time to Repair (MTTR) of 15 minutes or less

b. Maximum Time-To-Repair (MaxTTR) of 60 minutes or less

c. Mean Downtime (MDT) for laptops of 60 minutes or less

d. MDT for other TACLAN components of 30 minutes or less

3.11 LOGISTICS

TACLAN shall be capable of being logistically supported within the existing USSOCOM logistics infrastructure. The logistics support program shall be an integral part of the Contractor's management system. The Contractor shall ensure that all products are supportable through their life cycles. In addition, the Contractor should be capable of supporting all products as necessary for the entire length of the contract. The logistics support program will be used to develop and optimize an approach that allows for the best operational value to USSOCOM and to develop, acquire, or apply the necessary resources to achieve this best value. The support approach shall reflect best commercial practices with minimal tailoring to achieve USSOCOM support objectives. At a minimum, supportability efforts should include plans for the following: maintenance support, supply support, technical manuals, training, technical support, safety, and human systems integration.

In accordance with DFARS 252.211-7003, TACLAN shall be identified, through the use of item unique item identifier (UID) marking. Information regarding implementation of UID methods can be found at the Office of the Under Secretary of Defense for Acquisition Technology and Logistics website (http://www.acq.osd.mil/dpap/UID/) and the TACLAN UID Plan.

3.12 ENVIRONMENTAL CONDITIONS

TACLAN systems will be deployed worldwide. The systems will be exposed to various environmental conditions that include, wind, rain, snow, ice, sand, and dust when deployed. With the exception of the tactical teams (using FCDs vice TACLAN systems), TACLAN will typically be setup in an area with some type of sheltered facility (tent, warehouse, building, etc.) with varying degrees of environmental control. All items in the following paragraphs apply to the FCDs and RoIP Kit. For non-operating conditions only the Temperature, Vibration, Humidity and Shock requirements apply to the Suites and MPKS and for operating conditions only the Temperature, Humidity and Altitude requirements apply to the Suites and MPKs.

3.12.1 NON-OPERATING (SUITES, MPKS, FCDS)

TACLAN, when packaged for transport or storage and in any non-operating configuration, shall meet the performance requirements of this specification and tested in accordance with the following procedures, during/after exposure to any combination of the following conditions:

a. Temperature: Continuous exposure with air temperatures from -60°F to +185°F without solar radiation and with negligible air movement.

b. Vibration IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 514.5. The specific test procedures, levels and duration for all Transportation modes referenced in Table 514.5-1, Vibration Environment Categories, shall be implemented.

Truck/trailer/tracked environment shall use the loose cargo test procedures.

c. Humidity IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 507.4

d. Salt Fog IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 509.4

e. Sand and Dust IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 510.4

f. Shock IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 516.5 procedures II and IV (when packaged in transit cases).

g. Rain IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 506.4, Procedure 1

h. Altitude: Up to 10,000 feet above sea level (Threshold) and 12,000 ft (Objective).

3.12.2 OPERATING (SUITES, MPKS, FCDS)

TACLAN, when operating in any configuration, shall meet the performance requirements of this specification and tested in accordance with during/after exposure to any combination of the following conditions:

a. Temperature: Continuous exposure with air temperatures from -20°F to +130°F without solar radiation and with negligible air movement -

b. Humidity IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 507.4

c. Salt Fog IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 509.4

d. Sand and Dust IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 510.4

e. Rain IAW MIL-STD-810F (Change Notice 3 dated 5 May 2003), method 506.4, Procedure 1

f. Altitude: Up to 10,000 feet above sea level (Threshold) and 12,000 ft (Objective).

3.13 PACKAGING AND TRANSPORTABILITY

TACLAN shall be integrated into ruggedized transit cases that utilize a 19-inch equipment rack mount system. All fully configured/loaded transit cases shall be able to withstand the shock, vibration, and climatic requirements specified in Paragraph 3.12.

The transit cases, with their covers in place, shall be designed to protect the TACLAN equipment from direct exposure to the environmental conditions (i.e., rain, snow, ice, dust, etc.) that are likely to be encountered during worldwide military and commercial transport.

The system will be deployed worldwide as restrained cargo in military and commercial land/sea/air mobility platforms and all SOF fixed and rotary winged aircraft. The transit cases shall have the ability to be securely tied down for vehicular and/or palletized mode for air, sea, and rail transport. The system shall be compliant with 463L pallet requirements when packaged for transport. The transit cases shall have the ability to stack on top of and mechanically interlock with each other.

3.14 ELECTROMAGNETIC ENVIRONMENT

Commercial best practices shall be used to ensure electromagnetic compatibility with co-located equipment and to mitigate adverse effects of electromagnetic interference.

3.15 HUMAN PERFORMANCE/HUMAN ENGINEERING

The system design, including controls, displays, configuration, connections, required procedures, and operating environment, shall minimize human performance errors, interface problems, and workload requirements. All design and operation aspects of the components and network operating environment must conform to applicable human engineering design criteria to support ease of operation.

3.15.1 SAFETY

The system shall be designed IAW all applicable system safety standards so as to minimize safety risks associated with operating, maintaining, managing, or supporting the system. Any residual hazards or risks associated with installing, operating, or maintaining the system or its components must be identified, attended to in training and support materials, and made manageable. Particular emphasis shall be placed on minimizing risks of electrical shock and visual strain. A Safety Certification shall be completed on all new equipment.

3.15.1.1 SAFETY MARKINGS AND LABELS

The following specifications shall apply to TACLAN safety markings and labels:

a. Safety markings and labels shall be provided identifying any potential hazards to personnel.

b. Markings shall be readily visible.

c. All safety hazards not eliminated through design shall be addressed in the appropriate technical manuals (TM). Information regarding hazard-avoiding procedures and safety warning labels on equipment shall be included in all manuals. Maintenance TMs shall address replacement procedures for damaged or missing safety labels.

d. All transit cases shall be labeled, identifying the function and contents of the case.

Permanent markings shall be prominently placed on the module body to indicate fully-loaded weight, lift requirements, center of gravity, and top of case.

e. All cabling within and between transit cases shall be labeled appropriately.

f. All cabling will be color coded to insure classification isolation (black for Unclassified, red for Collateral, yellow for SCI).

g. Colors of safety critical controls and indicators shall be yellow for caution and red for danger. Any color is permitted for functional controls or indicators provided it is clear that safety is not involved.

3.15.1.2 MECHANICAL SAFETY

The following mechanical safety specifications shall apply:

a. The equipment shall provide maximum access and safety to personnel during installation, operation, and maintenance.

b. Under the operating conditions specified herein, the equipment shall not become physically unstable to the degree that it could become a hazard to operators or maintainers.

c. Provisions shall be made to prevent accidental pulling out of rack mounted equipment. Latches used to safely secure drawers, etc. in an open or closed position shall be reliable and accessible.

d. Equipment…