Attachment_0004_SURAC_Test_Evaluation_Master_Plan_Amendment_0006_25Jul2016.pdf

PDF 2 MB Posted Jul 25, 2016

Attached to: Subscriber Unit Radio and Accessory Contract (SURAC) Federal contract opportunity
Solicitation number: W52P1J-16-R-0073
Issued by: Department of the Army Materiel Command Joint Munitions Command

About this file

From the source

Attachment 0004 SURAC TEMP Amendment 0006

View the file

Other files for this federal contract opportunity

Other files attached to Subscriber Unit Radio and Accessory Contract (SURAC), newest first.
File	Type	Posted
W52P1J16R0073-0007.pdf	PDF	Jul 28, 2016
W52P1J16R0073-0006.pdf	PDF	Jul 25, 2016
Attachment_0002_Equipment_Submission_Form_Amendment_0006.docx	DOCX document	Jul 25, 2016
Attachment_0003_SURAC_Price_Matrix_Amendment_0006_25Jul2016.xlsx	XLSX spreadsheet	Jul 25, 2016
Attachment_0001_SURAC_Requirements_Statement_Amendment_0006.pdf	PDF	Jul 25, 2016
Attachment_0002_Equipment_Submission_Form_Amendment_0005.docx	DOCX document	Jul 8, 2016
W52P1J16R0073-0005.pdf	PDF	Jul 8, 2016
Attachment_0001_SURAC_Requirements_Statement_Amendment_0004.pdf	PDF	Jul 7, 2016
W52P1J16R0073-0004.pdf	PDF	Jul 7, 2016
W52P1J16R0073_P00003.pdf	PDF	Jun 28, 2016
Attachment_0003_SURAC_Price_Matrix_Amendment_0003.xlsx	XLSX spreadsheet	Jun 28, 2016
Attachment_0001_SURAC_Requirements_Statement_Amendment_0002.pdf	PDF	Jun 24, 2016
Attachment_0003_SURAC_Price_Matrix_Amendment_0002.xlsx	XLSX spreadsheet	Jun 24, 2016
W52P1J16R0073_P00002.pdf	PDF	Jun 24, 2016
Attachment_0006_SURAC_Solicitation_Questions_and_Answers_Amendment_0001.pdf	PDF	Jun 22, 2016
W52P1J16R0073P00001.pdf	PDF	Jun 22, 2016
Attachment_0003_SURAC_Price_Matrix_Amendment_0001.xlsx	XLSX spreadsheet	Jun 22, 2016
Attachment_0001_SURAC_Requirements_Statement_Amendment_0001.pdf	PDF	Jun 22, 2016
Attachment_0002_Equipment_Submission_Form.docx	DOCX document	Jun 3, 2016
Attachment_0005_SURAC_Test_Case_Scenarios_(A-E).pdf	PDF	Jun 3, 2016
Attachment_0001_SURAC_Requirements_Statement.pdf	PDF	Jun 3, 2016
W52P1J16R0073_Solicitation_03June2016.pdf	PDF	Jun 3, 2016
Attachment_0004_SURAC_Test_Evaluation_Master_Plan.pdf	PDF	Jun 3, 2016
Attachment_0003_SURAC_Price_Matrix.xlsx	XLSX spreadsheet	Jun 3, 2016

Show all 24

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Attachment 0004 SURAC Test Evaluation Master Plan – Amendment 0006, 25 July 2016

Product Lead Land Mobile Radio

(PL LMR)

Subscriber Unit Radio and Accessory Contract

(SURAC)

Test Evaluation Master Plan

25 July 2016

Change Log

Date Change

25 July 2016 Updated language in paragraph 9.1 and first bullet of paragraph 11.1.

Table of Contents

Executive Summary

1 Purpose

2 Background

3 Scope and Objective

4 Test Case Scenarios and Locations

Table 1 System Version Under Test

5 SURAC Equipment and Test Categories

Table 2 - First Responder (FR) Portable Subscriber Unit Tests

Table 3 - Non-First Responder (NFR) Portable Subscriber Unit Test

Table 4 - First Responder (FR) Mobile Subscriber Unit Test

Table 5 - Non-First Responder (NFR) Mobile Subscriber Unit Test

Table 6 - First Responder (FR) Desktop Subscriber Unit Test

Table 7 - Non-First Responder (NFR) Desktop Subscriber Unit Test

6 Government Assumptions

7 Offeror Required Test Equipment

8 Test Team Composition

9 APL Technical Acceptance

9.1 Step 1 – Identification of System Version, Radio Type, and OEM – Go/No Go

9.2 Test Scenario, Case and Script Development and Execution

9.3 Step 2 - Pre-Test Programming Platform Validation Procedures – Go/No Go

9.4 Subscriber Unit Test Date and Test Plan

9.5 Step 3 - Test Set-Up – Go/No Go

9.6 Step 4 - Interoperability Test Execution

10 Government Responsibilities

10.1 Government Pre-Test Responsibilities

10.2 Government Test Responsibilities

11 Offeror Responsibilities

11.1 Offeror Pre-Test Responsibilities

11.2 Offeror Test Responsibilities

12 Test Conduct

12.1 Test Documentation

12.2 Test Report

13 New Equipment Offerings and System Testing

Appendix A – Requirements Statement RADIO TYPE TABLES

Appendix A – Table 1 First Responder Portable

Appendix A – Table 2 Non First Responder Portables

Appendix A – Table 3 First Responder Mobile

Appendix A – Table 4 Non-First Responder Mobile

Appendix A – Table 5 First Responder Desktop

Appendix A – Table 6 Non First Responder Desktop

Appendix B – Radio Type and Test Correlation Tables

Appendix B – Table 1 First Responder Portable Correlation Table

Appendix B - Table 2 Non First Responder Portable Correlation

Appendix B – Table 3 First Responder Mobile Correlation

Appendix B – Table 4 Non First Responder Mobile Correlation

Appendix B – Table 5 First Responder Desktop Correlation

Appendix B – Table 6 Non First Responder Desktop Correlation

Appendix C – Sample Test Form

ATTACHMENTS A through E

List of Tables

Table 1 System Version Under Test

Table 2 - First Responder (FR) Portable Subscriber Unit Tests

Table 3 - Non-First Responder (NFR) Portable Subscriber Unit Test

Table 4 - First Responder (FR) Mobile Subscriber Unit Test

Table 5 - Non-First Responder (NFR) Mobile Subscriber Unit Test

Table 6 - First Responder (FR) Desktop Subscriber Unit Test

Table 7 - Non-First Responder (NFR) Desktop Subscriber Unit Test

SURAC TEMP Page 1

Executive Summary

The Subscriber Unit Radio and Accessory Contract (SURAC) Interoperability Test and

Evaluation Master Plan (TEMP) will serve as the overarching vehicle to qualify Offerors technically acceptable and approved Association of Public-safety Communications Officials

