9_AWS-3_EEP_Engineering_SMO_DSRMT_EEP_Training_Slides_10_NOV_2016.pdf

UNCLASSIFIED

Advanced Wireless Services-3 (AWS-3)

1755-1780 MHz

Early Entry Portal (EEP) version 2.2

November 2016

Engineering/SMO/DSRMT Training

• 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), and Deployment Plans (DPs) from AWS-3 Licensees

– Distribution of CRs 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 and DPs 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 and Deployment Plans.

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

• 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

Training Agenda

• Coordination Requests (Slide 6)

• DoD Post 60-Day Process (Slide 43)

• SATOPS (Slide 56)

• Coordination Agreements (Slide 58)

• Deployment Plans (Slide 67)

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

60-Day CR Analysis and Response

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)

• 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 CR submitted

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

Complete - Accepted CR Successfully validated and accepted for analysis

Incomplete – Resubmit CR had validation errors and must be resubmitted

Pending Analysis with Subcases CR is pending analysis. Assignments from one or more services might be impacted by the submitted laydown. This triggers a generation of subcases for the impacted service.

Pending Analysis – No Subcases CR is waiting to be analyzed

Analysis in Progress Analysis on CR has begun

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

Subcase Review Complete Impacted services have completed the review and provided the results

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

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

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

Engineering Landing Page

• The link list in the middle provides the number of New Messages in your Inbox and the total number of CRs, CAs, DPs, and current status of each.

• The pie chart shows the percentages for the different statuses of CRs, CAs, and DPs.

• The list at the far left provides links to the

Inbox, the Carrier Coordination Requests list, the SATOPS page, Statistics and Resources.

These links will always be available regardless of what screen is currently being displayed.

• Clicking on a specific status will display a filtered list by that status.

SMO Representatives

Landing Page

• The list at the far left provides links to the Inbox, the Carrier Coordination Requests list, SATOPS, 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, the number of your

Service CR subcases, SATOPS cases, and current status of each.

• The pie chart shows the percentages for the different statuses of CRs, CAs, and DPs.

• Clicking on a specific status will display a filtered list of CRs, CAs, and DPs by that status.

• The Total Coordination Requests Submitted link provides a list of all requests regardless of service.

DSRMT Landing Page

• The link list in the middle provides the number of

New Messages in your Inbox, the number of withdrawal requests, the total number of CRs, CAs, and DPs, and current status of each.

• The pie chart shows the percentages for the different statuses of CRs, CAs, and DPs.

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

• Clicking on a specific status will display a filtered list by that status.

DoD SATOPS Lead

Landing Page

• The list at the far left provides links to the Inbox, SATOPS, 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, the total number of CAs and DPs, and current status of each.

• The pie chart shows the percentages for the different statuses of CAs and DPs.

• Clicking on a specific status will display a filtered list by that status.

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

Engineer Carrier Coordination

Requests

• When the Carrier Coordination Requests link is selected from the Home Page, a list of current coordination requests will be listed. The icon to the left of the Case ID allows you to see, at a quick glance, where the coordination request is in the 10-, 60-Day Process or whether it was incomplete or withdrawn. If the case is in the Post 60-Day Process, N/A will be displayed for the times.

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

Coordination Request Details

• 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, Change Status, Send

Messages, or Close the screen. If a Coordination Request has been sent to a Federal Agency, the Change Status option is not available. The Federal Agencies will perform their own engineering analysis.

Engineering - Download Files

• The first step for the Engineering Cell staff is to locate those Coordination Requests that have been acknowledged by the Portal (current status is Acknowledged) and

Download Files. This starts the 10-Day Process.

• Files are taken to the EEP Analysis Capability (EEPAC) for an initial analysis.

• Engineers will receive notification if the Carrier laydown passed validation or not. If not, an error report is created.

• The engineer will then return to the EEP and change the statuses of the CRs that were

Acknowledged and upload any error reports.

Engineering - Change Status

Complete

• If complete, the Engineering Cell staff will change the status to Complete - Accepted and notifications are sent to the Licensee, the DSRMT members, and to the Service

SMO and/or the Federal Agency to which the Coordination Request was sent.

• This will start the 60-Day Process.

Engineering - Change Status

Incomplete

• If incomplete, the Engineering Cell Staff will changes the status to Incomplete - Resubmit and the Licensee is notified that the request has been rejected and is provided an error report.

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

Final Response_LCA455G000008.csv

Final Response_LCA455G000008.pdf

60-Day CR Analysis

• The Engineering Cell staff will then perform an Electromagnetic

Compatibility (EMC) analysis, including aggregate interference, from the carrier laydown to each potential DoD assignment to identify the impacted

Frequency Assignments based on the carrier laydown and notify the affected Service SMO Representatives, if any.

• This must be accomplished within the first 14 days of the 60-Day Process.

Engineering - Change Status

Pending Analysis - No Subcases

• If DoD assignments are not affected, the Engineering Cell staff will then change the status from

