1_DSO-SD-16-051_T3747-1_AWS-3_EEP_v2.3_System_Requirements_Specification_Rev2_29_June_2017.pdf

Defense Information Systems Agency

Defense Spectrum Organization

Strategic Planning Office

Annapolis, Maryland 21402

Software Document

Advanced Wireless Services-3 Early Entry Portal v2.3

System Requirements Specification

DSO-SD-16-051

15 June 2017

Prepared for:

Strategic Planning Office 2004 Turbot Landing

Annapolis, MD 21402-5064

Prime Contractor

Harris Corporation 141 National Business Parkway, Suite 200

Annapolis Junction, MD 20701

Distribution authorized to DoD Components only; Operational Use; June 2017. Other requests shall be referred to the DSO.

AWS-3 Early Entry Portal v2.3 System Requirements Specification

Defense Spectrum Organization ii

This report was prepared by Harris Corp. under Contract HC1047-07-D-0001 in support of the

Defense Information Systems Agency, Defense Spectrum Organization Directorate.

This report has been reviewed by the following Harris Corp. personnel:

LYNN CUMBERPATCH

Program Manager, Harris Corp.

ALEXANDRA FINKLER

Chief Software Engineer, Harris Corp.

This report is approved for publication by the following Government personnel:

HOWARD J. MCDONALD ROBERT L. SCHNEIDER

Chief, Advanced Access Initiatives Branch Technical Director

Strategic Planning Division Defense Spectrum Organization

Defense Spectrum Organization iii

REPORT DOCUMENTATION PAGE

Form Approved

OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN

YOUR FORM TO THE ABOVE ADDRESS.

1. REPORT DATE (MM-YYYY) 2. REPORT TYPE 3. DATES COVERED (From - To)

06-2017 Software Document

4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER

Advanced Wireless Services-3 Early Entry Portal v2.3 System Requirements Specification

HC1047-07-D-0001

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

Harris Corp. 3747-1 Project Team T3747-1 5e. TASK NUMBER

TO-1110

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION REPORT NUMBER Harris Corp.

141 National Business Parkway, Suite 200 Annapolis Junction, MD 20701

9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

Strategic Planning Office 2004 Turbot Landing Annapolis, MD 21402-5064

DSO/SPO

11. SPONSOR/MONITOR’S REPORT

NUMBER(S)

12. DISTRIBUTION / AVAILABILITY STATEMENT

Distribution authorized to DoD Components only; Operational Use; June 2017. Other requests shall be referred to the DSO.

13. SUPPLEMENTARY NOTES

14. ABSTRACT

The Advanced Wireless Services (AWS)-3 Early Entry Portal (EEP) is being designed and developed to facilitate the coordination of early entry of commercial users into the 1755 – 1780 MHz band while protecting the Government stations currently operating in the band during and after the transition period. This document specifies the system requirements for the

AWS-3 EEP.

15. SUBJECT TERMS

Advanced Wireless Services-3, AWS-3, Coordination Portal, Early Entry Portal, EEP, Frequency Assignment, Spectrum Auction, Spectrum Management

16. SECURITY CLASSIFICATION OF: 17. LIMITATION

OF ABSTRACT

18. NUMBER

OF PAGES

19a. NAME OF RESPONSIBLE JSC PERSON

a. REPORT b. ABSTRACT c. THIS PAGE Christopher Johnson

U U U SAR 36

19b. TELEPHONE NUMBER

301-225-3819

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std. Z39.18

Defense Spectrum Organization iv

This page intentionally left blank.

Defense Spectrum Organization v

Record of Changes

Change

Number Date

Section

Number Description Modified By

1 10/26/2016 N/A Updated with Harris logo and company name throughout document

J. Valentine

2 10/26/2016 2.4 GUI-03: Updated DoD supported versions of browsers from Internet

Explorer v10.0, Google Chrome v35.0, and Mozilla Firefox v32.0 to

Internet Explorer v11.0, Google

Chrome v51.0, and Mozilla Firefox v45.2

J. Valentine

3 5/5/2017, 6/15/2017

2.1 High-level requirements added: HL-

29, HL-29.1, HL-31, HL-32, HL-33,

HL-34, HL-35

J. Valentine

3 5/5/2017 2.4 User Interface Requirement: GUI-03:

Updated DoD supported versions of browsers: Google Chrome v51.0, Mozilla Firefox v53.0, and Edge 40

J. Valentine

3 5/5/2017 2.5 Personnel Requirement added: PR-

01.1, PR-02.1

J. Valentine

3 5/5/2017, 6/15/2017

3.1.1 AWS-3 Licensee Portal Access

Requirements added: AWS-01.1, AWS-01.2, AWS-02.1, AWS-03.1, AWS-04.1, AWS-04.2, AWS-09.1, AWS-09.2, AWS-10

J. Valentine

3 5/5/2017, 6/15/2017

3.1.2 DoD Spectrum Manager Portal

Access Requirements added: SMO-

03.1, SMO-04.1, SMO-05.1, SMO-

08, SMO-08.1, SMO-09

J. Valentine

3 6/15/2017 3.1.3 DSRMT Portal Access Requirement added: DSRMT-09

J. Valentine

3 5/5/2017 3.1.6 Federal Spectrum Manager Portal

Access Requirements added: FED-07

J. Valentine

3 5/5/2017 3.1.7 SATOPS Spectrum Manager Portal

Access Requirements added:

SATOPS-06

J. Valentine

3 5/5/2017 3.2 Portal Operational Requirements added: OPS-01.2, OPS-02.2, OPS-

04.2, OPS-05.1, OPS-06.2, OPS-

09.2, OPS-10.2, OPS-11.2, OPS-

12.2, OPS-13.2

J. Valentine

3 5/5/2017 3.3 Portal Database Requirements added:

DB-01.2, DB-02.2, DB-03.2, DB-

04.1

J. Valentine

Defense Spectrum Organization vi

Defense Spectrum Organization vii

Table of Contents

1. INTRODUCTION

1.1 BACKGROUND

1.2 SYSTEM OVERVIEW

1.2.1 System Objectives

1.2.2 System Scope

1.3 DOCUMENT OVERVIEW

1.3.1 Purpose

1.3.2 Scope

1.3.3 Intended Audiences

1.4 ASSUMPTIONS AND LIMITATIONS

2. GENERAL SYSTEM REQUIREMENTS

2.1 HIGH-LEVEL REQUIREMENTS

2.2 EXTERNAL INTERFACE REQUIREMENTS

2.3 INFORMATION ASSURANCE REQUIREMENTS

2.4 GENERAL USER INTERFACE REQUIREMENTS

