9_AWS-3 EEP User's Guide 29 June 2017.pdf

1755 - 1780 MHz Early Entry Portal

Version 2.3

AWS-3 Early Entry Portal (V2.3)2

Table of Contents

Foreword 0

Part I Welcome 6

Part II Copyright Information 8

Part III Background 10

Part IV Basic Workflow 12

Part V Coordination Requests Workflow 17

................................................................................................................................... 181 5-Day Process

................................................................................................................................... 192 10-Day Process

................................................................................................................................... 203 60-Day Process

Part VI SATOPS Coordination Agreements Workflow 22

Part VII SATOPS Deployment Plan Workflow 25

Part VIII Tactical Radio Relay (TRR) Workflow 29

Part IX Post 60-Day Process 32

................................................................................................................................... 321 Licensee Response

................................................................................................................................... 362 Engineering/DSRMT Closeout Accept

................................................................................................................................... 383 Engineering/DSRMT Closeout Object

Part X Messaging/Inbox 41

Part XI Messaging/Case Details 48

Part XII User Roles/Groups 51

Part XIII Changing Passwords 54

Part XIV Licensees 56

................................................................................................................................... 581 Licensee Carrier Coordination Requests

.......................................................................................................................................................... 61Submitting New Cases

.......................................................................................................................................................... 63Requesting a CR Withdrawal

.......................................................................................................................................................... 64Receiving CR Response

................................................................................................................................... 652 Licensee SATOPS

.......................................................................................................................................................... 67Licensee Coordination Agreements

3Contents

......................................................................................................................................................... 69Submitting New SATOPS Agreements

......................................................................................................................................................... 71Upload Supporting Files

......................................................................................................................................................... 72Remove Supporting Files

......................................................................................................................................................... 73Receiving CA Response

.......................................................................................................................................................... 74Licensee Deployment Plans

......................................................................................................................................................... 76Submitting New Deployment Plans

................................................................................................................................... 783 Licensee TRR Coordinations

.......................................................................................................................................................... 83Submit New TRR Case

.......................................................................................................................................................... 87Upload/Remove TRR Additional Support Files

Part XV DSRMT 90

................................................................................................................................... 921 DSRMT Carrier Coordination Requests

.......................................................................................................................................................... 95Change Status of Request

.......................................................................................................................................................... 96Upload/Remove Additional Files

.......................................................................................................................................................... 98Pause Case Clock

.......................................................................................................................................................... 99Acknowledge Withdrawal

.......................................................................................................................................................... 100Notify Exceeding 60 Days

................................................................................................................................... 1012 DSRMT SATOPS

.......................................................................................................................................................... 102DSRMT Coordination Agreements

.......................................................................................................................................................... 105DSRMT Deployment Plans

................................................................................................................................... 1073 DSRMT TRR Coordinations

Part XVI Service SMO Representatives 113

................................................................................................................................... 1151 SMO Carrier Coordination Requests

.......................................................................................................................................................... 118SMO Subcases

................................................................................................................................... 1192 SMO SATOPS

.......................................................................................................................................................... 120SMO Coordination Agreements

.......................................................................................................................................................... 122SMO Deployment Plans

................................................................................................................................... 1253 Army TRR Coordinations

.......................................................................................................................................................... 128Army TRR Support Files

.......................................................................................................................................................... 130Managing Army TRR Support Files

.......................................................................................................................................................... 135Army TRR Change Status

Part XVII Federal Agency Users 138

................................................................................................................................... 1391 Federal Agency Carrier Coordination Requests

................................................................................................................................... 1412 Federal Pause Case Clock

................................................................................................................................... 1423 Federal Notify Exceeding 60 Days

................................................................................................................................... 1434 Federal Change Status

................................................................................................................................... 1445 Federal Withdrawal Request

Part XVIII Engineering Analysis Staff 147

................................................................................................................................... 1481 Engineering Coordination Requests

.......................................................................................................................................................... 152Downloading CRs for Analysis

.......................................................................................................................................................... 152Engineering Change Status

................................................................................................................................... 1592 Engineering SATOPS

.......................................................................................................................................................... 161Engineering Coordination Agreements

.......................................................................................................................................................... 163Engineering Deployment Plans

......................................................................................................................................................... 165Change Status on Deployment Plans

AWS-3 Early Entry Portal (V2.3)4

................................................................................................................................... 1683 Engineering TRR Coordinations

Part XIX DoD SATOPS Lead 174

................................................................................................................................... 1751 DoD SATOPS

.......................................................................................................................................................... 176SATOPS Coordination Agreements

