DEPARTMENT
OF THE ARMY
DEVELOPMENTAL TEST COMMAND
ELECTRONIC PROVING GROUNDS
ELECTRONIC COUNTERMEASURES
DIVISION (ECMD)
200 Arizona Street
Fort
Huachuca, Arizona 85364
DTC-EPG-ECMD
04 December 2006
MEMORANDUM
FOR RECORD
SUBJECT:
Interoperability Testing Procedures
1.
Purpose
To
provide guidance to Test Engineers, Technicians, Managers, Support Personnel
and Observers of the Electronic Countermeasures Division (ECMD) on the proper
implementation of Interoperability Testing Procedures
2.
Scope
These
procedures are applicable to all units and activities requesting support.
3.
Mission
The
ECMD provides Interoperability Testing services. Interoperability tests measure whether or not two SUTs can
operate given the interference inherent with the SUTs. Simply put, this test answers the
question how well do these SUTs play together.
4.
References
A. Joint IED Defeat Organization Joint
Test Board Interoperability Compatibility Test Protocol (U)
Interoperability/Compatibility Test Protocol 18 Sep 2006
B. Electronic Counter Measures Devices
Team Electronic Proving Ground (EPG) STANDARD OPERATING PROCEDURE SOP) 18 July 2006
C. Electronic Counter Measures Devices
Team Electronic Proving Ground (EPG) Configuration Management Schematics 23
July 2006.
D. Electronic Counter
Measures Devices Team Electronic Proving Ground (EPG) Data Collection
Spreadsheet Guide
5. Recommendations: If you have any recommended
changes to this SOP that could benefit ECMD, please send them to:
U.S.
Army Electronic Proving Ground (EPG)
Attention:
Fort
Huachuca, AZ 85613
Recommendations
received by this office will be reviewed and evaluated for possible inclusion
into future SOP updates, which will be published as needed.
1.
POC: James A. Bretney NewTec / EPG 520-559-6532; email:
james.a.bretney@epg.army.mil
.
6. Hours of Operation
Test
hours and test sites for Interoperability testing vary from test to test. The ECMD Task Lead decides the length
of the test day and the test location.
The ECMD Task Lead can be reached at:
ECMD
Task Lead 520-538-4854 DSN 879-4854
EPG
Test Officer 520-533-8166 DSN
879-8166
Website:
http://www.epg.army.mil/
7. Pre-Planning
The
Task Lead receives a copy of the test plan from EPG Test Officer, coordinates
test support personnel and test site management with Yuma Proving Grounds (YPG)
and provides a copy of the test plan to the Test Engineer. At that time and throughout the test,
the Test Engineer can ask questions expectations he can meet, what the
standards are for pass or failure and any additional reporting requirements.
The
Test Engineer will draw up a list of necessary test equipment and supplies to
complete the test given the requirements of the test plan. He then coordinates with the ECMD
Logistics team and verifies the serviceability and availability. The Test Engineer looks at the program
load and either designs or identifies software files for the Spectrum Analyzer,
Oscilloscope or Signal Generator.
If
the mission allows, the Test Engineer will then draw up a Threat matrix. A Threat Matrix gives the test team a
sense of their progress by matching SUT combinations against threats.
|
Threats
|
|
|
A
|
See Plan
|
|
B
|
See Plan
|
|
C
|
See Plan
|
|
D
|
See Plan
|
Chart
1 (An Example of a Threat Chart)
|
SUT
|
|
|
1
|
See Plan
|
|
2
|
See Plan
|
|
3
|
See Plan
|
|
4
|
See Plan
|
|
5
|
See Plan
|
Chart
2 (An Example of a SUT Chart)
|
|
SOURCE
|
|||||||||||
|
1
|
2
|
3
|
4
|
5
|
||||||||
|
V
I
C
T
I
M
|
1
|
A
|
C
|
A
|
C
|
A
|
C
|
A
|
C
|
A
|
C
|
|
|
B
|
D
|
B
|
D
|
B
|
D
|
B
|
D
|
B
|
D
|
|||
|
2
|
A
|
C
|
|
|||||||||
|
B
|
D
|
|||||||||||
|
3
|
A
|
C
|
||||||||||
|
B
|
D
|
|||||||||||
Chart
3 (An Example of a Threat Matrix)
The
Test Engineer will look at threats and match them against the program load
specified in the test plan. The
Test Engineer will see if the manufacturer has programmed the SUT defeat the
threats. The Test Engineer will eliminate
those threats the SUT cannot defeat and annotate which threats that Test
Engineer has determined can not be tested.
|
|
|
Month
|
Year
|
|
|
|
|
Sunday
|
Monday
|
Tuesday
|
Wednesday
|
Thursday
|
Friday
|
Saturday
|
|
|
11
Day 1
1-2-A
|
12
Day 2
1-2-B
1-2-C
|
13
Day 3
1-2-D
|
14
Day 4
2-1-A
2-1-B
|
15
Day 5
2-1-C
2-1-D
|
16
Day 6
FLEX
|
|
17
|
18
Day 7
1-1-A
|
19
Day 8
1-1-B
1-1-C
|
20
Day 9
1-1-D
|
21
Day 10
1-3-A
1-3-B
|
22
Day 11
1-3-C
1-3-D
|
23
Day 12
FLEX
|
|
24
|
25
|
26
Day 13
3-1-A
|
27
Day 14
3-1-B
3-1-C
|
28
Day 15
3-1-D
|
29
Day 16
4-1-A
4-1-B
|
30
Day 17
FLEX
|
Chart
4 (An Example of a Tentative Schedule)
If
the mission allows, the Test Engineer will form a tentative schedule. Using the threat matrix as a guide and
placing some flex days in between, the Test Engineer will have a reasonable
expectation of the execution of the test plan is progressing.
If
the mission allows, the Test Engineer will draw up a tentative day 1 schedule. An example can be seen below:
|
|
Day 1
|
|
|
|
Task
|
|
|
Hour
|
Technician
|
Test
Engineer
|
|
1.00
|
Arrive on Site/ Environmental Scan
|
Arrive on Site/ Account for Equipment/ Supervise/
Coordinate/ Begin Report
|
|
1.25
|
Safety Brief
|
Safety Brief
|
|
1.50
|
Program Spec A
|
Threat CM
|
|
1.75
|
OTA
|
Install In Vehicle EME
|
|
2.00
|
Closed Loop
|
Install In Vehicle EME
|
|
2.25
|
Closed Loop
|
|
|
2.50
|
Closed Loop
|
|
|
2.75
|
VSWR
|
|
|
3.00
|
Pull Trace
|
Pull Trace
|
|
3.25
|
Program Spec A
|
Program Spec A
|
|
3.50
|
OTA
|
|
|
3.75
|
Closed Loop
|
|
|
4.00
|
Closed Loop
|
|
|
4.25
|
Closed Loop
|
|
|
4.50
|
VSWR
|
|
|
4.75
|
Pull Trace
|
Pull Trace
|
|
5.00
|
Set up IVS
/ Test IVS
|
|
|
5.25
|
Final Calibration
|
Begin Testing
|
|
5.50
|
Update Database
|
Threat Outbound
|
|
5.75
|
|
Threat Outbound
|
|
6.00
|
|
Threat Outbound
|
|
6.25
|
|
Threat Outbound
|
|
6.50
|
|
Threat Inbound
|
|
6.75
|
|
Threat Inbound
|
|
7.00
|
|
Threat Inbound
|
|
7.25
|
|
Threat Inbound
|
|
7.50
|
Post Target CM
|
End Testing
|
|
7.75
|
Pre Target CM
|
Begin Testing
|
|
8.00
|
Pull Trace
|
Threat Outbound
|
|
8.25
|
|
Threat Outbound
|
|
8.50
|
Post Target CM
|
Threat Outbound
|
|
8.75
|
Pull Trace
|
OTA
|
|
9.00
|
|
Pull Trace
|
|
9.25
|
|
OTA
|
|
9.50
|
|
Pull Trace
|
|
9.75
|
|
Environment Scan / Pull Trace
|
|
10.00
|
Off Site
|
Off Site
|
Chart
5 (An Example of a Day 1 Schedule)
The
Test Engineer will create files and folders in support of his data collection
and data management. The Test Plan
tasks the Test Engineer to track threat data, Configuration Management (CM),
Interoperability Data and Environmental scans
Throughout
the course of the test, the Test Engineer and the Technician will take target
traces from the handheld spectrum analyzer [see Paragraph 12 thru 15 of the Electronic
Counter Measures Devices Team Electronic Proving Ground (EPG) STANDARD
OPERATING PROCEDURE (SOP)].
It is the Test Engineer’s responsibility to ensure the test team
properly collects and stores this data.
The Test Engineer tracks threat (or target) data by construction a
threat database and using FSHVIEW the handheld spectrum analyzer’s interface
software.
The
Test Engineer must create spreadsheets (See Electronic Counter Measures Devices
Team Electronic Proving Ground (EPG) Data Collection Spreadsheet Guide) to track the proper CM of each SUT. The Test Engineer must look for CMs
of each SUT to build his own files. In other words, the Test Engineer needs
a reference point before he even starts to CM each SUT. The program load gives the Test
Engineer a rough idea what the CM of a particular SUT would look like. However, the results from other tests
serve as the best guides for
reference points.
|
Table 1 Interoperability Test Spreadsheet
|
|||||||
|
Title: (SUT
Name) Interoperability
|
|||||||
|
(Victim SUT) vs
(Threat Name) – (Frequency) MHz
|
|||||||
|
Date
|
|
Start Time
|
|
Stop Time
|
|
|
|
|
Source
|
(Source Name)
|
Victim
|
(Victim Name)
|
Outbound
|
<-----
|
----->
|
RX
|
|
S-V dist
|
S-T dist
|
T
|
TV
|
TVS
|
TS
|
T
|
IVS
|
|
10
|
60
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
|
20
|
70
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
|
30
|
80
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
|
Source
|
(Source Name)
|
Victim
|
(Victim Name)
|
Outbound
|
----->
|
----->
|
RX
|
|
S-V dist
|
S-T dist
|
T
|
TV
|
TVS
|
TS
|
T
|
IVS
|
|
30
|
80
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
|
20
|
70
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
|
10
|
60
|
10/10
|
0/10
|
0/20
|
10/10
|
10/10
|
10,10,10,10
|
Chart
6 An Example of the Interoperability Spreadsheets
The
Test Engineer has see that the excel spreadsheets used to capture
interoperability data and daily environmental scans are in place. The
Environmental Scans can be captured by using the Electronic Counter Measures
Devices Team Electronic Proving Ground (EPG) Data Collection Spreadsheet.
If
the files do not exist on the Spectrum Analyzer provided on site, then The Test
Engineer must program the Spectrum Analyzer for both CMs and injected Victim
Signals runs or IVS runs. The Test
Engineer must create or ensure the
CM files such as the VSWR, OTA and Closed Loop (CL) are loaded into the
Spectrum Analyzer.
No comments:
Post a Comment