14_DSO-HDBK-15-098-EEP_Analysis_Capability_SOP_11-30-2016_DRAFT_.pdf

Defense Information Systems Agency

Defense Spectrum Organization

Strategic Planning Division

Fort George G. Meade, MD 20755

Handbook

Early Entry Portal Engineering Analysis Capability Cell

Standard Operating Procedures (DRAFT)

DSO-HDBK-15-098

30 November 2016

Prepared for:

Defense Spectrum Organization 6916 Cooper Avenue

Fort George G. Meade, MD 20755-7901

Prime Contractor

Harris Corporation

16701 Melford Blvd., Suite 200 Bowie, MD 20715

Formatted: Font color: Red

Defense Information Systems Agency

Day Month 2010 iii Joint Spectrum Center

Distribution authorized to DoD Components only: Operational Use; November 2016. Other requests shall be referred to the

DSO.

Early Entry Portal Analysis Capability Standard Operating Procedure

Defense Spectrum Organization ii

This report was prepared by Harris Corp. under Contract HC1047-07-D-0001 in support of the Defense Information Systems Agency, Defense Spectrum Organization Directorate.

This report has been reviewed by the following Harris Corporation personnel:

LYNN CUMBERPATCH

Project Manager, Harris Corp.

ALEXANDRA FINKLER

Chief Software Engineer, Harris Corp.

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

HOWARD J. MCDONALD ROBERT L. SCHNEIDER

Chief, Advanced Access Initiatives Branch Technical Director Strategic Planning Division Defense Spectrum Organization

Defense Spectrum Organization iii

REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188

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

YOUR FORM TO THE ABOVE ADDRESS.

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

11-2016 Handbook

4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER Early Entry Portal Analysis Capability Standard Operating Procedure HC1047-07-D-0001

5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER Krush, Kathryn; Somerville, Michael E. T3747-4

5e. TASK NUMBER

TO-1138

5f. WORK UNIT NUMBER

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

NUMBER Harris Corporation 16701 Melford Blvd., Suite 200 Bowie, MD 20715 DSO-HDBK-15-098

9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S) Strategic Planning Division P.O. Box 549 Fort George G. Meade, MD 20755-0549

EEPAC SOP

11. SPONSOR/MONITOR’S REPORT

NUMBER(S)

12. DISTRIBUTION / AVAILABILITY STATEMENT

Distribution authorized to DoD Components only: Operational Use; November 2016. Other requests shall be referred to the

DSO.

13. SUPPLEMENTARY NOTES

14. ABSTRACT

This Early Entry Portal Analysis Capability (EEPAC) Standard Operating Procedure (SOP) document is intended to define and describe the use of EEPAC within the early entry workflow. Applicable processes, technical approaches, portal management techniques, continuity of operations, operational security, and modifications/enhancement approval mechanisms are detailed in this document.

15. SUBJECT TERMS

Advanced Wireless Services-3, AWS-3, Early Entry Portal, EEP, Early Entry Portal Analysis Capability, EEPAC, Engineering Analysis Cell, Advanced Wireless Services-3 EEP Engineering Analysis Cell, Coordination Agreement, CA, Coordination Request, CR, DoD AWS-3 Coordination and Management Portal, DACAMP, Project Management Plan, PMP, Satellite Operations, SATOPS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION

OF ABSTRACT

18. NUMBER

OF PAGES

19a. NAME OF RESPONSIBLE JSC PERSON

a. REPORT b. ABSTRACT c. THIS PAGE Henry Brus

U U U SAR 82 19b. TELEPHONE NUMBER 410-293-9265

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

Defense Spectrum Organization iv

This page intentionally left blank.

Defense Spectrum Organization v

Record of Changes Change Number Date Section

Number Description Modified By

Defense Spectrum Organization vi

Defense Spectrum Organization vii

Table of Contents

1. INTRODUCTION....................................................................................................... 1-1

1.1 BACKGROUND .......................................................................................................... 1-1

1.2 OBJECTIVE ................................................................................................................. 1-2

1.3 APPROACH ................................................................................................................. 1-2

2. KEY ELEMENTS ....................................................................................................... 2-1

2.1 WORKFLOW TOP-LEVEL DESCRIPTION ............................................................. 2-1

2.2 THE EEP....................................................................................................................... 2-2

2.3 EEPAC .......................................................................................................................... 2-3

2.4 AWS-3 LICENSEES .................................................................................................... 2-3

2.5 DACAMP ..................................................................................................................... 2-3

2.6 DSRMT ......................................................................................................................... 2-3

2.7 SERVICE SMOS .......................................................................................................... 2-3

2.8 EEP ENGINEERING ANALYSIS CELL ................................................................... 2-3

3. SCHEDULED PROCESSES ..................................................................................... 3-1

3.1 THE 5-DAY PROCESS ............................................................................................... 3-1

3.1.1 Key Elements ................................................................................................................ 3-1

3.1.2 Business Process ........................................................................................................... 3-1

3.1.3 Business Output ............................................................................................................ 3-1

3.2 THE 10-DAY PROCESS ............................................................................................. 3-1

3.2.1 Key Elements ................................................................................................................ 3-1