Complete - Accepted to Pending Analysis - No Subcases.

Engineering - Change Status

Pending Analysis - Subcases

• If DoD assignments are affected, the Engineering Cell staff will then change the status from

Complete - Accepted to Pending Analysis with Subcases and select the affected Service

SMOs. See examples below.

• The affected Service SMOs and the DSRMT will receive notification of the status change.

60-Day CR Analysis

• The Coordination Requests are then analyzed by the EEP Analysis Capability in the order in which they were uploaded.

• If there were no subcases, preliminary results will be available on the DACAMP for the services to view.

• If there were subcases involved, the Engineering Cell staff will change the status to Analysis in

Progress when the analysis starts.

• Once complete, Subcase reports are generated and posted to the DACAMP. The Engineering

Cell staff will change the status to Subcase Report Posted and the Service SMOs will be notified.

SMOs Subcase Review

• When the Service SMO Representatives receive a status of Subcase Report Posted for a

Coordination Request, they will review their subcase analysis from the DACAMP, 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.

• Once the Service SMO Representative completes the review, they will change the status to

Subcase Review Complete. If changes were made to the report, the With Changes box must be checked. This will add an entry in the Case Details and send a notification to the Engineering staff.

• If the SMO Representative does not respond, agreement with the report is assumed and the

Engineering Cell staff can change the status to Subcase Review Complete.

The SMOs, the Engineering staff and the DSRMT will receive notifications.

Engineering/SMOs - Change

Status Subcases

• Once the Service SMOs have reviewed the report, they will change the status to Subcase

Review Complete.

• Each service affected will add a separate Subcase Review Complete status. When all services have responded, the Event Details will indicate that the Subcase Review is complete.

• If any affected service does not respond, agreement with the report is assumed and the

Engineering Cell staff can change the status to Subcase Review Complete.

Engineering - Change Status

Results Letter

• Whether there were subcases or not, the Engineering Cell staff will create a Results Letter, change the status to Result Letter Available, and attach it to the Coordination Request Case Details.

The DSRMT will be notified.

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

Result Letter_LCA455G000008.csv

Result Letter_LCA455G000008.pdf

DSRMT - Change Status

Response Delivered

• Once a Coordination Request analysis has been completed and the Results Letter is available from the Engineering Cell staff, the DSRMT will prepare an integrated DoD response: either

Concurrence, Partial Concurrence, or Denial of the Coordination Request, change the status to

Response Delivered, and send the response to the AWS-3 Licensee.

• This must be accomplished within 12 days.

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

DSRMT Approve/Reject

Withdrawal Request

• When a Request for Withdrawal has been requested by the Licensee, the DSRMT member or the Administrative staff will receive a message in the Inbox and will see additional options when the Case Details are reviewed.

DSRMT Pause/Resume Case Clock

• At anytime during the Coordination Request process, the DSRMT member or a member of the Admin staff can pause the clock which will stop the 60-Day analysis. After displaying a Coordination Request, the option to Pause Case Clock will be available.

• A confirmation message will be displayed when the option is selected. Once confirmed, the Pause Case

Clock option changes to Resume Case Clock.

• The CR list will also show the pause icon and, depending upon how long you pause the clock, you can see the time remaining and the time elapsed.

DSRMT Notify Exceeding 60 Days

• If the analysis for the Coordination Request is going to exceed the 60-Day time limit, the DSRMT member or the Administration staff can extend the time limit using this option.

• After displaying the details of the CR that will exceed the 60-Day analysis, select the Notify

Exceeding 60 Days option at the top.

• A confirmation message will be displayed, messages will be sent to Engineering staff, SMOs, Admins, and the Event Details will reflect the change.

DoD POST 60-DAY PROCESS

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.

DoD Post 60-Day Process

Workflow Statuses

Workflow Status Description

Results Accepted Licensee accepts the engineering analysis results

Requested Discussion Licensee Conditionally Accepts or Objects to the analysis results and requests a meeting with the DoD

Discussion Result - Accept Licensee accepts final analysis and uploads the final response

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

Closeout Complete Accept If the results were Accepted by the licensee, the Electromagnetic Environment (EME) is updated with the request

Closeout Complete Object If the results were Objected To by the licensee, the request is permanently removed from the EME database

Closed - Accepted DSRMT member officially closes the request

Closed - Objected DSRMT member officially closes the request

Licensee Response

• Delivered with the Response Letter is a Template Letter that must be signed and uploaded as the Licensee Response. The Licensee has the following options:

• Accept the results (Results Accepted)

• Conditionally accept the results (Requested Discussion)

• Object to the results (Requested Discussion)

• The last two options require a meeting with the DoD to review the results contained in the Response Letter.

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

Engineering/DSRMT – Closeout

Complete Accept

• If the licensee accepts the results, the status is changed to Results

Accepted. The Engineering Cell staff will then change the status to Closeout

Complete Accept and update electromagnetic environment (EME).