......................................................................................................................................................... 179Change Status of Agreement

.......................................................................................................................................................... 181SATOPS Deployment Plans

Part XX Portal Administration Staff 185

................................................................................................................................... 1861 Administration Coordination Requests

.......................................................................................................................................................... 189Admin Change CR Status

................................................................................................................................... 1902 Administration SATOPS

.......................................................................................................................................................... 192Administration Coordination Agreements

......................................................................................................................................................... 194Change Status

......................................................................................................................................................... 194Remove Other SATOPS Files

.......................................................................................................................................................... 195Administration Deployment Plans

......................................................................................................................................................... 197Admin Change DP Status

................................................................................................................................... 1983 Administration Army TRR Coordination

.......................................................................................................................................................... 202Administration TRR Change Status

................................................................................................................................... 2034 Manage Users

................................................................................................................................... 2095 Manage Groups

Part XXI Resources 215

................................................................................................................................... 2161 Manage Resources

Part XXII Statistics 222

Part XXIII References 230

Index 231

Part

I

AWS-3 Early Entry Portal (V2.3)6

1 Welcome

Welcome to the Advanced Wireless Services-3 Early Entry Portal (AWS-3 EEP) Help system. This help file provides some basic background information, a brief description of the workflow process and detailed instructions for the various users of the AWS-3 EEP application.

Beginning with this version (2.3), the following Web browsers and versions are supported:

Internet Explorer 11.0 Google Chrome 51.0 Mozilla Firefox 53.0 Microsoft Edge 40.1

This software is copyrighted.

For questions and concerns, please contact the AWS-3 EEP Help Desk

Phone: 301-867-AWS3 (2973)

E-mail: res-1755eep@harris.com

II

AWS-3 Early Entry Portal (V2.3)8

2 Copyright Information

Copyright 2017 Harris IT Services Government Unlimited Rights (DFARS 252.227.7014)

III

AWS-3 Early Entry Portal (V2.3)10

3 Background

The Federal Communications Commission (FCC) reallocated the 1755-1780 Megahertz (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-3 (AWS-3) licenses. The Services and the Defense Information Systems Agency (DISA) 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 Department of Defense (DoD) and commercial systems operating in the 1755-1780 MHz band.

The FCC and National Telecommunications and Information Administration, issued the Coordination Procedures in the 1695-1710 MHz and 1755-1780 MHz Bands Public Notice [2] specifying 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.

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 EEP 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].

IV

AWS-3 Early Entry Portal (V2.3)12

4 Basic Workflow

The purpose of the AWS-3 Early Entry Portal (EEP) is to automate the routine processing and tracking of AWS-3 Coordination Requests, Satellite Operations (SATOPS) Coordination Agreements, SATOPS Deployment Plans, and Tactical Radio Relay (TRR) Coordination Requests in support of the DoD spectrum managers’ responsibility to protect government and military frequency assignments in the 1755–1780 MHz band.

Major functions of the EEP include:

Receipt of Coordination Requests (CRs), SATOPS Coordination Agreements (CAs), SATOPS Deployment Plans (DPs), and Tactical Radio Relay coordinations submitted from AWS-3 licensees

Distribution of CRs, SATOPS CAs, SATOPS DPs, and TRR coordinations to DoD and Federal Agency stakeholders as required

Response to licensees including: Receipt Acknowledgment; Complete/Incomplete Request;

Concurrence, Partial Concurrence, or Denial of CRs, CAs, DPs, and TRR coordinations

Automated status tracking and warehousing of documents throughout the coordination process

Establishment and management of Portal user accounts

The seven participants in the processing of these coordination requests and agreements are listed below with a brief description of their role.

Licensees - Commercial wireless companies responsible for submitting CRs, CAs, DPs, and TRR coordination.

DoD Spectrum Relocation Management Team (DSRMT) - Overall responsibility for the AWS-3 coordination process. DSRMT is responsible for each case submitted by the AWS-3 Licensee. DSRMT provides the integrated DoD response to the AWS-3 Licensee.

Service Spectrum Management Office (SMO) Representatives - Responsible for reviewing each of the sub-cases and analysis results. Service SMO Representatives make the final decision on each sub-case. (DoD only). In the case of a TRR coordination, only the Army SMO is involved.

Federal Agency Representatives - Responsible for reviewing cases submitted to them and providing a response. (non-DoD agencies DOJ and DOI)

Engineering Analysis Staff - Retrieve cases from the Portal, run validation processes, conduct electromagnetic compatibility analyses via the Early Entry Portal Analysis Capability (EEPAC) and provide analysis results.