(APCO) Project (P25) standard radios for entry onto the Army Land Mobile Radio (LMR)

Approved Products List (APL). Offerors seeking to add radios to Army LMR APL will be required to test each radio type they plan to market for inclusion onto the Army LMR APL to prove radios are 100 percent interoperable with Harris system versions (6.2.1, 9, 10x) and

Motorola system versions (7.5, 7.7, 7.8, 7.11, 7.13, 7.14, 7.15). The SURAC Interoperability

TEMP identifies test case scenarios and test locations (current and past APCO P25 upgraded

Installations) where testing will occur under Government observation.

Offeror APCO P25 compliant radios shall have the ability to operate on LMR narrowband trunked communication systems, providing support for first responder (FR), base support personnel and interoperability capability for Mutual Aid supporters. Offeror proposed radios shall be new and not refurbished and have the capability to support LMR software based infrastructure in accordance with SURAC Requirements Statement.

SURAC TEMP Page 2

1 Purpose This plan describes interoperability testing in order to develop an Army LMR APL for the

SURAC. The plan contains APCO P25 and non-APCO P25 test case scenarios. Offeror subscriber units shall be tested by the Offeror on selected government test bed locations to determine technical compliance and acceptance to decrease risk and costs to Offerors not able to meet the requirements. Subscriber units must pass ALL applicable test criterion to be placed on the Army LMR APL.

2 Background LMR Subscriber units are currently procured as part of an overall system concept, with services that include project management, systems engineering, site preparation, equipment installation optimization, security implementation and acceptance testing. The SURAC program will provide a contract vehicle to purchase additional subscribers to bring subscriber unit inventories up to the levels commensurate with mission requirements.

3 Scope and Objective The SURAC contract will serve as a vehicle to make technically qualified/approved LMR subscriber unit products and services available to government agencies to support legacy and new LMR systems. Subscriber Unit (SU) products include portable, mobile and desktop subscriber units, and accessories. Subscriber units shall be capable of supporting United States and Possessions (US&P) DoD, federal, and non-federal LMR spectral allocations and channel plans in UHF, VHF or 700/800MHZ or a combination thereof. Test locations will consist of

Army Installations identified in Table 1 that have undergone P25 and narrowband upgrades.

The scope of this test plan is to test the functionality of Offeror’s P25 and non-P25 compliant subscriber unit features and functions using the system versions defined in Table 1 to demonstrate required level of interoperability. Testing shall demonstrate interoperability exists between current systems and offered subscriber units. Interoperability testing demonstrates the

Offeror’s ability to provide subscriber units compliant with all requirements identified in the

SURAC Requirements Statement. Proposed subscriber equipment shall meet all requirements identified within the SURAC Requirements Statement and pass test criterion to be deemed technically acceptable.

The form, fit and function of the equipment version may be technically equal between some SU radio versions. In order to decrease Offerors expense of testing all equipment, the offers will be given the opportunity to attest to the form, fit and function compatibility of versions that are technically compatible.

4 Test Case Scenarios and Locations The Army currently has nine (9) LMR system versions in operation worldwide with varying features and functions. To test interoperability in this environment, the test cases are organized in a series of test cases grouped in five categories: general, telephone interconnect, OTAR, SURAC TEMP Page 3

OTAP and AES1. Offerors shall develop detailed test scripts matching their proposed equipment to prove interoperability. PL LMR has tentatively identified test bed locations for each system version to be utilized to complete interoperability testing. Where possible, two locations have been identified; however, only one installation will be chosen for testing a particular system version. Table 1 identifies the current LMR system versions and locations designated for subscriber unit interoperability testing. This table may be updated as systems are upgraded and are provided here for guidance. The Army intends to pilot the demonstration/interoperability testing at Ft Belvoir, VA for two weeks, followed by a week for retrospective actions. This pilot demonstration/interoperability testing will be the official test for Harris System version 10X.

The remaining locations will be tested after the interoperability pilot in a schedule that will be provided to acceptable Offerors described in paragraph 9 of this document. Any changes to that schedule will be well communicated to all participants during the Ft Belvoir test.

Table 1 System Version Under Test

System

Version

Offeror Frequency Band Test Bed Installation

6.2.1 Harris 380-399.9 Fort Benning or Fort Leavenworth, KS.

SR9X Harris 380-399.9 Fort Polk, LA

SR10X Harris 380-399.9 Fort Belvoir, VA or Rock Island, IL

7.5 Motorola 406.1-420 Fort Bliss, TX

7.7/7.8 Motorola 380-399.9 Ft Bragg, AL or Anniston AD, AL

7.11 Motorola 380-399.9 Fort Lee, VA or Hunter-Liggett, CA

7.13 Motorola 380-399.9 (Gordon)

138-150.8 (Rucker) Fort Gordon, GA or Fort Rucker, AL

7.14 Motorola 380-399.9

Fort Campbell, KY or Detroit Arsenal, MI

7.15 Motorola 380-399.9 Radford, VA

5 SURAC Equipment and Test Categories Subscriber Units (SU) will be broken up into two categories: First Responder (FR) and Non-First

Responder (NFR) for each LMR system in operation. All SUs shall be tested to ensure interoperability with the system versions listed in Table 1 above and any new system versions added to the contract in the future. After award, an annual testing cycle will commence to capture system upgrades for awardees in the future. Tables 2 through 7 correspond to the radio types identified in the SURAC Requirements Statement. The test tables identify which category of tests are required for each radio type. Contractors may choose to test SUs only for specific

1 OTAR - Over the Air Rekeying, OTAP -Over the Air Reprogramming, AES - Advanced Encryption Standard

SURAC TEMP Page 4 system versions or for all system versions. Contractors may choose to test all radio types identified or just specific radio types for each system. All testing expenses will be borne by the

Offeror.

Table 2 - First Responder (FR) Portable Subscriber Unit Tests

Table 2 - First Responder Portable Subscriber Unit Tests

Radio

Type General OTAP

Telephone

Interconnect

AES

Encryption

OTAR

Portable 1

Attachment

Attachment C Attachment D Attachment E

Portable 2

Attachment

Attachment C Attachment D

Portable 3

Attachment

B Attachment D Attachment E

Portable 4

Attachment

A Attachment D Attachment E

Portable 5

Attachment

A Attachment D Attachment E

Portable 6

Attachment

B Attachment D

Portable 7

Attachment

A Attachment D

Portable 8

Attachment

A Attachment D

Portable 9

Attachment

Attachment C Attachment D Attachment E

Portable 10

Portable 11

Attachment D

Portable 12

Portable 13

Attachment

Portable 14

Attachment

B Attachment C Attachment D

Portable 15

Attachment

Attachment C Attachment D Attachment E

Portable 16

Attachment

Attachment C Attachment D

Portable 17

Attachment

