15_Coordination_Business_Process_V1_1.pdf

PDF 277 KB Posted

Attached to
Advanced Wireless Services-3 (AWS-3) Early Entry Portal (EEP) Development, Operations and Maintenance Support Federal contract opportunity
Solicitation number
HC104718R4004
Issued by
Defense Information Systems Agency

About this file

Reference Materials

View the file

Other files for this federal contract opportunity

Other files attached to Advanced Wireless Services-3 (AWS-3) Early Entry Portal (EEP) Development, Operations and Maintenance Support, newest first.
File Type Posted
non_disclosure_agreement.docx DOCX document
additional_questions.docx DOCX document
9_Federal_EEP Training_Slides 29 June 2017.pdf PDF
Attachment_7_-_Provisions_and_Clauses.docx DOCX document
Attachment_5_-_Evaluation_Tables.docx DOCX document
AWS-3 EEP User's Guide 29 June 2017.pdf PDF
9_AWS-3 EEP Federal_EEP Training_Slides 10 NOV 2016.pdf PDF
10_T3747-1-OTH-17-479 T3747-1 AWS-3 EEP v2.3 Installation Guide.pdf PDF
AWS-3 EEP v2.3 DSO Form 19 - Software System Certification.pdf PDF
Attachment_6_-_Questions_and_Answers.docx DOCX document
15_Coordination Business Process V1_1.pdf PDF
Attachment_1_-_PWS.docx DOCX document
Attachment_3_-_Cost_Template.xlsx XLSX spreadsheet
1_DSO-SD-16-051 T3747-1 AWS-3 EEP v2.3 System Requirements Specification Rev2 29 June 2017.pdf PDF
Attachment_4_-_SCRM_Plan.docx DOCX document
Attachment_2_-_QASP.docx DOCX document
9_AWS-3 EEP User's Guide 29 June 2017.pdf PDF
(N4110) EEP VDD Summaries.pdf PDF
12_AWS-3 EEP Regression Tests.zip ZIP file
9_AWS-3 EEP Engineering_SMO_DSRMT_EEP Training_Slides 10 NOV 2016.pdf PDF
9_Engineering_SMO_DSRMT_EEP Training_Slides 29 June 2017.pdf PDF
6_T3747-1 AWS-3 EEP RTM - T3747-1-PD-17-478.pdf PDF
3_T3747-1-PD-17-467 T3747-1 AWS-3 EEP Software Design Document - v2.3 29 June 2017.pdf PDF
Attachment_6_-_Questions_Template.docx DOCX document
3_T3747-1-PD-17-467_T3747-1_AWS-3_EEP_Software_Design_Document_-_v2.3_29_June_2017.pdf PDF
Attachment_1_-_PWS.docx DOCX document
Attachment_3_-_CLIN_Pricing_Worksheet.xlsx XLSX spreadsheet
AWS-3_EEP_v2.3_DSO_Form_19_-_Software_System_Certification.pdf PDF
9_Licensee_EEP_Training_Slides_29_June_2017.pdf PDF
(N4110)_EEP_VDD_Summaries.pdf PDF
1_DSO-SD-16-051_T3747-1_AWS-3_EEP_v2.3_System_Requirements_Specification_Rev2_29_June_2017.pdf PDF
AWS-3_EEP_User's_Guide_29_June_2017.pdf PDF
9_Engineering_SMO_DSRMT_EEP_Training_Slides_29_June_2017.pdf PDF
7__T3747-1_AWS-3_EEP_v2.3_Architecture_29_June_2017.pdf PDF
9_Federal_EEP_Training_Slides_29_June_2017.pdf PDF
Attachment_4_-SCRM_Plan.docx DOCX document
Attachment_7_-_Provisions_and_Clauses.docx DOCX document
9_AWS-3_EEP_User's_Guide_29_June_2017.pdf PDF
9_Army_Tactical_Radio_Relay_(TRR)_Coordination_Training_Slides_29_June_2017.pdf PDF
HC104718R4004_Request_for_Proposal.DOCX DOCX document
10_T3747-1-OTH-17-479_T3747-1_AWS-3_EEP_v2.3_Installation_Guide.pdf PDF
12_AWS-3_EEP_Regression_Tests.zip ZIP file
8_EEP_Source_Code.zip ZIP file
Attachment_2_-_QASP.docx DOCX document
Attachment_7_-_Provisions_and_Clauses.docx DOCX document
HC104718R4004_Request_for_Proposal.DOCX DOCX document
Attachment_2_-_QASP.docx DOCX document
Attachment_1_-_PWS.docx DOCX document
Attachment_6_-_Questions_Template.docx DOCX document
Attachment_4_-SCRM_Plan.docx DOCX document
Show all 50

