FIA2T_AtchL-3_Sample_Task_1_S-SRD_20150728.docx

Attachment 3 System and Security Requirements Document (S/SRD) for Sample Task 1 Universal Cryptographic Module (UCM) Engineering and Manufacturing Development

Version 1.1 7/28/2015

Prepared by:

Cryptologic and Cyber Systems Division (AFLCMC/HNC) 250 Hall Blvd., Suite 132 Lackland AFB, TX 78243

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

LIST OF TABLES AND FIGURES

Table 41 Requirements Verification Cross Reference Matrix 20

Figure 31 Universal Cryptographic Module Functional Diagram and External Interfaces 12

THIS PAGE IS INTENTIONALLY LEFT BLANK

FA8307-16-R-0049

FIA2T Section L Attachment L-3 - Sample Task 1- S/SRD 28 July 2015

SCOPE

General This document describes the functional, performance, and support requirements for the Universal Cryptographic Module (UCM) capability. The Performance Section, Section 3, includes a set of requirements for the development of an Advanced Encryption Standard (AES) algorithm cryptographic engine with key sizes of 128 and 256 bits. This document will be the basis of potential offeror’s design concept, planning and cost information in support of the Flexible Information Assurance Acquisition Tool - Unlimited (FIA2T-U) Multiple Award Indefinite Delivery/Indefinite Quantity (MA IDIQ) proposal preparation.

Description The UCM will be a single channel cryptographic embeddable microelectronic component designed for integration into higher level communications component assemblies for fixed (both permanent and transportable) and mobile (i.e., human-portable, vehicular, ship-borne, airborne, and space-borne) platforms requiring encryption or decryption of data communications links at information data rates between 100 Mbps and 2.5Gbps, inclusively. The UCM will be used by those platforms that require integration of its cryptographic functions with other functionality in order to achieve higher levels of integration than a self-contained, box-level end cryptographic unit provides. The UCM will be a tailored NSA Information Assurance Security Requirements directive (IASRD) and Technical Security Requirements Document (TSRD) device for Top Secret and Below (TSAB); it will be a space qualified COMSEC embeddable solution. The UCM will be designed in accordance with the technical requirements contained in the UCM requirements (Section 3.1) of this document. For startup, self-test, reset, rekey or power-on, the default state for UCM after completing any function, is defined as the “FOP” (full operation) state.

Document Conventions The documentation conventions for the S/SRD are as follows:

a. Each requirement is given a unique number and that number is enclosed in parentheses at the beginning of each requirement.

b. To be determined <TBD> is used to indicate that the Government and the Contractor will determine the specification together at a later date.

c. To be supplied <TBS> is used to indicate that the Government will supply the missing information at a later date.

d. The word "shall" is used whenever a specification expresses a provision that is binding.

e. “Shall” statements that are not explicitly marked as objective requirements are threshold requirements.

f. The words "should" and "may" are used wherever non-mandatory provisions are specified.

g. The word "will" is used to show purpose.

System Overview The requirements in section 3 describe a generalized End Cryptographic Unit (ECU) that can be embedded in other devices as a solution for encryption and decryption requirements representative of typical development efforts envisioned to be executed on the FIA2T-U MA IDIQ.

Sample Task 1 outlines the technical requirements for a Universal Cryptographic Module (UCM) that contains only the core cryptographic functions. The UCM will either encrypt or decrypt data and will be the cryptographic core for embedment in multiple mobile and fixed (both permanent and transportable) platform’s communications systems.

The UCM will implement the AES cryptographic algorithm with key sizes of 128 and 256 bits. This design concept allows other UCMs implementing different algorithms to be developed in the future and be integrated into existing UCM-enabled platforms with minimal integration development work required. However, the security certification of a new device would still be required.

The UCM will be integrated into a variety of platforms. As a result, the devices must be able to survive a broad range of environmental conditions during operation. A “worst case” approach to establishing performance thresholds was used to establish the requirements contained in this document.

Universal Cryptographic Module (UCM) The UCM provides the following core cryptographic functions:

Startup The UCM performs a Self-Test to determine if it is ready for operation whenever power is applied to its power interface. The UCM provides a “RESET” indication and the status of its self-test.