B Attachment D Attachment E

Portable 18

Attachment

SURAC TEMP Page 5

Table 2 - First Responder Portable Subscriber Unit Tests

Radio

Type General OTAP

Telephone

Interconnect

AES

Encryption

OTAR

Portable 19

Attachment

A Attachment D Attachment E

Portable 20

Attachment

B Attachment D

Portable 21

Attachment

A Attachment D

Portable 22

Attachment

A Attachment D

Portable 23

Portable 24

Portable 25

Portable 26

Portable 27

Attachment

Attachment C Attachment D Attachment E

Portable 28

Attachment

Attachment C Attachment D

Portable 29

Attachment

Attachment C Attachment D Attachment E

Portable 30

Attachment

Attachment C Attachment D

Portable 31

Attachment

B Attachment D Attachment E

Portable 32

Attachment

A Attachment D Attachment E

Portable 33

Attachment

A Attachment D Attachment E

Portable 34

Attachment

B Attachment D

Portable 35

Attachment

A Attachment D

Portable 36

Attachment

A Attachment D

Portable 37

Portable 38

SURAC TEMP Page 6

Type General OTAP

Telephone

Interconnect

AES

Encryption

OTAR

Portable 39

Portable 40

Portable 41

Attachment

Attachment C Attachment D Attachment E

Portable 42

Attachment

Attachment C Attachment D

Portable 43

Attachment

Attachment C Attachment D Attachment E

Portable 44

Attachment

Attachment C Attachment D

Portable 45

Attachment

B Attachment D Attachment E

Portable 46

Attachment

A Attachment D Attachment E

Portable 47

Attachment

A Attachment D Attachment E

Portable 48

Attachment

B Attachment D

Portable 49

Attachment

A Attachment D

Portable 50

Attachment

A Attachment D

Portable 51

Portable 52

Portable 53

Portable 54

Portable 55

Attachment

Attachment C Attachment D Attachment E

Portable 56

Attachment

Attachment C Attachment D

Portable 57

Attachment

B Attachment D Attachment E

Portable 58

Attachment

SURAC TEMP Page 7

Type General OTAP

Telephone

Interconnect

AES

Encryption

OTAR

Portable 59

Attachment

A Attachment D Attachment E

Portable 60

Attachment

B Attachment D

Portable 61

Attachment

A Attachment D

Portable 62

Attachment

A Attachment D

Portable 63

Attachment

B Attachment D Attachment E

Portable 64

Attachment

A Attachment D Attachment E

Portable 65

Attachment

A Attachment D Attachment E

Portable 66

Attachment

B Attachment D

Portable 67

Attachment

A Attachment D

Portable 68

Attachment

Table 3 - Non-First Responder (NFR) Portable Subscriber Unit Test

Table 3 - Non-First Responder Portable Subscriber Unit Test

Radio Type General OTAP Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 1 Attachment

Attachment

C Attachment D

Attachment

NFR Portable 2 Attachment

Attachment

C Attachment D

NFR Portable 3 Attachment

Attachment

NFR Portable 4

NFR Portable 5

NFR Portable 6

NFR Portable 7

Attachment

B Attachment D

SURAC TEMP Page 8

Radio Type General OTAP Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 8 Attachment

A Attachment D

Attachment

NFR Portable 9 Attachment

A Attachment D

Attachment

NFR Portable 10 Attachment

Attachment

B Attachment D

NFR Portable 11 Attachment

A Attachment D

NFR Portable 12 Attachment

A Attachment D

NFR Portable 13

Attachment D

Attachment

NFR Portable 14

Attachment D

Attachment

NFR Portable 15

Attachment D

NFR Portable 16

Attachment D

NFR Portable 17

NFR Portable 18

NFR Portable 19

Attachment

C Attachment D

Attachment

NFR Portable 20 Attachment

NFR Portable 21

Attachment

C Attachment D

NFR Portable 22 Attachment

Attachment

NFR Portable 23

Attachment

C Attachment D

Attachment

NFR Portable 24 Attachment

Attachment

C Attachment D

NFR Portable 25 Attachment

Attachment

NFR Portable 26

NFR Portable 27

SURAC TEMP Page 9

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 28

NFR Portable 29

Attachment

B Attachment D

Attachment

NFR Portable 30 Attachment

A Attachment D

Attachment

NFR Portable 31 Attachment

A Attachment D

Attachment

NFR Portable 32 Attachment

Attachment

B Attachment D

NFR Portable 33 Attachment

A Attachment D

NFR Portable 34 Attachment

A Attachment D

NFR Portable 35

Attachment D

Attachment

NFR Portable 36

Attachment D

Attachment

NFR Portable 37

Attachment D

NFR Portable 38

Attachment D

NFR Portable 39

NFR Portable 40

NFR Portable 41

Attachment

C Attachment D

Attachment

NFR Portable 42 Attachment

NFR Portable 43

Attachment

C Attachment D

NFR Portable 44 Attachment

Attachment

NFR Portable 45

Attachment

C Attachment D

Attachment

NFR Portable 46 Attachment

Attachment

C Attachment D

NFR Portable 47 Attachment

Attachment

SURAC TEMP Page 10

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 48 Attachment

NFR Portable 49

NFR Portable 50

NFR Portable 51

Attachment

B Attachment D

Attachment

NFR Portable 52 Attachment

A Attachment D

Attachment

NFR Portable 53 Attachment

A Attachment D

Attachment

NFR Portable 54 Attachment

Attachment

B Attachment D

NFR Portable 55 Attachment

A Attachment D

NFR Portable 56 Attachment

A Attachment D

NFR Portable 57

Attachment D

Attachment

NFR Portable 58

Attachment D

Attachment

NFR Portable 59

Attachment D

NFR Portable 60

Attachment D

NFR Portable 61

NFR Portable 62

NFR Portable 63

Attachment

C Attachment D

Attachment

NFR Portable 64 Attachment

NFR Portable 65

Attachment

C Attachment D

NFR Portable 66 Attachment

Attachment

NFR Portable 67

Attachment

C Attachment D

SURAC TEMP Page 11

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 68 Attachment

Attachment

C Attachment D

NFR Portable 69 Attachment

Attachment

NFR Portable 70

NFR Portable 71

NFR Portable 72

NFR Portable 73

Attachment

B Attachment D

Attachment

NFR Portable 74 Attachment

A Attachment D

Attachment

NFR Portable 75 Attachment

A Attachment D

Attachment

NFR Portable 76 Attachment

Attachment

B Attachment D

NFR Portable 77 Attachment

A Attachment D

NFR Portable 78 Attachment

A Attachment D

NFR Portable 79

Attachment D

Attachment

NFR Portable 80

Attachment D

Attachment

NFR Portable 81

Attachment D

NFR Portable 82

Attachment D

NFR Portable 83

NFR Portable 84

NFR Portable 85