DoD SATOPS Lead - Responsible for reviewing each SATOPS CA and DP submitted by a Licensee, verifying them, and counter-signing the agreement.

Portal Administration Staff - Ensure the smooth operation of the Portal and establishing and maintaining user accounts.

When a licensee submits a Coordination Request, a SATOPS Coordination Agreement, a Deployment Plan, or a Tactical Radio Relay coordination to the Portal, the Portal automatically generates a Case Identifier (ID) for that request, which becomes a unique identifier for that submission. Case IDs are

Basic Workflow 13 alphanumeric and are 13 characters long. Each Case ID encapsulates a number of data elements and is structured as shown below.

NOTE: For SATOPS Coordination Agreements, the Market Area will always be 0CA and the Frequency Block will always be 0. For Deployment Plans, the Market Area will always be 0DP and the Frequency Block will be 0. For Tactical Radio Relay, the Market Area will always be TRR and the Frequency Block will always be 0.

An automated workflow is implemented within the portal to assist users with the overall case management process. Each case has a workflow object associated with it, which keeps track of the current status of the case, i.e. where in the process a given case resides. As the case transitions through various workflow states, a set of statuses is used to easily keep track of the case progress. The table below identifies all possible statuses and their descriptions.

Workflow Status Description

Submitted Initial request has been submitted to the EEP

Acknowledged Initial request is stored in the Portal and a unique Case ID is generated

Coordinating 1 The Army has received the request (TRR only) and is reviewing the memo

Complete - Closed 1 The Army has reviewed the TRR memo and sent a response to the Licensee

Complete - Accepted Request was successfully validated and accepted for analysis

Incomplete - Resubmit Request had validation errors and must be resubmitted

Paused The analysis clock has been paused for this Request

Pending Analysis with Subcases 2 Request has assignments from one or more services that might be impacted by the submitted laydown. This triggers a generation of subcases for the impacted services

AWS-3 Early Entry Portal (V2.3)14

Workflow Status Description

Pending Analysis - No Subcases 2 Request does not impact assignments from one or more services

Pending Action 3 Request (with SMO subcases) requires SMO review/ action

Analysis in Progress 2 Request is currently being analyzed

Subcase Report Posted 2 Analysis for each impacted SMO is available for SMO review

Subcase Review Complete 2 Impacted SMO completed the review and provided their results

Result Letter Available 2 An aggregated result letter has been prepared for delivery to Licensee

Response Delivered The response letter is delivered to the Licensee for a given case

Withdrawn 4 Request has been withdrawn and will no longer be processed

Results Accepted The Licensees have accepted the DoD response and analysis results for the Request

Results Objected The Licensee has objected to the DoD response and analysis results for the Request

Requested Discussion The Licensee has requested meetings to discuss the DoD response/analysis results for the Request

Discussion Result - Accept The Licensee has completed discussions with DoD and accepts the DoD response/analysis results for the Request

Discussion Result - Object The Licensee has completed discussions with DoD and objects to the DoD response/analysis results for the Request

Closeout Complete Accept The Request has been closed out in EEPAC. Only approved sectors from the Coordination/Field Trial Request has been integrated into the EEPAC background electromagnetic environment

Closeout Complete Object The Request has been closed out in EEPAC. No sectors from the Coordination/Field Trial Request have been integrated into the EEPAC background electromagnetic environment

Closed - Accepted Early entry coordination between the DoD and the Licensee has been completed. The Licensee accepts the DoD response/analysis results. The Request is closed.

Basic Workflow 15

Workflow Status Description

Closed - Objected Early entry coordination between the DoD and the Licensee has been completed. The Licensee objects to the DoD response/analysis results. The Request is closed.

1 Applies to Army TRR coordination only

2 DoD-only process statuses

3 Only pertains to SMO workflow

4 The Withdrawn status is displayed only when the DSRMT or a Federal Agency has accepted a Withdrawal Request from the Licensee. Depending upon where the Coordination Request is in the processing workflow, the DSRMT or a Federal Agency can accept or reject a Withdrawal Request from the Licensee.

The AWS-3 EEP stores some of the case data, i.e. initial CR submission data and final resolution letter;

however, all data containing sensitive assignment information, such as impacted records reports and subcase analysis reports, are stored outside of the portal for security purposes. The AWS-3 EEP captures the workflow and case statuses for communication and messaging purposes.

V

Coordination Requests Workflow 17

5 Coordination Requests Workflow

