Free Notice (Other) - District Court of Federal Claims - federal

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 1 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

CRYPTOGRAPHIC EQUIPMENT

.~-t .TTTT

PAGE

30

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 2 of 22

NAVAL 3.2

REGIONAL System

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-038g

Characteristics

The ATC shall consist of: an Electronic Cross-connect Switch (ECS), Network Management System (NMS), and all necessary ancillary items, equipment, sub-assemblies, connecting hardware, and cabling. These components shall have the ability to implement all minimum-required functions described below. 3.2.1 3.2.1.1 Electronic General automated circuit access are detailed in the and Cross-Connect Switch (ECS) Requirements

The ATC ECS shall provide route control. The ECS requirements following paragraphs. 3.2.1.2 Interface Requirements

The ATC ECS shall serve as the hub for circuits passing through or terminating at a shore-based Naval Computer and Telecommunications Station (NCTS). The ECS shall interface with various Command, Control, Computer, Communications, and Intelligence (~I) systems that are part of the NTS, DISN, and with commercial and military systems of other agencies and foreign governments. The ECS shall connect with, provide switching for, and have the ability to test and monitor each circuit. These circuits shall include 2-, 4-, and 6-wire 4 kHz voice circuits, and circuits operating from 50 baud direct current (DC) loop teletype to 2.048 Mbps Conference of European Postal and Telephone (CEPT) digital trunks. The ECS shall support common industry and military equipment/circuit interface standards to include: Electronic RS-232-D Industries Association (EIA)

RS-422-A RS-423-A RS-449

RS-530

Interface between Data Terminal Equipment and Data Communication Equipment Employing Serial Binary Interchange. Electrical Characteristics of Balanced Voltage Digital Interface Circuits. Electrical Characteristics of Unbalanced Voltage Digital Interface Circuits. General Purpose 37 Position Interface for Data Terminal Equipment and Data Circuit Terminating Equipment Employing Serial-Binary Data Interchange. High Speed 25-Position Interface for Data Terminal Equipment and Data Circuit Terminating Equipment.

PAGE

31

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 3 of 22

NAVAL

REGIONAL V.35

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 at 48,000 bps Band Circuits. using

Data Transmission 60-108 kHz Group

X.21

Interface between DTE and for Synchronous Operation Networks Message Service PUB 446 GOSIP Handling Elements. - System

DCE Equipment on Public Data

X.400

Model

-

FIPS Military

Standards Common Long Haul and Tactical Communications System Technical Standards Electrical Interface Transparency all data through formats and the switch. Characteristics Circuits of Digital

MIL-STD-188-100

MIL-STD-188-114A

3.2.1.2.1

Protocol

protocols 3.2.1.2.2

The ECS shall be transparent to contained within signals passing Special Interface Requirements

The ATC ECS shall interface with various Command, Control, Computer, Communications, and Intelligence (C4I) systems that are part of the Naval Telecommunications Systems (NTS). These systems utilize UHF SATCOM as its primary source for satellite interfaces from shore to ship. These systems, for simplistic terms to be categorized as Information Exchange Subsystems (IXS), are as follows: (a) CUDIXS - Common Subsystem (b) User Digital Information Exchange

AN/UYK-20 to ON-143(V)4 ON-143(V) 3 to KG-36 KG-36 to ON-143(V)4 ON-143(V)4 to AN/WSC-3 ON-143(V)4 to AN/WSC-5 ON-143(V)4 to TD-1271(B)U User Digital Information Exchange

CUDIXS II - Common Subsystem

PAGE

32

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 4 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

-

VME CHASSIS to ON-143(V) VME CHASSIS to KG-84A KG-84A to AN/WSC-3 KG-84A to AN/WSC-5 KG-84A to TD-1271(B)U - Tactical Intelligence Information Exchange

(c)

TACINTEL Subsystem LSI-9600 LSI-9600 LSI-9600 LSI-9600

