9_Licensee_EEP_Training_Slides_29_June_2017.pdf

UNCLASSIFIED

Advanced Wireless Services-3 (AWS-3) 1755-1780 MHz

Early Entry Portal (EEP) version 2.3

June 2017

• The Federal Communications Commission and National Telecommunications and Information Administration, issued a public notice specifying the procedures to be followed in allowing early entry into the 1755-1780 MHz frequency 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 1755-1780 MHz Early Entry Portal (EEP) was developed to support formal coordination between AWS-3 Licensees and the Department of Defense (DoD), the Department of Justice (DOJ), and the Department of the Interior (DOI) for early access to the 1755-1780 MHz band.

Background

• Major Functions

– Receipt of Coordination Requests (CRs), Satellite Operations (SATOPS)

Coordination Agreements (CAs), Deployment Plans (DPs), and Tactical Radio Relay

(TRR) requests from AWS-3 Licensees

– Distribution of CRs and TRR requests to DoD, DOJ, and DOI stakeholders as appropriate

– Distribution of SATOPS CAs and DPs to DoD stakeholders as appropriate

– Delivery of DoD, DOJ, and DOI responses to AWS-3 Licensees including: Receipt

Acknowledgement, Complete/ Incomplete, Concurrence/ Partial Concurrence/ Denial of CRs

– Automated status tracking and warehousing of CRs, SATOPS CAs, DPs, and TRR requests throughout the formal coordination process

– User account management

AWS-3 1755-1780 MHz EEP Portal Overview

The seven participants involved in the formal coordination for early entry into the 1755-1780 MHz band are listed below with a brief description of their role.

• AWS-3 Licensees – Commercial wireless companies responsible for submitting CRs, CAs, DPs, and TRR requests.

• DoD Spectrum Relocation Management Team (DSRMT) – Government staff with overall responsibility for the AWS-3 coordination process. DSRMT provides oversight of products and processes to include certifying analyses from

Engineering Analysis Cell staff and delivery of the integrated DoD response to the AWS-3 Licensee via the Portal.

• Service Spectrum Management Office (SMO) Representatives – Air Force, Army, and Navy/Marine Corps SMO staff responsible for review and coordination of EEPAC subcase reports/analysis results with their Service system owners. Service SMO Representatives provide the final decision on each subcase. In the case of a TRR request, only the Army SMO is involved.

• Federal Agency Representatives – DOJ and DOI staff responsible for review of DOJ and DOI cases and delivery of their Agency’s response to the AWS-3 Licensee via the Portal.

• Engineering Analysis Cell Staff – DSO contractor technical staff using EEP and EEPAC to support the CR and

SATOPS CA and DP business processes. Responsible for executing the 10- and 60-Day processes.

• DoD SATOPS Lead – Responsible for reviewing each SATOPS CA submitted by a Licensee, verifying it, and countersigning the agreement. Also responsible for reviewing deployment data

• Portal Administration Staff – DSO contractor staff responsible for ensuring the smooth operation of the Portal, and user account maintenance.

Participants

• Coordination Requests (Slide 6)

• DoD Post 60-Day Process (Slide 38)

• SATOPS (Slide 50)

• Tactical Radio Relay Requests (Slide 72)

Training Agenda

COORDINATION REQUESTS

5-Day Acknowledge Receipt of Coordination Request

• Licensee logs into the Portal

• Licensee submits CR

• Portal sets the workflow status of each coordination request to Submitted

• The CR is received via the Portal

• The Portal assigns a unique Case Number and time stamp

• Portal automatically notifies DSRMT, the Service SMO Representatives, the Engineering Cell, and the Federal agencies of the submission of a request

• Portal sets the workflow status of each coordination request to Acknowledged

• The Portal sends a notice to the Licensee acknowledging receipt of the CR

Portal Receives

CR

Portal Acknowledges

Receipt of CR

Licensee Submits

CR

10-Day Notification of Complete/Incomplete Request

• Engineering Cell staff performs validation on the CR using EEPAC to assess format, content, and correctness of the data

• EEPAC generates an error report identifying areas where the CR has failed validation rules

• If the CR data fails validation, the Engineering Cell staff sets the status to Incomplete - Resubmit and the Licensee is notified via the Portal that the CR has been rejected and is provided an error report

• If the CR data passes validation, the Engineering Cell staff sets the status to Complete - Accepted and the AWS-3 Licensee is notified via the Portal that the CR is complete and has been accepted for analysis