• Once the engineering database is closed out, the DSRMT officially closes the request and can upload or remove additional files (meeting minutes, discussions), or send a message.

• From this point on, the licensee can once again submit a new request for the same license.

Engineering/DSRMT – Closeout

Complete Object

• If the licensee objects to the results, the status is changed to Discussion Result - Object.

The Engineering Cell staff will then change the status to Closeout Complete Object and remove the request from the electromagnetic environment (EME).

• Once the engineering database is closed out, the DSRMT officially closes the request and can upload or remove additional files (meeting minutes, discussions, etc.) or send a message.

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

Resources Library

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

• The FILES tab provides several options for resource documents:

• Uploading

• Opening and checking out

• Managing

• Downloading

• Not all of these options are available to all users.

Resources Library

• The Resources page is slightly different for the DSRMT and

Portal Administration staff.

• There are three options available to upload a Resource Document:

– Resources Home Page

– Drag and Drop

– Files Tab

• The Help file lists the valid file types for upload.

Document Upload

Document Upload

• To add a document from the Resources

Home Page, select the new document link. Browse to select the file you wish to upload. To add version comments, enter the text in the Version Comments box.

Click OK to add the document.

• If this is the first time the document has been uploaded, you do not need to check the 'Add as a new version to existing files' check box.

• If you do not check the box, and a file already exists with the same name, a warning message will be displayed.

• Once the document has been uploaded successfully, a screen will be provided to update the properties of the file. Enter a

Title for the document, Save, Cancel or

Delete the document.

Resource Home Page

Document Upload

• To upload a document using the Drag and Drop option, select the files from your computer and drag and drop them to the new document area.

• The document will automatically be added to your list and not allow you to enter a document title.

• If you select a file that already exists in your list, a warning message will be displayed prompting you to

Replace the document or Cancel the upload.

• If you Replace the document, a new version will be created automatically.

The document list is displayed and a message indicating that the Upload was complete. Dismiss the message by clicking the DISMISS link.

Drag and Drop

Document Upload

• To upload a document using the FILES Tab option, select Upload Document from the

Files Tab. Browse to select the file you wish to upload. To add version comments, enter the text in the Version Comments box. Click OK to add the document.

• If this is the first time the document has been uploaded, there is no need to check the 'Add as a new version to existing files' check box.

• If you do not check the box, and a file already exists with the same name, a warning message will be displayed.

• Once the document has been uploaded successfully, a screen will be provided to update the properties of the file. Enter a

Title for the document, Save, Cancel or

Delete the document.

Files Tab

Document Download

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

• When a document is first uploaded, a green star will be displayed after the name. This will remain for 2 days indicating a new document.

• This FILES tab also allows the DSRMT and the Portal Administrative staff to

Open & Check Out, and Manage the resource documents.

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

• When the SATOPS link is selected from the Home Page, a list of all CAs and DPs, if any, submitted 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 download 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 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

SATOPS Lead - Change Status

• Coordination is performed with the SMOs and SATOPS stakeholders.

• If revisions are required, the Licensee is notified and responds.

• The Cycle repeats until the SATOPS Lead and Licensee agree.

• The SATOPS Lead countersigns the agreement, uploads it back to the Portal and changes the status to

Completed and all participants are notified.

Licensee - Upload/Remove

Supporting Files

• During the Coordination Cycle, the Licensee can Upload or Remove Other SATOPS files. These files include Mitigation Plans, Contact Information, or Safety Assurance documents.

• These are all .pdf files and are available to the SATOPS Lead, the DSRMT, the SMO’s, and the

Admin staff.

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

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

• 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

• 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 Deployment Plans

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

Deployment Plans Submitted link from the Home Page. A list of all deployment plans 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 DP 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.

Deployment Plan Validation

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

• The Engineering Cell staff performs SATOPS interference analysis on carrier laydown using the EEPAC to determine power received from SATOPS sites at AWS Licensee base stations.

• Status is set to Analysis in Progress.

• Engineering Cell staff prepares analysis results for each SATOPS site and posts the results to the portal for downloading by SATOPS Lead and Service SMO representatives. Status is set to Analysis Report Posted.

• Notifications are sent to SATOPS Lead, Administration, the DSRMT, the Engineering staff, and the Service SMO representatives.

Deployment Plan Analysis

• When complete, an analysis report is prepared and posted and the SATOPS Lead, the Administration staff, the DSRMT and the service SMO representatives are notified.

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

Engineering/DSRMT/Admin -

Statistics

• The AWS-3 EEP maintains a statistical database so that processing results can be produced. The Statistics page can only be accessed by users in the Administration, Engineer, DSRMT, and Federal roles.

Coordination Requests, Coordination

Agreements or Deployment Plans will be included in the statistics. Statistics are accessed from the Home Page.

• Options allow you to enter a specific Status, a

Time Unit, and dates.

• A graph will be displayed with results of your select.

• There is also an option to Export the results to a .csv file – both Chart data and All Data by

Cases.

• A second type of export allows the user to download the data organized by case.