2.5 PERSONNEL REQUIREMENTS

2.6 PORTAL PERFORMANCE REQUIREMENTS

3. FUNCTIONAL REQUIREMENTS

3.1 PORTAL ACCESS REQUIREMENTS

3.1.1 AWS-3 Licensee Portal Access Requirements

3.1.2 DoD Spectrum Manager Portal Access Requirements

3.1.3 Spectrum Engineer Portal Access Requirements

3.1.4 DSRMT Portal Access Requirements

3.1.6 System Administrator Portal Access Requirements

3.1.7 Federal Spectrum Manager Portal Access Requirements

3.1.8 SATOPS Spectrum Manager Portal Access Requirements

3.2 PORTAL OPERATIONAL REQUIREMENTS

3.3 PORTAL DATABASE REQUIREMENTS

4. REFERENCES

5. ACRONYMS

Defense Spectrum Organization viii

Defense Spectrum Organization ix

List of Tables

Table 2-1. Requirement ID and Description Table 2-2. Requirement Source and Description Table 2-3. High-Level Requirements Table 2-4. External Interface Requirements Table 2-5. Information Assurance Requirements

Table 2-6. General User Interface Requirements Table 2-7. Personnel Requirements Table 2-8. Portal Performance Requirements Table 3-1. AWS-3 Licensee Portal Access Requirements Table 3-2. DoD Spectrum Manager Portal Access Requirements

Table 3-3. Spectrum Engineer Portal Access Requirements

Table 3-4. DSRMT Portal Access Requirements

Table 3-5. System Administrator Portal Access Requirements Table 3-6. Federal Spectrum Manager Portal Access Requirements

Table 3-7. SATOPS Spectrum Manager Portal Access Requirements Table 3-8. Portal Operational Requirements

Table 3-9. Portal Database Requirements

Defense Spectrum Organization x

Defense Spectrum Organization 1

1. INTRODUCTION

1.1 BACKGROUND

The Federal Communications Commission (FCC) has reallocated the 1755 – 1780 MHz band for use by commercial entities (Amendment of the Commission’s Rules with Regard to

Commercial Operations in the 1695 – 1710 MHz, 1755 – 1780 MHz, and 2155 - 2180 MHz

Bands [1]) and completed its auction of Advanced Wireless Services (AWS)-3 licenses.

The Services and the Defense Information Systems Agency’s Defense Spectrum

Organization (DSO) have developed transition plans for their respective organizations to facilitate increasingly less-restrictive sharing arrangements for early entry of commercial

AWS systems and permanent sharing between the Department of Defense (DoD) and commercial systems operating in the 1755 – 1780 MHz band.

The FCC and the National Telecommunications and Information Administration (NTIA) issued Public Notice DA 14-1023, Coordination Procedures in the 1695 – 1710 MHz and

1755 – 1780 MHz Bands [2], which specified the procedures to be followed in allowing early entry into this band by the AWS-3 licensees as well as ongoing coordination that would continue to be applicable to the Government stations that would continue to operate in the band after the transition period. The AWS-3 Early Entry Portal (EEP) is being designed and developed to facilitate this coordination.

1.2 SYSTEM OVERVIEW

The AWS-3 EEP draws on the successful experience gained with the DoD portal used for coordination of early entry of commercial AWS-1 licensees into the 1710 – 1755 MHz band during the 2007 – 2011 time frame. Improved spectrum engineering algorithms will be provided by the Early Entry Portal Analysis Capability (EEPAC) for more precise assessment of aggregate interference from AWS-3 systems into the DoD systems being protected. For information on the AWS-3 EEP workflow, refer to the Advanced Wireless

Services-3 1755 – 1780 MHz Early Entry Portal End-to-End Business Process [3].

1.2.1 System Objectives

The AWS-3 EEP will facilitate effective coordination between stakeholders and timely responses to AWS-3 provider requests for early access to the 1755 –1780 MHz band to ensure that critical DoD test and training capabilities are protected during the transition phase and in longer-term sharing scenarios, as appropriate.

1.2.2 System Scope

The AWS-3 EEP is being implemented in phases. The AWS-3 EEP v1.0 focused primarily on an information exchange mechanism supporting a workflow that assesses commercial

AWS-3 provider requests for early access using existing analytical tools. The Full

Operating Capability (FOC) of the AWS-3 EEP will include development of enhanced analytical capabilities that provide increased analytical fidelity and computational speed.

Post-FOC efforts will focus on automation of most of the workflow to include automated

Defense Spectrum Organization 2 analysis of wireless service provider requests for access and integration into the NTIA

Federal Spectrum Management System.

1.3 DOCUMENT OVERVIEW

1.3.1 Purpose

This document specifies the capabilities to be implemented in the AWS-3 EEP. It is intended to provide the DSO with a set of requirements for its review and approval.

1.3.2 Scope

This document describes the requirements for the AWS-3 EEP system. This document will be updated and maintained as detailed requirements for the AWS-3 EEP are coordinated and agreed upon by the DSO, including feedback received from stakeholder tests to refine and decompose requirements.

1.3.3 Intended Audiences

DSO Management and Technical Staff – The DSO is the contract monitoring agency for this effort. The DSO Management and Technical Staff will review, modify, and approve the requirements listed in this document.

Spectrum Management Stakeholders – These stakeholders include the DoD spectrum management user community, the NTIA, other government agencies, and FCC licensees that may use or interface with the AWS-3 EEP.

Design, Development, Test, and Deployment Teams – The AWS-3 EEP architects, designers, developers, testers, and deployment specialists will use this document as an input for their efforts.

1.4 ASSUMPTIONS AND LIMITATIONS

The requirements in this document are based on the following assumptions and limitations:

The Defense Spectrum Relocation Management Team (DSRMT) will be responsible for combining responses from the spectrum management offices of the individual services to AWS-3 coordination requests into a consolidated DoD response.

All hardware and software handling and analyzing classified information will be physically separated from unclassified AWS-3 EEP hardware and software systems.

Requirements in this document are subject to review and revision as a result of consultations with stakeholders during the design of the portal.

Requirements in this document are subject to change if the DoD AWS-3 EEP is required to serve other Federal agencies or to interconnect with an NTIA portal that was developed to provide a single public-facing portal for all AWS-3 coordination requests.

Defense Spectrum Organization 3

2. GENERAL SYSTEM REQUIREMENTS

AWS-3 EEP requirements are presented in this document in a tabular format, and the items in the table columns are defined as follows:

Identification (ID) – A unique identifier for each requirement. Table 2-1 provides a short description of each identifier.

Table 2-1. Requirement ID and Description