Engineering Cell

Performs Validation of the CR data

Engineering Cell Sends

Notification to the AWS-3 Licensee

• Engineering Cell staff identifies frequency assignments that may be affected by the carrier laydown using EEPAC

• The affected frequency assignment report is posted to the DoD AWS Coordination and Management Portal (DACAMP) for review by each Service SMO Representative

• If the CR is submitted to the Federal Agencies (DOJ or DOI), the agencies will perform their own analysis and report back to the portal when complete.

• Engineering Cell staff performs Aggregate Interference analysis on carrier laydown using the EEPAC to determine aggregate interference from AWS Licensee base stations into each potential DoD Service system

• Engineering Cell staff prepares subcase analyses results for each Service SMO Representative and posts the subcases analyses results on the DACAMP for their review

• Each Service SMO representative reviews their respective subcase analysis and coordinates the AWS CR and analysis results with their affected Military Field Units

• Any concerns are conveyed to DSRMT

• Upon completion of review, the Service SMO Representative provides response back to DSRMT

• Engineering Cell staff compiles the response for all subcase analyses into a consolidated output and posts the file to the Portal

• Engineering Cell staff prepares a cover letter and posts to the Portal

• DSRMT reviews and signs the cover letter

• DSRMT uploads the cover letter to the Portal and updates the status code

• AWS-3 Licensee is notified via the Portal that the DoD Decision is available

Services Conduct Review and Convey Decision to

DSRMT

(21 Days)

Engineering Cell

Conducts Analysis and

Results Review

(18 Days)

Identify Affected

Frequency

Assignments

(2 Days)

DSRMT Prepares

Consolidated DoD

Decision

(12 Days)

60-Day CR Analysis and Response

• When a licensee submits a CR 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 alphanumeric and are 13 characters long

• Each Case ID encapsulates a number of data elements and is structured as shown below

CR Case Creation

Licensee Name (3 Characters)

Market Area (3 Digits) AWS-3 Frequency

Block (1 Character)

Unique Computer-generated

Number (6 Digits)

• When CR cases are displayed on the screen, there is an icon to the left of the Case ID that allows you to see, at a quick glance, where the coordination request is in the process. The following icons are used.

CR Case Progress

CR Workflow Statuses

Workflow Status Description

Submitted Initial request has been submitted

Acknowledged Initial request is stored in the Portal and a unique

Case ID is generated

Complete – Accepted Request was successfully validated and accepted for analysis

Incomplete – Resubmit Request had validation errors and must be resubmitted

Response Delivered The DoD response to the request is delivered to the

Licensee

Withdrawn The request has been withdrawn and will no longer be processed

Portal Account Request Form

• Each Agency/Organization must identify a Primary and Alternate Portal Account Management point of contact (POC) that will be responsible for managing the list of users that will have access to the AWS-3 1755-1780 MHz EEP from their organization.

• All users must establish accounts prior to accessing the AWS-3 1755- 1780 MHz EEP.

Portal User Accounts

• All users must establish accounts prior to accessing the AWS-3 1755-1780 MHz EEP

• Individuals requiring access to the 1755-1780 MHz EEP should:

– Notify your Organization Portal Account POC that you need to establish a Portal Account and provide the POC with a completed Portal Account Request form

– Have your Organization Portal Account POC submit the form to the DSO/DSRMT at the email address at the top of the form

• Upon review by the DSO/DSRMT, users will receive an email notification from the

Portal administrator when the user account has been created

– Please note that user account creation may take up to 10 days to complete depending on the volume of requests

– Users will receive a separate email with the password

Portal User Accounts

User Account Registration

• User Account Management

– Users are responsible for notifying the DSRMT and their agency/organization Portal Account Management POCs of any changes to account information or access requirements

– Primary and Alternate Portal Account Management POCs are responsible for managing (additions/deletions) their agency/ organization's user account list

– Any updates should be emailed to the email address listed at the top of the Portal Account Request form

• Passwords can and should be changed periodically

– Click the down arrow beside your name at the upper right of the screen and select Change Password

– Passwords must contain a minimum of 7 characters with at least

1 special character (not a letter or a digit)

Portal User Accounts

User Account Management

EEP Log-in Page

• Initial log-in: users log into the EEP with the user ID and password provided by the Portal

Administrator.

• After the initial log-in, users have the option to change their password.

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

