Attachment 4 Performance Specification.pdf

Revision

3.2.3.4.3.b:

3.2.3.6.2:

3.2.4.1:

3.2.10.2.b:

3.2.10.2.1.c:

3.2. 10.2.2:

3.2.10.4:

3.2.13.3:

4.2.3/4.2.4:

4.6.4:

4.6.7.b.2:

4.6. IO Title:

Appendix A:

Appendix B:

Table 1-6:

Table 4:

B Global :

2.2

3.2.1.5:

3.2.1.5.1

3.2.1.6

3.2.1.7:

3.2.2.1:

3.2.2.1.a:

3 .2.2.1.b:

3.2.2.1.c:

3.2.2.3:

PRF-PT-00543, Rev B 02 April 2012

REVISION HISTORY

Summaa of Changes Date

Deleted "/date"

Delete "from".

Changed the end of the first sentence to " .. . 264 hr alignment retention while expending 3,600 rounds per training exercise conditions."

Add to the beginning of the sentence "After receiving a low power indication, "

Deleted.

Deleted "(www.monmouth.army.mil/cecom/lrc)"

Changed "green or black" to " green, brown, or black"

Deleted " transit cases"

Moved "The system shall be inspected to verity that human engineering requirements have been met." from 4.2.3 to 4.2.4.

Added "(except the MAJiK)."

Changed "from 0.0001 to 0.01 millimeters" to "less than 150 µm."

Changed "SALT AND FOG" to "SALT FOG"

Changed APPENDIX A

Changed APPENDIX B

Changed Tables. Renumbered Tables 5-7.

Deleted table, incorporated number of rounds into paragraph 3.2.4.1.

Changed program name to I-MILES IWS 2 (formerly known as I- 02 Apr 12

MILES IWS 2010)

Removed Live Personal Area Network (PAN) Interface Standard (PRF-PT-00549). Added Tactical Vehicle System (TVS) ICD (ICD- TVS_ OT A-00 I) to Government documents

Deleted "MILES rNTERFACE"

Moved "INDUCTIVE LOOP INTERFACE" from 3.2.1.5.1 to 3.2.1.5

Moved "INFRARED (IR) INTERFACE" from 3.2.1.5.2 to new section 3.2.1.6

Added "RADIO FREQUENCY (RF) INTERFACE" section

Deleted "Example of wireless links are infrared, inductive loops, radio frequency (RF)"

Changed "a wireless link" to " an infrared interface"

Changed "a wireless link" to " an inductive loop interface"

Deleted 3.2.2. 1.c

Uodated Figure I to include TVS block diagram

Revision

3.3.3:

Appendix B:

REVISION HISTORY

Summary of Changes

PRF-PT-00543, Rev B 02 April 2012

Date

Added Item Unique Identification (JUID) requirement

Updated APPENDIX B lll

TABLE OF CONTENTS

Paragraph

PRF-PT-00543, Rev B

02 April 2012

1 SCOPE

1.1 SYSTEM DESCRIPTION

1.2 BACKGROUND

2 APPLICABLE DOCUMENTS

2.1 SPECIFICATIONS, STANDARDS AND HANDBOOKS

2.2 GOVERNMENT DOCUMENTS

2.3 CODE OF FEDERAL REGULATIONS (CFR)

2.4 NON-GOVERNMENT STANDARDS AND PUBLICATIONS

2.5 ORDER OF PRECEDENCE

3 REQUIREMENTS

3.1I-MILES IWS 2 DEFINITION

3.2 SYSTEM'S GENERAL CHARACTERISTICS

3.2.1 External System Interfaces

3.2.1.l Laser lnterface

3.2.1.2 Control/Display Interface

3.2.1.3 Host Weapon/Soldier lnterface

3.2.1.4 Instrumentation lnterface

3.2.1.5 Inductive Loop lnterface

3.2.1.6 Infrared (IR) lnterface

3.2.1.7 Radio Frequency (RF) Interface

3.2.2 Internal System Interfaces

3.2.2.1 Wireless Interface

3.2.2.2 Dry Fire Trigger to SAT Interface

3.2.2.3 Data Transfer Interface

3.2.3 System Components

3.2.3.1 SAT

3.2.3.1.1 SAT Physical Requirements

3.2.3.1.2 Blank Fire And Dry Fire

3.2.3.2 Detection Unit (halo, harness and control/display unit)

3.2.3.3 Interoperability and Pairing Performance

3.2.3.3.1 HIT (Laser Beam) Profile

3.2.3.3.2 Pairing Probabilities

3.2.3.3.2.1 Machine Gun Pairing

3.2.3.3.2.2 Other Weapon Pairing ....................................................... ,

3.2.3.4 Control/Display Unit

3.2.3.4.l Operator Functions

3.2.3.4.2 Administrative Control Functions

3.2.3.4.3 Display Interface

3.2.3.S BIT Characteristics

3.2.3.6 Lethality Effect Assessment Routine (LEAR)

3.2.3.6.1 Kill Assessments Effects

3.2.3.6.2 Near Miss Effects

3.2.3.6.3 Reset

3.2.3.6.4 Resurrection

3.2.3.6.5 Cheat or Tamper ....................................................................................................... ,

3.2.4 Ancillary Units

3.2.4.1 Alignment Devices

3.2.4.2 OFT

3.2.4.3 TOTO Requirements

3.2.4.4 AAR/Test Software

3.2.5 Computational System Requirements

iv

PRF-PT-00543, Rev B 02 April 2012

4.2 VERIFICATION METHODS .••••.••••••••...•.............•..•.••.•••.•••••••.......•......••..•••.....••....•.•••••..•............•..•..........•••••••••••••

4.2.1 Functionol Configuration Audit {FCA)

4.2.2 Physical Configuration Audit (PCA)

4.2.3 First Article Test (FAT)

4.2.4 System Verification Tests (SVT)

4.2.4.1 Laboratory Tests

4.2.4.2 Range Tests

4.2.5 Reliability Tests

4.2.6 Maintainability Demonstration

4.2. 7 System Integration Tests {SIT}

4.2.8 Production Qualification Tests .................................................................. ,

4.2.9 Developmental and Integration Testing

4.3 SYSTEM SOF1WARE .•...•..•.......... ·••·•··•···•··•••••·••·

4.4 TRANSIT CASES

4.5 TRANSPORTABILITY

4.6 ENVIRONMENTAL CONDITIONS

4.6.1 High Temperature

4.6.2 Low Temperature

4.6.3 Shock

4.6.4 Vibration

4.6.5 Humidity

4.6.6 Rain