For each initial CR submission, licensees are required to upload two files: a csv file with the laydown data, and the cover letter as a .pdf. Once received, the portal creates a unique case number for it, stores the case data and provides a notification to the licensee that the data had been successfully received and stored. The case workflow follows the 5-, 10-, and 60-day processes defined in the Coordination Procedures in the 1695-1710 MHz and 1755-1780 MHz Bands [2], as shown below. For a detailed description of the workflow, please refer to the Advanced Wireless Services-3 1755 – 1780 MHz Early Entry Portal End-to-End Business Process [3].

During the entire Coordination Request Process, not all of the users are able to change the statuses for each Coordination Request. The tables below shows which users are allowed to change which statuses. Workflow is different for DoD users and for Federal Users.

DoD Workflow

AWS-3 Early Entry Portal (V2.3)18

Federal Workflow

5.1 5-Day Process

For each initial Coordination Request submission, licensees are required to upload two files: a csv file

Coordination Requests Workflow 19 with the laydown data and the cover letter. Once received, the portal creates a unique case number for it, stores the case data and provides a notification to the licensee that the data had been successfully received and stored.

During the first five days of the AWS-3 EEP process

1. The Portal verifies that the submitter is an authorized AWS-3 EEP user.

2. The AWS-3 Licensee submits a Cover Letter (.pdf) and a Coordination Request (a comma separated value (.csv) formatted flat file) into the Portal.

3. The Portal creates a formal case ID for the Coordination Request.

4. The Portal acknowledges receipt of the Coordination Request from the AWS Licensee within 5 days of date of submission.

5. An Acknowledged status is applied to the Coordination Request.

6. Notification is sent to all groups.

The 5-day process continues to the 10-day process.

5.2 10-Day Process

After a Coordination Request has been Acknowledgment by the Portal, members of the Engineering staff download the Coordination Request and submit it to the EEP Analysis Capability (EEPAC) for an initial analysis. This is a manual process.

The 10-day notification of completeness cycle begins the same time as the 5-day acknowledge receipt of the request cycle. During this cycle, the data in the request is reviewed and is deemed complete or incomplete. If complete, the laydown data is moved into the Analysis Queue awaiting its turn for culling.

The complete request including the data package and culled frequency assignment records are sent to the affected Spectrum Management Office (SMO) Representatives and Federal Agencies as required for review.

During this 10-day process

1. The Engineering Staff downloads the Coordination Request and takes it to the EEPAC for validation.

2. The EEPAC assesses whether technical data in the Coordination Request is complete or incomplete.

3. The Engineering staff sends Notifications and statuses to all groups stating whether the Coordination Request is complete or incomplete.

4. If incomplete, the status is updated and a message with an error report is sent to all groups.

5. If complete, the status is updated and a complete message is sent to all groups.

The 60-Day Request Analysis process begins.

AWS-3 Early Entry Portal (V2.3)20

5.3 60-Day Process

NOTE: The details of this 60-day process apply to the DoD CR requests only. The Federal Agencies perform their own engineering analysis and then report back to the DSRMT and Engineering staff with their analysis results (response - concurrence, partial concurrence, or denial of the Coordination Request). The DSRMT will then notify the AWS-3 Licensee.

The 60-day process starts once the EEPAC has determined that the Coordination Request is complete and the Engineering staff has sent messages to the DSRMT, Licensee, the SMO Representatives and the Federal Agencies. A response to the CR is required within 60 days after the deadline for the notice of completeness. During these 60 days, the following activities will occur:

1. The Engineering staff identifies the impacted Frequency Assignments based on the carrier laydown and notifies the affected Service SMO Representatives.

2. The Engineering staff performs an Electromagnetic Compatibility (EMC) analysis, including aggregate interference, from the carrier laydown to each potential DoD assignment and prepares subcase analyses, if needed. This must be accomplished within 14 days.

3. The Service SMO Representatives review their subcase analyes, coordinate with the appropriate internal units and the Engineering Staff to address any concerns on the subcases. This must be accomplished within 21 days after notification of the EMC analysis.

4. The DSRMT prepares an integrated DoD response - concurrence, partial concurrence, or denial of the Coordination Request and sends the response to the AWS-3 Licensee. This must be accomplished within 12 days.

Once the response is delivered, the Post 60-day process begins.

VI

AWS-3 Early Entry Portal (V2.3)22

6 SATOPS Coordination Agreements Workflow