Attachment

C Attachment D

Attachment

NFR Portable 86 Attachment

NFR Portable 87

Attachment

SURAC TEMP Page 12

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable 88 Attachment

Attachment

NFR Portable 89

Attachment

C Attachment D

Attachment

NFR Portable 90 Attachment

Attachment

C Attachment D

NFR Portable 91 Attachment

Attachment

NFR Portable 92

NFR Portable 93

NFR Portable 94

NFR Portable 95

Attachment

B Attachment D

Attachment

NFR Portable 96 Attachment

A Attachment D

Attachment

NFR Portable 97 Attachment

A Attachment D

Attachment

NFR Portable 98 Attachment

Attachment

B Attachment D

NFR Portable 99 Attachment

A Attachment D

NFR Portable

Attachment

A Attachment D

NFR Portable

Attachment D

Attachment

NFR Portable

Attachment D

Attachment

NFR Portable

Attachment D

NFR Portable

Attachment D

NFR Portable

Attachment

C Attachment D

SURAC TEMP Page 13

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable

Attachment

C Attachment D

NFR Portable

Attachment

C Attachment D

Attachment

NFR Portable

Attachment

C Attachment D

NFR Portable

Attachment

B Attachment D

Attachment

NFR Portable

Attachment

A Attachment D

Attachment

NFR Portable

Attachment

A Attachment D

Attachment

NFR Portable

Attachment

B Attachment D

NFR Portable

Attachment

A Attachment D

NFR Portable

Attachment

A Attachment D

NFR Portable

Attachment D

Attachment

NFR Portable

Attachment D

Attachment

NFR Portable

Attachment D

NFR Portable

Attachment D

NFR Portable

SURAC TEMP Page 14

Telephone

Interconnect

AES

Encryption

OTAR

NFR Portable

Attachment

C Attachment D

Attachment

NFR Portable

Attachment

C Attachment D

NFR Portable

Attachment

Table 4 - First Responder (FR) Mobile Subscriber Unit Test

Table 4 - First Responder Mobile Subscriber Unit Test

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 1 Attachment

Attachment

B Attachment C

Attachment

FR Mobile 2 Attachment

Attachment

B Attachment C

FR Mobile 3

Attachment

FR Mobile 4

Attachment

FR Mobile 5 Attachment

FR Mobile 6

FR Mobile 7

A Attachment C

Attachment

FR Mobile 8 Attachment

A Attachment C

FR Mobile 9

Attachment

B Attachment C

Attachment

FR Mobile 10 Attachment

Attachment

B Attachment C

FR Mobile 11

Attachment

FR Mobile 12

SURAC TEMP Page 15

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 13 Attachment

FR Mobile 14

FR Mobile 15

A Attachment C

Attachment

FR Mobile 16 Attachment

A Attachment C

FR Mobile 17

Attachment

B Attachment C

Attachment

FR Mobile 18 Attachment

Attachment

B Attachment C

FR Mobile 19

Attachment

FR Mobile 20

Attachment

FR Mobile 21 Attachment

FR Mobile 22

FR Mobile 23

A Attachment C

Attachment

FR Mobile 24 Attachment

A Attachment C

FR Mobile 25

Attachment

B Attachment C

Attachment

FR Mobile 26 Attachment

Attachment

B Attachment C

FR Mobile 27

Attachment

FR Mobile 28

Attachment

FR Mobile 29 Attachment

FR Mobile 30

FR Mobile 31

A Attachment C

Attachment

FR Mobile 32 Attachment

A Attachment C

SURAC TEMP Page 16

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 33 Attachment

Attachment

B Attachment C

Attachment

FR Mobile 34 Attachment

Attachment

B Attachment C

FR Mobile 35

Attachment

FR Mobile 36

Attachment

FR Mobile 37 Attachment

FR Mobile 38

FR Mobile 39

A Attachment C

Attachment

FR Mobile 40 Attachment

A Attachment C

FR Mobile 41

Attachment

B Attachment C

Attachment

FR Mobile 42 Attachment

Attachment

B Attachment C

FR Mobile 43

Attachment

FR Mobile 44

Attachment

FR Mobile 45 Attachment

FR Mobile 46

FR Mobile 47

A Attachment C

Attachment

FR Mobile 48 Attachment

A Attachment C

FR Mobile 49

Attachment

B Attachment C

Attachment

FR Mobile 50 Attachment

Attachment

B Attachment C

FR Mobile 51

Attachment

FR Mobile 52

SURAC TEMP Page 17

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 53 Attachment

FR Mobile 54

FR Mobile 55

A Attachment C

Attachment

FR Mobile 56 Attachment

A Attachment C

FR Mobile 57

Attachment

B Attachment C

Attachment

FR Mobile 58 Attachment

Attachment

B Attachment C

FR Mobile 59

Attachment

FR Mobile 60

Attachment

FR Mobile 61 Attachment

FR Mobile 62

FR Mobile 63

A Attachment C

Attachment

FR Mobile 64 Attachment

A Attachment C

FR Mobile 65

Attachment

B Attachment C

Attachment

FR Mobile 66 Attachment

Attachment

B Attachment C

FR Mobile 67

Attachment

FR Mobile 68

Attachment

FR Mobile 69 Attachment

FR Mobile 70

FR Mobile 71

A Attachment C

Attachment

FR Mobile 72 Attachment

A Attachment C

SURAC TEMP Page 18

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 73 Attachment

Attachment

B Attachment C

Attachment

FR Mobile 74 Attachment

Attachment

B Attachment C

FR Mobile 75

Attachment

FR Mobile 76

Attachment

FR Mobile 77 Attachment

FR Mobile 78

FR Mobile 79

A Attachment C

Attachment

FR Mobile 80 Attachment

A Attachment C

FR Mobile 81

Attachment

B Attachment C

Attachment

FR Mobile 82 Attachment

Attachment

B Attachment C

FR Mobile 83

Attachment

FR Mobile 84

Attachment

FR Mobile 85 Attachment

FR Mobile 86

FR Mobile 87

A Attachment C

Attachment

FR Mobile 88 Attachment

A Attachment C

FR Mobile 89

Attachment

B Attachment C

Attachment

FR Mobile 90 Attachment

Attachment

B Attachment C

FR Mobile 91

Attachment

FR Mobile 92

SURAC TEMP Page 19

Telephone

Interconnect

AES

Encryption

OTAR

FR Mobile 93 Attachment

FR Mobile 94

FR Mobile 95

A Attachment C

Attachment

FR Mobile 96 Attachment

A Attachment C

FR Mobile 97

Attachment

B Attachment C

Attachment

FR Mobile 98 Attachment

Attachment

B Attachment C

FR Mobile 99

Attachment

FR Mobile 100

Attachment

FR Mobile 101 Attachment

FR Mobile 102

FR Mobile 103

A Attachment C

Attachment