• The link list in the middle provides the number of New Messages in your Inbox and the number of CRs, SATOPS CAs, DPs, and TRR requests, submitted by your organization, for each of the listed statuses.

This list also provides a link to submit a new CR, CA, DP, or TRR request.

• The pie chart shows the percentages for the different statuses.

• Clicking on a specific status will display a licensee-specific filtered list of requests by that status.

Licensee Landing Page

• The AWS-3 EEP messaging system is implemented inside of 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:

– Notifications – Messages auto-generated by the system to notify the users of a status change.

– AWS-3 EEP Messages – Messages that are generated by users and directed to other user groups. All users within those groups have the visibility and access to the message.

Inbox - Messages

• 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 or for viewing the Case Details.

• Folders are available for organizing your messages and there is an option 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.

• To view a message, click the link provided under the Subject.

Inbox - Messages

• 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.

Managing Messages

• 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. 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.

• 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.

NOTE: This capability exists for all the grids in the AWS-3 EEP system.

Managing Messages

• After you select a message to view, 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.

Inbox - Viewing Messages

Inbox – Creating Messages

• To create a new message, click the Create Message option to display the following screen.

• Select the To… option to display a list of recipients.

• Enter the Subject, a Case ID, and any text that you wish for the message.

• If you are sending a message from the Case Details list, the Case ID will be automatically filled with the

Case ID.

Note: This list will vary depending upon your groups privileges. Some groups are restricted from messaging certain other groups.

• When the Carrier Coordination Requests link is selected from the Home Page, a list of all cases submitted by the user’s organization will be displayed. The icon to the left of the Case ID allows the user to see, at a quick glance, where the CR is in the 10-, 60-Day Process, whether the CR was incomplete, or was withdrawn. If the case is in the Post 60-Day Process, N/A will be displayed for the times.

• To view a specific case, click on the link provided to display the Case Details including a status history and several options.

Carrier Coordination Requests

• 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. Options are available to Download Files, Request Withdrawal, Send a Message, or to Close the screen.

Coordination Request Details

• The Licensee can submit new CRs (cases) from two places: from the Landing Page or from the Carrier Coordination Requests List

Licensee - Submit New Case

• Select the agency to which the CR will be submitted

– DOI and DOJ are used for Federal submissions only

– There is also an option to submit to All agencies which will generate three (3) different cases (one for each Agency) with the same data

• Upload the two documents that comprise the

CR:

– Cover Letter (.pdf)

– Laydown (.csv file)

Licensee - Submit New Case

• After all information is entered, click Submit. A confirmation screen will be displayed showing the unique Case ID that was assigned. An example is shown below.

• Select OK to acknowledge the Case ID.

Submit New Case Confirmation

2821 October 2015

• Once the Portal acknowledges receipt of the CR, and assigns the unique Case ID, the current status is changed and the CR is listed under the Licensee Coordination Request list.

• To view the details, select the Case ID.

5-Day Acknowledge Receipt of Coordination Request

• The details of the submitted Case are depicted in the Status History and the Event Details

• Messages are sent to the Licensee, DSRMT members, Engineering staff, and the Service

SMO Representatives Inboxes

5-Day Acknowledge Receipt of

• Click on the users Inbox to view an automatically generated notification message informing the user of the Acknowledged status change

• Notification messages will be sent to the users Inbox based on permissions

• This completes the 5-Day Process.

5-Day Acknowledge Receipt of

• The Engineering Cell staff downloads the CR files and uploads the .csv file into EEPAC for validation.

• EEPAC assesses whether technical data in the Coordination Request is “complete” or “incomplete”.

• If validation errors are observed, the CR is deemed incomplete. The Engineering Cell updates the status and a message with an error report is sent to all groups.

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

• The 60-Day Analysis process begins.

10-Day Notification of Complete/ Incomplete Request Process

Licensee - Request Withdrawal

• If, for some reason, a Licensee wants to withdraw a coordination request, an option is available that will allow the licensee to submit a Request for Withdrawal. If approved, a Withdrawn status will be displayed. The Portal Administration staff also has the option to submit a Request for Withdrawal.

• Select the Case that you wish to be withdrawn from the list of all cases. The Case Detail screen will be displayed showing you the Request Withdrawal option.

• The withdrawal request will be logged in the Event Details and a message will be sent to the Portal

Administration staff and to the DSRMT members (if the request was sent to the DoD), or to the Federal agency to which the request was sent.