For each initial SATOPS Coordination Agreement (CA) submission, licensees are required to upload a signed Coordination Agreement in .pdf using the template provided by the Public Notice. Once received, the portal creates a unique case number for it, stores the case data and provides a notification to the licensee that the data had been successfully received and stored. The case workflow then follows a 30-day DoD counter-sign SATOPS CA process.

SUBMISSION and ACKNOWLEDGMENT

30-Day DoD Counter-sign SATOPS CA Process

SATOPS Coordination Agreements Workflow 23

Not all of the users are able to change the statuses for each CA. The table below shows which users are allowed to change which statuses.

VII

SATOPS Deployment Plan Workflow 25

7 SATOPS Deployment Plan Workflow

Licensees can also upload Deployment Plans that include technical characteristics for the base stations and associated mobile units relevant to the operation within the coordination zone. These Deployment Plans contain the same content and format as the Coordination Request and follow the same basic workflow.

AWS-3 Early Entry Portal (V2.3)26

SATOPS Deployment Plan Workflow 27

Not all of the users are able to change the statuses for each deployment plan. The table below shows which users are allowed to change which statuses.

VIII

Tactical Radio Relay (TRR) Workflow 29

8 Tactical Radio Relay (TRR) Workflow

Per the approved Army 1755-1780 MHz transition plan, “existing DoD Tactical Radio Relay (TRR)… operations will continue in the 1755-1780 MHz band in regions where there is no commercial broadband deployment in this band.”

The AWS-3 Early Entry Portal (EEP) provides current information on where Army TRR operations still remain in the 1755-1780 MHz band (TRR Support Files). Although no formal coordination is required, the DoD requests to be notified when commercial operations begin in the same geographic area to prevent inadvertent interference from these remaining Army TRR operations.

When a licensee plans to deploy inside one of the areas depicted in these files, the DoD requests that the licensee notify the DoD by submitting a memo through the 1755-1780 MHz portal.

The DSRMT will pass the memo to the Army for their coordination, review, and own internal processes.

Army will then develop a response memo which DSRMT is requested to return to the licensee through the Portal.

AWS-3 Early Entry Portal (V2.3)30

Not all of the users are able to change the statuses for each TRR case. The table below shows which users are allowed to change which statuses.

IX

AWS-3 Early Entry Portal (V2.3)32

9 Post 60-Day Process

Once a response has been delivered for a Coordination Request, the Post 60-day process begins.

9.1 Licensee Response

When the Licensee receives the Response Delivered status, the Analysis Results and the Results Cover letter are delivered by the DSRMT. Delivered with the Cover Letter is a Template Letter that must be signed and uploaded by the Licensee. The Licensee has the following options:

Accept the results from the engineering analysis Request a discussion, or Object to the results

The second option requires a meeting with the DoD to review the results contained in the response letter.

ACCEPT

First, display the Case Detail page for the CR (sample is shown below).

Post 60-Day Process 33

Option are available to Download Files, Change Status, Send Message, or to Close. Select the Change Status option.

If the Licensee accepts the results, the following screen will be displayed.

AWS-3 Early Entry Portal (V2.3)34

NOTE: The file name for the Licensee Response MUST contain the Case ID in it. An example for a fictitious carrier is shown below.

LicenseeResponse_LCA455G00008.pdf

Notifications are sent out and the Engineering Staff and DSRMT will closeout the request.

Requested Discussion

If the Licensee requests a discussion of the results, a status of Requested Discussion would be applied by the Licensee.

Post 60-Day Process 35

After the discussion, the licensee uploads an updated version of the option letter, called the Final Response, where the response is to Accept or Object to the results.

NOTE: The file names for the uploaded files MUST contain the Case ID in it. An example for a fictitious carrier is shown below.

Final Response_LCA455G00008.pdf

Notifications are sent out and the Engineering Staff and DSRMT will closeout the acceptance or closeout the objection.

AWS-3 Early Entry Portal (V2.3)36

9.2 Engineering/DSRMT Closeout Accept

If the results were accepted by the licensee, the Engineering Staff will first display the Case Details (a sample is shown below).

Option are available to Download Files, Change Status, Send Message, or to Close. Select the Change Status option.

The Engineering Staff will update the electromagnetic environment (EME) with the request, change the status to Closeout Complete, and a message will be sent to the DSRMT.

The DSRMT will display the Case Details (a sample is shown below).

Post 60-Day Process 37

Note that the DSRMT members can also upload or remove additional files (meeting minutes, discussions, etc.) and send a message.

The DSRMT will then add the final status of Closed for the Coordination Request.

The final status will be displayed in the Coordination Request. A sample is shown below.

AWS-3 Early Entry Portal (V2.3)38