FR Mobile 104 Attachment

A Attachment C

FR Mobile 105

Attachment

B Attachment C

Attachment

FR Mobile 106 Attachment

Attachment

B Attachment C

FR Mobile 107

Attachment

FR Mobile 108

Attachment

FR Mobile 109 Attachment

FR Mobile 110

FR Mobile 111

A Attachment C

Attachment

FR Mobile 112 Attachment

A Attachment C

SURAC TEMP Page 20

Table 5 - Non-First Responder (NFR) Mobile Subscriber Unit Test

Table 5 - Non-First Responder Mobile Subscriber Unit Test

Radio Type General OTAP Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 1 Attachment

Attachment

NFR Mobile 2 Attachment

Attachment

NFR Mobile 3

Attachment

NFR Mobile 4

NFR Mobile 5

NFR Mobile 6

Attachment

NFR Mobile 7

Attachment

NFR Mobile 8 Attachment

NFR Mobile 9

NFR Mobile 10

Attachment

NFR Mobile 11

NFR Mobile 12

NFR Mobile 13

Attachment

NFR Mobile 14 Attachment

Attachment

NFR Mobile 15

Attachment

NFR Mobile 16

NFR Mobile 17

NFR Mobile 18

Attachment

NFR Mobile 19

Attachment

NFR Mobile 20 Attachment

SURAC TEMP Page 21

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 21

NFR Mobile 22

Attachment

NFR Mobile 23

NFR Mobile 24

NFR Mobile 25

Attachment

NFR Mobile 26 Attachment

Attachment

NFR Mobile 27

Attachment

NFR Mobile 28

NFR Mobile 29

NFR Mobile 30

Attachment

NFR Mobile 31

Attachment

NFR Mobile 32 Attachment

NFR Mobile 33

NFR Mobile 34

Attachment

NFR Mobile 35

NFR Mobile 36

NFR Mobile 37

Attachment

NFR Mobile 38 Attachment

Attachment

NFR Mobile 39

Attachment

NFR Mobile 40

SURAC TEMP Page 22

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 41

NFR Mobile 42

Attachment

NFR Mobile 43

Attachment

NFR Mobile 44 Attachment

NFR Mobile 45

NFR Mobile 46

Attachment

NFR Mobile 47

NFR Mobile 48

NFR Mobile 49

Attachment

NFR Mobile 50 Attachment

Attachment

NFR Mobile 51

Attachment

NFR Mobile 52

NFR Mobile 53

NFR Mobile 54

Attachment

NFR Mobile 55

Attachment

NFR Mobile 56 Attachment

NFR Mobile 57

NFR Mobile 58

Attachment

NFR Mobile 59

NFR Mobile 60

SURAC TEMP Page 23

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 61 Attachment

Attachment

NFR Mobile 62 Attachment

Attachment

NFR Mobile 63

Attachment

NFR Mobile 64

NFR Mobile 65

NFR Mobile 66

Attachment

NFR Mobile 67

Attachment

NFR Mobile 68 Attachment

NFR Mobile 69

NFR Mobile 70

Attachment

NFR Mobile 71

NFR Mobile 72

NFR Mobile 73

Attachment

NFR Mobile 74 Attachment

Attachment

NFR Mobile 75

Attachment

NFR Mobile 76

NFR Mobile 77

NFR Mobile 78

Attachment

NFR Mobile 79

Attachment

NFR Mobile 80 Attachment

SURAC TEMP Page 24

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 81

NFR Mobile 82

Attachment

NFR Mobile 83

NFR Mobile 84

NFR Mobile 85

Attachment

NFR Mobile 86 Attachment

Attachment

NFR Mobile 87

Attachment

NFR Mobile 88

NFR Mobile 89

NFR Mobile 90

Attachment

NFR Mobile 91

Attachment

NFR Mobile 92 Attachment

NFR Mobile 93

NFR Mobile 94

Attachment

NFR Mobile 95

NFR Mobile 96

NFR Mobile 97

Attachment

NFR Mobile 98 Attachment

Attachment

NFR Mobile 99

Attachment

NFR Mobile 100

SURAC TEMP Page 25

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 101

NFR Mobile 102

Attachment

NFR Mobile 103

Attachment

NFR Mobile 104 Attachment

NFR Mobile 105

NFR Mobile 106

Attachment

NFR Mobile 107

NFR Mobile 108

NFR Mobile 109

Attachment

NFR Mobile 110 Attachment

Attachment

NFR Mobile 111

Attachment

NFR Mobile 112

NFR Mobile 113

NFR Mobile 114

Attachment

NFR Mobile 115

Attachment

NFR Mobile 116 Attachment

NFR Mobile 117

NFR Mobile 118

Attachment

NFR Mobile 119

NFR Mobile 120

SURAC TEMP Page 26

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 121 Attachment

Attachment

NFR Mobile 122 Attachment

Attachment

NFR Mobile 123

Attachment

NFR Mobile 124

NFR Mobile 125

NFR Mobile 126

Attachment

NFR Mobile 127

Attachment

NFR Mobile 128 Attachment

NFR Mobile 129

NFR Mobile 130

Attachment

NFR Mobile 131

NFR Mobile 132

NFR Mobile 133

Attachment

NFR Mobile 134 Attachment

Attachment

NFR Mobile 135

Attachment

NFR Mobile 136

NFR Mobile 137

NFR Mobile 138

Attachment

NFR Mobile 139

Attachment

NFR Mobile 140 Attachment

SURAC TEMP Page 27

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 141

NFR Mobile 142

Attachment

NFR Mobile 143

NFR Mobile 144

NFR Mobile 145

Attachment

NFR Mobile 146 Attachment

Attachment

NFR Mobile 147

Attachment

NFR Mobile 148

NFR Mobile 149

NFR Mobile 150

Attachment

NFR Mobile 151

Attachment

NFR Mobile 152 Attachment

NFR Mobile 153

NFR Mobile 154

Attachment

NFR Mobile 155

NFR Mobile 156

NFR Mobile 157

Attachment

NFR Mobile 158 Attachment

Attachment

NFR Mobile 159

Attachment

NFR Mobile 160

SURAC TEMP Page 28

Telephone

Interconnect

AES

Encryption

OTAR

NFR Mobile 161

NFR Mobile 162

Attachment

NFR Mobile 163

Attachment

NFR Mobile 164 Attachment

NFR Mobile 165

NFR Mobile 166

Attachment

NFR Mobile 167

NFR Mobile 168

Table 6 - First Responder (FR) Desktop Subscriber Unit Test

Table 6 - First Responder Desktop Subscriber Unit Test

Radio Type General OTAP Telephone

Interconnect

AES

Encryption

OTAR

FR Desktop 1 Attachment A Attachment

Attachment

FR Desktop 2 Attachment A Attachment

Attachment

FR Desktop 3 Attachment A