• If the Request for Withdrawal is Rejected, a message will be sent to the Licensee and the status will remain as before.

Withdrawal Request Rejected

Withdrawal Request Approved - Request Withdrawn

• If the Request for Withdrawal is approved, a message will be sent to the Licensee and a status of Withdrawn will be displayed.

• DSRMT, DOI, and/or DOJ prepare a response to the Licensee’s CR. The response is comprised of

– Results Letter (.pdf) indicating

• Concurrence (all sectors in the proposed laydown approved/green)

• Partial Concurrence with operating conditions (some sectors in the proposed laydown approved/green, some denied/red)

• Denial (all sectors in the proposed laydown denied/red)

– The assumptions used in the early entry analysis and resultant constraints on approved commercial operations during the transition period

– Analysis results (.csv file) indicating the operating conditions under which the Licensee may operate the proposed deployment (approved sectors shaded green; denied sectors shaded red)

– Licensee response guidance

• DSRMT DOI, or DOJ, as appropriate, changes the CR status to Response Delivered and uploads the Results Letter (.pdf) and the Deployment Operating Conditions (.csv)

DoD, DOI, DOJ - Response Delivered

• Notifications are sent to the Licensee and all groups and the current status will display as Response Delivered on their Coordination Requests list.

Licensee - Response Delivered

DoD POST 60-DAY PROCESS

Licensee - DoD Post 60-Day Process

The DoD Post

60-Day Process begins after the

DoD Results for a given CR has been delivered to the

Licensee via the

EEP.

• The DoD Post 60-Day Process workflow is shown in the following table.

DoD Post 60-Day Process Workflow

Workflow Status Description

Results Accepted The Licensee accepts the engineering analysis results

Results Objected The Licensee objects 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 accepts the final analysis and uploads the final response

Discussion Result - Object The Licensee objects to the final analysis and uploads the final response

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

Closeout Complete Object The Request has been closed out in EEPAC. No sectors from the

Request have been integrated into the EEPAC background electromagnetic environment

Close – Accepted DSRMT member officially closes the Request

Closed - Objected DSRMT member officially closes the Request

• The Licensee is requested to respond to the DoD Results Letter by indicating an election to accept, conditionally accept, or object to the DoD’s response (partial concurrence, operating conditions, or denial of the CR)

• The Licensee has the following options:

– Accept the results (Results Accepted)

– Object to the results (Results Objected)

– Conditionally accept the results (Requested Discussion)

• The third option requires a meeting with DoD to review the Results Letter and discuss technical proposals from the Licensee to relieve the denial, partial concurrence and/or operating conditions contained in the Results Letter

• After discussions between DoD and the Licensee have been completed, the Licensee prepares the Final Response Letter indicating acceptance or objection to the DoD results (and/or the results of the discussions)

Licensee - Response to DoD Results

Licensee - Results Accepted

• If the Licensee accepts the results, the Licensee will change the status to Results

Accepted, sign the template provided and upload it to the portal.

• Notifications are sent out to the Engineering staff and the

DSRMT.

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

Licensee is shown below.

Licensee Response LCA455G000008.pdf

Licensee - Results Objected

• If the Licensee objects to the results, the Licensee will change the status to Results

Objected, sign the template provided and upload it to the portal.

• Notifications are sent out to the Engineering staff and the

DSRMT.

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

Licensee – Request Discussion

If the Licensee Requests a

Discussion of the results, the

Licensee will change the status to Requested Discussion, sign the template provided and upload it to the portal.

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

• After discussions between DoD and the Licensee have been completed, the Licensee prepares the Final Response Letter indicating acceptance or objection to the DoD results (and/or the results of the discussions)

• Notifications are sent out to the Engineering staff and DSRMT

Licensee - Final Response

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

• If the final results have been accepted by the Licensee, the Engineering Cell staff will change the status to

Closeout Complete Accept.

• An Operator-to-Operator Agreement will be established between the DSRMT and Licensee for the CR based on the results of the Post 60-Day discussions, and posted to the EEP. After both parties sign, the

DSRMT will upload the agreement to the EEP, then change the final status to Closed – Accepted.

• The DSRMT will also upload all Post 60-Day related documentation (meeting materials and minutes, email correspondence, etc.) and can send messages.

Engineering Cell/DSRMT - Closeout Complete Accept

• If the final results were objected to by the Licensee, the Engineering Cell staff will change the status to Closeout Complete Object.