3.2.2 Business Process ........................................................................................................... 3-2

3.2.3 Business Outputs........................................................................................................... 3-5

3.3 THE 60-DAY PROCESS (DAYS 1 TO 2) .................................................................. 3-5

3.3.1 Key Elements ................................................................................................................ 3-5

3.3.2 Business Process: Identify Affected Records .............................................................. 3-5

3.3.3 Business Deliverables ................................................................................................... 3-8

3.4 THE 60-DAY PROCESS (DAYS 3 TO 22) ................................................................ 3-8

3.4.1 Key Elements ................................................................................................................ 3-8

3.4.2 Business Process: Analysis .......................................................................................... 3-8

3.4.3 Business Deliverables ................................................................................................. 3-11

3.5 THE 60-DAY PROCESS (DAYS 21 TO 43) ............................................................ 3-11

3.5.1 Key Elements .............................................................................................................. 3-11

3.5.2 Business Process: Subcase Review............................................................................ 3-11

3.5.3 Business Deliverables ................................................................................................. 3-14

3.6 THE 60-DAY PROCESS (DAYS 44 TO 56) ............................................................ 3-14

3.6.1 Key Elements .............................................................................................................. 3-14

3.6.2 Business Process: Results Letter ............................................................................... 3-14

3.6.3 Business Deliverables ................................................................................................. 3-17

3.7 THE SATOPS CA PROCESS .................................................................................... 3-17

3.7.1 Key Elements .............................................................................................................. 3-17

3.7.2 Business Process ......................................................................................................... 3-17

3.7.3 Business Outputs......................................................................................................... 3-19

3.8 THE SATOPS DP PROCESS: VALIDATE AND LOAD ....................................... 3-19

3.8.1 Key Elements .............................................................................................................. 3-19

3.8.2 Business Process ......................................................................................................... 3-19

Defense Spectrum Organization viii

3.9 THE SATOPS DP PROCESS: PERFORM ANALYSIS .......................................... 3-22

3.9.1 Key Elements .............................................................................................................. 3-22

3.9.2 Business Process ......................................................................................................... 3-23

3.9.3 Business Outputs......................................................................................................... 3-25

3.10 THE FIELD TRIAL REQUEST PROCESS .............................................................. 3-25

3.10.1 Key Elements .............................................................................................................. 3-25

3.10.2 Business Process ......................................................................................................... 3-26

3.10.3 Business Outputs......................................................................................................... 3-28

4. AD HOC PROCESSES .............................................................................................. 4-1

4.1 COORDINATION REQUEST WITHDRAWS ........................................................... 4-1

4.1.1 Key Elements ................................................................................................................ 4-1

4.1.2 Business Processes ........................................................................................................ 4-1

4.1.3 Business Deliverables ................................................................................................... 4-1

4.2 COORDINATION REQUEST ROLLBACKS ............................................................ 4-1

4.2.1 Key Elements ................................................................................................................ 4-1

4.2.2 Business Processes ........................................................................................................ 4-1

4.2.3 Business Deliverables ................................................................................................... 4-2

4.3 THE POST 60-DAY PROCESS................................................................................... 4-2

4.3.1 Key Elements ................................................................................................................ 4-2

4.3.2 Business Process ........................................................................................................... 4-2

4.3.3 Business Deliverables ................................................................................................... 4-5

5. SYSTEM ENGINEERING ........................................................................................ 5-1

5.1 THE ENGINEERING STUDIES PROCESS: STUDY DESIGN ............................... 5-1

5.1.1 Key Elements ................................................................................................................ 5-1

5.1.2 Business Process ........................................................................................................... 5-1

5.1.3 Business Outputs........................................................................................................... 5-5

5.2 THE ENGINEERING STUDIES PROCESS: PERFORM STUDY AND DOCUMENT

RESULTS .................................................................................................................................... 5-6

5.2.1 Key Elements ................................................................................................................ 5-6

5.2.2 Business Process ........................................................................................................... 5-6

5.2.3 Business Outputs........................................................................................................... 5-9

5.3 SUPPLEMENTAL DATA ........................................................................................... 5-9

5.3.1 Supplemental Data Generation ................................................................................... 5-10

5.3.2 Supplemental Data Modifications .............................................................................. 5-10

5.3.3 Supplemental Data Configuration Management......................................................... 5-10

5.4 EEPAC BASELINE DEFINITION ............................................................................ 5-10

5.4.1 Baseline Documentation ............................................................................................. 5-11

5.4.2 Baseline Modifications ............................................................................................... 5-11

5.4.3 Baseline CM ............................................................................................................... 5-11

6. BEST PRACTICES .................................................................................................... 6-1

6.1 ISSUE RESOLUTION ................................................................................................. 6-1

6.2 SYNCHRONIZING DATA SETS ............................................................................... 6-1

6.3 MANAGING CR CASE HISTORIES ......................................................................... 6-2

6.4 ENGINEERING QA..................................................................................................... 6-3

6.5 TRACKING METRICS ............................................................................................... 6-4

6.6 COOP ............................................................................................................................ 6-4

Defense Spectrum Organization ix

