DI-EMCS-82013
HEMP Protection Subsystem Performance Test Plan
Describes the methods of test analysis and inspection used by the contractor to verify compliance with HEMP interface and performance requirements of a ship during engineering development, enabling government understanding and duplication of verification methods.
Approval DateApril 4, 2016
AMSC Number9607
Preparing Activity—
Project Number—
OPRDTRA-DS
DTIC ApplicableYes
GIDEP Applicable—
Limitation—
Applicable FormsNone
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Related
DI-EMCS-82014DI-EMCS-82012
Application & Interrelationship
—
Use & Relationship
The HEMP Protection Subsystem (HPS) Performance Testing Plan describes the methods of test analysis and inspection used by the contractor to verify compliance with the HEMP interface and performance requirements of a ship during the engineering development phase. The Plan provides the means for the government to understand and duplicate verification methods used by the contractor to verify HEMP protection requirements.
1. This DID contains the format, content, and intended use information for the data product resulting from the work tasks described in Appendix B and Appendix C of MIL-STD-4023 and is intended for ship systems. It is normally applied to the System Design and Development phase of a program, but it can be used in any phase.
2. This DID is related to DI-EMCS-82014 and DI-EMCS-82012.
Preparation Instructions
1Reference documents.The applicable issuance of the documents cited herein, including their approval dates and any applicable amendments, notices, or revisions shall be as cited in the ASSIST Online at the time of the solicitation, or for non-ASSIST listed documents, as stated herein. HEMP Protection Subsystem Performance Test Plan classification shall be determined using DTRA Security Classification Guide for DoD Electromagnetic Pulse (EMP) Programs and Activities (U) available by mail request to ATTN: J9/NT-NTSA/Rooney M., Defense Threat Reduction Agency, 8725 John J. Kingman Road, MSC 6201 Fort Belvoir, Virginia 22060-6201 and any relevant system specific classification guides.
2Format.The Plan shall be in contractor format.
3Content.The Plan shall describe the test plan for Electromagnetic Barrier Point-of-Entry testing for each requirement specified in the contract for the ship being developed (see MIL-STD-4023 section 5 and Appendix C).
3.1Summary information.The Plan shall summarize the following:
3.1.1.1System description, including any pertinent information regarding HEMP protection performance testing issues.
3.1.1.2Statement of any assumptions and limitations associated with HEMP protection performance testing.
3.1.1.3General objectives.
3.1.2Scope.General description of overall test requirements matrix being used to demonstrate compliance with requirements, including the relative role of analyses, tests and inspections.
3.1.3Methods of verification.Abstracts of the procedures used for verifying each HEMP protection performance requirement listed in 3.2 below.
3.1.4Engineering factors.Any important engineering factors affecting the verification procedures or test performance, such as facilities, resources, safety, reports, and security.
3.2Detailed information.For protective elements testing a single test plan shall be prepared. The test plan shall contain the following information: a comprehensive, system-specific test plan and detailed test procedures for protective elements performance testing. These may be combined in a single document, or separate documents may be used. The document(s) shall contain the following information: a. A statement of test objectives and criteria to be met to achieve these objectives. b. Ship system and subsystem identification and descriptions (including drawings of the subsystems showing the locations of all Points of Entry, equipment layout inside the electromagnetic barriers, external cable interconnections; and a description of the HEMP protection measures). c. Data acquisition equipment descriptions (including manufacturer, model and serial numbers, characteristics, detailed calibration procedures and calibration traceability documentation). d. Detailed Test Procedures including system, subsystem, and circuit configuration requirements; test configuration diagrams; test point descriptions; step-by-step procedures, and test point locations. e. Any deviations from the requirements of MIL-STD-4023, Appendix C. f. Data management (including data quality control procedures, data acceptability criteria, annotation and preservation of data records, and pass/fail criteria). g. Safety, including electromagnetic radiation and electrical shock hazards. h. Test participants. i. Schedule, including priority of measurements.
3.2.1Pre-test analysis section.Pre-test analyses of Low Level Continuous Wave Immersion (LLCWI) and/or Pulse Current Injection (PCI) test data including calculations of threat responses from LLCWI and/or PCI testing is required for testing nonlinear PPDs, as required (see DI-EMCS-82012, Hardness Allocation Report).
3.2.2Post-test data analysisPost-test data analysis will include development of a corrective plan and, if applicable, the Hardness Allocation Report (DI-EMCS-82012) will be updated.
3.2.3Elements of HPS performance compliance testing.
3.2.3.1Models, techniques, and tools used for analysis and predictions and their specific application to this system.
3.2.3.2Step-by-step test procedures.
3.2.3.3Determination of as-built hardness margins.
3.2.3.4Selection of critical circuits, functions, and subsystems.
3.2.3.5Pass/fail criteria and methods of quantifying and evaluating failures.
3.2.3.6Description of test articles, test facilities, test equipment (including instrumentation on and off the system), support equipment, and calibration techniques.
3.2.3.7Method of simulating operational performance when actual operation is impractical.
3.3Other information sources.When other information sources contain data required by this DID, these sources shall be referenced rather than be duplicated within this report.
Schema v3.0Community-maintained · Verify against ASSIST