ID Description

ADMIN System Administrator Portal Access Requirement

AWS AWS-3 Licensee Portal Access Requirement

DB Portal Database Requirement

DSRMT DSRMT Portal Access Requirement

EXT External Interface Requirement

FED Federal Spectrum Manager Portal Access Requirement

GUI General User Interface Requirement

HL High-Level Requirement

IA Information Assurance Requirement

OPS Portal Operational Requirement

PERF Portal Performance Requirement

PR Personnel Requirement

SATOPS SATOPS Spectrum Manager Portal Access Requirement

SE Spectrum Engineer Portal Access Requirement

SMO DoD Spectrum Manager Portal Access Requirement

SATOPS – Satellite Operations

SMO – Spectrum Management Office

Short Name – A brief reference name for the requirement.

Description – An extended description of the requirement.

Source – The source for the requirement. Table 2-2 provides a description of each source.

Table 2-2. Requirement Source and Description

Source Description

Derived Requirements that were generated during the development of this document. In general, these requirements provide additional clarification or address gaps in the initial requirement set.

FCC/NTIA

Public Notice

Requirements that were taken directly from Public Notice DA

14-1023 [2] for coordination of DoD frequency assignments in the 1755 – 1780 MHz band.

PWS Requirements that were taken from the Advanced Wireless

Services-3 Early Entry Portal Proposal [4].

PWS – Performance Work Statement

Defense Spectrum Organization 4

Version – The AWS-3 EEP release where the implementation of this requirement was or will be satisfied.

The system requirements covered in Section 2 are general system requirements applicable to the entire AWS-3 EEP. Functional requirements of AWS-3 EEP components are presented in Section 3.

2.1 HIGH-LEVEL REQUIREMENTS

High-level requirements are defined in Table 2-3.

Table 2-3. High-Level Requirements

ID Short Name Description Source Version

HL-01 DoD Portal The AWS-3 EEP shall be an online portal that supports AWS-3 licensee requests for formal coordination with all DoD incumbents in the 1755 –

1780 MHz band.

FCC/NTIA

Public Notice v1.0

HL-02 Other Federal

Agency Portal

Support

The AWS-3 EEP shall be capable of supporting

AWS-3 licensee requests for formal coordination with other Federal incumbents in the 1755 – 1780

MHz band.

FCC/NTIA

Public Notice v1.0

HL-03 AWS Coordination

Process

The AWS-3 EEP shall support the formal coordination process specified by FCC and NTIA with respect to incumbent DoD frequency assignments.

FCC/NTIA

Public Notice v1.0

HL-04 Other Agency

Support

The AWS-3 EEP shall be capable of supporting the formal coordination process with respect to incumbent frequency assignments of other Federal agencies.

FCC/NTIA

Public Notice v1.0

HL-05 Non-USP DoD

Assignments

The AWS-3 EEP shall be capable of processing coordination requests with respect to non-USP DoD frequency assignments.

FCC/NTIA

Public Notice v1.0

HL-06 Other Non-USP

Assignments

The AWS-3 EEP shall be capable of processing coordination requests with respect to non-USP frequency assignments of other Federal agencies.

FCC/NTIA

Public Notice v1.0

HL-07 USP Assignments The AWS-3 EEP shall be capable of processing coordination requests with respect to USP frequency assignments of other Federal agencies.

FCC/NTIA

Public Notice v1.0

HL-08 Relocating DoD

Assignments

The AWS-3 EEP shall support AWS-3 coordination requests with respect to DoD assignments being relocated out of the 1755 – 1780 MHz band during the transition period.

FCC/NTIA

Public Notice v1.0

HL-09 Other Agency

Assignments

The AWS-3 EEP shall be capable of supporting

AWS-3 coordination requests with respect to the assignments of other Federal agencies being relocated out of the 1755 – 1780 MHz band during the transition period.

FCC/NTIA

Public Notice v1.0

HL-10 DoD Frequency

Assignments

The AWS-3 EEP shall support AWS-3 coordination requests with respect to DoD frequency assignments.

FCC/NTIA

Public Notice v1.0

HL-11 Coordination

Request Collection

The AWS-3 EEP shall collect coordination requests and the technical data submitted from AWS-3 licensees.

PWS v1.0

Defense Spectrum Organization 5

Table 2-3. High-Level Requirements (Continued)

ID Short Name Description Source Version

HL-12 Carrier Laydown

Verification

The AWS-3 EEP shall confirm that system designs were properly described and successfully exchanged.

PWS v1.0

HL-13 Coordination

Request

Completeness

The AWS-3 EEP shall check for the presence of both a laydown file (.csv) and a cover letter (.pdf) and notify the licensees when the coordination request submission is incomplete.

PWS v1.0

HL-14 Coordination

Request

Acceptance

The AWS-3 EEP shall notify licensees when their coordination requests and data packages have been entered into the DSO analysis queue.

PWS v1.0

HL-15 Coordination

Request Routine

Processing

Automation

The AWS-3 EEP shall automate routine processing and tracking of AWS-3 coordination requests from licensees.

PWS v1.0

HL-16 Status

Information

The AWS-3 EEP shall provide status information back to AWS-3 licensees, DSO, DoD, and Federal agency stakeholders through an automatic notification system.

PWS v1.0

HL-17 Analysis Results The AWS-3 EEP shall return analysis results to the AWS-3 licensees.

PWS v1.0

HL-18 Clearing House

Function

The AWS-3 EEP shall serve as a clearing house in disseminating coordination requests to affected parties.

PWS v1.0

HL-19 Information

Exchange

The AWS-3 EEP shall automate the exchange of information between commercial wireless service providers, Federal agency stakeholders, and the

DSO through a SharePoint portal.

PWS v1.0

HL-20 SATOPS

Coordination

Process

The AWS-3 EEP shall be capable of supporting the SATOPS streamlined coordination process specified by FCC and NTIA with respect to incumbent DoD frequency assignments.

FCC/NTIA

Public Notice v2.0

HL-21 Relocating DoD

SATOPS

Assignments

The AWS-3 EEP shall support AWS-3 SATOPS deployment plans with respect to DoD assignments being relocated out of the 1761 –

1780 MHz sub-band during the transition period.

FCC/NTIA

Public Notice v2.0

HL-22 SATOPS

Deployment Plan

Collection

The AWS-3 EEP shall collect SATOPS deployment plan requests and the technical data submitted from AWS-3 licensees.

PWS v2.0

HL-23 SATOPS

Deployment Plan

Acceptance

The AWS-3 EEP shall notify licensees when their deployment plans and data packages have been entered into the DSO analysis queue.