6.7 IA AND OPERATIONAL SECURITY ....................................................................... 6-5

6.8 EEPAC MODIFICATIONS/ENHANCEMENTS ....................................................... 6-7

6.9 CHANGE REQUEST MANAGEMENT ..................................................................... 6-8

7. REFERENCES ............................................................................................................ 7-1

8. ACRONYMS ............................................................................................................... 8-1

Defense Spectrum Organization x

Defense Spectrum Organization xi

List of Figures Figure 1-1. Documentation Diagram .......................................................................................... 1-3 Figure 2-1. Overall Early Entry Coordination Process Landscape Diagram .............................. 2-2 Figure 3-1. 10-Day Notification of Complete/Incomplete CR Procedure .................................. 3-3 Figure 3-2. Identify Affected Records (2 Days) ......................................................................... 3-6 Figure 3-3. Analysis (18 Days) ................................................................................................... 3-9 Figure 3-4. Subcase Review (21 Days)..................................................................................... 3-12 Figure 3-5. Results Letter (12 Days) ......................................................................................... 3-15 Figure 3-6. SATOPS CA Process (30 Days) ............................................................................ 3-18 Figure 3-7. SATOPS DP Process: Validate and Load ............................................................. 3-21 Figure 3-8. SATOPS DP Process: Perform Analysis .............................................................. 3-24 Figure 3-9. FTR Process ........................................................................................................... 3-27 Figure 4-1. Post 60-day Process.................................................................................................. 4-3 Figure 5-1. Engineering Studies Process: Study Design ........................................................... 5-2 Figure 5-2. Engineering Studies Process: Perform Study and Document Results ..................... 5-7

Defense Spectrum Organization xii

Defense Spectrum Organization 1-1

1. INTRODUCTION

This handbook provides a description and Standard Operating Procedure (SOP) for use of the Early Entry Portal Analysis Capability (EEPAC) to analyze coordination requests for early entrants into the Advanced Wireless Services-3 (AWS-3) 1755-1780 MHz frequency bands. The EEPAC is an automated Electromagnetic Compatibility (EMC) analysis tool that was developed to evaluate the aggregate interference effects of AWS deployments on Federal communications-electronics systems. The tool was designed for use by the Defense Spectrum Organization (DSO) and Contractor engineering staff to provide EMC analysis results through a web-based interface known as the DSO Early Entry Portal (EEP) and provide these results to the Department of Defense (DoD) Spectrum Relocation Management Team (DSRMT) and Federal Spectrum Management Offices (SMOs) for consideration in determining the need for restrictions on AWS deployment requests.

Section 2, Key Elements, provides a basic introduction for each of the key elements that make up the EEPAC SOP: EEP, EEPAC, AWS-3 Licensees, DoD AWS-3 Coordination and Management Portal (DACAMP), DSRMT, Service SMO, and EEP Engineering Analysis Cell (Engineering Cell). This section also contains a top-level description of the EEPAC workflow. Section 3, Scheduled Processes, describes in detail each of the processes that follow a set schedule: Coordination Request (CR) 5-day process, CR 10-day process, CR 60-day process, Satellite Operations (SATOPS) Coordination Agreement (CA) process, and SATOPS Deployment Plan (DP) process. Section 4, Ad Hoc processes, describes in detail each of the processes that do not occur within a specified time frame:

CR Withdraws, and the Post 60-day process. Sections 3 and 4 also contain a flowchart for each process and sub-process. Section 5, System Engineering, describes the SOP for EEPAC functions that are performed by the Engineering Cell outside of the formal processes described in sections 3 and 4. This section includes a description of the engineering studies process, which is used to evaluate which EEPAC process inputs have a significant impact on the process output, and what the target level of those inputs should be to achieve a desired result (output). Section 6, Best Practices, describes the practices that are followed by the Engineering Cell to ensure consistent quality and adherence to standards. This section provides procedures for issue resolution, synchronizing data sets, managing CR case histories, engineering Quality Assurance (QA), tracking metrics, Continuity of Operations (COOP), Information Assurance (IA), and change request management.

1.1 BACKGROUND

The Federal Communications Commission (FCC) has reallocated the 1755 – 1780 MHz band for use by commercial entities (Amendment of the Commission’s Rules with Regard to Commercial Operations in the 1695 – 1710 MHz, 1755 – 1780 MHz, and 2155 – 2180 MHz Bands [1]) and completed its auction of AWS-3 licenses. The Services and the Defense Information Systems Agency’s 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 DoD and commercial systems operating in the 1755 – 1780 MHz frequency band.

Defense Spectrum Organization 1-2

The FCC and the National Telecommunications and Information Administration (NTIA) issued Public Notice DA 14-1023, Coordination Procedures in the 1695 – 1710 MHz and 1755 – 1780 MHz Bands [2], to specify 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 EEP and EEPAC were developed to automate the AWS-3 CR and SATOPS DP processes associated with AWS-3 frequency bands (1755

– 1780 MHz) within the DoD both in the context of early entry applications as well as ongoing coordination applicable to Government stations that would to operate in the band after the transition period.