Advanced Wireless Services-3 (AWS-3) Early Entry Portal (EEP) Development, Operations and Maintenance Support has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DoD Advanced Wireless Services-3 (AWS-3) Coordination

As of 3 November 2015

Coordination Business Process V1.1

The information provided in this briefing is for general information purposes only. It does not constitute a commitment on behalf of the United States Government to provide any of the capabilities, systems or equipment presented and in no way obligates the United States Government to enter into any future agreements with regard to the same. The information may not be posted on a web site or disseminated without the express consent of the United States Government.

DISCLAIMER

• FCC/NTIA Joint Public Notice (DA 14-1023, July 18, 2014) provided guidance regarding coordination between Federal and non-Federal shared use for

AWS-3

• Portal will be operational on 2 November 2015

Basic Coordination Process

DoD 1755 MHz Portal

Complete Coordination

Request?

YES

NO

Deficiencies

CR Enters

DSRMT

Analysis Queue

DSRMT

Performs Analysis

Service Acceptance of

Results?

YES NO Final Report Prepared for

Carrier

5 calendar days after submittal - Acknowledge receipt of CR

10 calendar days after submittal - Notice of Complete/Incomplete

70 calendar days maximum length for end-to-end process

• 70 calendar days to coordinate with internal entities, complete EMC analysis, and post the AWS-3 concurrence, partial concurrence with operating conditions, or denial

– 10 days to acknowledge and determine if submission is complete

– 60 days to conduct analysis of request

CR – Coordination Request DSRMT – DoD Spectrum Relocation Management Team

DoD Infrastructure Supporting Coordination

Open Internet Closed Environment

EEP

DACAMP

(FOUO)

AWS-3

Licensees

Landing Page

Landing Page

Landing Page Service SMO

DOJ/DOI

DSRMT

Engineering Cell Landing

Page

Landing Page

EEP Analysis Capability

(EEPAC)

Access Controlled by

User Name / Password

Access Controlled by CAC Card and Permissions

Access Controlled by Permissions

CAC – Common Access Card DOI – Department of Interior DOJ – Department of Justice EEP – Early Entry Portal

FOUO –For Official Use Only SMO – Spectrum Management Office DACAMP – DoD AWS-3 Coordination and Management Portal

DoD Portal Case Workload Queuing n n n

Carrier “A” CR

Carrier “B” CR

Carrier “C” CR

Carrier A Q ueue

Carrier B Q ueue

Carrier C Q ueue

Legend

A B

C

Order

• Carrier Requests (CRs) are numbered in the order received at the portal

• Based on the scenario of Figure 1, the analysis order would be “1, 4, and 5” as shown

• If no other requests were received before the queue was cleared, the order would be 1,4,5,2,6,3. Figure 1

A B

C

Order 8

Figure 2

• Figure 2 shows that CRs 1,4, and 5 have ben processed, and some new requests were received (7, 8, 9 and 10)

• The round robin order has been established (A, B, then C)

• That order is used to process requests unless all Queues were cleared, and then it’s possible a new round robin order would be established

1 4 5

2 6 7 http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRw&url=http://imgbuddy.com/conveyor-belt-clipart.asp&ei=KqgRVZviIJL-gwTD8oHQCQ&bvm=bv.89184060,d.eXY&psig=AFQjCNENcImz6iRsOH7gwzfVVNs0_miqzw&ust=1427306699595767 http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRw&url=http://imgbuddy.com/conveyor-belt-clipart.asp&ei=KqgRVZviIJL-gwTD8oHQCQ&bvm=bv.89184060,d.eXY&psig=AFQjCNENcImz6iRsOH7gwzfVVNs0_miqzw&ust=1427306699595767

• 5-day “Acknowledge” Process

• 10-day “Complete/Incomplete” Process

• 60-day “Concur, Partial Concur, Denial” Process

• Post 60-day “Accept, Conditionally Accept, or Object” Process *

* Automation to support Post 60-day Process, if required, will be after 2 November 2015

CR Business Process for DoD

5-Day “Acknowledge” Process

• Licensee logs into the

EEP

• Licensee uploads CR*

• CR includes a Cover

Letter (.pdf) and a CR Laydown (.csv) - technical characteristics of the base stations and associated mobile units relevant to operation within the coordination zone