PWS v2.0

HL-24 SATOPS

Coordination

Agreement

Collection

The AWS-3 EEP shall collect SATOPS coordination agreements submitted from AWS-3 licensees.

PWS v2.0

HL-25 SATOPS

Countersigned

Coordination

Agreement

Collection

The AWS-3 EEP shall collect SATOPS countersigned coordination agreements from

SATOPS incumbents.

PWS v2.0

Defense Spectrum Organization 6

Table 2-3. High-Level Requirements (Continued)

ID Short Name Description Source Version

HL-26 SATOPS

Deployment Plan

Routine

Processing

Automation

The AWS-3 EEP shall automate routine processing and tracking of AWS-3 deployment plans from licensees.

PWS v2.0

HL-27 SATOPS

Supporting Files

Collection

The AWS-3 EEP shall collect SATOPS coordination agreement supporting files:

mitigation plans, contact information, and safety of life assurances.

PWS v2.0

HL-28 Post 60-Day

Process

The AWS-3 EEP shall be capable of supporting the Post 60-Day processes associated with carrier coordination after initial results of Coordination

Request assessments are provided to the carriers.

PWS v2.0

HL-29 Post 60-day

Process

Supporting Files

Collection

The AWS-3 EEP shall provide the capability for a

DSRMT user to upload Meeting Minutes and

Other files at any status after “Acknowledged” in the form of a PDF file.

Derived v2.0 v2.3

HL-29.1 Post 60-day

Process

Operator-to-

Operator

Agreement

The AWS-3 EEP shall provide the capability for a

DSRMT user to upload Operator-to-Operator

Agreement in the form of a PDF file after

“Engineering Closeout – Accepted” status.

Derived v2.0

HL-30 Resources

Library

The AWS-3 EEP shall provide a Resources library to store EEP-related information (FAQs, training materials, information briefs, etc.) on the portal, available for download by all users of the system and maintained by the DSRMT.

Derived v2.1

HL-31 TRR

Coordination

Process

The AWS-3 EEP shall be capable of supporting the Tactical Radio Relay (TRR) coordination process with respect to incumbent Army frequency assignments.

Derived v2.3

HL-32 TRR Memo

Collection

The AWS-3 EEP shall collect TRR memos (.pdf) and the technical data (.csv) submitted from AWS-

3 licensees.

Derived v2.3

HL-33 TRR Routine

Processing

Automation

The AWS-3 EEP shall automate routine processing and tracking of AWS-3 TRR memos from licensees.

Derived v2.3

HL-34 TRR Case

Additional Files

The AWS-3 EEP shall provide the capability for a user to upload additional files in PDF format and associate them to a TRR case.

Derived v2.3

HL-35 TRR Supporting

Files Collection

The AWS-3 EEP shall provide the capability for the Army SMO Representatives to upload supporting shape files and template files and make them available to the licensee..

Derived v2.3

CSV – Comma Separated Value

FAQ – Frequently Asked Question

PDF – Portable Document Format

TRR – Tactical Radio Relay

USP – United States and Possessions

Defense Spectrum Organization 7

2.2 EXTERNAL INTERFACE REQUIREMENTS

External interface requirements are defined in Table 2-4.

Table 2-4. External Interface Requirements

ID Short Name Description Source Version

EXT-01 Web Interface The AWS-3 EEP shall provide AWS-3 licensee access to its functionality by means of the Internet.

FCC/NTIA

Public Notice v1.0

EXT-02 EEPAC Interface The AWS-3 EEP shall provide the capability for providing AWS-3 coordination request data to

EEPAC and receive analysis results from EEPAC.

This capability is a manual process through the portal upload/download function.

Derived v1.0

2.3 INFORMATION ASSURANCE REQUIREMENTS

Information assurance requirements are defined in Table 2-5.

Table 2-5. Information Assurance Requirements

ID Short Name Description Source Version

IA-01 Information

Encryption

The AWS-3 EEP shall utilize encrypted links such as

Secure Sockets Layer for protecting the link between the user’s browser and the AWS-3 EEP.

Derived v1.0

IA-02 Account

Individual ID

The AWS-3 EEP shall require a user identifier, e.g., a unique token or user log-in identification, and password.

Derived v1.0

IA-03 Authentication

Controls

The AWS-3 EEP shall implement an access control solution to provide user authorizations for access to the system and functions.

Derived v1.0

IA-04 Access Control

Methods

The AWS-3 EEP shall utilize an access control method that permits a configurable method to set permissions based upon a differentiation between types of users.

Derived v1.0

IA-05 SSP Compliance The AWS-3 EEP shall satisfy the security requirements as specified in the SSP.

PWS v1.0

IA-06 AWS-3 EEP

COOP

The AWS-3 EEP implementation shall include a continuity of operations capability in accordance with the AWS-3 EEP COOP.

PWS v1.0

COOP – Continuity of Operations Plan

SSP – System Security Plan

2.4 GENERAL USER INTERFACE REQUIREMENTS

General user interface requirements are defined in Table 2-6.

Table 2-6. General User Interface Requirements

ID Short Name Description Source Version

GUI-01 User Help The AWS-3 EEP shall provide an online user guide. Derived v1.0

GUI-02 Support for

Unordered Data

Entry

The AWS-3 EEP shall provide the capability to allow users to enter data in any order when there are not sequential dependencies among the data.

Derived v1.0

Defense Spectrum Organization 8

Table 2-6. General User Interface Requirements (Continued)

ID Short Name Description Source Version

GUI-03 Web Browser

Support

The AWS-3 EEP shall support current versions of

Internet Explorer v11.0, Google Chrome v51.0, Mozilla Firefox v53.0, and Edge 40. browsers in use by DoD.

PWS v2.2 v2.3

GUI-04 Warning Banner The AWS-3 EEP shall display the standard DoD warning banner(s) to all users attempting to access the software.

Derived v1.0

2.5 PERSONNEL REQUIREMENTS

Personnel requirements are defined in Table 2-7.

Table 2-7. Personnel Requirements

ID Short Name Description Source Version

PR-01 AWS Licensee

Support

The AWS-3 EEP shall support AWS-3 licensees required to coordinate with DoD and other

Federal agencies.

PWS v1.0

PR-01.1 AWS SATOPS

Licensee Support

The AWS-3 EEP shall support AWS-3 SATOPS licensees required to coordinate with DoD

SATOPS personnel.

Derived v1.5 v2.0

PR-02 DoD Spectrum

Manager Support

The AWS-3 EEP shall support spectrum managers responsible for responding to coordination requests.

PWS v1.0

PR-02.1 Army Spectrum

Manager Support

