DRAFT_BAT_Performance_Specification _dated_8_Mar__16 _Rev_9.pdf

PD15WNAEBAT

DRAFT BAT System Performance Specification, 03/08/16, Rev 9

Page i of viii

DRAFT Bomber Armament Tester (BAT) System Performance Specification

03/08/16, Rev 9

DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.

(78 ABW/PA Certificate Number 15-05272).

Page ii of viii

1.0 SCOPE

1.1 SCOPE

1.1.1 Requirement Levels

1.1.2 Bomber Armament Tester Synopsis

1.2 UNIT UNDER TEST

1.2.1 B-2A Armament System Units Under Tests

1.2.2 B-1B Armament System Units Under Tests

1.2.3 B-52H Armament System Units Under Tests

2.0 APPLICABLE DOCUMENTS

2.1 GENERAL

2.2 GOVERNMENT DOCUMENTS

2.2.1 Specifications, Standards, and Handbooks

2.2.1.1 Military Standards

2.2.1.2 Military Specifications

2.2.1.3 Military Handbooks

2.2.2 Other Government Documents, Drawings, and Publications

2.3 OTHER DOCUMENTS

2.4 ORDER OF PRECEDENCE

3.0 REQUIREMENTS

3.1 GENERAL BOMBER ARMAMENT TESTER SYSTEM REQUIREMENTS

3.1.1 General System Design

3.1.2 Applicability

3.1.3 Modular Open System Architecture

3.1.4 Reserved

3.1.5 Markings

3.1.6 Identification Plate

3.1.7 Workmanship

3.1.8 Foreign Object Damage Prevention

3.1.9 Enclosures

3.1.10 Color

3.1.11 Cable Design

3.1.11.1 Connector Selection

3.1.11.2 Connector Finish

3.1.11.3 Connector Keying

3.1.11.4 Wire Shields

3.1.11.5 Shield Insulation

3.1.11.6 Shield Bonding

3.1.11.7 Safety Ground Conductor

3.1.11.8 Cable Crosstalk Mitigation

3.1.11.9 Protective Caps

3.1.11.10 Connector Positioning

3.1.11.11 Connector Population

3.1.12 Power

Page iii of viii

3.1.12.1 Operating Power

3.1.12.2 Master Power Switch

3.1.12.3 Power Cable Length

3.1.12.4 Unit Under Test Power

3.1.12.5 Power Consumption

3.1.12.6 Circuit Breakers

3.1.12.7 Power Monitoring

3.1.13 Grounding

3.1.13.1 Controlled Grounding Concept

3.1.13.2 Shock Protection

3.1.13.3 Ground Loop Prevention

3.1.13.4 External Safety Ground

3.1.14 Graphical Display

3.1.14.1 Graphical Display Size

3.1.14.2 Graphical Display Readability

3.1.14.3 Graphical User Interface

3.1.14.4 User Navigation

3.1.15 Human Factors

3.1.15.1 Operability with Chemical Warfare Gear

3.1.15.2 Transportability

3.1.15.3 Edges and Corners

3.1.15.4 Moving Parts

3.1.16 Environmental

3.1.16.1 Solar Radiation

3.1.16.2 Electromagnetic Interference

3.1.16.3 Explosive Atmosphere

3.1.16.4 Altitude

3.1.16.5 Drip Proof

3.1.16.6 Acoustic Noise

3.1.16.7 Corrosion Prevention

3.1.17 Nuclear Certification

3.1.17.1 System Safety

3.1.17.2 Single Failures

3.1.17.3 Dual Failures

3.1.17.4 Design Safety – Critical Functions

3.1.17.5 Design Safety – Internal Faults

3.1.17.6 Design Safety – Unintended Signals

3.1.17.7 Design Safety – Unintended Firing

3.1.17.8 Test Safety – End of Test

3.1.18 Test Safety – System Failures

3.1.19 Electromagnetic Environmental Effects Requirements

3.1.20 Cyber Security

3.1.20.1 User Auditing

3.1.20.2 Software Non-Repudiation

3.1.20.3 Endpoint Security

3.1.20.4 System Administration

Page iv of viii

3.1.20.5 Configuration Auditing

3.1.20.6 Malware Alerting

3.1.20.7 Wireless Network

3.1.20.8 Data at Rest Encryption

3.1.20.9 System Recovery

3.1.21 BAT Core Tester Self-Test/Built-In Test

3.1.21.1 Power-On Confidence Test

3.1.21.2 Self-Test

3.1.21.3 Self-Test Data

3.1.21.4 Self-Test Fault Detection

3.1.21.5 Self-Test Execution Time

3.1.21.6 Self-Test Fault Isolation Rate – 1 Component

3.1.21.7 Self-Test Fault Isolation Rate – 2 Components

3.1.21.8 Self-Test Fault Isolation Rate – 3 Components

3.2 SYSTEM CAPABILITY

3.2.1 Modular Open System Architecture (MOSA)

3.2.1.1 Open System Architecture Design

3.2.1.2 Test Program Set Software Architecture

3.2.1.3 Operating System Architecture

3.2.1.4 Test Executive Software Architecture

3.2.1.5 Memory Capacity

3.2.1.6 Memory Usage

3.2.1.7 Processor Usage

3.2.2 Suitability Requirements

3.2.2.1 Maintainability

3.2.2.2 Reliability

3.3 TEST PROGRAM SET REQUIREMENTS

3.3.1 Unit Under Test Data Log

3.3.2 Real Time Display of Test Results and Status

3.3.3 End of Test Report

3.3.4 Safe-To-Turn-On Test

3.3.5 Test Sequencing

3.3.6 Test Termination

3.3.7 Test Entry Points

3.3.8 Manual Test Sequencing

3.3.9 Test Control Selection

3.3.10 Test Data Transfer

3.3.11 Clearing Test Data

3.3.12 Pre-Test External Cable Identification Cable and Cable Testing

3.3.13 Stray Voltage Test

3.3.14 Unit Under Test Fault Detection

3.3.15 Unit Under Test Cooling

3.3.16 Interface Test Adapters

3.4 AIRCRAFT UNIQUE REQUIREMENTS

3.4.1 B-2A Unique Requirements

3.4.1.1 Rotary Launcher Assembly Tests

Page v of viii

3.4.1.2 Rotary Launch Assembly Line Replaceable Unit Bench Check

3.4.1.3 BRU-44 Operational Test Standalone Backshop