to LSI-9600 to AN/WSC-3 to AN/WSC-5 to TD-1271(B)U Submarine Information Exchange

(d)

SSIXS - Satellite Subsystem

- ON-143(V)4 to LSI-4800 - LSI-4800 to LSI-4800 - LSI-4800 to AN/WSC-3 (e) TADIXS (f) - Tactical Data Information Exchange Subsystem

AN/UYK-44 to ON-143(V) ON-143(V)6 to KG-84A ON-143(V) 6 to LSI-9600 LSI-9600 to DSD DSD to TD-1271(B)U TADIXS GATEWAY PROCESSOR to ON-143(V) ON-143(V) 6 to AN/WSC-3 ON-143(V) 6 to AN/WSC-5 ON-143(V) 6 to TD-1271(B) Tactical Command Information

OCTIXS - Officer in Exchange Subsystem -

LSI-9600 to LSI-9600 LSI-9600 to AN/WSC-3 LSI-9600 to AN/WSC-5 AN/UYK-44 to ON-143(V) ON-143(V) 6 to KG-84A KG-84A to ON-143(V) ON-143(V) 6 to LSI-9600 LSI-9600 to DSD to TD-1271(B)U ON-143(V) 6 to KG-36 KG-36 to ON-143(V) ON-143(V) 6 to AN/WSC-3

PAGE

33

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 5 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

- ON-143(V) - ON-143(V) The standard

6 to AN/WSC-5 6 to TD-1271(B) MIL-STD-188-114A as with the following Clock delays its primary exceptions: up

IXS interface employs interface specification Transmit ll5ms. Control circuits Lamp VDC. and Receive

(a)
(b)

(start/stop)

functions requiring ground contact closure with a reference voltage from +6 VDC to 0 V. circuits with a reference voltage of 28

(c)

indicator

(d)

Low Level Converter +/- 6 VDC (currently device interfacing transceivers). switch sizing

an external

3.2.1.3

The ECS shall allow for easy expansion in modular increments to accommodate evolutionary growth anticipated at 30% or more. Circuits identified will be a combination of DC loop, analog, and digital. Requirements for specific sizing of each candidate technical control are contained in the Site Specific Appendices to this specification. 3.2.1.4 Non-Blocking Architecture

The ECS shall utilize a non-blocking architecture. There shall be no distinction between inputs and outputs. Any port must be capable of interconnection with any other port, regardless of loading. Blocking of improper or illogical connections will be a function of the switch control software and network management software. 3.2.1.5 Connectivity The modes: (a) (b) (c) (d) Standard Broadcast (one (one DCE to one to DTE) ports) DTE to DTE) ECS shall Capability support the following port connectivity

port to

many or