The AWS-3 EEP shall support Army spectrum managers responsible for responding to TRR coordination cases.

Derived v2.3

PR-03 Spectrum

Engineer Support

The AWS-3 EEP shall support spectrum engineers responsible for analyzing the electromagnetic spectrum environment.

PWS v1.0

PR-04 DSRMT Support The AWS-3 EEP shall support DSRMT personnel responsible for managing AWS-3 transition activities.

PWS v1.0

PR-05 System

Administrator

Support

The AWS-3 EEP shall support system administrators responsible for managing the system.

Derived v1.0

PR-06 Federal Spectrum

Manager

Support

The AWS-3 EEP shall support Federal spectrum managers responsible for responding to coordination requests.

PWS v1.0

PR-07 SATOPS

Spectrum

Manager Support

The AWS-3 EEP shall support SATOPS personnel responsible for managing the

SATOPS Streamlined Coordination process.

PWS v1.5

Defense Spectrum Organization 9

2.6 PORTAL PERFORMANCE REQUIREMENTS

Portal performance requirements are specified in Table 2-8.

Table 2-8. Portal Performance Requirements

ID Short Name Description Source Version

PERF-01 Request

Acknowledgement

Period

The AWS-3 EEP shall be capable of acknowledging receipt of a coordination request within five calendar days of posting on the portal.

FCC/NTIA

Public Notice v1.0

PERF-02 Request

Completeness

Period

The AWS-3 EEP shall be capable of acknowledging the completeness or incompleteness of a coordination request within

10 calendar days of posting on the portal.

FCC/NTIA

Public Notice v1.0

PERF-03 Request Response

Period

The AWS-3 EEP shall be capable of completing the analysis and providing a response to a complete coordination request within 60 calendar days of posting on the portal.

FCC/NTIA

Public Notice v1.0

PERF-04 Tickler

Notifications

The AWS-3 EEP shall automatically send out tickler notices to a spectrum manager’s inbox before the due date on any outstanding required responses.

Derived v1.0

PERF-05 Total Users The AWS-3 EEP shall be capable of supporting

50 simultaneous users.

Derived v1.0

PERF-06 Concurrent Users The AWS-3 EEP shall be capable of supporting

50 users concurrently, while still meeting acceptable response times.

PWS v1.0

Defense Spectrum Organization 10

Defense Spectrum Organization 11

3. FUNCTIONAL REQUIREMENTS

This section specifies the AWS-3 EEP functional requirements.

3.1 PORTAL ACCESS REQUIREMENTS

AWS-3 EEP users requiring access to the portal are grouped into the following seven general categories:

AWS-3 licensees

DoD spectrum managers responsible for reviewing interference analyses and proposed responses and for responding to coordination requests

Harris spectrum engineers and analysts managing AWS-3 coordination request workflow and interference analyses

DSRMT personnel

AWS-3 EEP system administrators

Federal agency representatives

SATOPS representatives

3.1.1 AWS-3 Licensee Portal Access Requirements

AWS-3 licensee portal access requirements are specified in Table 3-1.

Table 3-1. AWS-3 Licensee Portal Access Requirements

ID Short Name Description Source Version

AWS-01 Coordination Request

Submission

An AWS-3 licensee shall be able to submit a coordination request via the portal.

FCC/NTIA

Public Notice v1.0

AWS-01.1 SATOPS Licensee

Request Submission

An AWS-3 SATOPS licensee shall be able to submit a coordination agreement or a deployment plan via the portal.

Derived v1.5

AWS-01.2 TRR Memo

Submission

An AWS-3 licensee shall be able to submit a

TRR memo via the portal.

Derived v2.3

AWS-02 Coordination Request

Withdrawal

An AWS-3 licensee shall be able to withdraw a coordination request via the portal.

Derived v1.0

AWS-02.1 TRR Memo

Withdrawal

An AWS-3 licensee shall be able to withdraw a TRR case memo via the portal.

Derived v2.3

AWS-03 Coordination Request

Status Check

An AWS-3 licensee shall be able to check the status of a coordination request once it has been submitted to the portal.

Derived v1.0

AWS-03.1 SATOPS Case Status

Check

An AWS-3 SATOPS licensee shall be able to check the status of a coordination agreement or a deployment plan once it has been submitted to the portal.

Derived v2.0

AWS-03.2 TRR Case Status

Check

An AWS-3 licensee shall be able to check the status of a TRR case once it has been submitted to the portal.

Derived v2.3

AWS-04 Coordination Request

Response Receipt

An AWS-3 licensee shall be able to receive responses regarding its requests via the portal.

Defense Spectrum Organization 12

Table 3-1. AWS-3 Licensee Portal Access Requirements (Continued)

ID Short Name Description Source Version

AWS-04.1 SATOPS Case

Response Receipt

An AWS-3 SATOPS licensee shall be able to receive responses regarding its SATOPS requests via the portal.

Derived v2.0

AWS-04.2 TRR Case

Response Receipt

An AWS-3 licensee shall be able to receive responses regarding its TRR case via the portal.

Derived v2.3

AWS-05 AWS Licensee

Correspondence

Support

An AWS-3 licensee shall be able to originate and receive correspondence regarding its requests via the portal.

Derived v1.0 v2.0 v2.3

AWS-06 AWS Laydown

Data Format

The AWS-3 EEP shall provide the capability for a licensee to input AWS laydown technical data in the form of a CSV file.

Derived v1.0

AWS-07 AWS Sector

Results Format

The AWS-3 EEP shall provide the capability for a licensee to download AWS results data in the form of a CSV or PDF file.

Derived v1.0

AWS-08 AWS Licensee

Inbox

The AWS-3 EEP shall provide an inbox capability for AWS licensees to receive status and messages.

Derived v1.0

AWS-09 Coordination

Records Lookup

The AWS-3 EEP shall provide the capability for

AWS licensees to perform a lookup of their coordination request records stored in the portal.

Derived v1.0

AWS-09.1 SATOPS

Records Lookup

The AWS-3 EEP shall provide the capability for

AWS SATOPS licensees to perform a lookup of their SATOPS records stored in the portal.

Derived v2.0

AWS-09.2 TRR Case

Lookup

The AWS-3 EEP shall provide the capability for

AWS licensees to perform a lookup of their TRR case records stored in the portal.

Derived v2.3

AWS-10 TRR Support

Files Download

The AWS-3 EEP shall provide the capability for

AWS licensees to download TRR supporting shape files and template files.

Derived v2.3

CSV – Comma Separated Value

SATOPS – Satellite Operations

TRR – Tactical Radio Relay

3.1.2 DoD Spectrum Manager Portal Access Requirements