• EEP sets the workflow status of each CR to ‘Submitted’

• The CR is received via the

EEP

• EEP assigns the CR a unique Case Number and time stamp

• EEP automatically notifies DSRMT and the Service SMO Representatives of the submission of a request

• EEP sets the workflow status of each CR to ‘Acknowledged’

• Within five days of submittal to the EEP, a notice is sent to the Licensee acknowledging receipt of the CR

EEP Receives

CR

EEP Acknowledges Receipt of CR

Licensee Submits

CR

* See slide deck titled “Coordination Request Data Elements” for more detail

10-Day “Complete/Incomplete” Process

• DSRMT uses EEPAC to perform validation on the CR laydown to assess format, content, and correctness of the data

• If the CR laydown fails validation, EEPAC generates an error report identifying areas where the CR failed

• If the CR data fails validation, the DSRMT sets the status to ‘Incomplete – Resubmit’ and the Licensee is notified that the CR must be resubmitted and is provided an error report via the

EEP

• If the CR data passes validation, the DSRMT sets the status to ‘Complete - Accepted’ and the AWS-3 Licensee is notified that the CR is complete and has been accepted for analysis via the EEP

DSRMT Performs Validation of the CR data

DSRMT Sends Notification to the AWS-3 Licensee

60-Day “Concur, Partial Concur, Denial” Process

• DSRMT identifies frequency assignments that may be affected by the carrier laydown

• The affected frequency assignment report is posted to DACAMP for review by each Service SMO

• DSRMT performs Aggregate Interference analysis on the carrier laydown using the EEPAC to determine aggregate interference from UEs into each affected DoD system

• DSRMT prepares subcase analyses results for each Service SMO and posts the subcases analyses results on

DACAMP

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

• Any concerns are conveyed to DSRMT

• Upon completion of review the SMO Conveys Decision on each Subcase to DSRMT via DACAMP

• DSRMT compiles results of all subcase analyses into a composite output

• DSRMT prepares a cover letter

• DSRMT posts the cover letter and composite results to the EEP

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

DSRMT

Conducts Initial

Analysis

Services Conduct Review and

Conveys Decision to DSRMT

DSRMT Prepares Consolidated DoD

Decision

Identify Affected Frequency

Assignments

• Since DoD is unable to provide analysis results via the EEP due to security concerns, we are establishing a post 60-day process to facilitate discussions with the carriers on the results and the impacts of potential modifications

• NDAs will need to be in place before we begin discussions

• Carriers asked to contact DoD at our AWS-3 e-mail address:

disa.usna.os.mbx.spo-aws-3-dsrmt@mail.mil

• Account is monitored within DSO and DoD CIO

• Once contact is made, DSO will assign the request to a member of the

DSRMT to coordinate discussions

Post 60-day “Accept, Conditionally Accept, or Object”

Process mailto:disa.usna.os.mbx.spo-aws-3-dsrmt@mail.mil

• All 5, 10, and 60-day Process Outputs to Licensees will be through the EEP

– 5-day “Acknowledge” Process

• EEP Notification to Licensee INBOX

– 10-day “Complete/Incomplete” Process

• If CR is “Incomplete”, a report will be provided

– 60-day “Concur, Partial Concur, Denial” Process (see next slide)

• A DoD Results letter (.pdf) and a spreadsheet (.csv or .xlsx)

Expected Portal Outputs

• DoD is planning on providing the same response as during AWS-1

• A DoD Results letter (.pdf) and a spreadsheet (.csv or .xlsx) will contain the deployment activation requirements at the sector level with each sector being identified as an approval (green) or denial (red)

• Due to the sensitive nature of DoD’s operations, analysis results will not be provided via EEP

– Carriers asked to contact DoD at our AWS-3 e-mail address: disa.usna.os.mbx.spo-aws-3-dsrmt@mail.mil

Response to Carriers

12 12

UNCLASSIFIED

DoD Advanced Wireless Services-3 (AWS-3) Coordination
DISCLAIMER
Basic Coordination Process
DoD Infrastructure �Supporting Coordination
DoD Portal Case Workload Queuing
CR Business Process for DoD
5-Day “Acknowledge” Process
10-Day “Complete/Incomplete”�Process
60-Day “Concur, Partial Concur, Denial” Process
Post 60-day “Accept, Conditionally Accept, or Object” Process
Expected Portal Outputs
Response to Carriers
Slide Number 13

File details come from the government source that posted it.