Self-Test The UCM performs various internal self-test functions when commanded by the next higher assembly (e.g., aerospace vehicle equipment, radio or avionics), during start-up, and during rekey. All self-test function requirements are specified in the Tailored IASRD for the UCM. The UCM provides a “SELFTEST” indication and the status of its self-test. After the successful conclusion of self-test, the UCM loads the last selected operational key into the cryptographic core and is ready for synchronization or encryption of data with no further command inputs.

Operation After the successful conclusion of startup, self-test, reset, rekey or power-on, the UCM receives a key from the next higher assembly and is ready for synchronization and processing of data. Reset at a minimum will clear all registers and performs a self-test as described in the Tailored IASRD for the UCM. The UCM provides a “FOP” (full operation) indication after completing any function.

Alarms If at any time the UCM detects an internal error or fault condition, it will stop processing data and enter into an alarm condition. The UCM will remain in this alarm condition until RESET by the next higher assembly. All requirements concerning internal error, fault, or alarm conditions are specified in the Tailored IASRD for the UCM. The UCM provides an “ALARM” indication.

Key Management The UCM only contains the current key it is using to process data. With the exception of retaining the current key during the self-test function, the UCM does not store any keys. When commanded by the next higher assembly, the UCM rekeys. If the UCM is unable to rekey, it will stop data processing activities and alarm. The UCM unwraps the black Over-The-Air Rekey (OTAR) key using the operational algorithm. This key will be used in operations and will not be saved in memory.

AES Algorithm Implementation The UCM will encrypt or decrypt data using the AES algorithm. The UCM will implement the Cipher Feedback Mode (CFB) and Galois/Counter Mode (GCM) of the AES algorithm. The UCM will provide a control signal that will be used to select either encrypt or decrypt mode. The UCM will provide a control that will be used to select either the GCM or CFB algorithm mode.

Synchronization The UCM will provide cryptographic synchronization capabilities.

Randomizer The UCM will implement a randomizer function used to seed the initialization of the algorithm circuitry as required in the Tailored IASRD for the UCM. The requirements for this randomizer function are provided in the the Tailored IASRD for the UCM.

Control The UCM control interface connects to the next higher assembly and allows it to control all UCM functions (e.g. encrypt/decrypt mode, algorithm mode, synchronization mode and rekey operations). Control commands that the UCM receives from the next higher assembly are not authenticated by the UCM since the next higher assembly is considered a trusted source and must have appropriate security evaluation certification.

Status The UCM status interface connects to the next higher assembly and provides the current status.

APPLICABLE DOCUMENTS

National Security Agency (NSA) and National Institute of Standards and Technology (NIST)

a. UCM Security Requirements (tailored Information Assurance Security Requirements Directive (IASRD)), UNCLASSIFIED//FOUO

