A3384650_PMC_Spec_Gen_II_draft_2022-11-18.docx

07 AUGUST 2012 FOR OFFICIAL USE ONLY A3335407

Requirements Specification for the Protected Anti-Scintillation / Anti-Jam Wideband Net-Centric System (PAAWNS) Management Component (PMC) Generation II

Specification Number A3384650

Version 2.0, DRAFT 18 November 2022

EXPORT CONTROLLED - ITAR

THIS ITEM CONTAINS TECHNICAL DATA CONTROLLED BY THE DEPARTMENT OF STATE, INTERNATIONAL TRAFFIC IN ARMS REGULATIONS (ITAR), 22 CFR, PARTS 120-130, AND CANNOT BE EXPORTED FROM THE UNITED STATES OR SHARED WITH A FOREIGN PERSON WITHOUT PRIOR APPROVAL FROM THE U.S. DEPARTMENT OF STATE.

Prepared for:

United States Army Project Manager Defense Communications and Army Transmission Systems (PM-DCATS) Ft Belvoir, VA 22060

Document Version History

· Added additional required sections

· Marked sections and paragraphs with classification

· Editing changes

· Incorporated September 2011 PAAWNS Program Management Review (PMR) comments

TABLE OF CONTENTS

1 (U) Scope

1.1 (U) PAAWNS Mission (U//FOUO) The Protected Anti-Scintillation/Anti-Jam Wideband Net-Centric System (PAAWNS) mission will be to provide survivable satellite communications (SATCOM) in the presence of nuclear scintillation caused by a High Altitude Nuclear Explosion (HANE), jamming, or a combination of both. PAAWNS equipment will be installed at key SATCOM nodes worldwide and interconnected to provide both protected user communications and network management communications. The PAAWNS Management Component (PMC) will provide the network management function for PAAWNS.

1.2 (U) Requirements Content (U//FOUO) This specification establishes the threshold component level functional and performance requirements for the PMC of the PAAWNS. The Gen I threshold requirements are defined in the PAAWNS Threshold Requirements Agreement (Reference 1) between the Missile Defense Agency (MDA) and the Project Manager Defense Communications and Army Transmission Systems (PM-DCATS).

1.3 (U) Specification Tree

(U) This specification (A3384650) is a second-tier document below the top-level PAAWNS system specification (Reference 14) as illustrated in Figure 11: (U) Specification Tree below.

Figure 11: (U) Specification Tree

1.4 PMC Overview

(U) The PMC will be implemented to provide situational awareness and control of the PAAWNS network. The PMC will support the provisioning and reconfiguration of the network as necessary to accommodate changing mission requirements and operating environments. When jamming and/or scintillation conditions occur or are anticipated to occur, the PMC would be utilized to make coordinated link state configuration changes in the Gen II modems and thus ensure network survivability and communications continuity.

(U) The overall PMC system will consist of individual PMC nodes connected via the PAAWNS management network. The PAAWNS management network will consist of local and wide area network segments. The wide area segments are called Management Transport Circuits (MTCs). MTCs may be provided via both SATCOM and terrestrial links for path diversity. Management data, including configuration commands and status information, will be transmitted between PMC nodes over an MTC and will be considered Sensitive but Unclassified (SBU). The PAAWNS management network should not be confused with the PAAWNS mission network which carries the actual user traffic. These two networks are logically separate although they may physically overlap and share layer 1 and layer 2 resources (e.g., they both may utilize the Gen II modems for transport).

(U) A PMC node will appear in one of two configurations, depending upon its physical location.

a. (U) A SATCOM Site PAAWNS Gen II Node will be situated at a SATCOM site. This node will combine the functionality of the Gen II modems and the SATCOM PMC functionality (PMC-S). This node will consist of PMC-S server resources required to provide the PMC’s functionality at the required availability. The PMC-S node will also interface with MTCs to reach other Management Site PMC (PMC-M) node(s).

b. (U) A PMC-M node will be situated at a PAAWNS management site. This node will consist of server and storage resources required to provide the PMC’s functionality at the required availability suitable for a management site that oversees an entire PAAWNS network.

(U) Each PMC node may assume one of two management roles. Future versions of the PMC may allow additional flexibility in assigning roles to PMC nodes. Management roles and associated functions are loosely aligned with the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T) Recommendations M.3010, Principles for a telecommunications management network (TMN), and M.3400, TMN management functions (References 14 and 15, respectively). M.3010 section 9.5 describes layers of a management system beginning with element management and network management. The PMC roles will address these two layers; service and business management layers are expected to be the fulfilled within the realm of the PAAWNS end user’s management systems. M.3400 addresses the management functions to be performed within each layer. These include fault, configuration, accounting, performance, and security management, which are more commonly referred to as the “FCAPS” model. The FCAPS model is tailored for use by the PMC. For example, accounting management is relevant to a service provider billing function which is not a PAAWNS requirement.

a. (U) The PAAWNS element management role includes monitoring and control of the Gen II Rack Type 150 (RT150) and its associated elements. The PMC-S will be embedded within the RT150, and unlike a Gen I PMC-S, the Gen II PMC-S will only monitor a single rack of equipment.

(U//FOUO) PMC workstations will be provided with each PMC node for local operators to access the PMC applications. These PMC workstations are expected to be situated in the operator console area of the facility and will be connected via local area network to the PMC nodes. It will also be feasible to implement a PMC workstation at a remote location (e.g., for situational awareness at that remote location) at a PMC-M node. In this case, the PMC workstation would be extended from a PMC node via a layer 2 transport service (e.g., such as the DISN).

2 (U) Applicable Documents

(U) The following documents of the exact issue shown or of the latest version form a part of this document to the extent specified herein. In the event of conflict between the referenced documents and the contents of this document, the contents of this document shall be considered a superseding requirement.

2.1 Government Documents

2.2 Non-Government Documents

Management Network (TMN) management functions, 02/2000

3 (U) Requirements

(U) Allocation of requirements to threshold is made in the Verification Cross Reference Matrix (VCRM) in Section 5 of this document.

3.1 (U) Hierarchical Distributed Management

a. (U) The PMC shall [PMC-01000] be structured as a hierarchical system with at least two levels. These levels consist of PMC nodes at the element manager level and a single primary PMC node at the network manager level. A backup PMC network manager node (COOP Node) may be provided in case of failure of the primary network manager node.

3.2 (U) Scope of PMC Node Responsibility

3.2.1 (U) SATCOM Site

a. (U) The responsibility of a PMC-S node in the element manager role shall [PMC-02010] be element management of a single Gen II rack, including Gen II modems and the PMC-S elements.

a. Note: The Gen II PMC-S will not interface with a Gen I PMC-S or the Gen I AS/AJ modem.

b. (U) The PMC-S node’s scope of responsibility shall [PMC-02020] be configurable by a PMC operator. This feature would be used, for example, during initial installation.

3.2.2 (U) Management Site Comment by Brian C. Gallagher: Management site is also responsible for maintaining the system IA posture and forwarding files as necessary for monitoring. Comment by Stephanie Gronewoller: Added €

a. (U) The responsibility of a PMC-M node shall [PMC-02030] include receiving summary status, events, and alarms from PMC-S nodes (element managers).

a. Note: The Gen II PMC-M will not interface with a Gen I PMC-S.

b. (U) The responsibility of a PMC-M node shall [PMC-02060] include exercising control over PMC-S nodes and their associated elements.

c. (U) The responsibility of a PMC-M node shall [PMC-02040] also include monitor and control of the elements of the PMC-M node itself.

d. (U) The PMC-M node’s scope of responsibility shall [PMC-02050] be configurable by a PMC operator.

e. (U) The responsibility of a PMC-M node shall [PMC-02070] include maintaining the system Information Assurance (IA) posture and forwarding files as necessary for monitoring. Comment by Stephanie Gronewoller: FIND REQUIREMENT NUMBER

3.3 (U) FCAPS Management PMC requirements for fault, configuration, performance, and security management are specified in the following four subsections. Management applies to monitor and control of PAAWNS elements included in Gen II racks. The term elements encompasses modems, switches where required based on network implementation, any external timing sources, PMC servers and PMC workstations, clients or laptops.

The PMC shall not control any EBEM modems installed in the rack. EBEMs will be controlled via their nominal control software from a laptop external to the Gen II rack.

3.3.1 (U) Fault Management (Monitoring)

3.3.1.1 (U) Element Monitoring

a. (U) The PMC shall [PMC-03010] provide a fault monitoring and reporting capability for PAAWNS elements within its scope of responsibility.

b. (U) The PMC fault monitoring capability shall [PMC-03020] include polling of PAAWNS elements within the PMC’s scope of responsibility.

c. (U) The PMC polling rate shall [PMC-03030] be configurable.

d. (U) The PMC fault monitoring capability shall [PMC-03040] include the ability to receive and process autonomously-generated reports from the PAAWNS elements within the PMC’s scope of responsibility. Examples of autonomously-generated reports include built-in test results, and self-test results.

e. (U) The PMC operator interface shall [PMC-03050] provide visible and audible alarms when critical events or failures are detected within the PMC node’s scope of responsibility.

f. (U) The PMC visible and audible alarms shall [PMC-03060] require PMC operator acknowledgement to be cleared and muted.

g. (U) The PMC fault monitoring capability shall [PMC-03061] include the ability to generate conditions that are derived from one or more faults.

3.3.1.2 (U) Network Manager Interaction

a. (U) PMC-S nodes shall [PMC-03070] report all fault and failure events to the PMC-M node.

b. (U) PMC-M node shall [PMC-03081] generate conditions derived from faults reported by PMC-S nodes.

3.3.2 (U) Configuration Management (Control)

3.3.2.1 (U) Element Control

a. (U) The PMC shall [PMC-03100] provide a configuration management capability for PAAWNS elements within the PMC’s scope of responsibility.

b. (U) The PMC configuration management capability shall [PMC-03110] be capable of controlling PAAWNS elements within the PMC’s scope of responsibility. Control of an element is defined as the ability to set and change parameters of that element’s configuration and to place the element in either online or offline state.

c. (U) The PMC configuration management capability shall [PMC-03120] be capable of setting the initial configuration of an element at boot time or post boot-time. This may include, for example, choosing one of several system images to boot. This feature will be dependent on specific element capabilities.

d. (U) The PMC-M node’s configuration management capability shall [PMC-03130] be capable of storing configuration command sequences. An example configuration command sequence may be a series of modem reconfigurations required to switch from one state to another (e.g., modify multi-carrier modem links).

e. (U) The PMC configuration management capability shall [PMC-03140] be capable of using the Gen II modem’s capability to schedule configuration changes to effect seamless state changes across multiple modems including multiple links per modem.

f. (U) The PMC configuration management capability shall [PMC-03150] be capable of setting a consistent Network Time Reference (NTR) carrier and NTR devolution order for the Gen II modems in a PAAWNS network. This capability may include auto-correct across the network.

g. (U) The PMC configuration management capability shall [PMC-03160] be capable of supporting the transfer of unclassified key material to the Gen II modem. Examples of Gen I key material include black Transmission Security Keys (TSK) and black Transmission Encryption Keys (TEK).

h. (U) The PMC shall [PMC-03180] provide a means of specifying and displaying priorities for each modem link in the PAAWNS mission network or the PAAWNS management network. The intention is that the use of priority will aid in focusing troubleshooting efforts.

i. (U) The PMC operator interface shall [PMC-03190] provide a capability for ensuring control of a given element by only one PMC operator at a time.

j. (U) The PMC operator interface shall [PMC-03210] provide a capability for ensuring exclusive control of a given modem by only one PMC operator at a time.

k. (U) The PMC exclusive-control capability shall [PMC-03200] contain a priority mechanism allowing higher priority PMC operators to override lower priority PMC operators.

3.3.2.2 (U) Network Manager Interaction

a. (U) PMC nodes in the network manager role shall [PMC-03300] be capable of distributing element configurations to PMC nodes in the element manager role.

b. (U) PMC nodes in the network manager role shall [PMC-03310] be capable of distributing command sequences to PMC nodes in the element manager role in order to implement specific link state and parameter changes in the Gen II modems.

c. (U) PMC nodes in the network manager role shall [PMC-03320] be capable of distributing commands to change system and component operational states (e.g. online, offline, etc.) to PMC nodes in the element manager role.

d. (U) PMC nodes in the network manager role shall [PMC-03330] be capable of distributing unclassified key material for the Gen II modems to PMC nodes in the element manager role (nominally the SATCOM site).

e. (U) PMC nodes in the element manager role shall [PMC-03340] report to the PMC node in the network manager role whenever configuration changes are implemented (e.g., by an operator).

3.3.2.3 (U) Configuration Archival

a. (U) The PMC configuration management capability shall [PMC-03400] be capable of storing current and historical configurations of PAAWNS elements within the PMC’s scope of responsibility.

b. (U) The PMC configuration management capability shall [PMC-03410] be capable of storing system images of the PAAWNS elements. System images may include software and firmware required for a given element’s operation. Elements may be configured to obtain their system images from the PMC or the PMC may pre-load an element with a system image.

c. (U) The PMC configuration management capability shall [PMC-03420] automatically log the configuration of PAAWNS elements within the PMC’s scope of responsibility.

d. (U) The PMC periodicity of automatic element configuration logging shall [PMC-03430] be configurable.

e. (U) The PMC configuration management capability shall [PMC-03440] also allow operator-initiated logging the configuration of PAAWNS elements within the PMC’s scope of responsibility.

3.3.3 (U) Performance Management

a. (U) A PMC node shall [PMC-03500] provide a performance monitoring capability for PAAWNS elements and links that are within the PMC node’s scope of responsibility.

b. (U) PMC-S nodes shall [PMC-03510] report PAAWNS connection status to the PMC-M node at a configurable rate.

c. (U) PMC-M node shall [PMC-03520] report PAAWNS connection performance at a configurable rate.

d. (U) PMC-S nodes shall [PMC-03530] report PAAWNS element status to the PMC-M node at a configurable rate.

e. (U) PMC-S nodes shall [PMC-03540] analyze element status to report trending alerts and threshold crossing alerts to the PMCs in the network manager role at a configurable rate. For example, an alert could be triggered when the Eb/No value for a SATCOM carrier exceeds a specified min or max threshold.

f. (U) PMC-S nodes shall [PMC-03550] provide the ability to configure threshold or boundary values of individual status types for use in triggering alerts.

g. (U) PMC-M node shall [PMC-03560] report PAAWNS link status to the PMC-S nodes at a configurable rate.

h. (U) PMC-M node shall [PMC-03570] report PAAWNS link performance at a configurable rate.

3.3.4 (U) Security Management Comment by Brian C. Gallagher: Should include the two-factor authentication via the Yubikey tokens. Comment by Stephanie Gronewoller: Added (d)

a. (U) The PMC shall [PMC-03600] provide Single-Sign-On access control enabling the operator to sign on only once to both the operating system and the PMC application.

b. (U) The PMC GUI shall [PMC-03610] provide access and capabilities based on the operator’s privileges.

c. (U) The PMC operator privileges shall [PMC-03620] be configurable based on functional area and site.

d. (U) The PMC shall [PMC-03630] provide two-factor authentication for operators. Comment by Hom, Alexander L.: Add to VCRM

3.4 (U) PMC Interfaces

3.4.1 (U) PAAWNS Component Interfaces

a. (U) The PMC shall [PMC-04000] interface with the PAAWNS Gen II rack for communication via Management Transport Circuits (MTC) when provisioned over Gen II modems, or EBEMs.

b. (U) The PMC shall [PMC-04010] interface with the Gen II modem for monitor and control (M&C) purposes. Note: The PMC will only interface with Gen II modems located within its Gen II Rack Type 150.

c. (U) The PMC shall [PMC-04030] interface with the elements of the PMC itself for M&C purposes. Elements of the PMC include elements of the PAAWNS Management Network (PMN).

d. (U) M&C interfaces shall [PMC-04040] utilize the public modem interface protocol, which may be Simple Network Management Protocol (SNMP) version 3.

a. (U) Note: M&C interfaces may utilize other protocols as necessary to compliment SNMP-provided capabilities. Other protocols may include but are not limited to: Secure Shell (SSH), Internet Control Message Protocol (ICMP), System Log (SYSLOG), and Secure Copy (SCP).

3.4.2 (U) External Interfaces

a. (U) A PMC node shall [PMC-04100] be capable of accepting and executing configuration changes in the PAAWNS network through manual user input via the GUI. The configuration changes are expected to be communicated either verbally or in writing to PMC operators who then make the entries via the PMC GUI.

b. (U//FOUO) A PMC node shall [PMC-04110] be capable of importing network configuration data, for example via database backup and restore functionality.

c. (U//FOUO) The PMC node shall [PMC-04120] allow the import of black KEYMAT files as provided on CD from the authorized KEYMAT provider, for example the National Security Agency (NSA).

d. (U) Each PMC node shall [PMC-04130] include a CD/DVD reader/writer.

e. (U//FOUO) A PMC node shall [PMC-04140] be capable of interfacing with DISA provided layer 2 transport services for terrestrial MTC connectivity.

f. (U) PMC-M node shall [PMC-04150] include an interface to a highly accurate external timing source through a timing distribution unit such as an external Network Time Protocol (NTP) server or GPS devicethat provides IRIG-B000.

g. (U) PMC-M node shall [PMC-04160] provide a highly accurate timing reference to the PMC-S nodesall elements within the RT150.

3.5 (U) PMC Operator Interface

3.5.1 (U) SATCOM Site Operator Access

a. (U) Each PMC-S node shall [PMC-05010] provide an operator interface to the server element via an attached keyboard, video, and mouse (KVM).

b. (U) Each PMC-S node shall [PMC-05020] support one up to twoor more workstations connected via local area network (LAN) for use as operator interfaces running the PMC graphical user interface application. A workstation may consist of either a laptop, desktop, rack mount computer or client connection to a virtual machine. The LAN connection will be a segment of the PAAWNS Management Network. Although one or more workstations may be supported, the decision on how many to field may be made on a case-by-case basis. Comment by Brian C. Gallagher: This should remain as at least one or more, with the actual number fielded being made on a case-by-case basis. As written, this “shall” limits the total to one. Comment by Stephanie Gronewoller: Changed to one or more

3.5.2 (U) Management Site Operator Access

a. (U) Each PMC-M node shall [PMC-05030] provide an operator interface to the server element via an attached keyboard, video, and mouse (KVM).

b. (U) Each PMC-M node shall [PMC-05040] support up to one or moretwo workstations connected via local area network (LAN) for use as operator interfaces running the PMC graphical user interface application. A workstation may consist of either a laptop, desktop, or rack mount computer or client connection to a virtual machine. The LAN connection will be a segment of the PAAWNS Management Network. Comment by Brian C. Gallagher: Same as above, why are we limiting support to only one workstation? Comment by Stephanie Gronewoller: Changed to one or more Comment by Hom, Alexander L.: Changing to two as the upper limit. Main constraint is number of 9300 ports.

3.5.3 (U) Remote Site Operator Access

a. (U) The PMC architecture shall [PMC-05050] support the addition of at least one remote site workstation per PMC-M node. A workstation may consist of either a laptop, desktop, or rack mount computer (pending decision). The remote connection will be a segment of the PAAWNS Management Network and provisioned via a layer 2 transport service between the management site node and the remote site workstation. A remote site workstation may provide read-only access subject to the operations plan.

3.5.4 (U) PMC Application Graphical User Interface

a. (U) The PMC Graphical User Interface (GUI) shall [PMC-05140] enable the operator to access all FCAPS features as described in previous sections.

3.6 (U) Modularity

a. (U) PMC software shall [PMC-06010] be the same for PMC-M and PMC-S nodes.

b. (U) Specific roles (element or network management) of PMC nodes shall [PMC-06020] be configurable.

3.7 (U) Scalability

a. (U) A PMC node in the element manager role shall [PMC-07010] be capable of managing up to six (6) Gen II modems within a single PAAWNS Gen II SATCOM rack.

b. (U) A PMC node in the network manager role shall [PMC-07020] be capable of managing up to 144 Gen II modems distributed among any number of RT150s (via intermediate element manager nodes).

3.8 (U) Timing The Network Time Protocol (NTP) server derives its time from a stratum 1 clock (e.g., Global Positioning System (GPS) or DISA Timing Rack) where the PMC-M is deployed. Comment by Brian C. Gallagher: PMC-M Comment by Stephanie Gronewoller: Changed.

a. (U) Each PMC node shall [PMC-08010] slave its clock to an NTP server, such as a GPS source or a management node.

b. (U) Each PMC node shall [PMC-08020] be capable of acting as an NTP server to local elements.

c. (U) Each PMC node shall [PMC-08030] be capable of acting as an NTP server to local PAAWNS Management Network elements. Comment by Brian C. Gallagher: For Gen II, is this any different than PMC-08020? Comment by Stephanie Gronewoller: Seems to be the same. Should we remove (c)?

3.9 (U) Historical Data Storage

a. (U) The PMC shall [PMC-09010] provide a capability for online historical data storage. Online indicates the data is currently stored and accessible on the PMC server.

b. (U) PMC-S nodes shall [PMC-09020] retain content online for at least 45 days.

c. (U) PMC-M nodes shall [PMC-09030] retain content online for at least 90 days. This data may be aggregated or summarized, or it may be the full detailed data collected from each Gen II rack. Comment by Hom, Alexander L.: Propose updating this to 45 days. This is currently and has always been 45 days. This is configurable and supported in PMC but the potential limiting factor is storage space

d. (U) The PMC online historical data storage capability shall [PMC-09040] retain monitoring information.

e. (U) The PMC online historical data storage capability shall [PMC-09050] retain faults, alerts and events.

f. (U) The PMC online historical data storage capability shall [PMC-09060] retain configurations.

g. (U) The PMC online historical data storage capability shall [PMC-09070] retain reconfiguration events.

h. (U) The PMC shall [PMC-09080] provide the capability to display online historical data.

i. (U) The PMC shall [PMC-09090] provide a capability to copy online historical data to offline storage. Offline storage may utilize media such as a compact disc (CD) or digital video disc (DVD).

j. (U) The PMC shall [PMC-09100] provide the capability to display historical data that was previously copied to offline storage.

3.10 (U) PAAWNS Management Network

a. (U) PMC nodes shall [PMC-10010] communicate with each other, e.g., between SATCOM site and management site nodes, via the PAAWNS Management Network (PMN).

b. (U//FOUO) Data flow between PMC nodes shall [PMC-10020] use different classes of service in accordance with the criticality of the information to the MDA mission and the PAAWNS network conditions.

c. (U//FOUO) The PMC shall [PMC-10030] allow for configuration of at least two classes of data flow between PMCs: critical and non-critical. Critical data should be expected to be AS-protected which infers longer path delay. Non-critical data is explicitly not expected to receive AS-protection and thus will enjoy low path delay.

d. (U//FOUO) Critical information flow between two PMC nodes over a single satellite hop (i.e. earth-satellite-earth) shall [PMC-10040] be capable of operating over a full-duplex link with the following characteristics:

i. Link capacity for critical information flow shall be no less than 256 Kbps per Gen II rack being managed over the given link.

ii. Link propagation delay (one-way) for critical information flow shall be no more than 13 seconds.

iii. Link Bit Error Rate (BER) for critical information flow shall be no greater than 10-6.

e. (U//FOUO) Non-critical information flow between two PMCs nodes over a single satellite hop (i.e. earth-satellite-earth) shall [PMC-10050] be capable of operating over a full-duplex link with the following characteristics:

i. Link capacity for non-critical PMC information flow shall be no less than 4 2 Mbps per Gen II rack being managed over the given link. Comment by Brian C. Gallagher: Is this right? Why are we provisioning 2 Mbps for these circuits and an additional 2 Mbps to support the IA stuff? Comment by Hom, Alexander L.: Added clarification

ii. Link propagation delay (one-way) for non-critical information flow shall be no more than 1 second.

iii. Link Bit Error Rate (BER) for non-critical information flow shall be no greater than 10-8.

f. (U//FOUO) For critical information flow between PMC nodes, the end-to-end message delay shall [PMC-10060] be met at least 99% of the time. Maximum message delay time is equal to twice the path delay plus message serialization delay. Path delay includes PMC processing, propagation delay, modem processing time, modem jitter, and interleaver depth.

g. (U) The PAAWNS management network shall [PMC-10070] be capable of unicast routing.

h. (U) The PAAWNS management network routing shall [PMC-10090] re-converge after link loss (RF or terrestrial).

3.11 (U) Information Assurance (IA)

(U) The PMC shall [PMC-11010] be designed to be capable of RMF Authorization to Operate (ATO) certification at the Mission Assurance Category (MAC) 1, Sensitive but Unclassified (SBU) level. This certification will be maintained via periodic IA patches to the PMC.

(U) The Approving Officer (AO) will levy Information Assurance (IA) requirements on the system. The following requirements may be modified at the discretion or the AO, WESS, and/or MDA:

a. (U) The PMC shall [PMC-11020] implement active log monitoring.

b. (U) The PMC shall [PMC-11030] implement active scanning.

c. (U) The PMC shall [PMC-11040] implement two factor authentication.

d. (U) The PMC shall [PMC-11050] interface to an existing active monitoring server on an approved Tier 2 network.

e. (U) The PMC shall [PMC-11060] roll up all IA monitoring capabilities to an approved Tier 2 network.

f. (U) The PMC shall [PMC-11070] provide Information Assurance Care Packages (IACPs) at a periodic interval.

g. (U) The PMC shall [PMC-11080] adhere to MDA software assurance policies, specifically Policy 16.

h. (U) The PMC shall [PMC-11090] implement and maintain Security Technical Implementation Guides (STIGs).

3.12 (U) Footprint and Environmental

3.12.1 (U) General

a. (U) PMC node equipment including servers, switches, and KVM shall [PMC-12010] be 19” rack-mountable. Operator workstations are not required to be rack mountable.

b. (U) The PMC shall [PMC-12020] be capable of operating within the ambient temperature range of 10°C to +35°C.

c. (U) The PMC shall [PMC-12030] be capable of operating within a maximum relative humidity range of 20% to 70%.

d. (U) The PMC shall [PMC-12040] be capable of operating at a maximum altitude of 10,000 feet above sea level. Note that increasing altitude may decrease the max operating temperature range.

3.12.2 (U) SATCOM Site Node

a. (U) For PMCs located at a SATCOM site, a PMC node’s physical size shall [PMC-12100] not exceed 15 40 rack units of height (7026.25”) and 26 inches depth. Comment by Brian C. Gallagher: Do we want to revisit these numbers for Gen II? Comment by Hom, Alexander L.: I believe 40 RU is the height of the rack

b. (U) For PMCs located at a SATCOM site, a PMC node’s weight shall [PMC-12110] not exceed 200 pounds.

c. (U) For PMCs located at a SATCOM site, a PMC node’s power shall [PMC-10120] not exceed 1000W.

3.12.3 (U) Management Site Node

a. (U) For PMCs located at a Management site, a PMC node’s physical size shall [PMC-12200] not exceed 20 40 rack units of height (3570”) and 30 inches depth. Comment by Brian C. Gallagher: Do we want to revisit these numbers for Gen II?

b. (U) For PMCs located at a Management site, a PMC node’s weight shall [PMC-12210] not exceed 250 pounds.

c. (U) For PMCs located at a Management site, a PMC node’s power shall [PMC-12220] not exceed 1500W.

3.12.4 (U) Workstation

a. (U) PMC workstation physical size shall [PMC-12300] not exceed 24 inches of height, 36 inches of width, and 24 inches depth. This is intended to accommodate a desktop computer with dual screens.

b. (U) PMC workstation weight shall [PMC-12310] not exceed 50 pounds.

c. (U) PMC workstation power shall [PMC-12320] not exceed 500W.

3.13 (U//FOUO) Availability, Reliability, and Maintainability

a. (U//FOUO) A PMC node availability shall [PMC-13010] be 99.99% or greater. Availability is defined as inherent availability, Ai.

b. (U//FOUO) A PMC node mean time between critical failures (MTCBF) shall [PMC-13020] be 50,000 hours or greater. The MTCBF is a measure of system reliability that includes the effects of any fault tolerance (redundancy) which may exist. Failures of backup equipment or failures of on-line equipment that are corrected by switchover to the corresponding backup equipment within the time limit given within the associated component performance specification are not considered critical failures.

c. (U//FOUO) A PMC node shall [PMC-13030] meet the Mean Time To Repair (MTTR) requirement of 30 minutes or less at the organizational level of maintenance.

d. (U//FOUO) The maximum time to repair (Mmax) for corrective maintenance at the organizational level, 95th percentile of the repair time distribution, shall [PMC-13035] not exceed two (2) hours.

e. (U//FOUO) The backup PMC-M node shall be capable of assuming the management site role for the PAAWNS network in the event of primary PMC-M failure. [PMC-13040]

f. (U//FOUO) ) The backup PMC-M node shall assume the management site role for the PAAWNS network within TBD hours upon detection of primary PMC-failure. [PMC-13050] Comment by Brianna Poulos: How many? Comment by Brian C. Gallagher: What is the absolute best we can do? It will probably never be as quick as they want it.

Repair time is defined as the total of the times required for fault location, fault isolation, equipment disassembly, element interchange, equipment reassembly, software installation and configuration, alignment, and check out. Repair time does not include administrative time, logistic time, time required to transit between equipment locations, or preventative maintenance time expended while the mission critical equipment is in operation.

Maintainability Notes:

a) MTTR and Mmax values were agreed upon prior to PMC engineering analysis, which later showed they may not be practical. Design will proceed with a "best effort" approach, with the explicit priority of delivering adequate Ai & MTBCF.

b) It may be necessary to fall back on higher repair times, such as MTTR = 2 hours and Mmax = 8 hours, to maintain PMC schedule. These are relevant to "PMC schedule risk" under formal risk management.

c) Overall system MTTR and Mmax numbers will be reported to MDA once finalized.

d) This is based on direction indicated via A3338198 "PAAWNS Threshold Requirements Agreement," Action Item 36, as well as general direction received at the PAAWNS PMR held 11 SEP 2012.

g. (U) The PAAWNS mission network shall [PMC-13040] continue to operate in the event of a failure or reconfiguration of any PMC node.

3.14 (U) Maintenance & Logistics

a. (U) The PMC software shall [PMC-14010] be field-upgradeable with no loss of PAAWNS mission network capability during upgrade.

b. (U) The PMC hardware shall [PMC-14020] be field-upgradeable during scheduled maintenance windows.

c. (U) An electronic user manual shall [PMC-14040] be provided for the PMC. This will address PMC operation and administration at the system level. Additional materials may be provided for individual COTS equipment.

d. (U) An electronic maintenance manual shall [PMC-14050] be provided for the PMC. This will address PMC hardware maintenance activities. Additional materials may be provided for individual COTS equipment.

e. (U) Logistics for the PMC shall [PMC-14060] be based on a life-cycle support concept which includes on-site maintenance and off-site maintenance. On-site maintenance shall [PMC-14070] consist of all maintenance to be performed by military personnel having the Military Occupational Specialty (MOS) 25S or other service equivalent or by civilian personnel possessing the same knowledge, skills and experience. Off-site maintenance shall [PMC-14080] include all of the functions required to sustain the PMC to meet the required availability, to include maintenance, supply support, training, documentation, and configuration management.

3.15 (U) Self-Test and Self-Monitoring

a. (U) The PMC shall [PMC-15010] monitor all online elements comprising the PMC during operation for both hardware and software anomalies.

b. (U) The PMC shall [PMC-15020] provide an offline self-test for diagnostic purposes.

c. (U) The PMC shall [PMC-15030] provide diagnostic functions for custom PMC software. These diagnostic functions shall not require the use of external equipment.

d. (U) The fault detection and diagnostic capability shall [PMC-15040] identify all critical faults to a single Line Replaceable Unit (LRU) with a 95 percent probability. For guidance, the following LRU’s are anticipated:

· Server (main unit)

· Server power supply (if hot-swappable)

· Server fan (if hot-swappable)

· Layer 3 switch (main unit)

· Layer 3 switch power supply (if hot-swappable)

· Layer 3 switch fan (if hot-swappable)

· KVM (integrated keyboard, mouse, video monitor, and switch)

· NAS (network-attached storage)

· Layer 2 switch (main unit)

· Layer 2 switch power supply (if hot-swappable)

· Layer 2 switch fan (if hot-swappable)

e. (U) All PMC LRUs shall [PMC-15050] be replaceable so that the operation of the user traffic is not disrupted.

f. (U) The PMC shall [PMC-15060] allow the operator to mute built-in-test (BIT) generated alarms while performing diagnostic and repair functions.

3.16 (U) Safety

a. (U) The PAAWNS equipment shall [PMC-16010] be designed so that under all conditions specified herein (installation, de installation, operation, and maintenance) and under a likely fault condition (including human error), it protects against the risk of electric shock and other hazards.

b. (U) All hazards shall [PMC-16020] be eliminated or reduced to the lowest risk level practical using methods in the following order of precedence: design; incorporation of safety devices; incorporation of warning devices; warnings in user manuals and training.

c. (U) Catastrophic and critical hazards (as defined in the Performance Work Statement (PWS)) shall [PMC-16030] not rely solely on warnings, cautions, or procedures/training for control of risk.

3.16.1 (U) Electrical Safety

(U) All equipment shall [PMC-16100] meet the following electrical safety standards:

a. (U) Equipment shall [PMC-16110] meet the applicable requirements of the NFPA-70.

b. (U) Where COTS equipment is used, the contractor shall [PMC-16120] select equipment that has been listed or certified by a Nationally Recognized Test Laboratory such as Underwriters Laboratories, Inc. (UL).

c. (U) Operators shall [PMC-16150] not be exposed to stored energy shock at the disconnecting means in accordance with (IAW) UL 60950-1, Paragraph 2.1.1.7.

d. (U) Protection shall [PMC-16160] be provided to personnel during installation, de-installation, operation and maintenance and repair to prevent unintentional contact with voltages exceeding 30V.

e. (U) Current sources exceeding 25 amperes shall [PMC-16170] be protected from accidental short-circuiting.

f. (U) Capacitors shall [PMC-16180] be discharged to less than 30 V and 20 Joules of energy prior to maintainer access.

g. (U) Voltage measurements required by maintainers shall [PMC-16190] not exceed 300 V.

h. (U) Circuits and components exceeding 500 V shall [PMC-16200] be completely enclosed and interlocked.

i. (U) Interlocks for circuits exceeding 500 V shall [PMC-16210] not be by-passable.

j. (U) Interlocks shall [PMC-16220] comply with UL 60950-1, Section 2.8.

k. (U) Interface with power sources and disconnecting means shall [PMC-16230] be IAW NFPA-70, and UL 60950-1, Section 3.4.

l. (U) Equipment grounding shall [PMC-16240] comply with the requirements of UL 60950-1, Paragraph 1.6.4, and Section 2.6.

m. (U) Hinges and slides shall [PMC-16250] not be relied upon as the sole means of grounding.

n. (U) Equipment leakage current to ground shall [PMC-16260] not exceed 3.5 mA when tested IAW UL 60950-1, Paragraphs 5.1.2 through 5.1.7.

o. Redundant equipment grounding conductors shall [PMC-16270] be required where currents exceed 3.5 mA and shall [PMC-16280] require Government approval.

p. (U) Wiring shall [PMC-16290] comply with the requirements of UL 60950-1, Paragraphs 3.1.1 through 3.1.3.

q. (U) AC supply conductors shall [PMC-16300] be color-coded black and white for line and neutral conductors, respectively.

r. (U) Grounding conductors shall [PMC-16310] be color-coded green or green and yellow.

s. (U) DC supply conductors shall [PMC-16320] be color-coded red and black for plus and minus polarity, respectively.

t. (U) Connector selection and design shall [PMC-16330] comply with or exceed the requirements of UL 60950-1, Paragraph 3.2.1, and 4.3.5.

u. Connectors shall [PMC-16340] include provisions for strain relief.

3.16.2 (U) Mechanical Safety

(U) All equipment shall [PMC-16400] meet the following mechanical safety standards:

1. (U) The equipment shall [PMC-16410] provide maximum access and safety to personnel during installation, operation, and maintenance.

1. (U) Equipment shall [PMC-16420] be able to be removed, handled, and lifted safely. Single person lift limits for equipment are as specified in Table 3-1 below.

Table 31: Lifting Limits

1. (U) Equipment exceeding single person lift limits shall [PMC-16430] be labeled with the total weight and required number of handlers. The values are doubled for two person lift limits (uniformly distributed equipment) with 75% added thereafter per person.

1. (U) Provisions shall [PMC-16440] be made to prevent accidental pulling out of drawers or rack mounted equipment.

1. (U) Latches used to safely secure doors, drawers, etc., in an open or closed position, shall [PMC-16450] be reliable and accessible.

1. (U) Operator accessible parts shall [PMC-16460] comply with the temperature limits shown in UL 60950-1, Paragraph 4.5.1.

1. (U) Equipment enclosures, as well as lenses, switches, wiring, and other items which enclose hazardous voltages, shall [PMC-16470] have adequate mechanical strength to withstand rough handling during expected use without breakage or deformation that would expose personnel to the enclosed hazardous voltages.

1. (U) Equipment power switches shall [PMC-16480] be protected so as to prevent accidental actuation and deactivation.

1. (U) Equipment shall [PMC-16490] comply with the mechanical stability and mechanical hazard requirements of UL 60950-1, Sections 4.1 and 4.2.

3.16.3 (U) Safety Markings and Labels

(U) All PAAWNS equipment shall [PMC-16500] meet the following safety marking and labeling standards:

1. (U) Safety markings and labels shall [PMC-16510] be provided identifying any potential hazards to personnel.

1. (U) Radio Frequency (RF) radiation hazards and voltages in excess of 30V shall [PMC-16520] use the signal word “WARNING.”

1. (U) Voltages in excess of 500 V shall [PMC-16530] use the signal word “DANGER.”

1. (U) Safety markings…