The EEPAC draws upon the experience gained by the DoD during the analysis of commercial AWS-1 licensees. The EEPAC shall automate carrier data validation, identification of affected systems, DoD report generation and consolidation of DoD sharing assessments, and will also provide an improved aggregate interference analysis capability of AWS-3 Long-Term Evolution User Equipment (UE) uplinks into DoD systems currently operating in the 1755 – 1780 MHz band. Please reference the AWS-3 Early Entry Portal Analysis Capability Software Requirements Specification [3] for a detailed description of EEPAC software requirements. Please reference the AWS-3 Early Entry Portal User Guide and On-line Help [4] and AWS-3 Early Entry Portal Analysis Capability User Manual and Help Files [5] for detailed instructions on how to use the EEP and EEPAC software.

1.2 OBJECTIVE

This EEPAC SOP document is intended to define and describe the use of the early entry workflow. Applicable processes, technical approaches, portal management techniques, COOP, operational security, and modifications/enhancement approval mechanisms are detailed in this document.

1.3 APPROACH

This document covers the retrieval of CRs and CAs from the EEP, managing the EEPAC analysis queue, status/progress tracking, CR and CA EMC analysis, QA, data set management, case history management, COOP, Engineering Cell interaction with DSRMT/SMOs, IA, operational security, and EEPAC changes/modifications/enhancements. The scope of this document is limited to providing a description of operator interactions between EEPAC, EEP, and DACAMP; an explanation of the various processes for the operation of EEPAC; and a description of the systems engineering processes that leverage EEPAC as a tool. A list of reference documents is provided in Section 7. The diagram in Figure 1-1 provides a graphical representation of the types of documents that are referenced and the relationship between them. These documents include Program Change Requests (PCRs), Algorithm Definition Documents (ADDs), Software Design Documents (SDDs), and System Requirements Specifications (SRSs).

Defense Spectrum Organization 1-3

Figure 1-1. Documentation Diagram

Defense Spectrum Organization 1-4

Defense Spectrum Organization 2-1

2. KEY ELEMENTS

2.1 WORKFLOW TOP-LEVEL DESCRIPTION

The AWS-3 EEP and EEPAC were developed to automate the AWS-3 CR and SATOPS CA and DP processes associated with AWS-3 (1755 – 1780 MHz) within the DoD both in the context of early entry applications as well as ongoing coordination applicable to Government stations that will operate in the band after the transition period. Public Notice DA 14-1023 [2], released by the NTIA and the FCC, describes the coordination procedures in the 1695 – 1710 MHz and 1755 – 1780 MHz bands, providing guidance to the AWS-3 licensees and the affected Federal incumbents regarding coordination between Federal and non-Federal for shared use of the 1695 – 1710 MHz and 1755 – 1780 MHz bands.

This public notice informed the EEP Business Process, which is described in detail in the AWS-3 1755 – 1780 MHz Early Entry Portal End-to-End Business Process [6] document.

Figure 2-1 below depicts the overall early entry coordination process landscape (Army Spectrum Management Office (ASMO), Air Force Spectrum Management Office (AFSMO), Electromagnetic Environment (EME), For Official Use Only (FOUO), Local Area Network (LAN), Navy-Marine Spectrum Center (NMSC)). This diagram depicts, beginning from the left, that Licensee CRs are entered into the EEP via a standard web browser with access control management via authorized user names and associated passwords.

The EEP is a Microsoft SharePoint capability that offers a public-facing component for AWS carrier access, as well as a private facing side that is available only to DSO, Federal, and Contractor staff. The EEP supports up to 50 simultaneous users and can be run under current versions of Internet Explorer, Google Chrome, and Mozilla Firefox browsers. The portal provides a conduit for the receipt and acknowledgement of CRs and SATOPS CAs and DPs from authorized/registered AWS licensees, distribution of CRs and SATOPS CAs and DPs to DSRMT, SMO, and contractor Engineering Cell personnel for EMC analysis, analysis review and coordination, and the formal provision of any AWS site/sector activation restrictions to the requesting AWS licensee, SMOs, and DSRMT. The EEP also provides automated status tracking and warehousing of CRs and SATOPS CAs and DPs throughout the coordination process. A detailed description of the EEP system requirements can be found in the AWS-3 Early Entry Portal System Requirements Specification [7]. A detailed description of the EEPAC software requirements can be found in the Software Requirements Specification [3].

Once CRs are uploaded to the EEP then the various SMOs, Agencies, DSRMT and EEPAC Engineers can access this information via a web-based interface. After an acknowledgement and validation process, EEPAC then performs analysis. After EEPAC analysis is complete, EEPAC results are then transferred back to the SMOs, Agencies, DSRMT and Engineers on the DoD Enterprise Portal Service (DEPS) DACAMP via a controlled network access requiring a Common Access Card (CAC) and password for Governmental review for additional as-desired analysis and decisional information/inputs back to the EEPAC Contractor. Once decisional information is available through EEPAC, and after consultation with the SMOs, Agencies and DSRMTs, summary decisional information is passed back to AWS-3 Licensees by way of a status change on the EEP.

Defense Spectrum Organization 2-2

Please reference the AWS-3 Early Entry Portal Software Design Document [8] for a detailed description of the EEP system architecture.