Attachment

FR Desktop 4 Attachment A Attachment

Attachment

FR Desktop 5 Attachment A

FR Desktop 6 Attachment A

FR Desktop 7 Attachment A

Attachment

FR Desktop 8 Attachment A Attachment

FR Desktop 9 Attachment A

Attachment

SURAC TEMP Page 29

Telephone

Interconnect

AES

Encryption

OTAR

FR Desktop 10 Attachment A Attachment

Attachment

FR Desktop 11 Attachment A

Attachment

FR Desktop 12 Attachment A Attachment

Attachment

FR Desktop 13 Attachment A

FR Desktop 14 Attachment A

FR Desktop 15 Attachment A

Attachment

FR Desktop 16 Attachment A Attachment

FR Desktop 17 Attachment A

Attachment

FR Desktop 18 Attachment A Attachment

Attachment

FR Desktop 19 Attachment A

Attachment

FR Desktop 20 Attachment A Attachment

Attachment

FR Desktop 21 Attachment A

FR Desktop 22 Attachment A

FR Desktop 23 Attachment A

Attachment

FR Desktop 24 Attachment A Attachment

FR Desktop 25 Attachment A

Attachment

FR Desktop 26 Attachment A Attachment

Attachment

FR Desktop 27 Attachment A

Attachment

FR Desktop 28 Attachment A Attachment

Attachment

FR Desktop 29 Attachment A

SURAC TEMP Page 30

Telephone

Interconnect

AES

Encryption

OTAR

FR Desktop 30 Attachment A

FR Desktop 31 Attachment A

Attachment

FR Desktop 32 Attachment A Attachment

FR Desktop 33 Attachment A

Attachment

FR Desktop 34 Attachment A Attachment

Attachment

FR Desktop 35 Attachment A

Attachment

FR Desktop 36 Attachment A Attachment

Attachment

FR Desktop 37 Attachment A

FR Desktop 38 Attachment A

FR Desktop 39 Attachment A

Attachment

FR Desktop 40 Attachment A Attachment

FR Desktop 41 Attachment A

Attachment

FR Desktop 42 Attachment A Attachment

Attachment

FR Desktop 43 Attachment A

Attachment

FR Desktop 44 Attachment A Attachment

Attachment

FR Desktop 45 Attachment A

FR Desktop 46 Attachment A

FR Desktop 47 Attachment A

Attachment

FR Desktop 48 Attachment A Attachment

FR Desktop 49 Attachment A

Attachment

SURAC TEMP Page 31

Telephone

Interconnect

AES

Encryption

OTAR

FR Desktop 50 Attachment A Attachment

Attachment

FR Desktop 51 Attachment A

Attachment

FR Desktop 52 Attachment A Attachment

Attachment

FR Desktop 53 Attachment A

FR Desktop 54 Attachment A

FR Desktop 55 Attachment A

Attachment

FR Desktop 56 Attachment A Attachment

FR Desktop 57 Attachment A

Attachment

FR Desktop 58 Attachment A Attachment

Attachment

FR Desktop 59 Attachment A

Attachment

FR Desktop 60 Attachment A Attachment

Attachment

FR Desktop 61 Attachment A

FR Desktop 62 Attachment A

FR Desktop 63 Attachment A

Attachment

FR Desktop 64 Attachment A Attachment

Table 7 - Non-First Responder (NFR) Desktop Subscriber Unit Test

Table 7 - Non-First Responder Desktop Subscriber Unit Test

Radio Type General OTAP Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 1 Attachment

Attachment

NFR Desktop 2 Attachment

Attachment

SURAC TEMP Page 32

Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 3 Attachment

Attachment

NFR Desktop 4

NFR Desktop 5

NFR Desktop 6

Attachment

NFR Desktop 7

Attachment

NFR Desktop 8 Attachment

NFR Desktop 9

NFR Desktop 10

Attachment

NFR Desktop 11

NFR Desktop 12

NFR Desktop 13

Attachment

NFR Desktop 14 Attachment

Attachment

NFR Desktop 15

Attachment

NFR Desktop 16

NFR Desktop 17

NFR Desktop 18

Attachment

NFR Desktop 19

Attachment

NFR Desktop 20 Attachment

NFR Desktop 21

NFR Desktop 22

Attachment

SURAC TEMP Page 33

Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 23

NFR Desktop 24

NFR Desktop 25

Attachment

NFR Desktop 26 Attachment

Attachment

NFR Desktop 27

Attachment

NFR Desktop 28

NFR Desktop 29

NFR Desktop 30

Attachment

NFR Desktop 31

Attachment

NFR Desktop 32 Attachment

NFR Desktop 33

NFR Desktop 34

Attachment

NFR Desktop 35

NFR Desktop 36

NFR Desktop 37

Attachment

NFR Desktop 38 Attachment

Attachment

NFR Desktop 39

Attachment

NFR Desktop 40

NFR Desktop 41

NFR Desktop 42

SURAC TEMP Page 34

Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 43

Attachment

NFR Desktop 44 Attachment

NFR Desktop 45

NFR Desktop 46

Attachment

NFR Desktop 47

NFR Desktop 48

NFR Desktop 49

Attachment

NFR Desktop 50 Attachment

Attachment

NFR Desktop 51

Attachment

NFR Desktop 52

NFR Desktop 53

NFR Desktop 54

Attachment

NFR Desktop 55

Attachment

NFR Desktop 56 Attachment

NFR Desktop 57

NFR Desktop 58

Attachment

NFR Desktop 59

NFR Desktop 60

NFR Desktop 61

Attachment

NFR Desktop 62 Attachment

Attachment

SURAC TEMP Page 35

Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 63 Attachment

Attachment

NFR Desktop 64

NFR Desktop 65

NFR Desktop 66

Attachment

NFR Desktop 67

Attachment

NFR Desktop 68 Attachment

NFR Desktop 69

NFR Desktop 70

Attachment

NFR Desktop 71

NFR Desktop 72

NFR Desktop 73

Attachment

NFR Desktop 74 Attachment

Attachment

NFR Desktop 75

Attachment

NFR Desktop 76

NFR Desktop 77

NFR Desktop 78

Attachment

NFR Desktop 79

Attachment

NFR Desktop 80 Attachment

NFR Desktop 81

NFR Desktop 82

Attachment

SURAC TEMP Page 36

Telephone

Interconnect

AES

Encryption

OTAR

NFR Desktop 83

NFR Desktop 84

NFR Desktop 85

Attachment

NFR Desktop 86 Attachment

Attachment

NFR Desktop 87

Attachment

NFR Desktop 88

NFR Desktop 89

NFR Desktop 90

Attachment

NFR Desktop 91

Attachment

NFR Desktop 92 Attachment

NFR Desktop 93

NFR Desktop 94

Attachment

NFR Desktop 95

NFR Desktop 96