· (U) (Reference Adobe PDF file “FOUO_FIA2T_Sample_Task_1_IASRD_20151215”

b. UCM Security Requirements (tailored Technical Security Requirements Document (TSRD)), UNCLASSIFIED//FOUO

· (U) (Reference Adobe PDF file “FOUO_FIA2T_Sample_Task_1_TSRD_20151215”

c. Software Analysis and Assessment Process Description (SAAPD) (untailored, for reference only for complying with TSRD), UNCLASSIFIED//FOUO

· (U) (Reference Adobe PDF file “FOUO_FIA2T_Sample_Task_1_SAAPD_20151215”

d. FIPS PUB 197, Advanced Encryption Standard (AES), 26 Nov 2001

e. SP 800-38A, Recommendation for Block Cipher Modes of Operation, 2001 Edition

f. SP 800-38D, Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC, November, 2007

g. SP 800-90 A, Recommendation for Random Number Generation Using Deterministic Random Bit Generators, January 2012

h. SP 800-90 B, DRAFT Recommendation for the Entropy Sources Used for Random Bit Generation, August, 2012

i. SP 800-90 C, DRAFT Recommendation for Random Bit Generator (RBG) Constructions, August, 2012

j. SP 800-130, A Framework for Designing Cryptographic Key Management Systems, August, 2013

k. SP 800-115, Technical Guide to Information Security Testing and Assessment, September, 2008

l. SP 800-161, DRAFT Supply Chain Risk Management Practices for Federal Information Systems and Organizations (Second Draft), June, 2014 U.S. Military and Government Specifications:

a. Aerospace TOR – 2004(3909)-3537, Rev B, Software Development Standard for Space Systems, 11 March 2005

b. NASA Specification SP-R-0022A, Addendum 1 and 2, Vacuum Stability Requirements of Polymeric Material for Space Application, February 24, 1984

c. MIL-HDBK-217F, Notice 1 and 2, Reliability Prediction of Electronic Equipment, 28 February 1995

d. MIL-HDBK-454B, General Guidelines for Electronic Equipment, 15 April 2007

e. MIL-PRF-38535K, General Specification for Integrated Circuits (Microcircuits) Manufacturing, 20 December 2013

f. MIL-STD-461F, Electromagnetic Emissions and Susceptibility Requirements for the Control of Electromagnetic Interference, 10 December 2007

g. MIL-STD-810G, Change 1, Environmental Engineering Considerations & Laboratory Tests, 4 March 2014

h. MIL-STD-882E, Standard Practice for System Safety, 11 May 2012

i. MIL-STD-883J, Change 5 Draft, Test Method Standard for Microcircuits, 5 September 2014

j. MIL-STD-1472G, Human Engineering, 11 January 2013

k. SMC-S-009 (2013), AFSC Space And Missile Systems Center Standard: Parts, Materials, And Processes Control Program For Space And Launch Vehicles (12 April 2013)

l. SMC-S-010 (2013), (U) SMC-S-010 (2013), AFSC Space And Missile Systems Center Standard: Technical Requirements For Electronic Parts, Materials, And Processes Used In Space Vehicles (12 April 2013)

m. MIL-STD-1580B, Change 3, Destructive Physical Analysis (DPA) for Electronic, Electromagnetic and Electromechanical (EEE)Parts, 4 March 2014

n. SMC-S-21, Technical Reviews and Audits for Systems, Equipment and Computer Software, Volume 1, 15 September 2009

o. SMC-S-008 (2008), AFSC Space And Missile Systems Center (SMC) Standard: Electromagnetic Compatibility Requirements For Space Equipment & Systems (13 June 2008) International Standards & Specifications:

a. IPC J-STD-001E, Requirements for Soldered Electrical and Electronic Assemblies, April 2010

b. International Printed Circuit (IPC) A-610E, Acceptability of Electronic Assemblies, April 2010

c. ASTM E595-07, Standard Test Method for Total Mass Loss and Collected Volatile Condensable Materials for Outgassing in a Vacuum

PERFORMANCE

UCM Requirements Definition The UCM will be a single channel cryptographic embeddable microelectronic component designed for integration into higher level communications component assemblies for fixed (both permanent and transportable) and mobile (i.e., human-portable, vehicular, ship-borne, airborne, and space-borne) platforms requiring encryption or decryption of data communications links. Figure 3-1 below provides a functional view of how the UCM will operate. The UCM will encrypt or decrypt digital data at all rates from 100 Mbps to 2.5 Gbps. The UCM will be a single component that will implement the AES algorithm. The UCM will be a tailored NSA IASRD and TSRD device for Top Secret and Below (TSAB); it will be a space qualified COMSEC embeddable solution. The UCM will be designed in accordance with the technical requirements contained in this document.

Functional Diagram A functional diagram is depicted in Figure 31 below.

Figure 31 Universal Cryptographic Module Functional Diagram and External Interfaces

External Interfaces Definition Figure 31 presents a functional view of the UCM interfaces. Input data enters the UCM for cryptographic processing after which, they exit the UCM. The data enter as either plaintext or ciphertext and exits as its compliment, ciphertext or plaintext depending on the commanded cryptographic processing configuration, either encrypt or decrypt, respectively. It is not required to perform encryption and decryption simultaneously. The UCM receives commands that enter through its control interface. The UCM provides its operating status, including responses to commands, through its Status Interface. The UCM receives the new active cryptographic key material for the cryptographic processing function via its key interface. The UCM receives power via its Power Interface. The UCM may require a stable reference clocking signal to drive digital signal processing, depending on design approach. The UCM is subject to environmental effects which it is required to compensate to maintain its operating state. These external interface requirements are functional requirements, and are not intended to identify a specific number of pins or dictate design. For example, the signals for clock and data could be encoded as a single data stream and still satisfy the requirements.

1.1.1.1.1 Input Data Channel

(1) The UCM Data Input Channel interface shall indicate when the input data signal is appropriately formatted based on either encryption or decryption processing state of the cryptographic processing function.

(2) The UCM Data Input Channel interface shall protect against appropriate security threats.

(3) The UCM Data Input Channel interface shall operate at all information data rates from 100 Mbps to 2.5 Gbps.

(4) The UCM Data Input Channel interface’s electrical and signal parameters shall conform to an open industry standard.

1.1.1.1.2 Output Data Channel

(5) The UCM Data Output Channel interface shall indicate when the output data signal is valid for output based on either encryption or decryption processing state of the cryptographic processing function.

(6) The UCM Data Output Channel interface shall protect against appropriate security threats.

(7) The UCM Data Output Channel interface shall operate at all information data rates from 100 Mbps to 2.5 Gbps.

(8) The UCM Data Output Channel interface’s electrical and signal parameters shall conform to an open industry standard.

1.1.1.1.3 Cryptographic Key Material Input

(9) The UCM Cryptographic Key Material Input shall provide the signals needed to load a single cryptographically protected key from authorized external source.

(10) The UCM Cryptographic Key Material Input shall protect against appropriate security threats.

(11) The UCM Cryptographic Key Material Input interface’s electrical and signal parameters shall conform to an open industry standard.

1.1.1.1.4 Control Input Channel

(12) The UCM Control Input Channel interface shall provide the signals needed to configure and initiate all of the UCM functions.

(13) The UCM Control Input Channel shall protect against appropriate security threats.

(14) The UCM Control Input Channel interface’s electrical and signal parameters shall conform to an open industry standard.

1.1.1.1.5 Status Output Channel

(15) The UCM Status Output Channel interface shall provide the signals needed to indicate that current status of all of the UCM functions.

(16) The UCM Status Interface shall protect against appropriate security threats.

(17) The UCM Status interface’s electrical and signal parameters shall conform to an open industry standard.

1.1.1.1.6 Reference Clock Signal

(18) The UCM Reference Clock Signal input interface shall provide externally-generated clock signal for reference to support synchronizations of external interfaces, if required.

(19) The UCM Reference Clock Signal input interface shall protect against appropriate security threats.

(20) The UCM Reference Clock Signal input interface’s electrical and signal parameters shall conform to an open industry standard

1.1.1.1.7 External Power Input

(21) The UCM power consumption shall not to exceed 4.7 watts.

(22) The UCM External Power Input interface shall protect against appropriate security threats.

(23) The UCM External Power Input interface’s Electrical parameters shall conform to an open industry standard.

1.1.1.1.8 Environmental Effects

(24) The UCM shall meet all performance requirements after exposure to test and operational environments as specified in sections 3.1.2.4.1, 3.1.2.5, and 4.1.

(25) The UCM Environmental Effects Input interface shall protect against appropriate security threats.

1.1.2 Characteristics

Performance

1.1.2.1.1 General

(26) The UCM shall be a single channel cryptographic component designed for embedment into fixed and mobile platform’s communications subsystems requiring encryption or decryption of data links.

(27) The UCM shall be command configurable through the control interface as either an encryptor or a decryptor. That is, the UCM shall not encrypt and decrypt data simultaneously.

(28) The UCM shall be a single cryptographic algorithm device.

(29) The UCM bit delay shall be a constant deterministic value. The design goal of the UCM will be to achieve the lowest possible bit delay.

(30) The UCM shall provide a constant propagation delay to within +/- 10%. The design goal of the UCM will be to achieve the lowest possible propagation delay.

(31) The UCM shall process traffic using synchronization immediately after reset without further command required from higher level assembly.

(32) The UCM shall process traffic using synchronization immediately after successful completion of self-tests without further command required from higher level assembly.

(33) The UCM shall process traffic using synchronization immediately after successful rekey without further command required from higher level assembly.

1.1.2.1.2 Cryptographic Processing

Processing

(34) The UCM shall cryptographically process data input based on control input configuration information defining:

· AES Encryption or Decryption algorithm in either GCM or CFB mode.

· Key size of either 128 or 256 bits.

· Throughput information rates from 100 Mbps to 2.5 Gbps for both the Data Input and Output Channels.

Synchronization

(35) The UCM shall create and output a cryptographic synchronization pattern until a control command to stop is received when encrypting.

(36) The UCM shall detect a cryptographic synchronization pattern and output a synchronization status when decrypting.

1.1.2.1.3 Key Management

(37) The UCM shall authenticate, using an approved tailored IASRD key establishment technique, the cryptographic key material inputted from the cryptographic key material input interface and prepare the cryptographic key for use by the cryptographic processing function.

(38) The UCM shall load only one cryptographic key material at any time.

(39) The UCM shall provide status of when in cryptographic key material loading mode and whether key loaded successfully or not when completed.

(40) The UCM shall be ready for operation in less than 1 second after receipt of cryptographic key material input.

1.1.2.1.4 Device Status

(41) The UCM shall provide all status defined below via its Status Output Channel interface.

(42) The UCM shall provide status whenever power is applied and upon any change in function.

(43) The UCM shall provide continuous status of all discrete signals.

(44) The UCM shall provide status upon receipt and execution of control command input.

(45) The UCM shall provide a status response to all control commands indicating the result of command execution in less than 1 second (measured from when the UCM receives the command until it completes execution).

Discrete Signals to cover the following status:

(46) The UCM shall indicate when it is ready for operational processing of data.

(47) The UCM shall indicate when it is in alarm.

Serial Telemetry Signals to cover the following status:

(48) The UCM shall indicate when it is ready for operational processing of data.

(49) The UCM shall indicate when it is in alarm.

(50) The UCM shall indicate when it is being reset.

(51) The UCM shall indicate when it is performing self-tests.

(52) The UCM shall indicate the results of self-tests.

(53) The UCM shall indicate when it is rekeying.

(54) The UCM shall indicate the results of rekeying.

(55) The UCM shall indicate when it is processing data.

(56) The UCM shall indicate when it is configured for encryption.

(57) The UCM shall indicate when it is configured for decryption.

(58) The UCM shall indicate the algorithm mode being used to process data.

(59) The UCM shall indicate the synchronization status.

1.1.2.1.5 Control

(60) The UCM shall execute reset, self-test, rekey, encryption, decryption, algorithm mode and synchronization actions in response to control commands.

(61) The UCM shall execute actions in less than 1 second or less (measured from when the UCM receives the command until it completes execution).

Physical Characteristics

(62) The UCM shall be designed as a single active hardware component (e.g., Integrated Circuit, Programmable Logic Device or Multi-Chip Module) as opposed to a printed circuit card or assembly.

(63) The UCM package size shall not exceed 40 x 40 mm.

Interoperability

(64) The UCM shall be cryptographically interoperable. That is, the encrypted output of a UCM can be decrypted by another UCM using the same key, algorithm, algorithm modes, synchronization modes, and data rates.

Reliability

(65) The UCM shall meet QML Class V, Class Level S requirements per MIL-PRF-38535K.

1.1.2.1.6 Service Life

(66) The UCM shall have a continuous operating life of 10 years.

Environmental Conditions

1.1.2.1.7 Operational

(67) The UCM shall meet operating performance requirements under environmental conditions as follows:

· Operating Temperature: -55 Deg C to +125 Deg C

· Operating Atmospheric Pressure: 0.00024 Torr

· Shock and Vibration: Per MIL-PRF-38535K, Table V, Subgroup 4 use relevant MIL-STD-883 test method and conditions for Class V (class level S).

(68) The UCM shall meet all operating performance requirements during exposure and at end-of-life (EOL) when operated in the following radiation environments:

· Radiation Hardness Assurance (RHA) Level H per MIL-PRF-38535K.

· The analysis of TID susceptibility shall include, but not be limited to, Enhanced Low Dose Rate Sensitivity (ELDRS). If ELDRS-sensitive parts are considered for use, they shall be tested to MIL-STD-883J, Method 1019.

· Displacement damage: The UCM shall meet all manufacturer’s performance specifications when exposed to a displacement damage level equivalent to a fluence of 1E12 neutrons/cm^2, 1-MeV equivalent. This requirement shall be verified through MIL-STD-883J, Method 1017.2.

· Single Event Effects (SEEs): The UCM shall meet all manufacturer’s performance specifications when exposed to heavy ions and protons of galactic origin, from solar flares, and from trapped radiation belts that are capable of inducing catastrophic damage as well as temporary disruptions in operation (SEUs). Specifically,

· Single Event Latch Up (SEL): The UCM shall not exhibit SEL at a level below 75 MeV-cm^2/mg.

· Single Event Burn Out (SEB): The UCM shall not exhibit SEB at a level below 75 MeV-cm^2/mg.

· Single Event Gate Rupture (SEGR): The UCM shall not exhibit SEGR at a level below 75 MeV-cm^2/mg.

· Single Event Upset (SEU): Features for autonomous recovery from SEUs shall be included in the design. Either (1) the UCM SEU threshold shall be at a level equal to or above 75 MeV-cm^2/mg, or (2) it will be demonstrated that the SEE environment shall not cause the SEU rate to exceed 1E-11 errors/bit/day, including Single Event Transients (SETs). For the purpose of verification of this requirement only, the SEU rate shall be calculated assuming the UCM is operated in a shielded SEE environment as defined by a geostationary orbit (GEO), including the background radiation environment plus two worst-weeks and one worst-day of solar particle events, as defined in CREME96[footnoteRef:1], over the mission duration. As a basis for SEU rate calculations, the shielding used shall be 100 mils of Al. The calculations shall include analysis of any error detection and correction circuitry. [1: Cosmic Ray Effects on Micro Electronics (CRÈME) was first developed in 1981 by a team led by Dr. Jim Adams of the Cosmic Ray Physics Section at Naval Research Laboratory. Since then, CREME has become a widely-used design tool in the aerospace industry. In addition, many other codes, which address the same issues as CREME, have incorporated routines from the original CREME program suite. The algorithms and tools for CREME96 calculations are found at https://creme.isde.vanderbilt.edu/

Security

(69) The UCM shall meet all of the security requirements stated in the tailored IASRD and the TSRD.

(70) The UCM shall be certified to protect data to TSAB.

Design and Construction Materials, Processes, and Parts

(71) The UCM shall use NASA specification SP-R-0022A when selecting materials and finishes. (Note: Total mass loss (TML) (due to outgassing) of not more than 1.0 percent and a collected volatile condensable material (CVCM) of not more than 0.1 percent when tested in accordance with ASTM E595-07 will be achieved. However, if the TML is greater than 1.0 percent, but it can be shown that contributions to the TML in excess of 1.0 percent are due only to adsorbed water vapor, the materials are acceptable).

(72) The UCM shall contain no pure TIN (Sn) or TIN alloy greater than 97% Tin by weight, or Pure ZINC, or Pure CADMIUM metal, coating, or plating finish used in the design and construction, internal or external, of parts or materials. Where electronic part terminals and leads and solder lugs are used in conjunction with bolts, nuts, or washers that apply a continuous load to the tin alloy surface and where solderability is a critical factor, these parts may be coated with a tin alloy layer, but this tin alloy shall contain a minimum of 37 percent of lead (Pb).

(73) If ZINC or CADMIUM-containing alloys are used in the UCM, the alloys shall have a final surface finish using non-prohibited materials or be carefully reviewed/analyzed for long term reliability in the intended space application and shown to present no deleterious effects or degradation, with margin.

(74) The UCM shall use no prohibited materials including alloys or compounds containing mercury, chlorinated fluorocarbons, non-chlorine-free parylene, asbestos-containing materials, and corrosive (acetic acid evolving) silicone sealants, adhesives or coatings; as described in SMC-S-010 (2013) .

(75) The contractor shall implement and require all subcontractors to implement procedures and processes for establishing lot date/batch number control and two-way traceability for parts, materials and processes manufactured into flight and qualification hardware.

(76) The contractor shall implement procedures and processes for performing Destructive Physical Analysis (DPA) for all standard and non-standard parts consistent with the System and Security Requirements Document (S/SRD) for Sample Task 1: Universal Cryptographic Module (UCM) Engineering and Manufacturing Development (this document) and MIL-STD-1580B.

(77) The contractor shall implement and require all subcontractors to implement shelf life control procedures and processes that identify the shelf life limitations for all parts and materials used on flight and qualification hardware.

(78) The contractor shall document, maintain and configuration control an As-Built Parts, Materials and Processes List (ABPMPL) for each end-item being delivered to the contractor’s facility.

(79) The UCM shall not use unnecessary toxic products and formulation.

(80) The UCM shall meet or exceed Class-S requirements as defined in MIL-PRF-38535 Rev. K Appendix B and the contractor shall implement a Parts, Materials, and Processes (PMP) Control Program in accordance with SMC-S-009 (2013) and SMC-S-010 (2013). In addition, the contractor shall implement a Radiation Hardness Assurance Program in accordance with Appendix C of MIL-PRF-38535 Rev. K. and Appendix A of SMC-S-010 (2013) .

Electromagnetic Compatibility

(81) The UCM, shall meet the electromagnetic interface design requirements contained in the following paragraphs of the MIL-STD-1541A, Electromagnetic Compatibility Requirements for Space Equipment and Systems:

· 4, 5.3, and 6.6 Interchangeability

(82) The mechanical design of the UCM shall meet the tests for interchangeability in accordance with MIL-HDBK-454B, Guideline 7.

Precedence

(83) In the event of inconsistency between this specification and tailored IASRD, the IASRD shall have precedence.

VERIFICATION

UCM Environmental Tests

(84) The UCM shall be tested in accordance with:

· MIL-PRF-38535K, General Specification for Integrated Circuits (Microcircuits) Manufacturing, 20 December 2013

· MIL-STD-883J, Test Method Standard for Microcircuits, 20 June 2014 Requirements Verification Each of the requirements defined in this S/SRD will be validated by one of the following methods: inspection (I); analysis (A); demonstration (D); and test (T). The qualification method(s) to be used for each of the performance requirements will be identified in the Verification Cross Reference Matrix (VCRM) and will be subject to Government approval.

(a) Inspection. Verification will be performed by visually examining the item, reviewing descriptive documentation, and comparing the appropriate characteristics with a referenced standard to determine conformance to requirements.

(b) Analysis. Verification will be performed by evaluation or simulation using mathematical representations, charts, graphs, circuit diagrams, and data reduction.

(c) Demonstration. Verification will be performed by operation, movement or adjustment of the item under a specific condition to perform the desired function without recording quantitative data except for check sheets.

(d) Test. Verification will be performed through systematic exercising of the applicable item under all appropriate conditions with instrumentation and test data collection, analysis, and evaluation of quantitative data.

Requirements Verification Cross Reference Matrix Table 41 Requirements Verification Cross Reference Matrix

(1)

(2)

(3)

(4)

Mechanical aspects verified through inspection

(5)

(6)

(7)

(8)

Mechanical aspects verified through inspection

(9)

(10)

(11)

Mechanical aspects verified through inspection

(12)

(13)

(14)

Mechanical aspects verified through inspection

(15)

(16)

(17)

Mechanical aspects verified through inspection

(18)

(19)

(20)

Mechanical aspects verified through inspection

(21)

(22)

(23)

Mechanical aspects verified through inspection

(24)

Mechanical aspects verified through inspection

(25)

(26)

(27)

(28)

(29)

(30)

(31)

(32)

(33)

(34)

(35)

(36)

(37)

(38)

(39)

(40)

(41)

(42)

(43)

(44)

(45)

(46)

(47)

(48)

(49)

(50)

(51)

(52)

(53)

(54)

(55)

(56)

(57)

(58)

(59)

(60)

(61)

(62)

(63)

(64)

(65)

(66)

(67)

(68)

(69)

(70)

(71)

(72)

(73)

(74)

(75)

(76)

(77)

(78)

(79)

(80)

(81)

(82)

(83) image2.png image1.png