9.3 Engineering/DSRMT Closeout Object

If the results were objected to by the licensee, the Engineering Staff will first display the Case Details (a sample is shown below).

Option are available to Download Files, Change Status, Send Message, or to Close. Select the Change Status option.

The Engineering Staff will remove the request from the electromagnetic environment (EME), change the status to Closeout Complete, and a message will be sent to the DSRMT.

The DSRMT will display the Case Details (a sample is shown below).

Post 60-Day Process 39

Note that the DSRMT members can also upload or remove additional files (meeting minutes, discussions, etc.) and send a message.

The DSRMT will then add the final status of Closed for the Coordination Request.

The final status will be displayed in the Coordination Request. A sample is shown below.

X

Messaging/Inbox 41

10 Messaging/Inbox

The AWS-3 EEP messaging system is implemented inside of the SharePoint and has no connectivity to any outside mail system. To view or send messages users must use the AWS-3 EEP Inbox. There are two types of messages that the AWS-3 EEP messaging system supports:

1. Notifications – messages that are auto-generated by the system to notify the users of a status change. A special kind of notification, called a tickler, warns the user about the expiration of an assigned task. Ticklers are not visible by all participants and are sent 3 calendar days before the task is due.

2. AWS-3 EEP Messages – messages that are generated by users and directed to other groups, with all users within those groups having the visibility and access to the message.

The structure of the Inbox is basically the same for all users. It contains messages pertaining to Coordination Requests, SATOPS Coordination Agreements, Deployment Plans, TRR Coordinations, Status Changes, and general messaging among the users of the system. This is strictly in internal messaging system and messages cannot be viewed outside the system. Messages can only be addressed to an entire group, with each user within the group having access and visibility to the received message.

A sample list of messages is shown below.

Messages contain the Subject, the Received date and time, the Case ID, who sent the message (From), and the message Type. Links are provided for viewing the actual message (click the blue link provided under the Subject), shown below, or for viewing the Case Details (click the blue link provided under the Case ID). The Case Details are different for each user and are explained under each users help topic.

Options are available to display 10, 25, or 50 cases per page. Select the down arrow to select the number of cases per page and use the arrows to the left and right of the counts at the bottom of the page to move between pages or go to the end or beginning of the list.

Messages can be sorted by each of the list headers by hovering over the header and clicking the down arrow to view the options. A sample form the Case ID header is shown below.

AWS-3 Early Entry Portal (V2.3)42

You can sort in ascending or descending order or you could filter by individual items. A unique list of entries for each column is listed for the sort. Select the entry on which you want to filter and only those entries will be displayed.

If a column is sorted in ascending order, the header will contain an up arrow. If it is sorted in descending order, the arrow will point down. If a filter has been applied to the column, another icon will be displayed.

Samples of each are shown below.

The capability to re-size the columns also exists. Hover the cursor over the left side of the column header until a double arrow is displayed. A sample is shown below to re-size the Licensee column.

Left click the mouse button and mover the cursor to the left or right to re-size the column. At the bottom of the screen is an icon after the page count that allows you to reset the column widths back to the defaults and an icon that allows you to remove all filters .

CREATE NEW MESSAGE

To create a new message, click the Create Message at the top

The following screen will be displayed.

Messaging/Inbox 43

To select the recipients, click the To... box to display a list of the groups. A sample is shown below.

The list above shows all possible groups. This list will vary depending upon your groups privileges.

Some groups are restricted from messaging certain other groups.

AWS-3 Early Entry Portal (V2.3)44

Select the recipients from the list and click the To-> button. This will add each group recipient to the box. When complete, click OK. The list of recipients will be displayed in the Message Detail. Enter a Subject, the Case ID, and the message. Click Send to send the message or Cancel to cancel the message.

VIEW AN EXISTING MESSAGE

To view a message, click the link provided for the message Subject. A sample message is shown below.

The message will be displayed on the screen. A sample is shown below.

From here you can Close the message and return to the message list, Delete the message, or, in some cases, Reply to the sender. Not all messages have the Reply button available. The Delete button would send the message to the Deleted folder and, once a message has been read, it is removed from the list and placed in the Read filter. A link is also provided to the Case ID details.

When the Reply button is activated, a screen similar to the following will be displayed.

Messaging/Inbox 45

Enter your reply message and click the Send button, or Cancel. You may also add other recipients.

There are three folders that are available that allow you to manage your message list. These folders are Inbox, Sent, and Deleted.

You can move messages to various folders using the Move To: drop down box. Depending upon which folder you are displaying, the Move To: options will be different.