• The DSRMT will change the final status to Closed – Objected.

• The DSRMT will also upload all Post 60-Day related documentation (meeting materials and minutes; email correspondence; etc.) and can send messages.

Engineering Cell/DSRMT - Closeout Complete Object

Resources Library

• When the Resources link is selected from the landing page, the

Resources page is displayed.

• The Resources page contains various types of documents that can

ONLY be uploaded by the DSRMT and Portal Administration staff.

• The document list contains a column to select documents, an icon that represents the document type (e.g., Excel, Word, etc.), the document Name and Title, and the time/date the document was uploaded (Modified) and by whom

(Modified By).

Document Download

Document Download

• The Name column will display a green star to indicate a new document and provides a direct link to the document.

The green star will remain for 2 days.

• At the top of the page there are two tabs. The BROWSE tab allows you to view all resource documents that have been uploaded. This is the default tab.

• Once you have selected a document using the check box column, the FILES tab allows you to View Properties of the document, view the Version

History of the document and to

Download a Copy. If you click the link under the Name column, you will not have the Files tab options available to you. The document will be immediately displayed for you.

Files Tab

SATELLITE OPERATIONS (SATOPS)

• SATOPS includes Coordination Agreements (CAs), Deployment Plans, and other SATOPS information (Mitigation Plans, Safety Assurance, and Contact Information).

• For each initial SATOPS CA submission, Licensees are required to upload a signed, Coordination Agreement in (.pdf) using the template provided in the Joint Public Notice. Supporting documentation can also be uploaded.

• Licensees can also upload Deployment Plans (DPs) that include technical characteristics for the base stations and associated mobile units relevant to the operation within the protection zone. These Deployment Plans contain the same content and format as the Coordination Request and follow a similar workflow.

SATOPS

SATOPS Coordination Agreement

Submission/Acknowledgement

Portal Receives

Signed SATOPS CA

Portal Routes Signed

SATOPS CA to DoD

SATOPS Lead and

Affected SMOs

Licensee Submits

Signed SATOPS CA

• Licensee logs into the Portal

• Licensee submits Signed SATOPS CA, pdf only

• Signed SATOPS CA includes a list of licenses that will operate in SATOPS Protection Zones

• Portal sets the workflow status of each Signed SATOPS CA to Submitted

• Signed SATOPS CA is received via the Portal; CA receives a unique Case Number and time stamp from Portal

• Portal notifies all participants of the submission of a Signed

SATOPS CA

• Portal sets the workflow status of each Signed SATOPS CA to Acknowledged

• Portal makes signed SATOPS CA available to DoD SATOPS Lead and all SMOs and sends out notifications to all participants

30-Day DoD Countersign CA

Coordinate Non-Template CA and Countersign

Portal Routes Countersigned

SATOPS CA to Licensee

Validate Use of CA Template in Joint Public Notice and

Countersign

• DoD SATOPS Lead determines if the Signed SATOPS CA complies with the template in the Joint

Public Notice and if it is complete

(outside the portal)

• If SATOPS CA uses the template in the PN and is complete, DoD

SATOPS Lead countersigns CA

• If SATOPS CA uses incorrect template, then DoD SATOPS

Lead will reject the CA within the

Portal, requiring the licensee to resubmit

• After additional coordination, resubmitted CA will have a new case number

• DoD SATOPS Lead coordinates the non-template CA with SMOs and SATOPS Stakeholders

(coordination outside of the portal)

• If required, proposed revisions are sent to the Licensee;

Licensee responds and cycle repeats until DoD SATOPS Lead and Licensee reach agreement

(coordination outside the portal)

• DoD SATOPS Lead countersigns the final agreed-upon CA

• Once DoD SATOPS Lead countersigns the CA, the SATOPS

Lead will upload the countersigned CA back to the

Portal and will change the workflow status to Completed, which will make it available to the

Licensee

• Notifications will go out to all participants

*30-day response only applies to CAs that use the template in the Joint Public Notice

• When a licensee submits a CA 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 alphanumeric and are 13 characters long

• Each Case ID encapsulates a number of data elements and is structured as shown below

CA Case Creation

Licensee Name (3 Characters)

CA Identifier

“0CA”

(3 Characters)

(Zero)

Unique Computer-generated

Number

• When CA cases are displayed on the screen, there is an icon to the left of the Case ID that allows you to see, at a quick glance, where the SATOPS Coordination Agreement is in the process. The following icons are used.