Figure 2-1. Overall Early Entry Coordination Process Landscape Diagram

2.2 THE EEP

The EEP allows licensees to submit their CRs, SATOPs CAs, and SATOPs DPs for early entry coordination. Please reference the End-to-End Business Process [6] for a detailed description of the EEP business process. The coordination procedures in the 1695 – 1710 MHz and 1755 – 1780 MHz bands are described in Public Notice DA 14-1023 [2], which was jointly released by the NTIA and the FCC. The purpose of the EEP is to automate the routine processing and tracking of AWS-3 CRs and SATOPS CAs in support of the DoD spectrum managers’ responsibility to protect government and military frequency assignments in the 1755–1780 MHz band. EEP is built on SharePoint, with the server currently residing at the Contractor data center. The EEP has a set of help files accessible to the end user, reference the AWS-3 EEP Help system. Please reference the System Requirements Specification [7] for detailed information on the EEP system requirements.

Coordination Requests (CR) from Licensees

• Deployment Laydowns

• Cover Letters

Landing Page

Landing Page

Landing Page

ASMO Subcases

• ASMO Affected Assignments

• EEPAC Analysis

• ASMO Responses NMSC Subcases

• NMSC Affected Assignments

• EEPAC Analysis

• NMSC Responses AFSMO Subcases

• AFSMO Affected Assignments

• EEPAC Analysis

• AFSMO Responses Agency Subcases

• Affected Assignments

• Agency Responses

AWS-3

Licensees

AWS-3 DEPS

SharePoint

Files

(FOUO)AWS-3

1755-1780 MHz

EEP

SMOs Agencies

DSRMT

Harris LAN

CRs

• Laydowns

• Cover Letters Complete/Incomplete Result Affected Assignments

• ASMO Assignments

• NMSC Assignments

• AFSMO Assignments

• Other Agency Assignments Svc /Agency Subcases

• EEPAC Analysis Files

• Svc/Agency Responses Consolidated DoD Responses Other Federal Agency Responses

EEPAC

Analysis Background Files

• Approved Laydowns

• DoD Systems Data

• “Perfect” Supplemental Data

- ASMO Records

- NMSC Records

- AFSMO Records

- Other Agency Records

• Background Wireless EME

- Block G

- Block H

- Block I

- Block J

DoD Consolidated CR Responses

• Concur

• Partial Concur

• Denials

Portal Access Controlled by

User Name / Password

DEPS Access Controlled by CAC Card and Permissions

Other EEPAC Files

EEP-07198

Receipt Acknowledgements Complete/Incomplete Responses

Portal Access Controlled by

User Name / Password

EEPAC CO

N

TRACTO

R

Defense Spectrum Organization 2-3

2.3 EEPAC

The EEPAC is a standalone software tool developed to perform aggregate interference analyses between licensee UEs and DoD systems in order to determine the potential for Electromagnetic Interference (EMI) from AWS-3 mobile transmitters into incumbent DoD systems. EEPAC leverages existing DSO capabilities including algorithms for Frequency Resource Record System record construction, receiving system noise power calculations, Terrain-Integrated Rough-Earth Model propagation modeling, ITU-R P.528 propagation modeling, directional antenna pattern modeling, Frequency-Dependent Rejection (FDR) calculations, and general mobile system modeling. The AWS-3 Early Entry Portal Analysis Capability Algorithm Definition Document [9] describes the algorithms in detail. The User Manual and Help Files [5] describes in detail the EEPAC application and provides operating instructions.

2.4 AWS-3 LICENSEES

The licensees are commercial wireless companies that won licenses in the AWS-3 auction.

These companies are seeking early access to operate in the auctioned spectrum and are responsible for submitting and withdrawing properly formatted CRs, CAs, and DPs to the

EEP.

2.5 DACAMP

The DACAMP supports the exchange of files related to the AWS-3 1755 – 1780 MHz band early entry CRs between the Engineering Cell, the DSO, and the SMOs. DACAMP uses DEPS, which provides information sharing and collaboration capabilities based on Microsoft SharePoint. Refer to the DACAMP User’s Guide Training Brief [10] for an overview of the DACAMP usage and file structure.

2.6 DSRMT

The DSRMT holds the overall responsibility for the AWS-3 coordination process.

DSRMT is responsible for many CR/DP workflow processes on the EEP, determining the final decision on a CR, and providing a DoD response to the licensee. The DSRMT is comprised of Government staff providing oversight of products and processes from the Engineering Cell.

2.7 SERVICE SMOS

Service SMO representatives (including contractor support) are responsible for reviewing subcase analysis results, and coordinating with their military field units. The SMOs are responsible for the prompt review, coordination of, and return of analysis results received from the Engineering Cell and will have final decision on subcases.

2.8 EEP ENGINEERING ANALYSIS CELL

The EEP Engineering Analysis Cell, commonly referred to as the Engineering Cell, is comprised of contracted technical staff who will utilize the EEP and the EEPAC to support AWS-3 licensee and SATOPS coordination business processes. The responsibility for smooth and successful EEPAC operations lies primarily with the Engineering Cell. The