3.4.1.4 Smart Bomb Rack Assembly (SBRA) Test Backshop

3.4.1.5 BRU-52 Operational Test Backshop

3.4.1.6 Smart Bomb Rack Controller Test Backshop

3.4.1.7 Monitor and Control Equipment and BRU-72 Carriage and Release

Equipment Test

3.4.1.8 Stores Management System Test On Aircraft Only

3.4.2 B-1B Unique Requirements

3.4.2.1 B-1B Weapon Carriage Systems

3.4.2.2 B-1B Aircraft Weapons Delivery System

3.4.2.3 Fault Isolate to a Line Replaceable Unit

3.4.2.4 14 Inch Ejector Rack Backshop Test

3.4.2.5 30 Inch Ejector Rack Backshop Test

3.4.2.6 MAU-12 Ejector Rack Backshop Test

3.4.3 B-52H Unique Requirements

3.4.3.1 Conventional Rotary Launcher Test

3.4.3.2 Wiring Tests

3.4.3.3 Backshop Tests

3.4.3.4 MAU-12 Ejector Rack Backshop Test

3.4.3.5 B-52H Unique Testing Times

4.0 VERIFICATION

4.1 GENERAL INFORMATION

4.1.1 Responsibility for Verification

4.1.2 Verification Methods

4.1.3 Design Verification

4.2 VERIFICATION OF GENERAL SYSTEM REQUIREMENTS

4.2.1 Verification of General System Design

4.2.2 Verification of Applicability

4.2.3 Verification of Modular Open System Architecture

4.2.4 Verification of Markings

4.2.5 Verification of Identification Plate

4.2.6 Verification of Workmanship

4.2.7 Verification of Foreign Object Damage Prevention

4.2.8 Verification of Enclosures

4.2.9 Verification of Color

4.2.10 Verification of Cable Design

4.2.10.1 Verification of Connector Selection

4.2.10.2 Verification of Connector Finish

4.2.10.3 Verification of Connector Keying

4.2.10.4 Verification of Wire Shields

4.2.10.5 Verification of Shield Insulation

4.2.10.6 Verification of Shield Bonding

4.2.10.7 Verification of Safety Ground Conductor

4.2.10.8 Verification of Cable Crosstalk Mitigation

4.2.10.9 Verification of Protective Caps

Page vi of viii

4.2.10.10 Verification of Connector Positioning

4.2.10.11 Verification of Connector Population

4.2.11 Verification of Power

4.2.11.1 Verification of Operating Power

4.2.11.2 Verification of Master Power Switch

4.2.11.3 Verification of Power Cable Length

4.2.11.4 Verification of Unit Under Test Power

4.2.11.5 Verification of Power Consumption

4.2.11.6 Verification of Circuit Breakers

4.2.11.7 Verification of Power Monitoring

4.2.12 Verification of Grounding

4.2.12.1 Verification of Controlled Grounding Concept

4.2.12.2 Verification of Shock Protection

4.2.12.3 Verification of Ground Loop Prevention

4.2.12.4 Verification of External Safety Ground

4.2.13 Verification of Graphical Display

4.2.13.1 Verification of Graphical Display Size

4.2.13.2 Verification of Graphical Display Readability

4.2.13.3 Verification of Graphical User Interface

4.2.13.4 Verification of User Navigation

4.2.14 Verification of Human Factors

4.2.14.1 Verification of Operability with Chemical Warfare Gear

4.2.14.2 Transportability

4.2.14.3 Verification of Edges and Corners

4.2.14.4 Verification of Moving Parts

4.2.15 Verification of Environmental

4.2.15.1 Verification of Solar Radiation

4.2.15.2 Verification of Electromagnetic Interference

4.2.15.3 Verification of Explosive Atmosphere

4.2.15.4 Verification of Altitude

4.2.15.5 Verification of Drip Proof

4.2.15.6 Verification of Acoustic Noise

4.2.15.7 Verification of Corrosion Prevention

4.2.16 Verification of Nuclear Certification/System Safety

4.2.16.1 Verification of System Safety

4.2.16.2 Verification of Single Failures

4.2.16.3 Verification of Dual Failures

4.2.16.4 Verification of Design Safety – Critical Functions

4.2.16.5 Verification of Design Safety – Internal Faults

4.2.16.6 Verification of Design Safety – Unintended Signals

4.2.16.7 Verification of Design Safety – Unintended Firing

4.2.16.8 Verification of Test Safety – End of Test

4.2.17 Verification of Test Safety – System Failures

4.2.18 Verification of Electromagnetic Environmental Effects Requirements

4.2.19 Verification of Cyber security

4.2.19.1 Verification of User Auditing

Page vii of viii

4.2.19.2 Verification of Software Non-Repudiation

4.2.19.3 Verification of Endpoint Security

4.2.19.4 Verification of System Administration

4.2.19.5 Verification of Configuration Auditing

4.2.19.6 Verification of Malware Alerting

4.2.19.7 Verification of No Wireless Network

4.2.19.8 Verification of Data at Rest Encryption

4.2.19.9 Verification of System Recovery

4.2.20 Verification of Tester Self-Test/ Built In Test

4.2.20.1 Verification of Power-On Confidence Test

4.2.20.2 Verification of Self-Test

4.2.20.3 Verification of Self-Test Data

4.2.20.4 Verification of Self-Test Failure Detection

4.2.20.5 Verification of Self-Test Execution Time

4.2.20.6 Verification of Self-Test Fault Isolation Rate – 1 Component

4.2.20.7 Verification of Self-Test Fault Isolation Rate – 2 Components

4.2.20.8 Verification of Self-Test Fault Isolation Rate – 3 Components

4.3 SYSTEM CAPABILITY

4.3.1 Modular Open System Architecture

4.3.1.1 Verification of Open System Architecture Design

4.3.1.2 Verification of Test Program Set Software Architecture

4.3.1.3 Verification of Operating System Architecture

4.3.1.4 Verification of Test Executive Software Architecture

4.3.1.5 Verification of Memory Capacity

4.3.1.6 Verification of Memory Usage

4.3.1.7 Verification of Processor Usage

4.3.2 Verification of Suitability Requirements

4.3.2.1 Verification of Maintainability

4.3.2.2 Verification of Reliability Requirements

4.4 VERIFICATION OF TEST PROGRAM SET REQUIREMENTS

4.4.1 Verification of Unit Under Test Data Log

4.4.2 Verification of Real Time Display of Test Results and Status