DoD spectrum manager portal access requirements are specified in Table 3-2.

Table 3-2. DoD Spectrum Manager Portal Access Requirements

ID Short Name Description Source Version

SMO-01 SMO Account

Set-Up

The initial account set-up for an SMO shall be made by an AWS-3 EEP system administrator.

Derived v1.0

SMO-02 Designated Spectrum

Manager

A spectrum manager shall be designated as the point of contact for every DoD frequency assignment to be protected by the SMO responsible for that assignment.

Derived v1.0

SMO-03 Spectrum Manager

File Access

Limitations

A DoD spectrum manager shall only be able to access analysis results associated with DoD frequency assignments which his/her office is specifically responsible for protecting.

Derived v1.0

SMO-03.1 Army File Access

Permissions

An Army spectrum manager shall also be able to access files associated with TRR records.

Derived v2.3

Defense Spectrum Organization 13

Table 3-2. DoD Spectrum Manager Portal Access Requirements (Continued)

ID Short Name Description Source Version

SMO-04 Spectrum

Manager Queries

The AWS-3 EEP shall provide the capability for a

DoD spectrum manager to look up AWS-3 coordination requests by carrier, dates, and/or status.

Derived v1.0

SMO-04.1 Army Spectrum

Manager TRR

Case Queries

The AWS-3 EEP shall provide the capability for an Army spectrum manager user to look up AWS-

3 TRR cases by carrier, dates, and/or status.

Derived v2.3

SMO-05 Spectrum

Manager Records

Lookup

The AWS-3 EEP shall provide the capability for a

DoD spectrum manager user to perform a lookup of coordination records stored in the portal.

Derived v1.0

SMO-05.1 Army Spectrum

Manager TRR

Case Records

Lookup

The AWS-3 EEP shall provide the capability for an Army spectrum manager user to perform a lookup of coordination records stored in the portal.

Derived v2.3

SMO-06 Spectrum

Manager Results

Format

The AWS-3 EEP shall provide the capability for a spectrum manager user to download AWS results data in the form of a CSV or PDF file.

Derived v1.0

SMO-07 Spectrum

Manager

Notification

The AWS-3 EEP shall provide a notification capability for spectrum manager users to receive status notifications and messages.

Derived v1.0

SMO-08 Spectrum

Manager

Correspondence

A spectrum manager shall be able to send and receive correspondence with licensees, Engineers, and the DSRMT concerning an AWS-3 coordination request, coordination agreement, and deployment plan cases.

Derived v1.0 v2.0

SMO-08.1 Army Spectrum

Manager

Correspondence

An Army spectrum manager shall be able to send and receive correspondence with licensees, Engineers, and the DSRMT concerning a TRR case.

Derived v2.3

SMO-09 TRR Support

Files

Management

The AWS-3 EEP shall provide the capability for the Army spectrum manager user to manage TRR supporting shape files and template files.

Derived v2.3

3.1.3 Spectrum Engineer Portal Access Requirements

Spectrum engineer portal access requirements are specified in Table 3-3.

Table 3-3. Spectrum Engineer Portal Access Requirements

ID Short Name Description Source Version

SE-01 Spectrum

Engineer Account

Set-Up

AWS-3 EEP accounts for spectrum engineers shall be set up by an AWS-3 EEP system administrator.

Derived v1.0

SE-02 Spectrum

Engineer Account

Permissions

AWS-3 EEP account permissions for spectrum engineers shall be managed by an AWS-3 EEP system administrator.

Derived v1.0

SE-03 Spectrum

Engineer AWS

Licensee Record

Access

The AWS-3 EEP shall provide spectrum engineers with read-only access to all AWS-3 licensee records.

Derived v1.0

SE-04 Spectrum

Engineer

Correspondence

A spectrum engineer shall be able to send and receive correspondence with SMOs and the

DSRMT concerning an AWS-3 case.

Derived v1.0 v2.0 v2.3

Defense Spectrum Organization 14

Table 3-2. Spectrum Engineer Portal Access Requirements (Continued)

ID Short Name Description Source Version

SE-05 Spectrum

Engineer

Queries

The AWS-3 EEP shall provide the capability to look up coordination records by carrier, dates and/or status.

Derived v1.0 v2.0 v2.3

SE-06 Spectrum

Engineer

Records Lookup

The AWS-3 EEP shall provide the capability for a spectrum engineer analyst to perform a lookup of coordination records stored in the portal.

Derived v1.0 v2.0 v2.3

SE-07 Spectrum

Engineer Results

Format

The AWS-3 EEP shall provide the capability for an engineer to download AWS results data in the form of a CSV or PDF file.

Derived v1.0

SE-08 Spectrum

Engineer

Notification

The AWS-3 EEP shall provide a notification capability for spectrum engineers to receive status notifications and messages.

Derived v1.0 v2.0 v2.3

3.1.4 DSRMT Portal Access Requirements

DSRMT portal access requirements are specified in Table 3-4.

Table 3-4. DSRMT Portal Access Requirements

ID Short Name Description Source Version

DSRMT-01 DSRMT Account

Set-Up

AWS-3 EEP accounts for DSRMT members shall be set up by an AWS-3 EEP system administrator.

Derived v1.0

DSRMT-02 DSRMT Account

Permissions

AWS-3 EEP account permissions for DSRMT members shall be managed by an AWS-3 EEP system administrator.

Derived v1.0

DSRMT-03 DSRMT AWS

Licensee Record

Access

The AWS-3 EEP shall provide DSRMT members read-only access to all AWS-3 licensee records.

Derived v1.0

DSRMT-04 DSRMT

Correspondence

A DSRMT member shall be able to send and receive correspondence concerning an AWS-3 case.

Derived v1.0 v2.0 v2.3

DSRMT-05 DSRMT Queries The AWS-3 EEP shall provide the capability to

DSMRT to lookup AWS-3 coordination records by carrier, dates and/or status.

Derived v1.0

DSRMT-06 DSRMT Records

Lookup

The AWS-3 EEP shall provide the capability for

DSRMT members to perform a lookup of coordination records stored in the portal.

Derived v1.0

DSRMT-07 DSRMT Results

Format

The AWS-3 EEP shall provide the capability for

DSRMT members to download AWS results data in the form of a CSV or PDF file.

Derived v1.0

DSRMT-08 DSRMT

Notification

The AWS-3 EEP shall provide a notification capability for DSRMT members to receive status notifications and messages.

Derived v1.0

DSRMT-09 TRR Support

Files

Management

The AWS-3 EEP shall provide the capability for

DSRMT members to manage TRR supporting shape files and template files.