Defense Spectrum Organization 2-4

Engineering Cell is responsible for CR and CA retrieval from the EEP, data validation, and analysis, tracking, and status changes on the EEP. Within the Engineering Cell are the following individuals and/or groups:

• Engineering Cell manager: responsible for smooth and successful operation of the Engineering Cell. The Engineering Cell manager also assigns analysis responsibilities and is the first to receive notification of issues requiring resolution or escalation.

• Engineering Cell operations staff: responsible for retrieving CRs and CAs from the EEP every business day and moving data to EEPAC for validation activities.

• Engineering Cell engineers: responsible for performing analysis on CRs using the EEPAC tool.

• EEP administration staff: responsible for establishing and maintaining user accounts and resolving any issues, maintenance, and updates to the EEPAC software.

Defense Spectrum Organization 3-1

3. SCHEDULED PROCESSES

Scheduled processes are those that occur when defined entry criteria are met and that are required to be completed within a specified time period.

Scheduled processes for the EEPAC and Engineering Cell begin at the 10-day process;

previous processes are included for completeness.

All days are measured in calendar days.

3.1 THE 5-DAY PROCESS

3.1.1 Key Elements

• Licensees

• The EEP

3.1.2 Business Process

Licensees will log onto the EEP and submit their CRs accompanied by a cover letter, which will begin the workflow. The EEP receives the CR and cover letter and changes the EEP status to “Submitted”. Licensees may choose from one of three federal agencies to submit to when uploading a CR to EEP: DoD, Department of Interior (DOI), or Department of Justice (DOJ).

The EEP will assign a unique case number and time stamp. The EEP will then change the status of each CR to “Acknowledged”.

Licensees also have the ability to withdraw CRs by using the EEP to change the status of the CR to “Withdrawn”.

It is important to note that the status changes are automatic and immediate on the EEP; the 5-day window is in place in the event that the EEP is down for maintenance.

3.1.3 Business Output

• CR Acknowledgement

3.2 THE 10-DAY PROCESS

3.2.1 Key Elements

• The EEP

• Engineering Cell

• The EEPAC

• Federal Agency Representatives

Defense Spectrum Organization 3-2

3.2.2 Business Process

The Engineering Cell operations staff will download any new CRs in the Acknowledged state from the EEP every business day. The CRs are archived on a solid-state drive and then loaded into EEPAC. Engineering Cell operations staff will press the button labeled “Perform Validate and Load”, on the “Validate and Load” tab in EEPAC, to begin the 10-day process. There is a separate EEPAC database for each of the 3 federal agencies that use EEPAC for Validate and Load: DoD, DOI, and DOJ.

EEPAC will systematically review the data contained in the CRs for any data errors that may be present. If there are errors in the data, EEPAC will generate an error report. Please refer to the Supplemental CR Spreadsheet [11] for detailed information on the data format that is required when submitting a CR.

Engineering Cell operations staff will log onto the EEP and change the status of the CR to either “Complete – Accepted” if there are no errors or “Incomplete – Resubmit” if errors occurred. If errors occurred, the error report generated by EEPAC will also be posted to

EEP.

The 10-day process is initiated when a licensee submits a CR on the Portal. Each step in the 10-day process is depicted in Figure 3-1 and described in detail below.

Defense Spectrum Organization 3-3

Figure 3-1. 10-Day Notification of Complete/Incomplete CR Procedure

1. The EEP automatically acknowledges the CR. This is included in the 5-day process which is a subset of the 10-day process.

2. The Engineering Cell Manager assigns the CR to an Engineering Cell team member.

Defense Spectrum Organization 3-4

a. The Engineering Cell Manager, or alternate, checks the EEP each morning to see if new CRs have been submitted to the portal.

b. The Engineering Cell Manager assigns the new CRs to an Engineering Cell team member based on current workload.

3. The Engineering Cell team member performs validate and load in EEPAC.

a. The Engineering Cell team member downloads the Laydown (.csv) file for the assigned CRs from EEP to the portable drive designated for EEP and places them in the appropriate folder for DoD, DOI, or DOJ. Please reference the User Guide and On-line Help [4] for detailed information on how to download files from

EEP.

b. The Engineering Cell team member uploads the assigned CRs to the EEPAC workstation designated for Validate and Load and places them in the appropriate folder for that federal agency. DoD CRs are placed in the EEP-IN folder; DOI CRs are placed in the DOI-IN folder; and DOJ CRs are placed in the DOJ-IN folder. Validate and Load was designed to be completed quickly and therefore only needs to be run on a single workstation.

c. The Engineering Cell team member runs Validate and Load on the assigned CRs in the EEPAC instance designated for DoD, DOI, or DOJ, as appropriate. For a detailed description of how to run Validate and Load in EEPAC, please reference the User Manual and Help Files [5].

4. The Engineering Cell team member checks whether the CRs are complete and valid.

a. The Engineering Cell team member records the CRs that successfully completed

Validate and Load and the CRs that failed to complete validate and load. The recording can be done on a spreadsheet or on paper so that it can be referred back to when doing QA checks and updating DACAMP.