4.4.3 Verification of End of Test Report

4.4.4 Verification of Safe-To-Turn-On Test

4.4.5 Verification of Test Sequencing

4.4.6 Verification of Test Termination

4.4.7 Verification of Test Entry Points

4.4.8 Verification of Manual Test Sequencing

4.4.9 Verification of Test Control Selection

4.4.10 Verification of Test Data Transfer

4.4.11 Verification of Clearing of Test Data

4.4.12 Verification of Pre-Test External Cable Identification

4.4.13 Verification of Stray Voltage Test

4.4.14 Verification of Unit Under Test Fault Detection

4.4.15 Verification of Unit Under Test Cooling Cart Interface

4.4.16 Verification of Interface Test Adapters

Page viii of viii

4.5 VERIFICATION OF AIRCRAFT UNIQUE REQUIREMENTS

4.5.1 Verification of B-2A Unique Requirements

4.5.2 Verification of B-1B Unique Requirements

4.5.3 Verification of B-52H Unique Requirements

5.0 PACKAGING

5.1 PACKAGING / HANDLING / STORAGE / TRANSPORTATION

6.0 ACRONYMS

APPENDIX A: UUT REFERENCE DOCUMENTS

APPENDIX B: KEY PERFORMANCE PARAMETERS

1.0 SCOPE

1.1 Scope

This specification establishes the performance requirements for the Bomber Armament Tester (BAT) System. This specification establishes the minimum performance parameters for the BAT System. This document describes the functional and interface characteristics of the BAT System and the verification required to demonstrate the achievement of those specified characteristics and performance parameters.

1.1.1 Requirement Levels

This specification lists two values for certain performance parameters. The threshold (T) is the minimum acceptable level. The objective (O) is the desired level at which performance of the BAT System results in an operationally significant increase in capabilities. When only one requirement value is stated, it is the threshold requirement. All Key Performance Parameters (KPPs) identified in Appendix B of this specification must be met for program success.

1.1.2 Bomber Armament Tester Synopsis

The “BAT System” is hereby defined as: consisting of the common core tester and the Units Under Test (UUT) Test Program Sets (TPSs) required to support respective B-2A, B-1B, and B- 52H weapon systems. The BAT “Core Tester” includes hardware, operating system software, firmware, test executive software, power-on confidence test TPS, user-selectable self-test TPS, and calibration TPS. A UUT TPS includes all cables, Interface Test Adapters (ITAs), software, and technical documentation required to test a UUT.

The BAT System shall be a versatile, adaptable, common tester featuring modular, open system architecture which can be easily modified and updated to resolve obsolescence or support future requirements. The BAT System shall provide organizational level, on and off-equipment capability to support fault detection/isolation and diagnostics of UUTs to identify system or component malfunction to the appropriate faulty Line Replaceable Unit (LRU) for the armament systems UUTs.

The BAT System shall certify the operational readiness of bomber weapon suspension and release equipment, which includes nuclear weapon delivery capability. The BAT System shall support B-2A, B-1B, and B-52H organizational level stores station maintenance (on-aircraft) and back-shop armament system component maintenance (off-aircraft).

For purposes of the BAT System, the organizational level is defined as on-Air Craft, on the flight line where temperature, dust, rain etc. cannot be regulated, and is further defined by specification paragraph 3.1.16 and its sub-paragraphs.

1.2 Unit Under Test

The following sections provide the B-2A, B-1B, and B-52H armament systems UUTs that shall be supported by the BAT System.

1.2.1 B-2A Armament System Units Under Tests

UUT NAME NIIN PART NO.

Rotary Launcher Assembly (RLA) (Nuclear item; see

MNCL)

01-600-0627 DAA3510A001-101

Nuclear Weapon Control Monitor (NWCM, NWIU) 01-435-0603, 01-435-0141

DAA3383E040-117,

DAA3383E040-119

Bomb Status Relay Assembly (BSRA) 01-435-1816 DAA3383E080-107 Missile Status Relay Assembly (MSRA) 01-435-0605 DAA3383E090-109 Ejector Relay Assembly (ERA) 01-315-6294 DAA3383E100-103 Transformer Rectifier Unit (TRU) 01-315-6293 DAA3383P033-107 Bomb Ejector Rack Unit 44 (BRU-44B/A) 01-511-0578 6127100-02 , Boeing p/n

464-55605-1 Bomb Ejector Rack Unit 52 (BRU-52/A37B-1B5) 01-381-5850 DAA3529A047-001 Smart Bomb Rack Assembly (SBRA) A/A 37B-1B5 01-519-6360 DAA3520A001-011, DAA3520A001-013

Monitor and Control Equipment (MACE) 01-597-1730 DAF3520A500-001 Smart Bomb Rack Controller (SBRC) - part of MACE 01-513-9507, 01-597-3119 70P993000-1013, 70P993000-1017

Bomb Rack Unit 72/B (BRU-72) Carriage and Release Equipment (CARE) - for MOP

01-596-7293 464-95813-9

Junction Box Assembly (JBA), Forward CARE N/A 464-19252-1 Junction Box Assembly (JBA), Aft CARE N/A 464-58563-1 On aircraft tests (SMS harness connectivity test) N/A N/A

Table 1-1 B-2A UUTs

1.2.2 B-1B Armament System Units Under Tests

UUT NAME NIIN PART NO.

Multi-Purpose Rotary Launcher (MPRL) 01-613-2984 L6316202-041 Rack, Bomb Ejector, 30 Inch (BRU-56/A) 01-412-0831 L6410301-081 Conventional Bomb Module (CBM) 28 station 01-323-9577 L6317310-061 Rack, Bomb Ejector, 14 Inch 01-278-5999

01-423-8778 L6314201-061 L6314202-041

1760 Enhanced Conventional Bomb Module (SECBM) 10 station

01-592-8399 L6317801-031

Common Weapons Interface Unit (CWIU) 01-488-4261 400-17165-114 Ejector Rack, MAU-12D/A 01-398-7497 69J13060-9 On aircraft test (Weapons Delivery System) N/A N/A

Table 1-2 B-1B UUTs

1.2.3 B-52H Armament System Units Under Tests

UUT NAME NIIN PART NO.

Ejector Rack, MAU-12C/A 01-100-3892 69J13060-7 Ejector Rack, MAU-12D/A 01-398-7497 69J13060-9 Pylon Assy, B-52 Integrated Conventional Weapons NA 398-10652-25, ‘-26, ‘-27, ‘-28