"Null-Modem" Loopback (loop

(DCE

DCE

toward

signal

source)

PAGE

34

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 6 of 22

NAVAL 3.2.1.6

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

Redundant

Capability

A single point of failure is unacceptable. Redundancy of key elements shall be built into the system to maintain continuity of operations should a key component fail. At a minimum, redundant key elements of the ECS shall include: (a) (b) (c) (d) Power All supply logic

control source units

Timing Memory

These redundant, key elements shall come on-line automatically, immediately upon the failure of the primary element and with no loss of capabilities or data. There shall be a visual, audible, and printed-report alarm at the control console. In addition, there shall be a visual indication at the equipment cabinet to alert maintenance personnel of the failure. 3.2.1.7 Power Loss Recovery

The ECS shall automatically return to the last configuration held prior to loss of power or reboot. The ECS shall maintain this ability for a minimum of eight (8) hours after a power failure. 3.2.1.8 Test and Monitor

The ECS shall provide intrusive and non-intrusive access for testing and monitoring circuits. The system shall be capable of testing circuits utilizing recognized and accepted industry and military standard test procedures, performed from designated test positions. 3.2.1.9 Performance Standards

There are three major categories of performance standards for digital systems. They are (i) error performance measurements; (2) jitter; and, (3) slip. Subparagraphs 3.2.1.9.1 through 3.2.1.9.3 identify the criteria on which these parameters are based.

3.2.1.9.1

Error

Performance

Measurements

PAGE

35

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 7 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

Error measurement is the most important criteria on which a digital system is judged. Commercial error performance indicators include Bit Error Rate (BER), Errored Seconds (ES), Block Errors, and average BER. BER and ES are the most widely used indicators. 3.2.1.9.1.1 Bit Error Rate (BER)

The ATC ECS shall not exceed bit-error-rate performance objectives as set forth in CCITT Recommendation G.821, Paragraph 2, Table I/G.821. 3.2.1.9.1.2 Errored Seconds (ES) not exceed ES Recommendation performance G.821, Paragraph

The ATC ECS shall objectives as set forth in CCITT 2, Table I/G.821. 3.2.1.9.2 Jitter

The ATC ECS performance objectives G.824, Paragraph 4.2. 3.2.1.9.3 Slip

shall not exceed as set forth in

jitter and wander CCITT Recommendation

The ATC objectives as set 3, Table I/G.822. 3.2.1.10 RED/BLACK The requirements 3.2.1.11

ECS shall not exceed slip performance forth in CCITT Recommendation G.822,

Paragraph

Engineering

Criteria RED/BLACK 5203 and installation MIL-HDBK 232A.

ATC must satisfy the established in NACSIM Criteria in accordance Synchronization

TEMPEST (Deleted

with

Amendment

1 Paragraph

3).

3.2.1.12

Timing

and

The ATC ECS shall incorporate an internal clock to synchronize switch operations. The switch shall be capable of being triggered by an external clock system, i.e., LORAN C, NAVSTAR Global Positioning System (GPS), or any other precision unit. The ATC ECS shall be capable of military and commercial connections (DCE/DCE, DCE/DTE, DTE/DTE, Null Modem); providing timing internally through any switch port(s) without loss timing accuracy at the selected port rate (i.e. without use of

PAGE

36

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 8 of 22

NAVAL

REGIONAL

CONTRACTING port

CENTER clock

WASHINGTON distribution

N00600-94-C-0389 equipment,

additional external cabling, or IDF). 3.2.1.13 Availability

timing

The ATC ECS shall meet service availability standards set forth in CCITT Recommendations G.821, Annex A and G.106, Definition 2.6. Availability for the ATC ECS shall be 99.998 percent or greater. 3.3 Installation and Workmanship

The ECS installation shall conform to accepted industry standards for installation of electronic equipment, cabinets, and cabling. Workmanship shall conform to standards set forth in MIL-STD-454M and MIL-STD-188-124B. Vendor shall define intended installation technique criteria in proposal submission. Any specific Government requirements shall be negotiated. 3.3.1 Interchangeability

All "like" units, assemblies, subassemblies, and replacement parts of the ECS shall be physically, electrically, and functionally interchangeable. 3.3.2 Safety

The ATC ECS shall meet all Occupational Safety Health Administration (OSHA) and Original Equipment Manufacturer (OEM) standards, as well as applicable Government safety regulations. 3.4 Network Management System management (NMS) requirements are defined in the

following 3.4.1

ATC network paragraphs. System

Description contain control

The NMS is that portion of the ATC which will the hardware and software required to allow centralized and monitoring of the network through software-definable commands.

3.4.1.1

Redundancy of failure is unacceptable. Redundancy built into the system to maintain should a key component fail. These

A single point of key elements shall be continuity of operations

PAGE

37

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 9 of 22

NAVAL

REGIONAL

CONTRACTING elements primary

CENTER

WASHINGTON on-line with no

N00600-94-C-0389 automatically upon the loss of capabilities

redundant, key failure of the or data. 3.4.2 NMS

shall come element and

Applications

The NMS shall be the hub of the ATC and shall oversee and manage all system management and network restoration functions within the ATCo Such operations shall include, but are not limited to, the following: (a) (b) (c) (d) Alarm surveillance Network Performance Isolation and Status and Control

Real-time Network Fault

Monitoring Service Restoral and Administrative

(e) Network/Equipment Recordkeeping The NMS control,

Operation

partition 3.4.2.1

shall provide operator and access for remote with External NMS

password protection, workstations.

Interface

Programs

The vendor shall provide the Government with necessary interface data giving the Navy access to the system database in order to use the information to run existing external network management programs through the provided ATC NMS. Security NMS 3.4.3.1 security is discussed in the following paragraphs.

Authorized

Access

A comprehensive security system based on user ID and password shall be provided. The system shall include multiple levels of security to prevent unauthorized access to the system. Statistics on operator access shall be maintained in the form of ID, time, date, and duration of use. 3.4.3.2 Databases The NMS shall include databases which shall support all functions of the ATC as listed in Appendix I, and shall at a minimum, the following:

required contain,

PAGE

38

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 10 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 that shall store faults and

An Alarm and Performance Database contain the capability to log and alarms corresponding to identified their diagnostic results.

A Trouble Database that shall contain the pertinent referred trouble reports and trouble ticket administrative data. An Equipment Database that shall contain equipment configuration data, parameter settings, maintenance status, testing thresholds, hardware configurations, and appropriate administrative data. 3.4.3.2.1 Load/Update Capability

The NMS workstation shall have the capacity for initial loading and subsequent reloading of the NMS database. The NMS workstation shall also have a near-real-time update capability when operating on-line. 3.4.3.2.2 Minimum Required Capabilities

The NMS shall provide a menu-driven, user-friendly, command interpreter, including the following features for each workstation: (a) (b) Command Plain prompts English and text menus error messages to memorize codes

(u) No req~i~r complex commands (d) An display (e)

operator

on-line, context-sensitive HELP command usage and meaning of available commands to bypass commands. the menu and provide the use

The ability of shorthand

3.4.3.3

System

Control operators enabling dynamic, apprised of all current him/her to react to user requirements, natural

The NMS shall keep system operating conditions, changing circuit conditions,

PAGE

39

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 11 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER path

WASHINGTON and

N00600-94-C-038W equipment

or manmade failures. 3.4.3.3.1

transmission

interruptions,

System

Control

Functions

For the NMS to successfully accomplish the system control requirements, it shall provide certain control functions discussed in the following paragraphs. Additionally, the NMS shall automatically disseminate announcements of events to all concerned operators and record the event in the appropriate system database log. 3.4.3.3.2 System Administrator/Operator Capability

Operators shall be able to invoke commands allowing the controller to implement several commands with a single command (macros). The ability to exercise these control capabilities shall be restricted and locally administered by the system administrator with a modifiable password hierarchy program that may limit individual operators to specific capabilities. 3.4.3.3.3 Surveillance Functions

The NMS shall monitor the operational status of the ATC, providing operators with the ability to select circuits and equipment to be monitored. The surveillance function shall result in the collection of circuit, system, and equipment status data that will allow the ATC operator to perform those control and circuit management functions previously discussed in paragraphs 3.1.1.1 through 3.1.1.5. Data requirements for the ATC are driven by: (a) The operational continuity The need circuits to responsibility to maintain circuit

(b)

assign

alternate

route

paths

to

(c)

The requirement to flag high priority systems for management purposes

circuits

and

A database detailing the configuration and interrelationships between all circuits entering or exiting the ATC shall be maintained in the NMSo Equipment configuration and operational status data must be collected to provide operators: (a) An indication that there is an existing impending problem with the network or

PAGE

40

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 12 of 22

NAVAL

REGIONAL (b)

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 manual

The information to override procedures configurations Restoration

intelligently implement or modify programmed

3.4.3.3.4

Service

Information

To effectively restore and/or reroute critical circuits and trunks, NMS operators must possess current, accurate knowledge of the configuration and operational status of all inhouse circuits and equipment. In addition to the logical trunk, circuit, or link outage indications, NMS operators shall be provided detailed information about any outage. For example, the system shall provide, at a minimum, the following: (a) (b) (c) The The location time of of the circuit, link, link, or or trunk fault of the fault

a circuit,

trunk (RP)

The user and restoration faulty service The reason the of circuit, equipment

priority

(d) (e)

link,

or trunk for

is down restoring

The status service

available

(f)

The status of station level circuits, links, and trunks

efforts

to

reroute

on a single reaction. 3.4.4 3.4.4.1

All information concerning an outage shall be displayed screen to facilitate operator comprehension and

Alarms Alarm and On-Occurrence Data

The requirement for ATC alarm data is driven by the requirement to remain aware of the operational condition of the network and to ensure service to users. The NMS shall continuously monitor the operational status of the network at all times. Current connected equipment status information shall be available upon request. When a change of status is recognized in the network, the status change should be reflected in real-time with a new entry in the NMS system operations database. All alarms must be acknowledged before they can be removed from the alarm display screen. 3.4.4.2 Port Alarm Monitoring

PAGE

41

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 13 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 to the occur: of operator if

any

of

the

The NMS shall generate notification following circuit fault conditions (a) Any fault port that affects the

status

a connected

(b)

The loss of a locally-defined ECS's connectivity capability

threshold

of

the

The NMS shall have the ability to monitor, store, and display external alarm sources that indicate failures or Hazardous Conditions (HAZCONs). Failures could be events such commercial power failures, transmission path failures, etc. HAZCONs include, but are not limited to the following: The failure of any combination of primary, backup, or spare hardware where failure of another like component would cause a reportable outage (e.g., primary or auxiliary AC power source failure, Central Processing Unit (CPU) failures, external timing source, main memory failures) and failure of environmental equipment ~ where rapid restoration is necessary for ATC operations to continue (e.g., heating or air conditioning system failures). 3.4.4.3 Alarm Prioritization

Each alarm shall be assigned a level of criticality. There shall be a minimum of two definable levels of station alarms, appropriately color coded, for which the operator shall respond to. These are: L~vei i: Alarm of a station-aezinea ma3or condition requiring immediate acknowledgement or corrective action. This alarm indicator shall be color coded RED. An example of a major (RED) alarm might be: Loss Loss Loss Loss Loss of of of one one of two of two memories power supplies

a transmission timing

path source power source.

of station of the

commercial

PAGE

42

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 14 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

(b) Level 2: Alarm of a station-defined minor condition requiring expeditious handling, but not to the degree of a major alarm. This alarm indicator shall be color coded AMBER. An example of a minor (AMBER) alarm might be: Individual thresholds Group pilot circuit exceeding pre-determined

alarms alarms

Housekeeping

The operator shall be made aware of Level 1 alarms first. If two alarms occur simultaneously, or an alarm occurs during another, the operator shall be clearly apprised of the level of each alarm. If the operator needs to leave the alarm screen (e.g., to go to a trouble-shooting menu), then other alarms of lesser priority should be queued, but additional Level 1 alarms must be displayed i~mediately. The data that the operator was working with before the alarm shall also be saved for later retrieval. 3.4.4.4 Alarm Selection and Display

The NMS shall provide flexibility, through password controls, in selecting which alarms and status indications (visual and audible) will be presented to the operator and what priority will be assigned to each incoming message type. 3.4.5 Operations and Maintenance the

following

This section describes ATC requirements for Operations and Maintenance (O&M) functions: (a) (b) (c) Operations Maintenance Trouble Ticket Processing Support

3.4.5.1

Operations The

Support type of operations support shall be

following

required:

PAGE

43

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 15 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

(a) The NMS shall have the capability, under local control, to input new or modified ATC ECS routing information. This capability is intended to support the development and maintenance of accurate configuration records for the ATC. (b) The NMS shall have application ATC resources based on circuit requirements. functions performed by this software are: software Examples to of assign the

(1)

Assign line or circuit identifiers with a minimum of 16 alpha-numeric characters and flag special circuits. The flags will indicate conditions such as Special Interest circuits, Commercial Carrier circuits, G and H Route circuits, 55-1 reportable circuits, etc. The flag field shall be a minimum of two alpha-numeric characters Assign cable and pair, multiplex etc., designators with a minimum alpha-numeric character location identification numbers Assign equipment designators with of 16 alpha-numeric characters Assign a local identifier. service order channel, of a 16

(2)

(3)

a minimum

(4)

alpha-numeric

(c) The NMS shall provide the capability to update the database with new, service-oriented configuration data in advance of actual system changes. The NMS shall be capable of flagging this data as pending (i.e., not yet operational), and then change its status to operational when a completion notice is received. (d) The NMS shall possess the capability database for pending service orders. These queries the selection of other parameters such as projected activation and service features. 3.4.5.2 Maintenance to query the should allow date of

The NMS shall support both Corrective and Preventive Maintenance (PM) functions. The NMS should also be capable creating and modifying trouble tickets and other maintenance records utilizing the databases described in paragraph 3.4.3.2. Examples of currently-used Navy forms are included in Appendix H. These forms are intended to be informative only, and do not bind the vendor to their use. However, if vendor generated forms are

PAGE

44

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 16 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 integrity of the

used, the format must retain data required on the provided 3.4.5.2.1 Corrective

the informational Navy forms.

Maintenance

Corrective maintenance activities include the identification, isolation, and analysis of network and user service problems; correction of the problems; verification that the corrective actions have restored service to the appropriate levels; and logging of activities for maintenance records and trend analysis. NMS support of these functions shall be userfriendly. 3.4.5.2.2 Preventive Maintenance (PM) prevent

The NMS shall support PM of the ATC in order to non-critical equipment faults from degrading into critical faults. The NMS shall provide the following capabilities: (a) (b) Allow the operator to schedule PM test downtime and

Store preventive guidelines Maintain and test interface Generate Ticket

maintenance

service

(c)

records of preventive maintenance actions results in a database with the ability to with external systems follow-up Processing trouble ticket as a minimum, processing the following maintenance work orders

(d) 3.4.5.2.3

Trouble

The NMS shall provide support. The NMS shall provide, capabilities:

(a)

Create and modify trouble tickets that provide the circuit and/or system involved, the date and time of the fault, the reported fault, space to record agencies coordinated with, and space to record remarks and other information related to the outage. An example of a currently used trouble ticket is included in Appendix H. Close-out Generate trouble trouble tickets ticket status reports as required

(b) (c)

PAGE

45

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 17 of 22

NAVAL

REGIONAL (d)

CONTRACTING

CENTER

WASHINGTON all trouble

N00600-94-C-0389 tickets for the past

Maintain on-line, thirty days Query trouble operator, etc Store completed data file

(e)

ticket

files

by time

period,

port,

(f)

trouble

tickets

in

an historical

3.4.6

Administration

The NMS shall support the planning, report generating, data collecting, and general record keeping functions that are necessary to provide user services and fulfill circuit reporting requirements. Planning and report generating activities require large amounts of accurate, easily accessible data. Data collecting and record keeping activities required for planning, report generating, system control, and O&M functions are discussed in the following paragraphs. 3.4.6.1 Record Keeping

The following sections describe "files" and "records" of various data that shall be kept by the NMS databases. These files and records represent data that should be kept but does not mandate the specific database struoture required to record keeping data:

(a)

Record keeping is a "global" function in that it encompasses all pertinent data stored. This ranges from volatile data, such as alarms, to relatively non-volatile data like equipment inventories and operating procedures. All data shall be available for access, interrogation, or file transfer to any NMS workstation, subject to security and procedural constraints. The NMS shall maintain configuration control for all equipment, circuits, trunks, lines, etc., utilized to support efficient and reliable circuit switching. The NMS shall contain a complete set of data for the network elements under its control.

(b)

3.4.6.1.1

General

Inventory a general status.

equipment

The NMS shall be capable of maintaining inventory by type, number on hand, and

PAGE

46

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 18 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389

3.4.6.1.2

Unassigned

Equipment

Inventory

The NMS shall provide information of spare switch ports and interface equipment. The operator shall be able to call up a screen showing him/her what spare equipment and transmission assets he/she has to work with, including, but not limited to, name, type, service, location, and quantity. 3.4.6.1.3 Switch Configuration Files files shall include all port

Information in these configurations for the ECS. 3.4.6.1.4 Circuit Records

The NMS should contain information related to each circuit. This should include the name and location of the users, type of service, restoration priority, and any special requirements of subscribers. The circuit record shall contain, as a minimum, information required on the Circuit Layout Record (CLR) Card found in Appendix 3.4.6.1.5 ECS Maintenance Records

activities. maintenance 3.4.6.1.5.1

The NMS shall store records of all ECS maintenance These records shall be accessible as both active and historical maintenance files. Active Maintenance Files

The active maintenance file shall contain information concerning ECS hardware and software service problems for which the maintenance activities have not been completed. The initiation of the appropriate command to transfer the individual records in the active maintenance file should only be switched upon completion of the action which clears the equipment fault and returns the equipment for service. 3.4.6.1.5.2 Historical Maintenance Files complete in an

historical off-line, 3.4.6.1.6

The historical maintenance file shall include data for all completed maintenance activities permanent storage database. General Historical Records

The NMS shall provide the capability to store, archive, and retrieve data from alarm logs, trouble reports, repair reports, O&M data, inventory control, etc.

PAGE

47

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 19 of 22

NAVAL 3.4.6.2

REGIONAL

CONTRACTING Generation

CENTER

WASHINGTON

N0060.0-94-C-0389

Report

Reports shall be available through simple operator initiated commands. The NMS shall be capable of storing, displaying, editing, and printing reports. Reports that are printed out must fit on 8 1/2" X Ii" or 14 1/2" X ii" size paper. These reports shall provide near-real-time and long-term historical status information on communications facilities, links, trunks, circuits, and equipment to assist management personnel in maintaining required records. Examples of such reports are listed below and are not all-inclusive. Listing Listing all all circuits circuits for a location as Special a given Interest date or

flagged

Listing all trouble tickets for period between two given dates Listing Listing Listing all all all trouble open tickets for

a given

circuit

trouble

tickets carrier trouble tickets.

commercial

operations. processing 3.4.6.3

The primary purpose of ATC is to support real-time Therefore, non-real-time administrative report shall not interfere with real-time processing. Event Reporting

Event reports detail the results of all ATC system operations. The event report should provide the operator with a chronological list of events to include operator log-on/log-off, time, date, commands, configuration changes, subsystem failures, port alarms, and any other pertinent information necessary to support overall network management. The NMS event database shall be able to produce a report via the system event logging printer and shall be available to the operator via the control console.

3.4.7

Dedicated

Functions to support a extended report

The NMS shall have the capability dedicated edit/word processing function for generation.

PAGE

48

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 20 of 22

NAVAL 3.4.7.1

REGIONAL

CONTRACTING Mode

CENTER

WASHINGTON

NO0600-94-C-O38q

Training

mode that functions. 3.4.8 3.4.8.1

The NMS shall allow the simulates administration,

operator to operating,

have and

a training maintenance

NMS

Workstation

Characteristics Criteria

RED/BLACK The

Engineering

requirements 3.4.8.2

ATC must satisfy the RED/BLACK installation established in NACSIM 5203 and MIL-HDBK 232A. Criteria in accordance with Amendment 1 Paragraph 3).