b. For DoD CRs that successfully completed Validate and Load, the Engineering Cell team member downloads the Complete CR Report (.csv) and Carrier CR Report (.csv) from the DSO-OUT folder to the portable drive designated for

DACAMP.

c. For CRs that failed to complete Validate and Load, the Engineering Cell team member downloads the Error Report (.csv) from the EEP-OUT, DOI-OUT, or DOJ-OUT folder to the portable drive designated for EEP.

d. The Engineering Cell team member does a QA check to ensure that all assigned CRs generated either a Complete CR Report or an Error Report.

5. The Engineering Cell team member changes status in EEP.

a. For CRs that successfully completed Validate and Load, the Engineering Cell team member changes the status in EEP to Complete-Accepted. Please reference the User Guide and On-line Help [4] for detailed information on how to change the status of a CR in EEP.

b. For CRs that failed to complete Validate and Load, the Engineering Cell team member changes the status in EEP to Incomplete-Resubmit, and uploads the Error Report to EEP.

c. The Engineering Cell team member does a QA check to ensure that all statuses are correct within EEP. A rollback can be performed if an incorrect status is identified.

Defense Spectrum Organization 3-5

d. The Engineering Cell team member sends a summary email to the Engineering Cell to indicate that the 10-day process is complete for the assigned CRs. The summary email should include the list of CRs that successfully completed validation and are now in the Complete-Accepted status in EEP and the list of CRs that failed to complete validation and are now in the Incomplete-Resubmit status in EEP.

e. The Engineering Cell team member updates the Executive Summary and Master CR Status Log posted to DACAMP. Detailed information on posting files to DACAMP can be found in the User’s Guide Training Brief [10].

3.2.3 Business Outputs

The business outputs for the 10-day process are:

• Change in EEP status to Complete-Accepted or Incomplete-Resubmit

• Complete CR Report and Carrier CR Report for CRs that successfully complete validation

• Error Report for CRs that fail to complete validation

3.3 THE 60-DAY PROCESS (DAYS 1 TO 2)

3.3.1 Key Elements

• The EEPAC

• Engineering Cell

• DACAMP

• The EEP

3.3.2 Business Process: Identify Affected Records

The Engineering Cell operations staff will open EEPAC and run the Validated CRs that reside in the “Affected Records” tab and press the “Identify Affected Records” button to begin the analysis to determine which Spectrum Analysis Records (SARs) are affected by each CR. EEPAC will generate affected records reports and maps of the affected SARs for each CR. Engineering Cell staff will upload the affected records reports and maps to DACAMP. The affected records report identifies each transition plan record, which may be affected by tower sites/antenna sectors contained in the CR, with a check mark. The report is used to notify each Service SMO of the specific tower sites/sectors that may need to be reviewed. The User Manual and Help Files [5] contains descriptions and examples of the EEPAC reports.

The Identify Affected Records stage is initiated when the CR status is Complete-Accepted on EEP. Each step in the Identify Affected Records stage is depicted in Figure 3-2 (Technical Reports (TRs), Air Force (AF), Army (AR), Navy (N)) and described in detail below.

Defense Spectrum Organization 3-6

Figure 3-2. Identify Affected Records (2 Days)

1. The Engineering Cell team member performs Identify Affected Records in EEPAC.

a. The Engineering Cell team member initiates Identify Affected Records for CRs within the EEPAC instance that has been designated for Identify Affected Records. The User Manual and Help Files [5] contains additional information on the EEPAC User Interface (UI) and user controls within the Identify Affected

Defense Spectrum Organization 3-7

Records tab. Identify Affected Records was designed to be completed quickly and therefore only needs to be run on a single workstation.

b. The Engineering Cell team member checks that all CRs have completed Identify Affected Records.

2. The Engineering Cell team member checks which services have records affected by the

CR.

a. The Engineering Cell team member records which services have records affected by the CR. The recording can be done on a spreadsheet or on paper so that it can be referred back to when doing QA checks and updating DACAMP.

b. The Engineering Cell team member downloads the Affects TRs Reports (.csv) and the Affects TRs Maps (.pdf and .kmz) from the DSO-OUT folder to the portable drive designated for DACAMP.

c. The Engineering Cell team member does a QA check to ensure that all assigned CRs generated Affects TRs Reports and Affects TRs Maps. This is done by checking the list of reports that was transferred from the DSO-OUT folder to the portable drive designated for DACAMP to ensure that none of the reports are missing.

3. The Engineering Cell team member posts the reports to the appropriate DACAMP site.

a. The Engineering Cell team member posts the Complete CR Report (.csv) and the

Affects TRs DSO Report (.xlsx) to the DSO DACAMP site.

b. If Air Force records are affected, the Engineering Cell team member posts the

Complete CR Report (.csv), the Affects TRs AF Report (.xlsx), and the Affects TRs AF Maps (.pdf and .kmz) to the AFSMO DACAMP site.

c. If Army records are affected, the Engineering Cell team member posts the Complete CR Report (.csv), the Affects TRs AR Report (.xlsx), and the Affects TRs AR Maps (.pdf and .kmz) to the ASMO DACAMP site.