Bomb Release and Arming Control (R/H and L/H) 00-475-2437 00-475-2436

68J34000R-01 68J34000L-01

Conventional Rotary Launcher (CRL) 1760 N/A 405-22003* Cluster Bomb Rack (CBR) 00-219-3641 5-69557-1,-505,-507,-508,-509 On aircraft testing (SMS testing) N/A N/A On aircraft testing (SUU 67 pylon disconnect) N/A N/A *Note: Part number 405-22003-1 for CRL is preliminary and dash number may change.

Table 1-3 B-52H UUTs

2.0 APPLICABLE DOCUMENTS

2.1 General

While every effort has been made to ensure the completeness of the referenced Government documents in section 2.2, all specified requirements of documents cited in this specification shall be met, whether or not they are listed. The documents listed in sections 2.2 and 2.3 are referenced in section 3 of this specification.

2.2 Government Documents

2.2.1 Specifications, Standards, and Handbooks

The documents listed below form a part of this specification to the extent specified herein. The applicable revision of all documents referenced herein shall be the issue in effect on the date of contract solicitation issuance. The procuring activity has determined that canceled, inactive, or superseded documents referenced herein do not have a suitable substitute, or would create inconsistencies with existing documents. Therefore, canceled, inactive, or superseded documents referenced herein shall have the same effect as active documents. Documents can be accessed through Defense Logistic Agency ASSIST quick search web application 33TUhttp://quicksearch.dla.mil U33T/.

2.2.1.1 Military Standards

MIL-STD-882 Department of Defense Standard Practice: System Safety Rev. E, 11 May 2012

MIL-STD-461 Department of Defense Interface Standard Requirements Rev. F, 10 Dec 2007 for the Control of Electromagnetic Interference

MIL-STD-464 Department of Defense Interface Standard Electromagnetic Rev. C, 1 Dec 2010 Environmental Effects Requirements For Systems

MIL-STD-1472 Department of Defense Design Criteria Standard Rev. G, 11 Jan 2012 Human Engineering

MIL-STD-1553B Department of Defense Interface Standard for Digital Notice 4 15 Jan 1996 Time Division Command/Response Multiplex Data Bus http://quicksearch.dla.mil/

MIL-STD-1686 Electrostatic Discharge Control Program for the Protection Rev. C, 25 Oct 1995 of Electrical and Electronic Parts, Assemblies and

Equipment (Excluding Electrically Initiated Explosive Devices)

MIL-STD-1760E Department of Defense Interface Standard Aircraft/Store Notice 1 24 Oct 2007 Electrical Interconnection System

MIL-STD-810G Department of Defense Test Method Standard for Notice 1 15 Apr 2014 Environmental Engineering Considerations and Laboratory Tests

MIL-STD-130N Identification Marking of U.S. Property Change 1 16 Nov 2012

MIL-STD-704F Department Of Defense Interface Standard: Aircraft Notice 2- Validation Electric Power 25 Oct 2013

MIL-STD-1366E Transportability Criteria 31 Oct 2006

MIL-STD-1568C Materials and Processes for Corrosion Prevention and 12 Aug 2014 Control in Aerospace Weapons Systems

MIL-STD-2073-1E(1) Standard Practice for Military Packaging 07-Jan-2011

MIL-STD-3018 Parts Management Change 2 02 June 15

2.2.1.2 Military Specifications

MIL-DTL-38999 Connector, Electrical, Circular, Miniature High Density, Rev. M Supplement 1 Quick Disconnect (Bayonet Threaded and Breech 11 Feb 2015 Coupling), Environment Resistant, Removable Crimp and Hermetic Solder Contracts, General Specification for

MIL-P-15024/5 Plates, Tags and Bands for Identification of Equipment 21 Apr 2014

MIL-PRF-28800 Test Equipment for use with Electrical and Electronic Rev. F 24 Jun 1996 Equipment, General Specification for

MIL-PRF-32070A Performance Specification for Test Program Sets Rev. A 10 Jan 2012

MIL-PRF-39019F Circuit Breakers, Magnetic, Low-Power Sealed, Trip-Free

NOTICE 1 General Specification for 13 Feb 2015

MIL-STD-1332B Definitions of Tactical, Prime, Precise, and Utility NOTICE 2 Terminologies for Classification of the DoD Mobile 10 July 2001 Electric Power Engine Generator Set Family

2.2.1.3 Military Handbooks

MIL-HDBK-189 Department of Defense Handbook Reliability Growth Rev. C 14 Jun 2011 Management

MIL-HDBK-217F Reliability Prediction for Electronic Equipment Change Notice 2 28 Feb 1995

MIL-HDBK-419A Grounding, Bonding and Shielding for Electronic Change Notice 1 28 Feb 1995 Equipments and Facilities, (Handbook Contains both Volume I Basic Theory, and Volume II Applications)

MIL-HDBK-454B General Guidelines for Electronic Equipment Notice 1 12 Dec 2012

2.2.2 Other Government Documents, Drawings, and Publications

The following government documents, drawings, and publications listed below form a part of this specification to the extent specified herein. Unless otherwise specified, documents listed in Appendix A are provided for reference only. Appendix A is provided with no guarantee of completeness, accuracy or currency.

AFMAN 91-118 Safety Design and Evaluation Criteria for Nuclear Weapon 28 July 2015 Systems

AFMAN 91-119 Safety Design and Evaluation Criteria for Nuclear Weapon 05 Jun 2012 Systems Software

AFI 91-107 Design, Evaluation, Troubleshooting, and Maintenance 11 Dec 2012 Criteria for Nuclear Weapon Systems

CNSSI No. 1253 Security Categorization and Control 27 Mar 2014 Selection for National Security Systems

DoDI 8500.01 and .02 Cyber Security 14 Mar 2014

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information

12 Mar 2014 Technology (IT)

FED-STD-595C Colors Used for Government Procurement 595C Change Notice 1 31 Jul 2008

Specification Standard Basic Interface Specification, System 1 No. SYS 1001-02 1 July 2008

Specification Standard System 2 Basic Interface Specification No. SYS 2001-04A

AMAC POG SYS 2

11 Dec 2012

TO 00-25-234 General Shop Practice Requirements for the Repair, Change 1 Maintenance, and Test of Electrical Equipment 23 March 2014

TO 1-1A-14 Installation and Repair Practices Volume 1 Aircraft Electric 15 April 2014 and Electronic Wiring