6 Government Assumptions In an effort to streamline interoperability testing, the Army has made the following assumptions:

Frequency band will not impact test results. Offerors will test SU models in the band identified for each system. Therefore, both Ultra High Frequency (UHF) and Very High

Frequency (VHF) versions of each SU model will not be tested. However, all J/F 12 and ruggedized, submersible, Hazardous Location must be provided for each frequency band proposed.

SU models that pass the most comprehensive tests (AES, Telephone Interconnect, OTAR, and OTAP) do not need to be re-tested for different radio types requiring those

SURAC TEMP Page 37 features. For example, if an Offeror tests a First Responder (FR) Portable 1 (the most comprehensive) and passes all tests, that SU model does not need to be re-tested to be proposed for a less comprehensive radio need. Key pad differences will require testing each type of keypad proposed. A cross-reference of features correlation to tests is provided in Appendix B.

The form, fit and function of the equipment version may be technically equal between some SU radio versions. In order to decrease Offerors expense of testing all equipment, Offerors will be given the opportunity to provide a Certificate of Conformance for versions that are technically compatible.

A Desktop SU is the same as a Mobile SU. The Offeror will provide a Desktop SU for testing. That Desktop SU will be accepted for all Mobile SU testing of same features/functions for that specific model.

All parameters that have the possibility of impacting terminal equipment performance are set to values that will allow all vendor terminal products to be properly evaluated.

Ruggedized, Submersible, and Hazardous Location will not be tested. The Offeror shall provide documentation of successful factory testing of these features in order to be considered. Factory Mutual (FM) Intrinsically Safe (IS) or Underwriter Laboratories

(UL) “HazLoc” certification are acceptable.

Control heads have no impact on testing SU types.

7 Offeror Required Test Equipment Offerors are responsible for providing all equipment for the test, such as; subscriber units, programming platforms, cables and accessories to each testing location. Legacy subscriber units will be available for testing interoperability between proposed equipment and legacy systems.

All proposed radio types must be tested as described within the guidelines in the APL Technical

Acceptance section. Interoperability tests will require the following (at a minimum):

Each type of subscriber unit (including all accessories required for operation)

Key management (KVL/KMF)

Spare battery

Battery charger

Programming Platform, including interface cables

Desktop/Mobile Subscriber units (any required cabling and accessories)

Scanning tool (platform)

Removable media: CD or DVD (to dump setup scans). Flash media is not allowed.

8 Test Team Composition The Test Team shall consist of the following:

SURAC TEMP Page 38

PL LMR Lead

United States Army Information Systems Engineering Command Fort Detrick

Engineering Directorate (USAISEC-FDED) engineer(s)

Installation Network Enterprise Center (NEC)-LMR Administrator(s)

Cybersecurity Team (USAISEC)

No more than three Offeror Representatives at each location

9 APL Technical Acceptance Validation testing will be completed to ensure interoperability with the current system versions listed in Table 1 and consists of several steps.

9.1 Step 1 – Identification of System Version, Radio Type, and OEM – Go/No Go

The Offeror shall provide a technical proposal to the Army Contracting Command-Rock Island

(ACC-RI) Contracting team that contains a list of system versions and radio types. Radio type(s) identified shall correspond to the radio types described in the Requirements Statement. The

Offeror shall complete the Equipment Submission Form (Attachment 0002 of the RFP) for each radio version being proposed. Offerors shall fill in the CLIN number and description (as listed on the Price Matrix) in the first column, name of the proposed radio version in the second column, and a “Yes” in appropriate columns for the system version(s) that apply. Leave the column blank if the system version does not apply. In addition to completing the Equipment

Submission form, Offerors shall submit the following information for each subscriber model proposed as part of their technical proposal.

Inter-department Radio Advisory Committee (IRAC) document

J/F-12 and Spectrum Planning Subcommittee numbers

Approval to operate on all DoD LMR frequency bands (VHF/UHF). The Offeror shall provide a statement that summarizes the received approval (i.e. spectrum documentation) to operate on the DoD LMR frequency bands for each radio proposed. The statement shall include the radio nomenclature as identified on the spectrum documentation, the approved frequency ranges and emission designators.

For all proposed radio versions which have not received spectrum approval (Approval to operate on DoD frequencies), the Offeror shall submit a copy of the “Request to

Demonstrate” submitted to the Federal Communications Commission (FCC) for proposed equipment on a trunked system which identifies the locations and system versions affected. This copy shall indicate when the “Request to Demonstrate” was submitted to the FCC and to whom it was submitted.

Factory test documentation for ruggedized housing, submersible, Factory Mutual and

Hazardous Location (Haz Loc)

FIPS 140-2 Certification Number and version numbers

Any system specific information required by the Offeror for SU programming (i.e., system ID, WACN ID, Radio Serial Numbers, etc.) The Government will provide Talk

Group Names/Aliases to be used in Sections 9.2, 9.5 and 9.6 of the TEMP.

SURAC TEMP Page 39

Programming Software configuration needs for proposed equipment

Certificate of Conformance waiving interoperability testing on listed Radio Types and acceptance of actual damages if in error (if applicable). The Certificate of Conformance addresses the operation of the firmware and mandatory P25 features/functions for the radios that would be validated in Section 9.6 of the TEMP. The Certificate of

Conformance DOES NOT address performance covered by the Spectrum Approval process (i.e. JF-12, SPS, IRAC). All proposed radios must have Spectrum Approval or

FCC Approval to Demonstrate.

Offeror’s definition of identified Emission Designations

Offeror’s number of Talk Groups requested for Interoperability demonstration/testing should the Offeror proceed to testing

Written proof that they are an OEM of proposed LMR subscriber equipment or have and provide written proof of a business partnership or agreement, specifically for the SURAC effort, with a LMR subscriber equipment OEM.

If the documentation is complete and valid for the radio type proposed, the Offeror will receive a

“Go” decision from the Government and the Offeror will be provided information to scan the programming platform(s) and a test schedule. The validation is completed by reviewing the database of the IRAC/JF-12 and spectrum planning subcommittee numbers.

If documentation cannot be validated or is incomplete, the Offeror will receive a “No Go” decision and will not proceed to the next step of validation testing this cycle.

Note: Once an Offeror receives the “Go” decision to proceed to the next step, the Offeror cannot change or substitute radio types to be tested.

9.2 Test Scenario, Case and Script Development and Execution

As each Offeror may vary in how they meet the requirements, each Offeror receiving a “Go” decision from Step 1 shall develop detailed test scripts for each test case scenario needed for the radio type proposed. Test case scenarios are organized into attachments to this document:

General, OTAP, Telephone Interconnect, AES Encryption, and OTAR. Test scenarios and test cases are provided by the Government and contain APCO P25 and non-APCO P25 tests as well as integrated testing such as Patching, Simul-Select, Emergency Declaration, and Mutual Aid