TEMPEST (Deleted

3.4.8.3

Human Human with Network

Engineering engineering criteria and MIL-STD 454M, Requirement Status Display principles 62. shall be in

accordance 3.4.8.4

The NMS workstation shall be equipped with a color graphics monitor so that the current network alarm or alert status can be determined by color at a glance. 3.4.8.5 Display and Control Concepts

The NMS functional status shall include all Displays shall be access: (a) (b)

shall provide the capability to display the of the ATC at each workstation. The status circuits, equipment, and current alarms. "user friendly" with a minimum of two means

of

Pre-defined

structured

(menu

driven) and

Direct (an expert code to bypass the menu provide the use of shorthand commands) shall have placement, a windowing and sizing capability of various

The NMS dynamic selection, displays. 3.4.8.6 Modularity

that allows windows and

and

Flexibility future display NMS subsystems

The modification,

NMS design shall facilitate particularly as the various

grow,

as

PAGE

49

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 21 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON

N00600-94-C-0389 dictate, defined as

new subsystems are added, as mission requirements demand, through NMS usage. 3.4.8.7 Multi-Tasking

technology and as new

refreshments displays are

Sessions be capable NMS system of supporting requirements.

simultaneous 3.4.9

Each NMS workstation shall sessions to perform all NMS Workstation

Communications have the capability associated with the to ATC.

communicate 3.5 3.5.1

The NMS workstation shall with other workstations Factors

Quality

Availability The demonstrated percent or greater. Reliability availability of the ATC shall be

99.998 3.5.2

The ATC shall meet the reliability standards set forth in CCITT Recommendation G.106, Paragraph 2.5 and shall function continuously 24 hours per day. ATC reliability is defined in terms of critical system failure. A critical system failure is defined as those failures which deny user access to information, computations, reports generation, or other functions that could adversely affect mission accomplishment. The following specific failures are applicable: (a) A loss ports at any one time of 5% or more of system

(b) (c) (d) (e) (f)
ATC

A loss

of the

system

controller due to software

A failure A failure A loss A loss

of the of

system

a workstation system system clock power.

of internal of internal

Interoperability with a variety of DTE, Specific equipment and

crypto

The ATC shall be interoperable devices, and test equipments.

PAGE

50

Case 1:02-cv-00796-FMA

Document 46-5

Filed 03/18/2005

Page 22 of 22

NAVAL

REGIONAL

CONTRACTING

CENTER

WASHINGTON for candidate

N00600-94-C-0389 sites are

corresponding interface requirements found in Appendices A through G. 3.5.4 ATC System Recovery

Following an ATC system failure, one of the two following types of system restarts shall be provided. A "cold" start shall be required when all queues and temporary files are empty and all initializing data must be re-entered. The time required to perform a "cold" start shall not exceed five minutes. A "warm" start shall be required when an error has occurred which has caused minimal system degradation. The time required to perform a "warm" start shall not exceed five minutes. 3.5.5 ATC Diagnostic Tests

Diagnostic and Built-in-Test (BIT) programs shall provide isolation to a Lowest Replaceable Unit (LRU). Test programs shall be available prior to program loading and during operations to verify system malfunctions or to check the operational status of a specific system component or program. 3.5.6 Safety

The ATC shall comply with the Occupational Safety and Health Administration (OSHA) and Navy Occupational Safety and Health (NOSH) safety requirements established by the Government for industry. 3.6 3.6.1 Logistics Maintenance Support shall provide maintenance for all system hardware, support firmware, for the and

The vendor life of the contract software.

3.6.1.1

Technology

Refreshment

The design of the ATC NMS shall permit incorporation of future technology refreshments, as they occur. Updates to equipment hardware, firmware, and software shall be made available for implementation throughout the ATC life cycle and shall be installed at the option of the Government. Examples of

PAGE

51