2.3 Other Documents

IEEE 1636.1-2013 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA):

Exchanging Test Results and Session Information via the eXtensible Markup Language (XML)

ISO 7779:2010 Acoustics -- Measurement of airborne noise emitted by information technology and telecommunications equipment

2.4 Order of Precedence

In the event of a conflict between the text of this specification and the references cited herein the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3.0 REQUIREMENTS

3.1 General Bomber Armament Tester System Requirements

3.1.1 General System Design

The BAT System shall be designed in accordance with (IAW) MIL-PRF-28800F, Test Equipment for use with Electrical and Electronic Equipment, General Specification for Class 1.

3.1.2 Applicability

The BAT System shall be designed to test all of the UUTs listed in Tables 1-1, 1-2, and 1-3. The BAT Core Tester shall contain the functions such as a system controller, analog and digital stimulus, measurement, signal switching, power and Input/Output devices, and software necessary to test the UUTs listed in Tables 1-1, 1-2, and 1-3.

3.1.3 Modular Open System Architecture

The BAT System shall be based on a Modular Open System Architecture (MOSA) design per paragraph 3.2.1.

3.1.4 Reserved

This section was intentionally left blank.

3.1.5 Markings

All external devices which require an operational or maintenance interface shall be marked IAW MIL-STD-130. Painted markings shall be 1-inch high block letters unless prohibited by the available space. In such cases, the markings shall be the largest size possible but shall not be less than 1/2-inch high. Markings, Information/Caution shall be Lusterless Black Color Number 37038 of FED-STD-595 and Markings Warning/Danger shall be Lusterless Red Color Number 31136 of FED-STD-595.

3.1.6 Identification Plate

The system end items shall be properly identified IAW MIL-STD-130.

3.1.7 Workmanship

MIL-HDBK 454 Guideline 9 shall be used as a guide to workmanship.

3.1.8 Foreign Object Damage Prevention

All parts and components shall be securely attached to prevent loss and to prevent Foreign Object Damage (FOD) to the B-2A, B-1B, and B-52H aircraft as well as the BAT System or any other equipment.

3.1.9 Enclosures

Enclosures for the BAT System and cables/accessories shall be designed IAW MIL-PRF- 28800F. Accessory enclosures shall prevent cable bends beyond manufacturer specification in storage.

3.1.10 Color

Exterior color shall be color number 26173 (grey) as defined by FED-STD-595.

3.1.11 Cable Design

Cables shall be designed to tolerate 90-degree flexing imposed by the weight of themselves during use, over their service life without damage to the internal wiring, cable exterior, connectors, or connector/cable interface IAW MIL-PRF-32070A. The cable branching limit imposed by MIL-PRF-32070A, Paragraph 3.4.4.2, is waived. The number of cable branches and connectors shall be minimized while optimizing size, weight, sustainment considerations and TPS run-time.

3.1.11.1 Connector Selection

Connectors shall be selected using MIL-DTL-38999 and shall utilize environmentally sealed connectors with crimp style pins. Connectors that are not MIL-DTL-38999 compliant shall require government approval.

3.1.11.2 Connector Finish

Connectors used to terminate shields shall have a conductive finish.

3.1.11.3 Connector Keying

Connectors shall be keyed to prevent inadvertent application or use unless prevented by UUT.

3.1.11.4 Wire Shields

Except for coaxial cables, wire shields, shall not be used as a return nor shall they be used to conduct power.

3.1.11.5 Shield Insulation

A layer of insulation shall cover all wire shields.

3.1.11.6 Shield Bonding

Overall cable shields shall be terminated at a connector backshell that provides peripheral bonding of the shield.

3.1.11.7 Safety Ground Conductor

All power cables shall have a safety ground conductor IAW MIL-STD-464 and MIL-HDBK- 419A.

3.1.11.8 Cable Crosstalk Mitigation

Cables shall be designed to prevent crosstalk.

3.1.11.9 Protective Caps

Cables shall have a protective end-cap permanently attached by a lanyard and shall be ruggedized.

3.1.11.10 Connector Positioning

Cable connectors shall be positioned to mitigate strain and to facilitate ease of installation and/or removal without incurring ancillary accommodations (e.g., disconnection or removal of adjacent cables).

3.1.11.11 Connector Population

To provide structural integrity when seating connectors, cable connectors shall be completely filled with pins and sockets.

3.1.12 Power

3.1.12.1 Operating Power

The BAT System shall be capable of operating from 28 VDC and 120/240 VRMS 50 Hz, 60 Hz, and 400 Hz AC (single and multi-phase). Operating power shall comply with the requirements listed in MIL-PRF-28800F, MIL-STD-704F and MIL-STD-1332B. Automatic and operator initiated shutdown shall provide an orderly, sequential system shutdown to preclude damage to the Automatic Test Equipment (ATE) or UUT and shall not degrade the ATE hardware or software.

Operating power for the BAT Core Tester computer/controller shall have the capability of being isolated from the test power being used to power the UUTs.

3.1.12.2 Master Power Switch

The BAT System shall be equipped with a master power On/Off switch with an indicator lamp.

3.1.12.3 Power Cable Length

Power cable length shall be sufficient to enable UUT testing to be performed without repositioning tester for all test points on a given UUT for on and off aircraft testing.

3.1.12.4 Unit Under Test Power

The BAT System shall be capable of switching external power as required by the UUT. The BAT System shall control on/off switching of power to the UUT as required by the UUT TPS.

Operating power for the BAT Core Tester computer/controller shall have the capability of being isolated from the test power being used to power the UUTs.

3.1.12.5 Power Consumption

The BAT Core Tester, excluding the UUT, shall consume no more than 1.3 kW for operation of internal stimulus and measurement devices.

3.1.12.6 Circuit Breakers

The BAT System shall have circuit breakers with manual reset capability accessible to the maintainer IAW MIL-PRF-39019F. Circuit breakers shall not be capable of being manually over ridden during an over current condition.

3.1.12.7 Power Monitoring

The BAT System shall measure and report input power, VRMS for each phase, phase sequence, and frequency information to the operator as follows:

a. As part of the power-up sequence.

b. At the start of all test sequences.

c. During each step while the test load is still connected. Report as part of the data for each failure, or for each step if in manual mode.

The BAT System shall detect and respond to the presence of more than 6 VRMS between the Neutral and Chassis Ground as follows:

a. If during power-up, notify the operator of a power fault and prevent the BAT Core Tester power-up sequence.

b. If during operation, notify the operator and perform an orderly shutdown.

3.1.13 Grounding

3.1.13.1 Controlled Grounding Concept

A controlled grounding concept shall be used so that grounding will not adversely impact the functional testing/operation of the UUT. This concept shall provide for a single point ATE signal ground as well as a single point safety ground IAW the guidelines of MIL-HDBK-419A.

3.1.13.2 Shock Protection

The grounding scheme for the BAT System shall provide protection of personnel and equipment from electrical shock hazards during normal operations and under ground fault conditions.

3.1.13.3 Ground Loop Prevention

The BAT System shall be designed to eliminate ground loops and minimize common ground impedance which can degrade system noise margins.

3.1.13.4 External Safety Ground

The BAT System shall provide an external safety ground stud or bar.

3.1.14 Graphical Display

3.1.14.1 Graphical Display Size

The display shall be adequately sized to clearly show at a minimum all applicable information as defined in specification paragraph 3.3.2 (e.g., status, menus, test data, fault codes, messages, etc.)

in a manner that is easily readable by the user. The display shall meet the requirements of MIL- STD-1472G, Section 5.2.

3.1.14.2 Graphical Display Readability

The display shall be readable in all lighting conditions, including full daylight ambient conditions; direct sunlight; and night time IAW MIL-STD-1472G, Section 5.2. The brightness setting shall not allow the display to "black-out".

3.1.14.3 Graphical User Interface

The BAT System graphical user interface functions shall enable the operator to interact with the test system, to include but not be limited to, enabling TPS diagnostic advancement and/or referral to alternate test instructions, explanations and/or troubleshooting trees; authentication;

test instruction initiation and/or termination; and test result save commands as necessary to achieve UUT test requirements.

3.1.14.4 User Navigation

The BAT System shall provide controls to allow the operator to move between pages of display information, between selection options, and selection of a menu item/option.

3.1.15 Human Factors

3.1.15.1 Operability with Chemical Warfare Gear

The BAT System shall be capable of being operated and decontaminated by personnel in Mission Oriented Protective Posture (MOPP) Level 4 Chemical Warfare Defense Ensemble (CWDE) IAW MIL-STD-1472G, Section 4.10.

3.1.15.2 Transportability

3.1.15.2.1 Weight

The contractor shall strive to minimize the size, weight and total number of transit cases of the overall system without adversely affecting performance. The BAT System footprint for the B- 2A aircraft shall not exceed that of the current legacy tester(s) and cable sets being replaced by the BAT System for testing B-2A armament. The BAT System footprint for the B-1B aircraft shall not exceed that of the current legacy tester(s) and cable sets being replaced by the BAT System for testing B-1B armament. The BAT System footprint for the B-52H aircraft shall not exceed that of the current legacy tester(s) and cable sets being replaced by the BAT System for testing B-52H armament.

The weight of the BAT Core Tester including tester power cables and self-test cables or of any one accessory container for the BAT System shall not exceed a two-person lift to 36 inches as defined for the “male only” population per MIL-STD-1472G, Section 5.8.6.3.1 (T) with an objective of a two-person lift to 36 inches as defined for the “male and female” population per MIL-STD-1472G, Section 5.8.6.3.1 or less (O).

The BAT Core Tester shall not exeed two (2) transit cases. If the BAT Core Tester is packaged in two transit cases, the weight of each transit case shall not exceed a one person lift to 36 inches as defined for the “male only” population per MIL-STD-1472G, Section 5.8.6.3.1 (T) with an objective of a one-person lift to 36 inches as defined for the “Male and female” population per MIL-STD-1472G, Section 5.8.6.3.1 or less (O).

3.1.15.2.2 Handles

The BAT System shall be provided with recessed and/or foldable handles or other suitable means for grasping, handling, and carrying IAW MIL-STD-1472G.

3.1.15.3 Edges and Corners

The BAT System shall include provisions for smooth edges/corners, prevent accidental contact with high and low surface temperatures, and provide pinch point prevention, IAW MIL-STD- 1472G.

3.1.15.4 Moving Parts

All moving/mechanical parts shall be inaccessible to the operator during system operation to prevent inadvertent contact (e.g., cooling fan).

3.1.16 Environmental

The BAT System shall conform to the performance specified herein when subjected to the environmental conditions as specified in MIL-PRF-28800F, Paragraph 3.8, for Class 1 equipment. Deviations from and clarifications of MIL-PRF-28800F (detail specification references) are specified in the following paragraphs.

3.1.16.1 Solar Radiation

In addition to the temperature requirements specified in MIL-PRF-28800F, the BAT System shall meet High Temperature with Solar Radiation per requirements defined in MIL-STD-810G, Method 505.5, Procedure I, in a simulated Hot Dry (A1) climate. The BAT System shall be in operational configuration and shall be required to successfully pass system self-test as well as a simulation of typical steady state loading and use of stimulus and measurement devices as anticipated for the most strenuous and lengthy B-2A UUT TPS, during the maximum BAT System temperature response period of the exposure cycle.

3.1.16.2 Electromagnetic Interference

The BAT System shall be Electromagnetic Interference (EMI) qualified IAW the following emission and susceptibility requirements from MIL-STD-461F, Section 5.3, Table V, for Air Force Ground equipment.

TABLE 3-1 EMI REQUIREMENTS

MIL-STD-461F

Requirement

Description

CE102 Conducted Emissions, Power Leads, 10 kHz to 10 MHz CS101 Conducted Susceptibility, Power Leads, 30 Hz to 50 KHz CS114 Conducted Susceptibility, Bulk Cable Injection, tailored to 10 kHz to

200MHz CS115 Conducted Susceptibility, Bulk Cable Injection, impulse excitation CS116 Conducted Susceptibility, Damped Sinusoidal Transients, cables and power leads, 10 kHz to 100 MHz RE102 Radiated Emissions, Electric Field, 10 k Hz to 18 GHz RS103 Radiated Susceptibility, Electric Field, 2 MHz to 40 GHz

3.1.16.3 Explosive Atmosphere

The BAT System shall be designed to be Explosive Atmosphere Qualified per MIL-STD-810G, Method 511.6, Procedure I. The BAT System design shall have the ability to operate in a fuel vapor environment without igniting the environment.

3.1.16.4 Altitude