CA Case Progress

SATOPS Deployment Plan Submission/Acknowledgement

Licensee Submits

SATOPS DP

Portal Receives

SATOPS DP

• Licensee logs into the Portal

• Licensee submits SATOPS DP (same content and format as CR), which includes technical characteristics of the base stations and associated mobile units relevant to operation within the Protection Zone (PZ)

• Portal sets the workflow status of each SATOPS DP to Submitted

• The SATOPS DP is received via the Portal; DP receives a unique Case Number and time stamp from Portal

• Portal automatically notifies all participants of the submission of a DP

• Portal sets the workflow status of each DP to Acknowledged

Note: DP should be associated with the appropriate CA by license

SATOPS Deployment Plan Validation

• Engineering Cell staff performs validation on the DP using Early Entry Portal

Analysis Capability (EEPAC) to assess format, content, and correctness of the data

• If the DP data fails validation, the Engineering Cell staff provides an error report and sets the DP status to

Incomplete – Resubmit;

Portal notifies the Licensee that the DP must be resubmitted

• If the DP data passes validation, the Engineering Cell staff sets the status to

Complete – Accepted; Portal notifies the AWS-3 Licensee that the DP has been accepted

• Messages of completion or incompletion are sent to all participants

Note: DP validation should be the same as CR validation

Portal Notifies AWS-3

Licensee

Portal Notifies

Participants of

Complete/Incomplete DP

Engineering Cell 1st Level

Validation of the DP data

• When a licensee submits a DP 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 alphanumeric and are 13 characters long

• Each Case ID encapsulates a number of data elements and is structured as shown below

DP Case Creation

Licensee Name (3 Characters)

DP Identifier

“0DP”

(3 Characters)

(Zero)

Unique Computer-generated

Number

• When Deployment Plans are displayed on the screen, there is an icon to the left of the Case ID that allows you to see, at a quick glance, where the Deployment Plan is in the process.

The following icons are used.

DP Case Progress

• When the SATOPS link is selected from the Home Page, a list of all CAs and DPs, if any, submitted by the user’s organization will be displayed. The icon to the left of the Case ID allows the user to see, at a quick glance, where the CA or DP is in the process.

• This screen allows you to submit new CAs, new DPs, download cases or view cases.

All SATOPS Cases

SATOPS Coordination Agreements

• To view only Coordination Agreements, the All SATOPS list can be filtered or you can select the Total

Coordination Agreements Submitted link from the Home Page. A list of all agreements submitted by the user’s organization will be displayed. The icon to the left of the Case ID allows the user to see, at a quick glance, where the CA is in the process.

• To view a specific case, click on the link provided to display the Case Details including a status history and several options.

• 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. Options are available to Download All Files, Upload Other SATOPS files, Remove Other SATOPS Files, Send Messages, or to Close the screen.

SATOPS Coordination Agreement Details

• The Licensee can submit new CAs from two places: from the Landing Page or from the

SATOPS Coordination Agreement List.

Licensee - Submit New Agreement

Licensee - Submit New Agreement

• Enter a Title for the

Agreement (required) and a Point of Contact and

Notes if desired.

• Select the SATOPS

Coordination Agreement

(.pdf) to upload and click

Submit.

• The other required SATOPS supporting documents can be uploaded from the Coordination Agreement case details screen.

• These files include Mitigation Plans, Contact Information, or Safety Assurance documents.

• These files can be uploaded before or after the CA is completed/fully executed.

Other SATOPS Files

Other SATOPS Files

To upload, select the Upload Other

SATOPS File option, select the file type and then browse to locate the file to upload. Click OK.

To remove files, select the Remove Other

SATOPS Files option, select the file or files to remove and click Remove.

Any number of Mitigation Plans, Safety Assurance Files and Contact Information files can be uploaded if they have different file names. Uploading a file with the same file name and type will overwrite the previous version.

• Once a SATOPS CA has been acknowledged by the portal, the DoD SATOPS Lead, the

SMOs, and the DSRMT members are notified.

The SATOPS Lead will download the agreement and determine if the signed agreement complies with the template provided in the Public Notice and if it is complete.

Coordination is performed outside the portal.

• If the CA does not comply with the template or is incomplete, the SATOPS Lead will change the status to Incomplete - Resubmit and notifications will be sent to the Licensee, the