Interoperability. Offerors shall modify these test case scenario documents by expanding them to identify each step needed to prove the test case scenario in a test script. Tests may require the interaction with the Offerors radios, local radios, and local consoles. Test Frequencies, test talk groups, and console operators will be provided by the Government where required. The Offeror must identify where this interaction is required when submitting test scripts. In addition to the test scripts, the Offeror shall matrix the test case scenarios, test cases, and test results into a Test

Completion Results document using the form in Appendix C.

SURAC TEMP Page 40

Test Case Scenarios need only be detailed into test scripts for those radio types proposed (e.g., if the Offeror is not testing OTAP, test scripts for OTAP test cases do not need to be provided).

Since the system configuration may impact the test script steps, the proposal will include a dry run of test scripts to give Offerors time to correct any test script errors. Please see section 9.4

Step 3 Test Set up for details regarding dry run tests. Once formal testing begins, the test scripts must be followed exactly as written during on site testing. If the test script is not followed exactly the test will be marked as failed, and the equipment will not be technically acceptable. The Offeror will not move to step 2 – Pre-Test Programming Platform

Validation Procedures for any test scripts that fail.

9.3 Step 2 - Pre-Test Programming Platform Validation Procedures – Go/No Go

All Offerors receiving a “Go” decision from Step 1 will undergo a preliminary cybersecurity screening. Each Offeror shall pre-scan the programming platform(s) while hardening the programming platform with the applicable programming software versions technical security controls, settings, and mitigation measures identified by the Department of Defense Instruction

(DoDI) 8500.2, AR 25-2 and Defense Information Systems Agency (DISA) Security Technical

Implementation Guides (STIG) prior to Security Compliance Assessment. In addition to the scan results, the Offeror shall provide the ACC-RI Contracting team with a document that lists all controls NOT implemented IAW the DoDI 8500.2, AR 25-2, and all current applicable DISA

STIGs. The document shall also provide justification as to why any technical security controls, settings, and mitigation measures were NOT applied.

The Offeror shall provide the results of the pre-scan, documentation of controls, and one programming platform to the ACC-RI Contracting team who will provide it to the Information

Systems Engineering Command (ISEC) Cybersecurity team. The Cybersecurity team will review the documentation provided and conduct an assessment of the programming platform. The

Offeror will receive a “Go/No Go” decision based on the assessment. To receive a “Go” decision the programming platform must be hardened with the applicable STIGS, meet technical needs and have favorable assessment results. Any Offeror who meets these standards and provides sound mitigation that does not compromise cybersecurity will receive a favorable assessment.

If a programming platform should not meet the standards referenced in the Requirements

Statement, the Offeror will receive a “No Go” decision and associated SU will not be technically acceptable and will not move forward to step 3.

9.4 Subscriber Unit Test Date and Test Plan

Offerors who receive a Step 2 - Pre-Test Programming Platform “Go” decision will be provided test dates and locations. Changes to the test date scheduled must be coordinated with Army

Contracting Command-Rock Island and may not be flexible. Should the Offeror not be able to meet a test date that cannot be moved, the Offerors will be deemed ineligible. Any Offeror who receives a “No-Go” will have the opportunity to demonstrate capability during an on-ramp cycle.

SURAC TEMP Page 41

9.5 Step 3 - Test Set-Up – Go/No Go

All Offerors receiving a “Go” decision from Step 2 will utilize the first day of testing to set up and conduct an on-site Information Assurance Security Engineering Directorate (ISAED), or

ISEC, Certification and Accreditation Toolset (ICAT) scan of the programming platform. The

ISEC engineer on-site will verify the configuration and observe the scan. Each Offeror will scan the programming platform and provide scan results via CD/DVD to the ISEC engineer on-site and the ACC-RI Contracting team. The ISEC engineer will send the scan results to the ISEC

Cybersecurity team to validate the scans with the system information gathered from the pre-test programming platform validation. The ISEC Cybersecurity team will send a “Go” or “No Go” decision within 48 hours to the on-site ISEC engineer who in turn will notify the ACC-RI

Contracting team who will send the “Go” or “No Go” decision to the Offeror.

To receive a “Go” decision, the on-site programming platform must match the baseline hardened during the Pre-Test Programming Platform Validation. If a “Go” is received, the Offeror may proceed immediately into a dry run of their detailed test scripts against the legacy system. The dry run affords each Offeror the opportunity to modify radio configuration and test scripts where the legacy system may impact the procedures. Local support staff will be available for consultation with all test participants throughout testing events, including the pre-test dry run.

Offerors may modify their detailed test scripts during the dry run. An electronic version and two hardcopies of the modified test scripts are deliverables that shall be provided to the on location

POC and an electronic version shall be provided to the ACC-RI Contracting team.

Offerors shall document any issues that arise that cannot be resolved via a test script or radio configuration change. If a configuration change is needed that does not violate the ATO for the platform, the ISEC engineer, Test Lead, and Contracting Officer may allow the configuration change and allow the test to continue. If a change is needed that violates the ATO, the Offeror will not be allowed to proceed. If a “No Go” is received, the Offeror will not be allowed to proceed with testing.

The Offeror shall scan, copy and provide electronic and hardcopies of any redlined test scripts to the Government prior to the commencement of the interoperability tests.

9.6 Step 4 - Interoperability Test Execution

The Government witnessed Interoperability Test shall include testing of all equipment and will be strictly based on the pass/fail criteria in the test procedures. If a test is successfully executed, that feature is deemed to be compliant and results in a Pass. Failed tests cannot be repeated or modified. If an Offeror’s item of equipment is deemed to be malfunctioning, and a duplicate item of equipment configured exactly the same is available to test, the test may be executed on that piece of Offeror’s equipment. Configuration of a replacement item will be validated by the

Government SME and/or ISEC engineer on site. If the test is successful on the duplicate equipment, the feature will be deemed compliant and results in a Pass. The Offeror will annotate on the test any situation when equipment is replaced.

SURAC TEMP Page 42

In test cases where more than one radio is required, an Offeror’s SU will be used as well as a legacy SU to test compatibility.

Any SU radio type which passes all required tests for that radio type will be technically acceptable.

Any issues found during testing will be recorded on the test form. Successful or failed execution of each test results in recording of initials from both the Offeror and Government witnesses.

10 Government Responsibilities The Government will be responsible for the following during the Pre-test and Testing.

10.1 Government Pre-Test Responsibilities

Validate SPS/IRAC/JF-12 documentation

Validate FIPS certification

Provide “Go/No Go” for Statement of Intent documentation (Step 1)

Provide the list of applicable test case scenarios and Test Correlation Tables

Provide cybersecurity scan configuration

Conduct programming platform assessment

Provide “Go/No Go” for pre-test programming platform assessment (Step 2)

Provide test date for each system and test location

Provide test location system…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Nov 14, 2017.