AWS-3 Early Entry Portal (V2.3)46

A filter is also available that allows you to view All of your messages, only the ones that have been Unread, or only those that have been Read. These options apply to the currently displayed folder, only.

An option is also available to Delete Selected messages. This option is not activated until you select a message or messages on the list. There is no confirmation message and the message or messages will be moved to the Deleted folder.

XI

AWS-3 Early Entry Portal (V2.3)48

11 Messaging/Case Details

An option is available from the Case Details page that allows you to send a message to any user concerning that specific case. The Case ID will automatically be populated for your message.

When the Send Message button is selected from the Case Details page, a screen similar to the following will be displayed.

Note that the Case ID has already been populated. To select the recipients, click the To... box to display a list of the groups. A sample is shown below.

Messaging/Case Details 49

The list above shows all possible groups. This list will vary depending upon your groups privileges.

Some groups are restricted from messaging certain other groups.

Select the recipients from the list and click the To-> button. This will add each group recipient to the box. When complete, click OK. The list of recipients will be displayed in the Message Detail. Enter a Subject and the message. Click Send to send the message or Cancel to cancel the message.

XII

User Roles/Groups 51

12 User Roles/Groups

There are seven types of User Roles within the AWS-3 EEP:

Licensees - Commercial wireless companies responsible for submitting CRs, CAs, DPs, and TRR Coordinations.

DoD Spectrum Relocation Management Team (DSRMT) - Overall responsibility for the AWS-3 coordination process. DSRMT is responsible for each case submitted by the AWS-3 Licensee. DSRMT provides the integrated DoD response to the AWS-3 Licensee.

Service Spectrum Management Office (SMO) Representatives - Responsible for reviewing each of the sub-cases and analysis results. Service SMO Representatives make the final decision on each sub-case. In the case of a TRR coordination, only the Army SMO is involved.

Federal Agency Representatives - Responsible for reviewing cases submitted to them and providing a response.

Engineering Analysis Staff - Retrieve cases from the Portal, run validation processes, conduct electromagnetic compatibility analyses via the Early Entry Portal Analysis Capability (EEPAC) and provide analysis results.

DoD SATOPS Lead - Responsible for reviewing each SATOPS CA and DP submitted by a Licensee, verifying them, and counter-signing the agreement.

Portal Administration Staff - Ensure the smooth operation of the Portal and establishing and maintaining user accounts.

Groups are used to aggregate users belonging to the same organization within a given role into a single entity with the same permissions, privileges, and access control. All User Roles are pre-set upon AWS- 3 EEP deployment, as all of the organizations participating in the AWS process are defined and known.

This simplifies the deployment process and reduces administrative maintenance. The table below describes the relationship between the User Roles and the groups.

User Role Groups

AWS-3 Licensees One for each carrier submitting requests. Groups will be named based on the company name

DSRMT DSRMT

Service SMO Representative Air Force Spectrum Management Office (AFSMO), Army Spectrum Management Office (ASMO), Navy Marine Corps Spectrum Center (NMSC)

Federal Agency User Department of Justice, Department of Interior

Engineering Analysis Staff Engineers

DoD SATOPS Lead DoD SATOPS Lead

Portal Administration Staff Administrators

NOTE: The DSRMT, Engineering Staff, DoD SATOPS Lead, and Administration Staff have only one

AWS-3 Early Entry Portal (V2.3)52 group (same name as role)

Each group can belong to only one User Role and each user is assigned to only one group by the AWS- 3 EEP administrator. All members of the group have the same permissions, privileges and data visibility. This allows any member of the group to act on behalf of the group.

The AWS-3 EEP Administrator creates new users, assigns them to groups, can delete users and reset user passwords. The Administrator can also create new groups, but only for the Licensees, the Service SMO Representatives or for the Federal Agency Users. DSRMT, Engineering, and Administration Roles do not have groups.

Each AWS-3 EEP user is provided an individual user ID and password. Users can change their own passwords through the portal. Each user belongs to a group based on the user’s role in the AWS business process. Upon successful authentication through the portal, based on their role, users are re-directed to the landing pages with permissions and privileges that have been allotted to their role.

The user has 5 chances to to log on within a 10 minute time frame. If he tries 3 or 4 times and is still unsuccessful, he can wait for 10 minutes and the 10 minute time limit will reset. If he tries 5 times and is unsuccessful, the user account will be locked and can only be unlocked by an administrator.

XIII

AWS-3 Early Entry Portal (V2.3)54