4.6.7 Sand and Dust

4.6.8 Immersion

4.6.9 Corrosion

4.6.10 Salt Fog

4.7 ELECTROMAGNETIC ENVIRONMENTAL EFFECTS (E

4.7.1 Radiated Emissions

4.7.2 Radiated Susceptibility

4. 7.3 Electrostatic Discharge (ESD) Effects

4. 7.4 life Cycle, e

Hardness . ............................................................................................ ,

4. 7.5 Electromagnetic Radiation Hazards

4.8 INTERCHANGEABILITY ...................•.••.•.....•..•..••....•..................•..•...........•...................•••..•................................•..••... 36

4.9 SYSTEM SAFETY ..... ···········•••••••••••••·•••···········•················•···••·•••••••·•··•··•••············•··••·••••••••··••·········· ......•••.•••••••••.•••• 36

4.9.1 Electrical Safety

4.9.2 Hazardous Materials

4.9.3 Mechanical Safety

4.9.4 Personnel Safety

4.9.5 Ionizing Radiation

4.9.6 Laser Safety

4.9.7 Radioactive Material Restrictions in Optical Products

5 PACKAGING

6 NOTES

6.1 DEFINITIONS

6.2 ABBREVIATIONS AND ACRONYMS

VI

PRF-PT-00543, Rev B

02 April 2012

APPENDIX A - I-MILES IWS 2 CONFIGURATIONS .................................................................................................... A-1

APPENDIX B - I-MILES IWS 2 PK TABLES .................................................................................................................. 8-1

FIGURE 1: I-MILES IWS INTERFACES AND COMPONENTS

TABLE 1: SATS VERSUS DETECTION UNITS

TABLE 2: PAIRING REQUIREMENTS FOR EFFECTIVE RANGE

TABLE 3: PAIRING REQUIREMENTS FOR SUPPRESSION RANGE

TABLE 4: MAXIMUM COMPONENT WEIGHT

TABLE 5: DESIGN REFERENCE MISSION PROFILE PER 96 HR EXERCISE

TABLE 6: METHOD OF VERIFICATION

Vll

1 SCOPE

PRF-PT-00543, Rev B

02 April 2012

This performance specification defines the performance requirements of the Instrumentable Muhiple Integrated Laser Engagement System (I-MILES) Individual Weapon System (IWS) 2 which was originally called the IWS 2010.

1.1 SYSTEM DESCRIPTION

The I-MILES IWS 2 requirement is for the replacement of the existing U.S. Army direct fire dismounted MILES devices (Basic MILES, I-MILES IWS and MILES 2000) with the laser based Tactical Engagement Simulation System (TESS) training devices. All I-MILES IWS 2 training devices shall be interoperable with Simulated Area Weapons Effects/MILES II, MILES 2000, MILES XXI, I-MILES IWS and all legacy MILES training devices (i.e. Shoulder Launched Munitions (SLM), Combat Vehicle System (CVS), Tactical Vehicle System (TVS), Independent Target System (ITS), Wireless lTS (WITS), Universal Controller Device (UCD) and Micro-Controller Device (MCD), etc). Interoperability is defined as being able to encode/decode MILES messages from other MILES devices and being able to communicate with the specified instrumentation systems. The I-MILES IWS will be fielded worldwide and used in all geographical areas. All I-MILES IWS 2 training devices and components will be interchangeable with the MILES 2000 IWS and I-MILES IWS training devices as an objective.

Interchangeability is defined as having the ability to swap major components (halo, vest, and Small Arms Transmitter (SAT)) between dismounted MILES systems and still be able to operate as a system. The I-MILES IWS 2 shall not require new manpower assets, personnel requirements, or qualifications.

1.2 BACKGROUND

The family of the Basic MILES was developed in the late 1970's using technology and designs then avai I able. Enhancements have included player identification (PIO), fratricide identification, multiple levels of kill, and vulnerability due to direction of attack. New v_;eapons, ammunition, and weapon performance have also been accommodated.

02 April 2012

2 APPLICABLE DOCUMENTS

The following documents of issue, specifications, standards, and handbooks shown on the Document Summary List apply to the extent specified herein.

2.1 SPECIFICATIONS, STANDARDS AND HANDBOOKS

The following Specifications, Standards and Handbooks form a part of this specification to the extent specified herein. Copies are available at https://assist.daps.dla.mil/guicksearch/.

MIL-STD-461 Rev F

MIL-STD-810 Rev G

MIL-STD-14 72 Rev F

2.2 GOVERNMENT DOCUMENTS.

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

Environmental Engineering Considerations and Laboratory Tests

Human Engineering Design Criteria for Military Systems, Equipment and Facilities

Government documents, drawings, and publications below form a part of this specification to the extent specified herein. Copies are available from PEO STRI, 12350 Research Parkway, Orlando, FL 32827-3276.

ICD 3262-01

ICD 290065

ICD 706014

I-HITS ICD-

001-12202005

PEO STRI 10-

W022

PMT 90-S002

Rev B 1 Nov 10

Rev D

Rev F Ch 1

Rev B, 20 Dec 05

Rev A 02 Apr 12

RevM 02 Feb 11

ICD for the I-MILES IWS

ICD for the Data Interface Between the Range Communication System, Range Data Management System, Data Communication Interface (DCI) Unit, and Tetrapol Central Node for the National Training Center Instrumentation System (IS)

ICD for the DCI to Detection Device Interface Design for the Combat Training Centers - IS

ICD for lnterim-Homestation Instrumentation and Training System (I-HITS) Instrumentation Unit to the MILES 2000 Tactical Engagement Simulator Harness

Statement of Work for I-MILES IWS 2

MILES Communication Code (MCC) Standard

PRF-PT-00551 09 Sep 10

PRF-PT-00552 Rev B 14 Nov 11

ICD-TVS OTA 27 Jan 11 -001

SAIB Jan 06

SPS 3262-01 Rev A

PRF-PT-00543, Rev B

02 April 2012

Interface Control Document for Backward Compatibility Development of the I-MILES Shoulder Launched Munitions

Instrumentation System (IS) Tactical Engagement Simulation Systems (TESS) fnterface Standard interface Control Document (ICD) for the Instrumentable Multiple Integrated Laser Engagement System Tactical Vehicle System (I-MILES TVS) Over The Air (OTA)

Small Arms Integration Book (SAIB)

Software Product Specification for the 1-MILES IWS

2.3 CODE OF FEDERAL REGULATJONS (CFR)

CFR's below f01m a part of this specification to the extent specified herein. They are available at http://wv-.rv.'.access.gpo.gov/nara/cfr/cfr-table-search.html.

10 CFR 40

21 CFR 1040

29 CFR 1910.1200

Domestic Licensing of Source Material

Performance Standards for Light-Emitting Products

Class I and Class II Stratospheric Ozone Depleting Substances

2.4 NON-GOVERNMENT STANDARDS AND PUBLICATIONS

The following documents form a part of this specification to the extent specified herein. Copies are available at http://www.nssn.org or http://www.sei.cmu.edu/.

ANSI/NEMA 2535.3-2007

ANSI/NEMA Z535.4-2007

ANSl/NFP A 70-08

ANSI Z 136.1-2007

ANSI ZI 36.6-2005

ASTM D3951

ATA SPEC 300, Rev 18

2.5 ORDER OF PRECEDENCE

Criteria for Safety Symbols

Product Safety Sign and Labels

National Electrical Code

Safe use of Lasers

Safe use of Lasers in an Outdoor Environment

Standard Practice for Commercial Packaging

Packaging of Airline Supplies

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

3 REQUIREMENTS

3.1 I-MILES IWS 2 DEFI JTION

PRF-PT-00543, Rev B

02 April 2012

The lnstrumentable-Multiple Integrated Laser Engagement System (I-MILES) Individual Weapon System (IWS) 2 shall consist of a family of laser-based training devices for soldiers with their individual weapons. The system shall consist of a detection unit (that covers the torso and the head of a soldier) and a laser transmitter (which shall be appended to the soldier's weapon). The system shall provide force-on-force engagement simulations to obtain feedback on the effects of direct fire weapon engagement simulations: on personnel, independent targets, crew served weapons, combat vehicles, and aircraft systems. I-MILES JWS 2 shall be interoperable with the Simulated Area Weapons Effects (SA WE)/MILES II, MILES 2000, MILES XXI, I-MILES IWS and other legacy MILES training devices (i.e. SLM, CVS, TVS, ITS/WITS, UCD, MCD, etc). Interoperability is defined as being able to encode/decode MILES messages from other MILES devices and being able to communicate with the specified instrumentation systems. I-MILES IWS 2 shall be interchangeable with the MILES 2000 IWS and I-MILES IWS training devices as an objective. Interchangeability is defined as having the ability to swap major components (halo, vest, and SAT) between dismounted MILES systems and still be able to operate as a system.

3.2 SYSTEM'S GENERAL CHARACTERISTICS

1-MILES IWS 2 shall be compliant with the MILES Communication Code (MCC) Standard PMT 90 S002 including Appendix G (Design Requirements). These devices shall:

a. Pair attackers with targets and assess the lethality effects of engagements.

b. Indicate the engagement results to the controller/observer using visual and audible cues.

c. Incorporate modular open system architecture for flexibility to accommodate product improvements.

d. Have the capability for use during periods of reduced visibility and ambient illumination ranging from darkness to full sunlight within the capabilities of the weapons with which it is being used.

e. Provide the capability to be programmed in less than three (3) minutes without being opened (software revisions).

f. All components shall be modular so PK tables shall be externally programmable independent of re-loading the system software.

3.2.1 EXTERNAL SYSTEM INTERFACES

3.2.1.1 LASER INTERFACE

I-MILES IWS 2 shall interface and be compatible with legacy and other MILES training devices using a laser light beam communication channel through the atmosphere In Accordance With (IA W) MCC Standard PMT 90-S002. Casualty assessments shall pair shooters with targets whether the I-MILES IWS 2 is the shooter or the target. They shall be able to pair using the player identification (PID).

3.2.l.2 CONTROL/DISPLAY INTERFACE

02 April 2012

I-MILES IWS 2 shall interface with individual operators and controllers to allow them to input data, select system parameters, and receive/transfer/display system data.

3.2.1.3 HOST WEAPON/SOLDIER INTERFACE

I-MILES IWS 2 shall be appended to weapon systems and individual operators and not interfere with any tactical equipment on the soldier or weapon.

3.2.1.4 INSTRUMENTATION INTERFACE

I-MILES IWS 2 shall provide an external RS-232 serial interface (Lemo connector) to send and receive real-time data necessary to interface and be interoperable (communicate) with the maneuver CTCs and Homestation's instrumentation systems (IS) and the Instrumentation System (IS) Tactical Engagement Simulation Systems (TESS) Interface Standard. The I-MILES IWS 2 shall operate at a baud rate from 9,600 to 57,600 bits per second. The RS-232 interface shall be capable of being located at both the lower front or lower back left corners of the harness. This interface shall be tested IAW ICD 706014, ICD 290065, I-HITS ICD 001-12202005 and PRF

PT-00552.

3.2.1.5 INDUCTIVE LOOP INTERFACE

a. As a threshold, the I-MILES IWS 2 shall have an inductive loop for interfacing to legacy surrogate weapons JAW PRF-PT-00551.

b. As an objective, using I-MILES IWS ICD 3262-01 and I-MILES IWS SPS-3262-01, the I-MILES IWS 2 halo shall be able to interface with legacy MILES harnesses.

c. As an objective, using I-MILES IWS ICD 3262-01 and I-MILES IWS SPS-3262-01, the I-MILES IWS 2 harness shall be able to interface with legacy MILES halos.

3.2.1.6 INFRARED {IR) INTERFACE

a. As an objective, using I-MILES IWS ICD 3262-01, and I-MILES IWS SPS-3262-01, the I-MILES IWS 2 harness shall be able to interoperate with the I-MILES IWS SA Ts via infrared inter faces.

b. As an objective, using I-MILES IWS ICD 3262-01, and I-MILES IWS SPS-3262-01, the I-MILES IWS 2 SA Ts shall be able to interoperate with the I-MILES IWS harnesses via infrared interfaces.

3.2.J.7 RADIO FREQUENCY (RF) INTERFACE

The I-MILES IWS 2 SATs shall associate with the I-MILES Tactical Vehicle System (TVS) lA W TCD-TVS OTA-001.

3.2.2 [NTERNAL SYSTEM INTERFACES

3.2.2.1 WIRELESS INTERFACE

There shall be no direct mechanical connection, including electrical wire links between the SAT, the halo and/or the harness.

a. The harness and SAT shall communicate via an infrared interface.

b. The harness and halo shall communicate via an inductive loop interface.

3.2.2.2 ORY FIRE TRIGGER TO SAT INTERFACE

The interface between the Dry Fire Trigger (DFT) and SAT is not required to be wireless.

3.2.2.3 DATA TRANSFER INTERFACE

I-MILES IWS 2 components shall interface and be compatible with Personal Digital Assistants (PDA), laptop computers or similar devices. The interface shall allow for upgrading software, modifying I-MILES IWS 2 characteristics, downloading events, and modifying vulnerability data (Pk table data).

Weapons

Legacy IWS Harnesses

All Existing

MILES Devices

I

Figure 1: I-MILES IWS Interfaces and Components

I-MILES IWS 2

Alignment Device Dry Fire Trigger

(OFT)

I-MILES IWS 2

SAT

I

I

I

TDTD Functionality (AAR, event download & SW updates)

I

Detection Unit •

I-MILES IWS 2

Halo

I-MILES IWS 2

Harness

Control/Display Unit

Instrumentation Systems

Legacy IWS Harnesses

All Existing / MILES Devices

Legacy IWS SATs

Legacy IWS Halo and

Surrogate Weapons

3.2.3 SYSTEM COMPONENTS

The I-MILES IWS 2 shall consist of the following components:

a. Small Arms Transmitter (SAT)

b. Detection Unit (halo, harness and control/display unit)

c. Ancillary Devices

I . Alignment Device

2. Dry Fire Trigger (OFT)

3. Training Data Transfer Device (TDTD)

4. After-Action Review (AAR)/Test Software

3.2.3.1 SAT

PRF-PT-00543, Rev B 02 April 2012

When an operator fires a weapon, the I-MILES I WS 2 SAT (laser unit) shall transmit MILES laser communication code IA W the MCC Standard. The SAT shall

a. Be capable of being fired by any individual with a MILES detection unit that is not in a kill casualty assessment mode.

b. Transmit the associated operator's unique PID, weapon and ammunition type.

c. Be disabled within a half of a second (0.5 seconds) when a kill assessment message has been received from the associated detection unit.

d. Transmit the MILES light weapon (Code 27) routine for the following weapon types:

l. Ml6A2/M4

2. M24

3. M240

4. MllO

5. M249 Squad Automatic Weapon (SAW)

e. Transmit the MILES heavy machine gun (Code 24) routine for the following weapon types:

I. Ml07

2. M2

3. M2Al

4. XM806 (Objective)

3.2.3.1.1 SAT PHYSICAL REQUIREMENTS

The following are the minimum requirements that the SA Ts shall meet:

a. The SA Ts shall be appended to weapon systems and shall not interfere with any tactical equipment on the weapon.

b. All SA Ts shall incorporate a Picatinny Rail attachment.

02 April 2012

c. Code 27 SAT shall be used for the light weapons (Ml 6A2/M4, M249, and M240).

d. Code 24 SAT shall be used for the heavy machine guns (M2, and M2A 1 ).

e. Sniper Weapon Systems shall have their own unique SA Ts.

f. A universal barrel clamp shall be required for light weapon SATs to mount on weapons where the Picatinny Rail is not available.

g. The SATs shall have no interconnecting cables to the other components of the I-MILES IWS 2 except the OFT.

h. The SA Ts shall provide the operator a visual indication that it has fired properly.

1. The SA Ts shall have no external power switches.

J. The SA Ts shall transmit the laser beam at a wavelength of 904.5 ± 25 nanometers.

k. The SA Ts shall meet the human factor requirements in paragraph 3 .3 .6 Human Engineering.

3.2.3.1.2 BLANK FIRE AND DRY FIRE

The SAT shall work with both blank fire and dry fire. The SAT shall:

a. Fire a laser transmission when activated by the firing of a blank.

b. Operate with blanks as a normal operating condition when mow1ted on a small arms weapon.

c. Have only one laser transmission per blank fired.

d. Have a dry fire mode of operation which is not dependent on blanks and not independently available to the operator.

e. Fire a laser transmission when manually activated in dry fire mode.

f. Not have any laser transmissions with the bolt action of the weapon.

3.2.3.2 DETECTION UNIT (HALO, HARNESS AND CONTROL/0ISPLA Y UNIT)

The detection unit shall be capable of being used with night vision goggles, the soft cap headgear and combat helmets (which include Personnel Armor System for Ground Troops Helmets, Advanced and Enhanced Combat Helmets). The detection units shall not interfere with the soldier's Light Forces Vest, load bearing equipment, Modular Lightweight Load-bearing Equipment, or Interceptor Body Annor. The detection units shall:

a. Associate v.,.ith Surrogate Weapon Systems (i.e.: AT-4) via inductive loops.

b. Associate with SATs wirelessly.

c. Utilize detectors with maximum response centered in the 904.5±25 nanometer range.

d. Pair throughout 360° of detection coverage in azimuth and± 45° of detection coverage in elevation off the centerline of the target.

e. Store and utilize in the casualty assessment the individual operator's PK values, with and without body armor. The assessment shall be a hit, kill or near-miss IA W the IWS PK tables in Appendix B.

f. Prevent the host system from assessing a self-kill from its own encoded laser transmission. The laser transmission is composed of the PIO, weapon type and ammunition type. The self-kill assessment shall be based on all three components of the laser transmission.

g. Be capable of being engaged by any MILES transmitter.

h. Meet the human factor requirements in paragraph 3.3.6 Human Engineering.

3.2.3.3 INTEROPERABILITY AND PAIRING PERFORMANCE

The I-MILES IWS 2 shall be tested for interoperability to the following SA Ts and Detection Units (see Table 1):

a. The test targets are I-MILES IWS, MILES 2000 IWS, the WITS (using the non-armored

- ITS Pk tables) and the I-MILES IWS 2 halo and harness detection unit.

b. The test SA Ts are the I-MILES TWS 2 SA Ts, I-MILES IWS and/or MILES 2000 IWS SATs.

Table 1: SATs versus Detection Units

SATs Detection Units

• I-MILES IWS

I-MILES IWS 2 SA Ts Versus

• I-MILES IWS 2

(Code 24 and Code 27) • MILES 2000 IWS

• WITS

I-MILES IWS SATs

(M2, M240, M16A2/M4, M249, M l IO, Versus • I-MILES IWS 2 M107)

MILES JWS 2000 SA Ts Versus I-MILES IWS 2

(M2, M240, MI6A2/M4, M249)

3.2.3.3.1 HIT (LASER BEAM) PROFILE

The statistical hit profile for the front, back and sides of the I-MILES IWS 2 shall consist of aim points that pair SA Ts with targets.

a. The SA T's laser beam shal.l project a laser beam onto a target conveying the Code 24 or Code 27 Weapon Routine laser information as specified in MCC Standard PMT 90-S002.

b. The detection unit shall be mounted such that a hit profile of an infantry soldier is created. Thus, when measured in the dry fire mode at 50% of the Weapon's effective range, the hit profile shall be larger than a circle with a diameter of 0.2 m, and fit inside a rectangle measming 2 m in the horizontal plane and 2.5 m in the vertical plane.

c. The detection unit's Near Miss Profile (when measured in the dry fire mode at 50% of the Weapon's effective range) shall be larger than the hit profile. The Near Miss profile shall be a minimum of I 0% and a maximum of 25% larger in all directions than the measured hit profile as an objective.

3.2.3.3.2 PAIRING PROBABILITIES

The SA Ts shall transmit engagement data encoded on the laser beam for shooter to target pairing. The weapons and their effective and suppression ranges are in Appendix A.

a. The I-Ml LES IWS 2 shall be capable of being used in all climates, geographical locations, environmental conditions and weather conditions. (See paragraph 3.2.13 Environmental Conditions)

b. A valid pairing shall include the correct decoding of the PID and the weapon/ammunition type.

c. Pairing requirements shall be IA W Table 2: Pairing Requirements for Effective Range and Table 3: Pairing Requirements for Suppression Range.

d. The aim point for the pairing test shall be the center of the target's profile.

3.2.3.3.2.1 MACHINE GUN PAIRING

For machine guns (M2, M240 and M249 ):

a. The firing mode shall be bursts with six to nine shots using three targets.

b. The targets shall be placed side-by-side with 1 ± 0 .1 m between the centers of each target.

c. An assessment indication on any of the targets is considered a pairing.

3.2.3.3.2.2 OTHER WEAPON PAIRING

For the other weapons listed in appendix A:

a. The firing mode shall be single shots using one target.

b. An assessment indication on the target is considered a pairing.

Table 2: Pairing Requirements for Effective Range

Weapons Assessment Effective Range -18 to 20 Indication (°C)

Ml6A2/M4, M24, M107, Ml 10 Hit or Kill 15%, 50%, 90% > 90%

M249, M240, M2 Hit or Kill 15%, 50%, 90% >80%

M24,M110, Ml07 Hit or Kill 170%

<25% (Roll-off) Roll-off

>20 to 30 >30 to 49 (°C) (°C)

> 95% > 90%

> 85% > 80%

<20% <25%

Table 3: Pairing Requirements for Suppression Range

Assessment Suppressive -18 to 20 >20 to 30 >30 to 49 Weapon

Indication Range (QC) (

C) (QC)

M249, M240 and M2 Hit, Kill or

90% > 80% > 85% >80% Near Miss

M249, M240 and M2 Hit or Kill 130%

<25% <20% <25% (Roll-oft) Roll-off

3.2.3.4 CONTROL/DISPLA V UNIT

The control/display unit shall provide operator functions, control functions and a display interface. The control unit shall:

a. Allow control and monitoring of the I-MILES IWS 2 device events and parameters.

b. Have an internal clock containing day, month, year, and time information which shall be able to be synchronized by controller devices. The internal clock shall:

1 . Be accurate within 30 seconds during a 96 hour period.

2. Display the date as DDMMMYYYY, where DD is Day, MMM is month, and YYYY is year.

3. Display time as xx:yy:zz-where xx represents hours (00-24), yy represents minutes, and zz represents seconds.

c. Store (Record) event data, administrative events, and Built-In Test (BIT) results with the host PID and time of occurrence. The event data fields shall include, at a minimum, the following:

1. Initiation events, to include power up, SAT association and BlT results.

2. Power down events.

3. Lethality assessment events.

a. Lethality assessment, to include hit, kill, and near miss

b. PID of attacker

c. Weapon and ammunition type

d. Determination of fratricide by comparison of shooter and target PlD

4. Cheat Events, to include tampering attempts and specific cheat information.

5. Administrative events, to include time synchronization, administrative kills, resurrect, reset, BIT failures (by type), low battery indications and other administration functions.

d. Retain all data regardless of system power status.

e. Have sufficient memory capacity to record, store and download the data of the last 500 events.

f. Retain PIDs and PK infom1ation in memory such that it shall be selectable by authorized perso1me1 upon power up as pari of initialization. The info1mation shall be able to be overwritten by downloading additional information from the data transfer interface.

g. Transfer event data to instrumentation systems.

h. Provide a means to detect player efforts to inhibit I-MILES IWS 2 equipment performance.

1. Whenever the player tampers with a11 I-MILES IWS 2 component to interfere with normal power supply, cable co1mections, detectors, or display unit; the system shall detect a tamper attempt and perform a kill on the I-MILES IWS 2.

2. The tamper attempt shall be stored in the event storage as a cheat kill.

1. Perfom1 a catastrophic kill at the time of system power up.

J. Meet the huma11 factor requirements in paragraph 3.3.6 Human Engineering.

3.2.3.4.1 OPERATOR FUNCTIONS

The display unit shall allow the operator to:

a. Display system status (Alive/Kil led).

b. Command a BIT.

c. Display weapon status.

d. Enable or disable weapons.

e. Display battery stan,s.

f. Display instrumentation status.

g. Adjust the back light.

h. Display events.

1. Activate an Operator Instrumentation "Ale1i" feature for emergencies which shall:

1. Self-kill the operator's harness with its own PIO.

2. Report a self-kill to IS (Exercise Control) when instrumented.

3. Prevent accidental activation by operator.

4. Provide an audible tone and visual message on the control/display unit.

5. Require the IS (Exercise Control or Exercise Operator/Controller (OC)) to reset it once it has been activated.

6. Not be sent if an operator has terminated the signal prior to the message being sent.

3.2.3.4.2 ADMINISTRATIVE CONTROL FUNCTIONS

02 April 2012

a. Administrative control functions shall not be independently available to the operator and require controller personnel interaction using the MILES "Controller Mode ON" command.

b. Required functions are listed in the MCC Standard PMT 90 S002, Appendix F.

c. Additional Administrative Control Functions required (but not limited to):

l . Manually select a PK table.

2. Modify the operator's PIO.

3. Modify the operator's ammunition type.

3.2.3.4.3 DISPLAY INTERFACE

a. At least 16 of the most recently recorded exercise events, administrative events, and BIT results shal I be displayed upon request.

b. Displayed events shall include the host PIO and time stamp.

c. Display shall be readable during both day and night conditions.

d. Messages shall be displayed (screens) for 7.5 ± 2.5 sec or until a key is depressed.

e. Display shall be readable at a distance of two feet from the display unit regardless of environmental conditions.

3.2.3.5 BIT CHARACTERISTICS

A BIT fault detection and locating system shall be provided to detect performance degradation and failures and provide Go/No-Go status for the I-MILES IWS 2. The BIT system shall:

a. Provide an assessment of overall system integ1ity in not more than one ( 1) minute upon command. The BIT shall occur:

1. When powering on the system (Power-On BIT).

2. When requested from the system operator (Manual BIT).

3. Every hour as an objective (Periodical BIT)

b. Diagnose problems and faults to at least the major component level (excluding transit cases).

c. Self-test the battery power level for immediate operation without the use of special tools or modification for I-MILES lWS 2 components that use batteries. This test shall be performed automatically upon battery insertion and shall notify the operator of the battery power status.

d. Function on-line, be entirely self-contained, and require no external measurement equipment.

e. Be displayed to the system operator when the system has completed an integrity checkout.

3.2.3.6 LETHALITY EFFECT ASSESSMENT ROUTINE (LEAR)

02 April 2012

The LEAR shall be initiated in response to a hit signal being received and decoded. The I MILES IWS 2 shall process the PID portion of each engagement message group for linkage with lethality assessment. In the event that only the MILES code portion of the message is decoded (no valid PlD is decoded) the detection unit shall still perform the casualty assessment.

3.2.3.6.1 KILL ASSESSMENTS EFFECTS

When a kill ( cheat or catastrophic) is assessed, the SAT shall be automatically disabled within 500 millisecond, inhibiting the transmission of the MILES message after receiving a kill message. Continuous audible tones shal I be generated for a minimum of five seconds. The maximum time shall be one minute unless the individual operator acknowledges the Kill indication, or the Harness bas been reset or resurrected. At two feet from the source, the tones shall be between 68 dB to 88 dB.

3.2.3.6.2 NEAR MISS EFFECTS

When a near miss is assessed, two audible tones at 68 dB to 88 dB shall be generated at two feet from the signal source. The tones shall be 0.65 sec.± .35 sec. in duration.

3.2.3.6.3 RESET

When a reset is assessed, the detection unit shall be returned to a fully operational state.

3.2.3.6.4 RESURRECTION

When a resurrection is assessed, the system shall be returned to a fully operational state with the SAT automatically re-associated to the detection unit.

3.2.3.6.5 CHEAT OR TAMPER

Tn the event of a Cheat Event or a Tamper Event, a kill shall be assessed.

3.2.4 ANCILLARY UNITS

3.2.4.1 ALIGNMENT DEVICES

The contractor shall provide a means of mounting and aligning the SA Ts to the weapon system sights within five (5) min or less with at least 264 hr alignment retention while expending 3,600 rounds per training exercise conditions. The SA Ts shall be capable of being aligned to the host weapon sights to allow the systems to perform as specified without interfering with tactical capabilities. The alignments shall be made by adj us ting the SAT and not the host weapon sights.

These requirements shall be e ffective regardless of whether the weapon is zeroed or not. Tf Alignment Device(s) are required, they shall not be permanently attached to the I-MILES IWS 2 components. The alignment device shall meet the human factor requirements in paragraph 3.3.6 Human Engineering.

3.2.4.2 DFT

02 April 2012

The DFT shall provide a single shot dry fire mode for pairing without firing blank ammunition.

The DFT shall be available to verify aligmnent of the SAT with the weapon sights and to test.

The DFT shall meet the human factor requirements in paragraph 3.3.6 Human Engineering.

3.2.4.3 TDTD REQUIREMENTS

The TDTD shall:

a. Within 3 minutes, upload/download information to/from a computer to initialize an I MILES JWS 2 with unique performance capabilities. The information shall include weapon type(s), MILES codes, PID, and vulnerability data commensurate with the system on which the I-MILES IWS 2 is installed.

b. Within 3 minutes, upload existing stored event data from a minimum of 25 devices at one time. As an objective, the TOTO shall be interoperable with existing MILES system and be used to download their events.

c. Upload a custom PK table from a computer system and download it to the I-MILES JWS 2.

d. Interface with a computer based device which allows software/data (examples are Pk tables or the AAR/test software) to be generated and manipulated.

e. Meet the human factor requirements in paragraph 3.3.6 Human Engineering.

f. Allow program software to be reloaded on the I-MILES IWS 2 components.

3.2.4.4 AAR/TEST SOFTWARE

The data shall be self-contained and readable as an event log using Microsoft programs (Access, Excel, Word, etc) Version 2007 or newer. A new application may be written that uses the above programs to clarify the data. The test software program shall accept all recorded event data and provide the following I-MILES lWS 2 test reports:

a. A list of each downloaded event records by time and date.

b. A list of all fratricide incidents and the associated PIDs.

c. A list of each of the downloaded lethality assessment events and the associated event information.

d. A list of each of the downloaded cheat events and the associated event information.

e. A list of each of the downloaded system's administrative events and the associated event.

f. The ability for the test operator to generate ad hoc reports using the downloaded data.

3.2.5 COMPUTATIONAL SYSTEM REQUIREMENTS

The I-MILES lWS 2 computational system shall consist of computer systems and system software. The system software consists of developed software, reused software, and commercial software. These software include application programs, suppo11 programs, and control programs.

3.2.5.1 COMPUTER SYSTEMS

02 April 2012

The computer systems shall consist of one or more commercial item processors and peripherals, interface hardware, controllers, and cables. Each processor shall have a word size, operating speed, installed memory, and bus bandwidth to fulfill the system requirements and spare capacity requirements of this Specification. Stored information shall be retained regardless of system power status The operational computer system(s) shall provide the following spare resources to allow for expansion and modification. Spare requirements shall be met during worst-case system operating conditions where maximum demands are placed on processors, memories, and input/output (I/O) channels. The required spare resources are as follows:

a. Spare memory. The system shall provide spare memory for each processor equal to 50% of the installed memory for that processor. Spare memory for any shared memory equal to 75% of the installed memory shall also be provided. All installed spare memory shall be directly addressable by the delivered processor and operating system.

b. Spare I/O capacity. The spare I/O channel tlu·oughput capacity shall equal or exceed 75% of the total installed I/O channel capacity.

3.2.5.2 SYSTEM SOFTWARE

Software developed under this Contract shall have been developed using modern software engineering methods, and using a commercial item programming language and compiler. All machine dependent code and compiler dependent code shall be logically grouped into separate packages with meaningful names. Adaptation of previously-developed or reused software to make it fully compliant with the MILES requirements shall also be accomplished using modern software engineering methods.

3.2.5.2.1 RUN TIME ENVIRONMENT

If used, the run time environment shall consist of a conm1ercial item real-time operating system.

3.2.5.2.2 FIRMWARE

Code or data which is stored in hardware devices (e.g., in a Programmable Read Only Memory) is software and shall be incorporated into the appropriate Computer Software Configuration Jtems (CSCI) with the same requirements as other software.

3.2.6 FALSE ALARM RATE

The I-MILES IWS 2 shall have a false alarm rate of not more than one false ala1111 per 100 hours of field operations for 100 I-MILES lWS 2.

3.2.7 INSTALLATION AND REMOVAL REQUIREMENTS

All I-MILES IWS 2 components shall be installed, operated, and removed without physical damage to or permanent modification of the host weapon system.

3.2.8 MOUNTING

02 April 2012

I-MILES IWS 2 components that are mounted shall be as transparent as possible to the individual. Mounting devices shall include all devices required to secure I-MILES TWS 2 components to the host platforn1. Fasteners manipulated by the soldiers in the field shall be of the captive type.

3.2.9 TRANSJT CASES

System level transit cases shall be used to protect I-MILES IWS 2 components during transportation, storage, and handling. Where practical, the cases shall hold all the components of one or more kits of a pm1icular configuration. The transit cases shall be built to comply with A TA SPEC 300, category I container. The transit case shall provide protected areas for attachment of all hardware. Top and bottom case surfaces shall be interlocking. Transit Cases shall be strong enough to stack 3 high in a storage environment. All transit cases requiring a two-person or higher lift shall have handles on all four sides. Transit cases shall have a data plate, inside the case, indicating type and amount of components stored within. A picture or line drawing shall be used to represent the layout of components.

3.2.10 PHYSICAL CHARACTERJSTICS

3.2.10.1 WEIGHT AND SIZE

All I-MILES IWS 2 component assemblies shall be transportable and maneuverable by one person. When assembled in their respective operating configuration, the weight and center of gravity of each system (and component) shall not exceed that prescribed by the lift and carry requirements nor shall they impede the carrying, movement and functioning abilities of the individual or crew in conducting training. Table 4: Maximum Component Weight provides the maximum weight with battery, that each component shall not exceed.

Table 4: Maximum Component Weight

COMPONENT

MAX WEIGHT

(LBS)

Code 24 SAT 1.0

Code 27 SAT 1.0

Code 27 Universal banel clamp 0.5

M2 Mounting Bracket Assembly 2.0

Ml 07 SAT (with bracket) 2.0

Mll0 SAT (v.,ith bracket) 1.0

Harness 2.5

Halo 0.5

3.2.l 0.2 POWER

02 April 2012

All I-MILES IWS 2 components shall have a self-contained power source. A commercially available power source shall be used. The components shall:

a. Not have an external power switch.

b. After receiving a low power indication, have a time delay of 2.5 ± .5 minutes before assessing a cheat kill when the power source is removed.

c. Provide a visual or audible low power indication for components as a threshold and both as an objective.

d. Provide a visual power level status.

e. Use the same batteries (Objective).

3.2.10.2.1 POWER OPERATION

The power supplies shall satisfy the following power operation requirements:

a. The SAT shall be powered by a power source which shall provide power for a minimum of 10,000 shots over a period of 336 hours (threshold) and 528 hours (objective) of field use before power source replacement is required.

b. The detection unit shall provide a minimum of 336 hours (tlu-eshold) and 528 hours (objective) of continuous operation without power source replacement, while sustaining at least 20 near miss assessments/day and 2 catastrophic kills/day.

c. The alignment device, if powered, shall provide a minimum of 100 hours of continuous operation without power source replacement, while performing 60 alignments/day.

d. The TDTD shall provide a minimum of 100 hrs of continuous operation while uploading/downloading data.

3.2.10.2.2 REPLACEABLE BATTERIES

All replaceable batteries shall take no more than two (2) minutes to replace. All repJaceable batteries shall be easily accessible to the operator without need for tools. All replaceable batteries shall be U.S. Army Communications-Electronics Command (CECOM) approved.

3.2.10.2.3 LONG-LIFE BATTERIES

Long-Life Batteries are batteries that shall power the system for at least two (2) years. All long life batteries shall take no more than ten minutes to replace. All long-life batteries shall be U.S.

Army Communications-Electronics Command (CECOM) approved. All long-life batteries shall be easily accessible to the operator without need for special tools. The 96 hr exercise is most frequently expected, and therefore shall be used as the Design Reference Mission Profile (DRMP), see Table 5: Design Reference Mission Profile per 96 Hr Exercise. Any given piece of Ml LES equipment is expected to be used the equivalent of fmiy-eight exercises a year that are 96 hr each, for a total of 4608 hr/yr.

Table 5: Design Reference Mission Profile per 96 Hr Exercise

Rounds Expended Number of Number of System/Platform Per 96 Hr Near Catastrophic

I-MILES IWS 2 Exercise Misses/Day Kills/Day

Code 27 SAT 3600 20 2

Code 24 SAT 3600 20 2

M24/Ml 10/M107 30 20 2

3.2.10.3 FINISH

All exterior surfaces ofl-MILES IWS 2 components shall be treated to resist corrosion or deterioration due to exposure to the elements.

3.2.10.4 COLOR

Selection of color for all surfaces shall be the low visibility, lusterless, non-reflective type. The color of the components shall be green, brown, or black, with the exception of surfaces required for the transmission or reception of electromagnetic signals.

3.2.10.5 TRANSPORTABILITY

Lift limits for devices shall be: One person (Male & Female - assuming 5 ft lift) - 3 7 pounds, Two-persons - 74 pounds, Tlu·ee-persons 101.75 pounds, Four-persons - 129.5 pounds. Devices exceeding one person lift limits shall be prominently labeled with the total weight and required number of handlers. I-MILES IWS 2 training devices, when packed in their transit cases, shall withstand damage due to stresses incidental to movement, handling in transit, and tie-down aboard common carrying vehicles such as aircraft or trucks.

3.2.11 RELIABILITY

Each I-MILES IWS 2 and Alignment Device shall have a minimum acceptable Mean Time Between Essential Functional Pai lure (MTBEFF) requirement of l 640 hours. The TOTO shall have a MTBEFF of 1900 hrs.

3.2.12 MAINTAINABILITY

The maximum acceptable Mean Time to Repair (MTTR) for each I-MILES IWS 2, alignment device and TOTO shall be 60 minutes or less. All equipment shall be easy to maintain and service with the minimum of personnel, material, parts, special tools and equipment.

3.2.13 ENVIRONMENT AL CONDITIONS

The I-MILES IWS 2 device, component parts and ancillary devices shall be assembled in their operational mode and powered on. They shall not be damaged and shall function correctly before, during and after they are subjected to the environmental conditions tailored from MIL-

STD-810G, described below. All components shaJJ be subject to the immersion test or the rain test.

3.2.13.1 HIGH TEMPERATURE

The I-MILES JWS 2 components, alignment device, TOTO and transit cases, shall comply with the following high temperature requirements, Method 505.5 Solar Radiation (Sunshine), Procedure 1 (Cycling for thermal effects.) and Method 501.5 High Temperature, Procedure 1 (Storage.). The maximum operational temperature shall be 49° C with a solar loading of 1120 W/m2, and a storage temperature with a maximum temperature of 71 ° C.

3.2.13.2 Low TEMPERATURE

The I-MILES IWS 2 components, alignment device, TOTO and transit cases, shall comply with the following low temperature requirements, Method 502.5 Low Temperature, Procedure 1 (Storage) and Procedure 2 (Operation). The minimum operational temperature shall be -I 8° C and the minimum storage temperature shall be -33° C.

3.2.13.3 SHOCK

The I-MILES IWS 2 components and TOTO shall comply with the following shock requirements, Method 516.6 Shock, Procedure I (Functional Shock.) Components in their transit cases shall comply with the following shock requirements, Method 516.6 Shock Procedure IV (Transit Drop) Table 516.6-VI Transit Drop Test.

3.2.13.4 VIBRATION

The I-MILES IWS 2 components, TOTO, transit cases and alignment device shall comply with the following vibration requirements: Method 514.6, Procedure 2, Vibration Category 5 (Loose Cargo).

3.2.13.5 HUMIDITY

The I-MILES IWS 2 components, TOTO, and alignment device shall comply with the following humidity requirements, Method 507.5 Humidity, Procedure 1 (Induced (Storage & Transit) and Natural and Cycles) Cycle B2, Figure 507.5-5 (Natural temperature B2 - Cyclic High Humidity) and Part One, Table C-1 of Part One Annex C. The components and alignment devices shall be subject to relative humidity conditions up to 100% humidity.

3.2.13.6 RAIN

The alignment device and transit cases shall comply with the following rain requirements, Method 506.5 Rain, Procedure I (Rain and blowing rain).

Rainfall rate:

Droplet size:

Wind velocity:

3.2.13.7 SAND AND DUST

4 in/hr

PRF-PT-00543, Rev B 02 April 2012

0.5 mm - 4.5 mm in diameter

40 mph

The I-MILES IWS 2 components, TDTD, alignment device, and transit cases shall comply with the following sand and dust requirements, Method 510.5 Sand and Dust, Procedure 1 (Blowing Dust) and Procedure II (Blowing Sand).

Blowing sand air velocity:

Sand concentration:

Blowing dust air velocity:

Dust concentration:

Dust composition:

3.2.13.8 IMMERSION

29 m/sec

1.1 ± 0.3 g/m3

8.9 ± 1.3 m/sec

10.6 ± 7 g/m3

Silicon Flour

The I-MILES IWS 2 components and TDTD shall comply with the following immersion requirements, Method 512.5 Procedure I-Basic Leakage. There shall be no evidence of water leakage when immersed in water to a depth of one meter.

3.2.13.9 CORROSION

The I-MILES IWS 2 components, TDTD, transit cases, ancillary and internal circuitry shall be treated to resist corrosion and deterioration due to condensation.

3.2.13.10 SALT FOG

All I-MILES IWS 2 components and TDTD exterior surfaces, including transit cases, sball comply with the following salt fog requirements, Method 509.5. Exposed surfaces shall exhibit no blistering, lifting of the coating system and substrate corrosion after being subjected to a 5% sodium chloride atomized spray.

3.3 CONSTRUCTION

3.3.1 MATERIAL AND PARTS

The I-MILES IWS 2 components shall maximize the use of commercial and non-developmental products.

3.3.2 ELECTROMAGNETIC RADIATION.

The equipment shall be electromagnetically compatible with itself such that system operational perfo1mance requirements can be met. All hardware intended for field use shall be Electromagnetic Compatible (EMC) with all other adjacent operating systems intended for field use. The equipment shall be electromagnetically compatible with the defined external Electromagnetic Envirom11ent (EME) such that system operational performance requirements shall be met. Inter-system EMC covers compatibility with, but is not limited to, the installation site EME, adjacent facilities and friendly emitters ( other MILES equipment (MILES 2000, MILES XXI, I-MILES), CB, UHF, VHF, cellular, etc.).

3.3.2.1 RADIATED EMISSIONS

The radiated emission limits of MIL-STD-461F, RE102, for electric fields, ground installed equipment, shall be met for the frequency range of ten kHz to 18 GHz. The I-MILES IWS 2 components and devices when operating shall not be a source of radiated emissions so as to create electromagnetic interference, malfunctions, degradation of performance, or deviations from operational parameters to adjacent operating electronic or electrical equipment.

3.3.2.2 RADIATED SUSCEPTIBILITY

The I-MILES IWS 2 components shall operate in the following radiated electrical field levels using MIL-STD-46lf, RS-103, without degradation in performance.

FREQUENCY RANGE

10 kHz - 2 MHz

ELECTRIC FIELD INTENSITY

20V/m

2 MHz- 30 MHz 50 V/m 30 MHz - 1 GHz 50 V/m

1 GHz - 18 GHz 50 v/m

3.3.2.3 ELECTROSTATIC DISCHARGE (ESD) EFFECTS

The I-MILES IWS 2 operator accessible electronic equipment and controls shall be designed to minimize degradation of performance when subjected to ESD. ESD EME (interior and exterior levels) shall be less than four ( 4) K v.

3.3.2.4 NON-DEVELOPMENTAL AND COMMERCIAL ITEMS

The Non-developmental and commercial items shall meet the Electromagnetic Environmental Effects (E3) requirements suitable for ensuring that the system's operational performance requirements are met.

3.3.2.5 LIFE CYCLE E

3 HARDNESS

The I-MILES IWS 2 equipment operational performance and E3 requirements shall be met throughout the rated life cycle of the equipment and shall include the following: maintenance, repair, surveillance, and corrosion control.

3.3.2.6 ELECTROMAGNETIC RADIATION HAZARDS (EMRADHAZ)

The equipment design shall protect personnel, fuels, and ordnance from any hazardous effects of electromagnetic radiation…