Defense Spectrum Organization 15

3.1.6 System Administrator Portal Access Requirements

System administrator portal access requirements are specified in Table 3-5.

Table 3-5. System Administrator Portal Access Requirements

ID Short Name Description Source Version

ADMIN-01 Portal Account

Management

The AWS-3 EEP shall provide system administrators the capability to manage all portal user accounts, including adding, deactivating, activating accounts and modifying account permissions.

Derived v1.0

ADMIN-02 Software

Preference

Settings

The AWS-3 EEP shall provide system administrators the capability to manage all software system preference settings.

Derived v1.0

ADMIN-03 Workflow

Rollback

The AWS-3 EEP shall provide system administrators the capability to rollback a case to to a previous status in the workflow.

Derived v1.0

3.1.7 Federal Spectrum Manager Portal Access Requirements

Federal spectrum manager portal access requirements are specified in Table 3-6.

Table 3-6. Federal Spectrum Manager Portal Access Requirements

ID Short Name Description Source Version

FED-01 Federal User

Account Set-Up

AWS-3 EEP accounts for Federal Users shall be set up by an AWS-3 EEP system administrator.

Derived v1.0

FED-02 Federal User

Account

Permissions

AWS-3 EEP account permissions for Federal

Users shall be managed by an AWS-3 EEP system administrator.

Derived v1.0

FED-03 Federal User

Notification

The AWS-3 EEP shall provide a notification capability for Federal users to receive status notifications and messages.

Derived v1.0

FED-04 Federal User

Queries

The AWS-3 EEP shall provide the capability to lookup AWS-3 coordination requests by carrier, dates and/or status.

Derived v1.0

FED-05 Federal Records

Lookup

The AWS-3 EEP shall provide the capability for a federal spectrum manager user to perform a lookup of coordination requests stored in the portal.

Derived v1.0

FED-06 Federal User

Results Format

The AWS-3 EEP shall provide the capability for a federal user to download results data in the form of a CSV or PDF file.

Derived v1.0

FED-07 Federal User

Correspondence

A federal user shall be able to send and receive correspondence concerning an AWS-3 case that was submitted to his/her agency.

Defense Spectrum Organization 16

3.1.8 SATOPS Spectrum Manager Portal Access Requirements

SATOPS spectrum manager portal access requirements are specified in Table 3-7.

Table 3-7. SATOPS Spectrum Manager Portal Access Requirements

ID Short Name Description Source Version

SATOPS-01 SATOPS User

Account Set-Up

AWS-3 EEP accounts for SATOPS spectrum managers shall be set up by an AWS-3 EEP system administrator.

Derived v1.5

SATOPS-02 SATOPS User

Account

Permissions

AWS-3 EEP account permissions for SATOPS spectrum manager users shall be managed by an

AWS-3 EEP system administrator.

Derived v1.5

SATOPS-03 SATOPS User

Notification

The AWS-3 EEP shall provide a notification capability for SATOPS spectrum managers to receive status notifications and messages.

Derived v1.5

SATOPS-04 SATOPS User

Queries

The AWS-3 EEP shall provide the capability for a SATOPS spectrum manager to lookup AWS-3 coordination agreements and deployment plans by carrier, dates and/or status.

Derived v2.0

SATOPS-05 SATOPS User

Results Format

The AWS-3 EEP shall provide the capability for a SATOPS spectrum manager to download results data in the form of a PDF file.

Derived v1.5

SATOPS-06 SATOPS User

Correspondence

A SATOPS spectrum manager shall be able to send and receive correspondence concerning an

AWS-3 SATOPS case.

Derived v2.0

3.2 PORTAL OPERATIONAL REQUIREMENTS

Portal operational requirements are specified in Table 3-8.

Table 3-8. Portal Operational Requirements

ID Short Name Description Source Version

OPS-01 Coordination

Request

Completeness

Check

The AWS-3 EEP shall determine whether a coordination request contains all required information.

Derived v1.0

OPS-01.1 SATOPS

Completeness

Check

The AWS-3 EEP shall determine whether a coordination agreement or a deployment plan contains all required information.

Derived v2.0

OPS-01.2 TRR

Completeness

Check

The AWS-3 EEP shall determine whether a TRR case contains all required information.

Derived 2.3

OPS-02 Coordination

Request Status

The AWS-3 EEP shall maintain a record of the current status of a coordination request throughout its entire processing cycle.

Derived v1.0

OPS-02.1 SATOPS

Coordination

Status

The AWS-3 EEP shall maintain a record of the current status of a coordination agreement and deployment plan throughout its entire processing cycle.

Derived v2.0

OPS-02.2 TRR

Coordination

Status

The AWS-3 EEP shall maintain a record of the current status of a TRR case throughout its entire processing cycle.

Defense Spectrum Organization 17

Table 3-8. Portal Operational Requirements (Continued)

ID Short Name Description Source Version

OPS-03 Analysis

Response

Tracking

The AWS-3 EEP shall track the response from each agency whose assignments are affected by a coordination request.

Derived v1.0

OPS-04 Internal

Response

Tracking

The AWS-3 EEP shall track and maintain a copy of all correspondence between and among AWS-3 licensees, DoD spectrum managers and the

DSRMT relating to a coordination request.

Derived v1.0

OPS-04.1 SATOPS Internal

Response

Tracking

The AWS-3 EEP shall track and maintain a copy of all correspondence between and among AWS-3 licensees, SATOPS Leads and the DSRMT relating to coordination agreements and deployment plans.

Derived v2.0

OPS-04.2 TRR Internal

Response

Tracking

The AWS-3 EEP shall track and maintain a copy of all correspondence between and among AWS-3 licensees, Army SMO Representatives and the

DSRMT relating to a TRR case.

Derived v2.3

OPS-05 Responses to

Licensee

The AWS-3 EEP shall post the approved coordination request response to the licensee on the portal and a notification that the response is available to the AWS licensee.

Derived v1.0

OPS-05.1 TRR Responses to Licensee

The AWS-3 EEP shall post the approved TRR coordination response to the licensee on the portal and a notification that the response is available to the AWS licensee.

Derived v2.3

OPS-06 Unique Request

Monitoring

The AWS-3 EEP shall assign a unique request tracking number to each submitted coordination request.

Derived v1.0

OPS-06.2 TRR Unique

Request

Monitoring

The AWS-3 EEP shall assign a unique request tracking number to each submitted TRR case.

Derived v2.3

OPS-07 Due Date

Assignment

The AWS-3 EEP shall assign a DSRMT response due date that is at most 60 calendar days from the day an AWS request is categorized as “accepted.”

Derived v1.0