13 Changing Passwords

To change your password, click the Change Password option from the user drop down at the upper right of the screen.

The following screen will be displayed.

Enter your Old Password, your New Password, and then re-enter the new password to confirm it. When complete, click the Change Password button at the bottom. To cancel, click the Cancel button.

Passwords must contain a minimum of 7 characters with at least 1 special character (not a letter or a digit).

XIV

AWS-3 Early Entry Portal (V2.3)56

14 Licensees

After signing in to the portal as a commercial wireless company responsible for submitting Coordination Requests, SATOPS Coordination Agreements, SATOPS Deployment Plans, and Tactical Radio Relay Coordinations, you will be directed to your home page. A sample from a fictitious carrier is shown below.

This will display the Home page for the commercial carrier.

The list at the far left provides links to the Inbox, the Carrier Coordination Requests list, SATOPS, Army TRR Coordinations, and Resources. These links will always be available regardless of what screen is currently being displayed.

The upper right shows the user ID, the access to Help , and an icon that will suppress the title

Licensees 57 and the list at the far left of the screen. See sample below.

The link list in the middle provides the number of New Messages in your Inbox and the number of Coordination Requests for each of the listed statuses, the number of Coordination Agreements for each of the listed statuses, the number of Deployment Plans for each of the statuses, the number of TRR Coordinations for each of the statuses, and a pie chart for each showing the percentages for the different statuses. This list also provides links to submit a new case, to submit a new coordination agreement, to submit a new deployment plan, or to submit a new TRR Case. Clicking on a specific status will display a filtered list of coordination requests, agreements, deployment plans, or TRR cases by that status.

NOTE: Percentages listed on the pie chart are rounded percentages and may not add up to 100% exactly.

The down arrow next to the user ID allows you to change your password and to sign out.

AWS-3 Early Entry Portal (V2.3)58

14.1 Licensee Carrier Coordination Requests

When the Carrier Coordination Requests link is selected from the list at the left of the Home Page, a list of current coordination requests for the licensee will be listed. This list can also be accessed by selecting the Total Coordination Requests Submitted link in the middle of the Home Page. A sample is shown below.

Listed is the Case ID, the Case Title, the FCC License ID, Agency to which the request was sent, Licensee, Current Status, the Time Remaining, the Time Elapsed, the Date Submitted, the user that the coordination request was Submitted By, the date the request was Last Modified, and a Point of Contact.

NOTE: On the All Cases page, if a case is in the Post 60-day stage, N/A will be displayed for the Time Remaining and the Time Elapsed.

The icon to the left of the Case ID allows you to see, at a quick glance, where the coordination request is in the process. The following icons are used.

Options are available to display 10, 25, or 50 cases per page. Select the down arrow to select the

Licensees 59

The case list can be sorted by each of the list headers by hovering over the header and clicking the down arrow to view the options. A sample from the Case ID header is shown below.

You can sort in ascending or descending order or you could filter the list. A unique list of entries for each column is listed for the filter. Select the entry on which you want to filter, and only those entries will be displayed on the Case Details screen. This filter will be retained when you return to the All Cases screen.

If a column is sorted in ascending order, the header will contain an up arrow. If it is sorted in descending order, the arrow will point down. If a filter has been applied to the column, another icon will be displayed.

Samples of each are shown below for Case ID.

NOTE: The default sort is in descending Date Submitted order.

The capability to re-size the columns also exists. Hover the cursor over the left side of the column header until a double arrow is displayed. A sample is shown below to re-size the Licensee column.

Left click the mouse button and mover the cursor to the left or right to re-size the column. At the bottom of the screen is an icon after the page count that allows you to reset the column widths back to the defaults and an icon that allows you to remove all filters .

This screen allows the Licensee to Submit New Cases or Download Selected Cases.

To view specific cases, links are provided. Click on the Case ID you wish to view and the Case details will be displayed.

AWS-3 Early Entry Portal (V2.3)60

Some details from the Coordination Request are displayed with options to Download Files, Request Withdrawal, Send a Message, or to Close the screen. Shown at the bottom of the screen is the status log of the request showing the Status History, the Date/Time that the status was applied, the Event Details, the Event Type, and which user applied the status (By User).

The Event Details may indicate that there are files attached to the case. In that event, a link is provided allowing you to either download, or save the attachments.

NOTE: If a Withdrawal Request has already been submitted for a case or the case has completed the 60-day process, the Request Withdrawal option will not be available on this screen.

NOTE: On the Case Detail page, if a case is in the Post 60-day stage, N/A will be…