d. If Navy or Marine Corps records are affected, the Engineering Cell team member posts the Complete CR Report (.csv), the Affects TRs N Report (.xlsx), and the Affects TRs N Maps (.pdf and .kmz) to the NMSC DACAMP site.

f. The Engineering Cell team member does a QA check to ensure that all reports have been posted to the appropriate DACAMP site. This is done by checking the list of reports posted to each DACAMP site to ensure that none of the reports are missing or in the wrong folder. Detailed information on posting files to DACAMP can be found in the User’s Guide Training Brief [10].

4. The Engineering Cell team member updates the status on EEP to Pending Analysis with Subcases.

a. The Engineering Cell team member changes the status in EEP to Pending Analysis with Subcases for all CRs that have completed Identify Affected Records. Please reference the User Guide and On-line Help [4] for detailed information on how to change the status of a CR in EEP.

b. The Engineering Cell team member uses the drop down menu in EEP to indicate which services have affected records for each CR.

c. The Engineering Cell team member sends a summary email to the Engineering Cell to indicate that the Identify Affected Records process is complete for the assigned CRs. The summary email should include the list of CRs that

Defense Spectrum Organization 3-8 successfully completed Identify Affected Records and are now in the Pending Analysis with Subcases status in EEP.

d. The Engineering Cell team member updates the Executive Summary and Master CR Status Log posted to DACAMP.

3.3.3 Business Deliverables

The following are the business outputs for the Identify Affected Records stage:

• Affects TRs Reports for DSO and the affected services

• Affects TRs Maps for the affected services

• Change in EEP status to Pending Analysis with Subcases

3.4 THE 60-DAY PROCESS (DAYS 3 TO 22)

3.4.1 Key Elements

• The EEPAC

• Engineering Cell

• DACAMP

• The EEP

3.4.2 Business Process: Analysis

The Engineering Cell operations staff will open EEPAC and initiate Analysis for CRs that reside in the “Analysis” tab and press the “Perform Aggregate Interference Analysis” button to begin the analysis to determine which sectors need to be removed from the CR in order to avoid harmful interference. EEPAC will generate subcase reports and laydown maps of the approved and denied sectors for each CR. Engineering Cell staff will upload the subcase reports and maps to DACAMP.

The Analysis stage of the 60-day process is initiated when the CR status is Pending Analysis with Subcases on the EEP. Each step in the Analysis stage of the 60-day process is depicted in Figure 3-3 and described in detail below.

Defense Spectrum Organization 3-9

Figure 3-3. Analysis (18 Days)

Defense Spectrum Organization 3-10

1. The Engineering Cell team member requests authorization from the Engineering Cell manager to begin Analysis of CRs in EEPAC.

a. The Engineering Cell team member postpones Analysis of CRs until written or verbal authorization is received. Some examples of reasons to postpone Analysis might be: waiting for a new version of supplemental data to be released; waiting for a new version of relative margins to be released; or waiting for a new version of EEPAC software to be released. The Analysis phase of the 60-day process can take several days, therefore software and database releases need to be timed around EEPAC Analyses.

2. The Engineering Cell team member initiates Analysis in EEPAC.

a. Once authorization is given, the Engineering Cell team member initiates Analysis in EEPAC. The Algorithm Definition Document [9] provides a detailed description of the algorithms that are used to analyze a CR in EEPAC.

b. Cumulative analysis is performed on production EEPAC machines for routine CRs. Non-cumulative analysis can be performed on Studies EEPAC machines if needed. The User Manual and Help Files [5] contains additional information on the EEPAC UI and user controls within the Analysis tab.

c. Separate instances of EEPAC are used for each analysis in order to reduce processing time. This allows the analyses to be performed in parallel rather than in series. Separate machines are designated for analysis, as it is computationally intensive and can take several days to complete an analysis. Using separate machines allows quicker running processes, like Validate and Load, to be completed while an analysis is running.

d. The Engineering Cell team member changes the status of the CRs to Analysis in Progress in the EEP.

e. The Engineering Cell team member monitors the progress of the Analysis and records which CRs have completed Analysis, which CRs are in progress, and which CRs are queued.

3. The Engineering Cell team member posts Analysis reports to DACAMP.

a. Once a CR has completed Analysis, the Engineering Cell team member downloads the Subcase Report DSO (.xlsx), Subcase Report {AF, AR, N} (.xlsx), and Laydown Map {AF, AR, N} (.pdf and .kmz) from the DSO-OUT folder to the portable drive designated for DACAMP.

b. The Engineering Cell team member posts the Subcase Report DSO (.xlsx) to the DSO DACAMP site.

c. If Air Force records are affected, the Engineering Cell team member posts the Subcase Report AF (.xlsx) and the Laydown Map AF (.pdf and .kmz) to the AFSMO DACAMP site.

d. If Army records are affected, the Engineering Cell team member posts the Subcase Report AR (.xlsx) and the Laydown Map AR (.pdf and .kmz) to the ASMO DACAMP site.

e. If Navy or Marine Corps records are affected, the Engineering Cell team member posts the Subcase Report N (.xlsx) and the Laydown Map N (.pdf and .kmz) to the NMSC DACAMP site.

Defense Spectrum Organization 3-11

g…