The BAT System shall conform to the specified performance and accuracy requirements when operated at an altitude 15,000 feet (4,600 meters) or less IAW MIL-STD-810G Method 500.5 Procedure II (operating configuration), and after return from an altitude of 40,000 feet, IAW MIL-STD-810G, Method 500.6, Procedure III (storage/transit configuration).

3.1.16.5 Drip Proof

The BAT System shall comply with the drip proof requirements of MIL-PRF-28800F paragraph

3.8.6.3. MIL-PRF-28800F, Paragraphs 3.8.6.1 and 3.8.6.2, do not apply to the BAT System.

3.1.16.6 Acoustic Noise

Acoustic noise requirements shall be as specified in MIL-PRF-28800F, Paragraph 3.8.12. The BAT System shall not generate acoustic noise in excess of 70 dBA sound pressure level (SPL) when measured at the operator and bystander positions, IAW ISO 7779.

3.1.16.7 Corrosion Prevention

The BAT System shall be constructed of parts and materials that are corrosion and deterioration resistant, or coated to resist corrosion and deterioration, IAW MIL-STD-1568C.

3.1.17 Nuclear Certification

3.1.17.1 System Safety

System safety for the BAT System shall be conducted IAW the requirements of MIL-STD-882E.

The BAT System design shall be compliant with requirements defined by AFMAN91-118 and

AFMAN91-119.

3.1.17.2 Single Failures

The BAT System shall be designed such that no single component failure, common mode failure, human error, or a design feature shall cause a mishap of catastrophic or critical mishap severity categories as defined in MIL-STD-882E.

3.1.17.3 Dual Failures

The BAT System shall be designed such that no dual independent component failures, dual independent human errors, or a combination of a component failure and a human error involving safety critical command and control functions, shall cause a mishap of catastrophic or critical mishap severity categories.

3.1.17.4 Design Safety – Critical Functions

The BAT System design shall prevent faults in the test equipment or test circuits that could operate critical functions or apply unintended power to the weapon interface.

3.1.17.5 Design Safety – Internal Faults

The BAT System design shall prevent internal faults within the tester that could degrade the nuclear or conventional safety of the equipment to be tested.

3.1.17.6 Design Safety – Unintended Signals

The BAT System design shall prevent the introduction of signals, voltages, or currents into the weapon system that could degrade nuclear or conventional safety of the equipment to be tested.

3.1.17.7 Design Safety – Unintended Firing

The BAT System shall prevent operation or firing of an item under test, except when specifically designed for that purpose.

3.1.17.8 Test Safety – End of Test

The BAT System shall ensure a weapon system component, which has been operated during testing, is in the safe or inactivated position when the test ends. A positive indication verifies the safe position of such components.

3.1.18 Test Safety – System Failures

The BAT System failures or shutdowns shall leave the components under test in a safe or inactivated condition. The BAT System shall provide a clear indication of UUT failure status.

3.1.19 Electromagnetic Environmental Effects Requirements

The BAT System shall be compatible with ordnance classified as Hazards of Electromagnetic Radiation to Ordnance (HERO) SAFE ORDNANCE IAW the requirements of MIL-STD-464C, section 5.9.3, Table 9.

3.1.20 Cyber Security

a. The BAT System shall maintain a mission effective capability in the face of a full spectrum of cyber threats.

b. The BAT System design shall implement cyber security IAW DoDI 8500.01, DoDI 8500.02, DoDI 8510.01, and CNSSI No. 1253. If a commercial operating system is used, the applicable Defense Information Systems Agency (DISA) developed Security Technical Implementation Guide shall be implemented.

c. The requirements listed in Paragraphs 3.1.20.1 through 3.1.20.9 shall be implemented in the design in a manner to minimize the impact on operational and maintenance procedures in the flight line environment.

3.1.20.1 User Auditing

The BAT System shall incorporate an electronic auditing trail that unambiguously identifies and records the initiating user of the operational test or any log-on event. This includes auditing the installation of BAT System Software, Test Program Sets, and Firmware as applicable.

3.1.20.2 Software Non-Repudiation

All BAT System Software, TPSs, and firmware created, delivered, and installed shall utilize non-repudiation techniques to guarantee the integrity and origin of the System Software, TPSs and firmware throughout the entire System Software, TPSs and firmware lifecycle.

3.1.20.3 Endpoint Security

The BAT System shall only include necessary and functional information data ports to interface with authorized data-transfer media. Data ports will be disabled when not in use.

3.1.20.4 System Administration

The BAT System shall deny software configuration changes for all but administrator user accounts. The operating system, test executive, and TPS software shall only be capable of being loaded by those users who have administrator privileges. The BAT System shall permit only authorized software code to execute on the system.

3.1.20.5 Configuration Auditing

The BAT System shall perform a configuration audit during system start to identify malware or unauthorized changes to the approved configuration.

3.1.20.6 Malware Alerting

The BAT System shall notify the user of any detected malware or unauthorized changes and not allow activation of the test connections if malware is detected during system start up as defined in Paragrpah 3.1.21.1 of this specification.

3.1.20.7 Wireless Network

Wireless network hardware, software, and firmware shall not be present within the BAT Core Tester.

3.1.20.8 Data at Rest Encryption

The BAT System shall encrypt all data at rest on the nonvolatile storage media used to boot the BAT System, store the operating system, store the test executive and store the Test Program Set Software.

3.1.20.9 System Recovery

The BAT Core Tester shall be capable of being recovered to a known clean state by the system administrator from any cyber security incident.

3.1.21 BAT Core Tester Self-Test/Built-In Test

The BAT Core Tester Self-Test/Built in Test (BIT) shall be designed IAW MIL-PRF-32070A.

If faults are discovered, the core tester’s functional status shall be displayed to the user and shall not require the use of external technical manuals to determine functional status.

3.1.21.1 Power-On Confidence Test

The BAT Core Tester shall provide a Power-On Confidence Test to ensure proper operation prior to initiation/stimulation of UUT test. The Power-On Confidence Test shall be automatically performed upon BAT System power-up and shall include running the malware detection defined in 3.1.20.6 of this specification. Power-On Confidence test shall be completed in 10 minutes or less (T) with an objective of 2 minutes (O).

3.1.21.2 Self-Test

The BAT Core Tester shall have an integrated Self-Test capability for failure detection and fault isolation of all system components, and shall provide indications of out of range conditions of the tester. The Self-Test shall ensure that stimulus and measurement devices are operating within tolerance. Self-Test shall run upon system start up and when manually commanded by the user. Self-Test during TPS execution shall not be enabled.