SMO's, the SATOPS Lead, and the DSRMT members.

• Coordination continues until the CA is agreed upon by all stakeholders.

• The SATOPS Lead countersigns the agreement and uploads it to the portal and changes the status to Completed.

• Notifications will be sent to the Licensee, the

SMOs, and the DSRMT members.

Licensee - Countersign Received

• The Licensee can submit new Deployment Plans from two places: from the Landing Page or from the SATOPS Deployment Plan List.

Licensee - Submit New Deployment Plan

Licensee - Submit New Deployment Plan

• Enter a Title for the

Deployment Plan (required), The FCC License ID, a

Point of Contact, and Notes

(if desired).

• Select the Cover Letter

(.pdf) Deployment Plan

(.csv) to upload and click

Submit.

• 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. Options are available to Download Files, Send Messages, or to Close the screen.

SATOPS Deployment Plan Details

• The Engineering Cell staff downloads the DP files and performs validation to assess format, content and correctness of data

• EEPAC assesses whether technical data in the Deployment Plan is complete or incomplete

• If validation errors are observed, the DP is deemed incomplete.

The Engineering Cell staff updates the status and a message with an error report is sent to all groups.

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

Deployment Plan Validation

TACTICAL RADIO RELAY

REQUESTS

Background

• 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.

Tactical Radio Relay Workflow

Tactical Radio Relay Workflow (cont’d)

• When a licensee submits a TRR request 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 alphanumeric and are 13 characters long

• Each Case ID encapsulates a number of data elements and is structured as shown below

TRR Case Creation

Licensee Name (3 Characters)

Market Area (TRR) AWS-3 Frequency

Block (0)

Unique Computer-generated

Number

• When TRR requests are displayed on the screen, there is an icon to the left of the Case ID that allows you to see, at a quick glance, where the TRR case is in the process. The following icons are used.

TRR Request Progress

• When the Army TRR

Coordination link is selected from the list at the left of the

Home Page, a list of current

TRR requests for the licensee will be listed. The icon to the left of the Case ID allows the user to see, at a quick glance, where the request is in the process

• To view a specific case, click on the link provided to display the

Case Details including a status history and several options.

TRR Requests

• 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. Options are available to Download Files, Request Withdrawal, Upload or Remove TRR Additional Files, Send a Message, or to Close the screen.

TRR Request Details

• The Licensee can submit new TRR cases from two places: from the Landing Page or from the All TRR Cases List.

Licensee - Submit New TRR Case

• The Licensee should review the TRR Support Files before the memo and technical data are created to determine what Army areas are affected. Also available in this list are templates for the TRR Coordination

Memo and Technical Data.

TRR Support Files

Licensee - Submit New TRR Case

• Enter the FCC License ID, a Title for the

Agreement, and a Point of Contact

(required) and Notes if desired.

• View the TRR Support Files to determine if commercial operations will affect Army TRR operations in a specific geographical area.

• Select the TRR Coordination Memo and

TRR Technical Data to include (templates can also be found on the TRR Support Files list.

• Select Submit. A unique Case ID will be assigned and, once acknowledged by the portal, the DSRMT and the Army SMO are notified.

Licensee - Request Withdrawal

• If, for some reason, a Licensee wants to withdraw a TRR Case, an option is available that will allow the licensee to submit a Request for Withdrawal. If approved, a Withdrawn status will be displayed. The

Portal Administration staff also has the option to submit a Request for Withdrawal.

• Select the Case that you wish to be withdrawn from the list of all cases. The Case Detail screen will be displayed showing you the Request Withdrawal option.

• The withdrawal request will be logged in the Event Details and a message will be sent to the Portal

Administration staff .

• If the Request for Withdrawal is Rejected, a message will be sent to the Licensee and the status will remain as before.

Withdrawal Request Rejected

Withdrawal Request Approved - Request Withdrawn

• If the Request for Withdrawal is approved, a message will be sent to the Licensee and a status of Withdrawn will be displayed.

Upload/Remove TRR Additional Files

• At any time during the process, the Licensee, the Army or the DSRMT can upload\remove TRR Additional Files containing related documentation (meeting materials and minutes, email correspondence, etc.)

Army – TRR Closeout

• The Army will perform their own internal processing of the TRR case.

• The Army will develop a response memo with either a cessation date or request for coordination.

• The memo is then distributed to the Licensee and the Army sets the status to Closed. The Portal will notify the DSRMT.