OPS-08 Spectrum

Manager

Notification

The AWS-3 EEP shall automatically send a notification to the spectrum manager assigned to reviewing coordination requests for the affected frequency assignment when an EEPAC analysis is ready for review.

Derived v1.0

OPS-09 DSRMT

Manager

Notification

The AWS-3 EEP shall automatically notify the

DSRMT of the submission of a coordination request, the distribution of EEPAC analysis results to DoD spectrum managers, and the availability of the response of each affected spectrum manager.

Derived v1.0

OPS-09.1 SATOPS Lead

Notification

The AWS-3 EEP shall automatically notify the

SATOPS Lead of the submission of a coordination agreement and deployment plan.

Derived v2.0

OPS-09.2 Army SMO

Representative

Notification

The AWS-3 EEP shall automatically notify the

DSRMT and Army SMO Representatives of the submission of a TRR case.

Derived v2.3

OPS-10 Coordination

Request

Workflow Status

The AWS-3 EEP shall provide the capability to maintain the status of the workflow of each coordination request.

Defense Spectrum Organization 18

Table 3-8. Portal Operational Requirements (Continued)

ID Short Name Description Source Version

OPS-10.1 SATOPS

Coordination

Workflow Status

The AWS-3 EEP shall provide the capability to maintain the status of the workflow of each coordination agreement and each deployment plan.

Derived v2.0

OPS-10.2 TRR

Coordination

Workflow Status

The AWS-3 EEP shall provide the capability to maintain the status of the workflow of each TRR case.

Derived v2.3

OPS-11 Time Stamp

Entries

The AWS-3 EEP shall provide the capability to automatically time stamp entries to each coordination request data element.

Derived v1.0

OPS-11.1 SATOPS Time

Stamp Entries

The AWS-3 EEP shall provide the capability to automatically time stamp entries to each coordination agreement data element and each deployment plan data element.

Derived v2.0

OPS-11.2 TRR Time Stamp

Entries

The AWS-3 EEP shall provide the capability to automatically time stamp entries to each TRR case data element.

Derived v2.3

OPS-12 User Account ID The AWS-3 EEP shall provide the capability to automatically record the user account ID responsible for the change in coordination request status.

Derived v1.0

OPS-12.1 SATOPS User

Account ID

The AWS-3 EEP shall provide the capability to automatically record the user account ID responsible for the change in the coordination agreement and the deployment plan status.

Derived v2.0

OPS-12.2 TRR User

Account ID

The AWS-3 EEP shall provide the capability to automatically record the user account ID responsible for the change in TRR case status.

Derived v2.3

OPS-13 Historical Record

Maintenance

The AWS-3 EEP shall provide the capability to maintain the historical record of all AWS-3 coordination requests.

Derived v1.0

OPS-13.1 SATOPS

Historical Record

Maintenance

The AWS-3 EEP shall provide the capability to maintain the historical record of all AWS-3 coordination agreements and deployment plans.

Derived v2.0

OPS-13.2 TRR Historical

Record

Maintenance

The AWS-3 EEP shall provide the capability to maintain the historical record of all AWS-3 TRR cases.

Derived v2.3

OPS-14 Carrier Accepts

CR Results

The AWS-3 EEP shall provide the capability for a licensee to accept the CR results in the Post 60-day process.

Derived v2.0

OPS-15 Carrier Objects

CR Results

The AWS-3 EEP shall provide the capability for a licensee to object to the CR results in the Post 60-day process.

Derived v2.0

OPS-16 Carrier Requests

Discussion

The AWS-3 EEP shall provide the capability for a licensee to request a meeting with the DoD to discuss the Results Letter in the Post 60-day process, and to accept or object to the CR results after the meeting.

Derived v2.0

Defense Spectrum Organization 19

3.3 PORTAL DATABASE REQUIREMENTS

Portal database requirements are specified in Table 3-9.

Table 3-9. Portal Database Requirements

ID Short Name Description Source Version

DB-01 Request

Database

The AWS-3 EEP shall maintain a searchable database of all coordination requests.

Derived v1.0

DB-01.1 SATOPS

Request

Database

The AWS-3 EEP shall maintain a searchable database of all coordination agreements and deployment plans.

Derived v2.0

DB-01.2 TRR Request

Database

The AWS-3 EEP shall maintain a searchable database of all TRR cases.

Derived v2.3

DB-02 Response

Database

The AWS-3 EEP shall maintain a searchable database of all responses to coordination requests.

Derived v1.0

DB-02.1 SATOPS

Response

Database

The AWS-3 EEP shall maintain a searchable database of all responses to coordination agreements and deployment plans.

Derived v2.0

DB-02.2 TRR Response

Database

The AWS-3 EEP shall maintain a searchable database of all responses to TRR cases.

Derived v2.3

DB-03 Correspondence

Database

The AWS-3 EEP shall maintain a searchable database of all correspondence performed through the portal that is associated with the processing of coordination requests.

Derived v1.0

DB-03.1 SATOPS

Correspondence

Database

The AWS-3 EEP shall maintain a searchable database of all correspondence performed through the portal that is associated with the processing of coordination agreements and deployment plans.

Derived v2.0

DB-03.2 TRR

Correspondence

Database

The AWS-3 EEP shall maintain a searchable database of all correspondence performed through the portal that is associated with the processing of TRR cases.

Derived v2.3

DB-04 Portal CR

Statistics

Database

The AWS-3 EEP shall maintain a searchable database of all portal CR processing statistics.

Derived v1.0 v2.0

DB-04.1 Portal SATOPS

Statistics

Database

The AWS-3 EEP shall maintain a searchable database of all portal SATOPS processing statistics.

Derived v2.1

Defense Spectrum Organization 20

Defense Spectrum Organization 21

4. REFERENCES

1. Amendment of the Commission’s Rules with Regard to Commercial Operations in the

1695 – 1710 MHz, 1755 – 1780 MHz, and 2155 – 2180 MHz Bands. GN Docket No.

13-185. Report and Order, 29 FCC Record 4610. FCC. 2014 (reconsideration pending).

2. Coordination Procedures in the 1695 – 1710 MHz and 1755 – 1780 MHz Bands.

Public Notice DA 14-1023. FCC/NTIA. 18 July 2014.

3. AWS-3 Early Entry Portal End-to-End Business Process.pptx. DSO. Annapolis, MD:

June 2017.

4. Advanced Wireless Services-3 Early Entry Portal Proposal. Exelis Inc. Bowie, MD:

01 September 2015.

Defense Spectrum Organization 22

Defense Spectrum Organization 23

5. ACRONYMS

AWS Advanced…