3.1.21.3 Self-Test Data

The BAT Core Tester on-board fault and Self-Test data shall be collected, stored, and provided IAW IEEE 1636.1 compatible formats to maintenance personnel during and after maintenance operations.

3.1.21.4 Self-Test Fault Detection

The BAT Core Tester Self-Test shall detect 100 percent of detectable faults. A detectable fault is a failure of a Tester Replaceable Unit (TRU) that is exhibited at the interface of the TRU and is outside the defined performance parameter or threshold for that particular function.

3.1.21.5 Self-Test Execution Time

The BAT Core Tester Self-Test execution time shall be no longer than 10 minutes (T) with an objective of 1 minute (O).

3.1.21.6 Self-Test Fault Isolation Rate – 1 Component

The BAT Core Tester Self-Test shall isolate at least 90% of detected faults to a single system component (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.)

3.1.21.7 Self-Test Fault Isolation Rate – 2 Components

The BAT Core Tester Self-Test shall isolate at least 95% of detected faults to two system components (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.)

3.1.21.8 Self-Test Fault Isolation Rate – 3 Components

The BAT Core Tester Self-Test shall isolate 100% of detected faults to three or less system components (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.).

3.2 System Capability

3.2.1 Modular Open System Architecture (MOSA)

3.2.1.1 Open System Architecture Design

The BAT System shall be a MOSA design. The following system architecture design characteristics shall be utilized:

a. Open Architecture – The contractor shall develop and maintain an architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b. Modular, Open Design – The contractor shall develop an architecture that is layered and modular and uses standards-based hardware interfaces, operating systems, and middleware that all utilize either non-proprietary or non-vendor-unique key module or component interfaces. The contractor’s design approach shall be applied to all subsystems and components.

i. Module Coupling – The contractor’s design approach shall result in modules that have minimal dependencies on other modules (loose coupling), as evidenced by simple, well-defined interfaces and by the absence of implicit data sharing.

The purpose is to ensure that any changes to one module will not necessitate extensive changes to other modules, and hence facilitate module replacement and system enhancement.

ii. Module Cohesion – The contractor’s design shall result in modules that are characterized by the singular assignment of identifiable and discrete functionality (high cohesion). The purpose is to ensure that any changes to system behavioral requirements can be accomplished by changing a minimum number of modules within the system.

c. System Requirements Accountability – The contractor shall ensure that all system requirements are accounted for through a demonstrated ability to trace each requirement to one or more modules that consist of components that are self-contained elements with well-defined, open and published interfaces implemented using open standards.

d. Inter-component Dependencies – The contractor’s design approach shall result in a layered system design, maximizing software independence from the hardware, thereby facilitating technology refresh. The design shall be optimized at the lowest component level to minimize inter-component dependencies. The layered design shall also isolate the application software layers from the infrastructure software (such as the operating system) to enhance portability and to facilitate technology refresh. The design shall be able to survive a change to the computing infrastructure with minimal or no changes required to the application logic. The interfaces between the layers shall be built to open standards or the technical data describing the interface shall be Unlimited Data Rights.

The system architecture shall minimize inter-component dependencies to allow components to be decoupled and reused, where appropriate, across various DoD or Service programs and platforms.

3.2.1.2 Test Program Set Software Architecture

The BAT System software environment shall allow TPSs to be instrument independent (hardware abstraction). Each TPS shall be a distinct configuration item, separate from the operating system and test executive, and not dependent upon other TPSs. TPSs shall be developed utilizing a contractor developed, Government approved BAT System TPS style guide.

3.2.1.3 Operating System Architecture

Operating System Software shall be designed with middle-ware to interface TPSs and the Test Executive Software with the operating system such that updates to operating system do not affect TPS qualification. The BAT Systems operating system shall be supportable and/or upgradable over the service life of the tester without modifying TPSs.

3.2.1.4 Test Executive Software Architecture

Test Executive Software shall be designed with middle-ware to interface TPSs with the operating system such that updates to operating system do not affect TPS qualification.

3.2.1.5 Memory Capacity

The BAT System shall have non-volatile memory large enough to store the operating system, TPS software, test results, and any supporting software with at least 50% open capacity for future growth.

3.2.1.6 Memory Usage

The BAT System shall be designed to utilize less than 50% of the system’s volatile memory.

3.2.1.7 Processor Usage

The BAT System shall be designed to utilize less than 50% of the processor’s throughput.

3.2.2 Suitability Requirements

3.2.2.1 Maintainability

3.2.2.1.1 Maintenance Concept

The BAT System shall be designed for 2-level (organizational and depot) maintenance.

Organizational level maintenance shall include replacement of minor externally accessible hardware. The contractor shall utilize respective MIL-HDBK 454 guidelines.

3.2.2.1.2 Accessibility

The BAT System shall be designed to be accessible. MIL-HDBK-454 Guideline 36 shall be used as a guide.

3.2.2.1.3 Cable Repair

The BAT System cables and interface adaptors shall be field-repairable IAW T.O. numbers 1- 1A-14 and 00-25-234. The BAT System shall be capable of testing repaired cables post field actions.

3.2.2.1.4 Service Life

The BAT System’s service life shall be a minimum of 20 years with corrective maintenance.

Service life begins at initial fielding.

3.2.2.1.5 Storage Life

The BAT System shall have a storage life of 5 years without maintenance.

3.2.2.1.6 Scheduled Maintenance

The BAT System shall be designed to minimize scheduled maintenance activities.

3.2.2.1.7 Calibration

The BAT System shall be capable of being calibrated, if calibration is required.

3.2.2.2 Reliability

3.2.2.2.1 Mean Time Between Failure

The BAT System operational Mean Time Between Failure (MTBF) shall be at least 1500 hours, with 95% confidence.

MTBF is defined as the mean average time between failures.

Express MTBF as: MTBF= (Operating Hours)/(Number of failures)

A failure is any observed or indicated condition which requires the system to undergo unscheduled maintenance. A failure shall be counted for each separate root cause. Failures include software root causes, but exclude conditions induced by operator error. Failures may occur during both mission and non-mission time. Failures and indicated failures reported during inspection, or discovered by maintenance or calibration will be included in this metric.

3.2.2.2.2 Elapsed Time Indicator

The BAT System shall have an elapsed time indicator visible to the maintainer to display total operating hours.

3.3 Test Program Set Requirements

All armament…