UNITED STATES MARINE CORPSI MARINE EXPEDITIONARY FORCE

U. S. MARINE CORPS FORCES, PACIFICBOX 5S5300

CAMP PENDLETON, CA 92058-5300

2400G-6

POLICY LETTER 4-18rAnG 1 3 2016

From: Commanding General, I Marine Expeditionary ForceTo: Distribution List

Subj: I MARINE EXPEDITIONARY FORCE SUPPLEMENT TO THE MARINE FORCES PACIFICSATELLITE ACCESS REQUEST AND GATEWAY ACCESS REQUEST POLICY

Ref: (a) USPACOM Satellite Access Request and Gateway Access Request Policy(b) CJCSI 6250.D1E/l4 Mar 2013Cc) CTO 09-016/release of Classified WSOM Information to AUS(d) The UHF Satellite Communications Security Classification Guide,

ID 06-021.1 (November 2007)Ce) CJCSI 6261.0W/3D Nov 2012(f) CM-Dl82-17/CJcS Memorandum for 1W Mandate(g) Wideband Standards and Operations Procedures/22 Jun 2015(h) MARFORPAC Satellite Access Request and Gateway Access Request

PolicyCi) I MEFBUL 1050

End: (1) I Marine Expeditionary Force Supplement to the MARFORPAC SatelliteAccess Request (SAR) and Gateway Access Request (GAR) Policy

(2) MARFORPAC SATCOM Priority Quick Reference(3) I MEF/MARFORPAC SAR/c-AR Submission Timeline Calendar(4) MARFORPAC Exception to Policy (ETP) Request Format(5) Ku Bandwidth Request Form(6) World Wide Reach Back (WWRB) Request Form(7) Exercise Support Request (ESR)

1. Purpose. In accordance with (lAW) reference (a) through (i) , this letterestablishes I Marine Expeditionary Force’s policy for Satellite AccessRequest (SAR) and Department of Defense Gateway Access Requests (c-AR) in theUnited States Pacific Command Area of Operations. It articulates thecategories and priorities of Satellite Communications (SATCOM) services andidentifies operational processes and management responsibilities.

2. Information

a. The Assistant Chief of Staff G-6, I Marine Expeditionary Force (I MEF)is responsible for the I MEF SAR/GAR process, and will update this policy asnecessary to provide current and relevant standards. All questionspertaining to the I MEF policy for SAR and GAR should be directed to: the IMEF G-6 Space and Waveform Integration Officer, Chief Warrant Officer 4 GeoffBeatty at geoff.beatty@usmc.mil, or DSN 312-361-2639 or Commercial 760-763-2639 and the I MEF G-6 Technical Control Engineer Master Gunnery SergeantRodney Gentry at rodney.gentry@usmc.mil, or DSN 312-361-2634 or Commercial760-763—2634.

Distribution Statement A: Approved for public release, distribution isunlimited.

24000-6

b. All personnel responsible for submitting, reviewing, and validatingSAR/GAR will familiarize themselves with references (a) , (h) and thissupplement.

3. Scope

a. Enclosure Cl) captures the timelines and submission requirements forMarine Forces Pacific, Pacific Cotrsnand, Strategic Command and Regional SATCOMSupport Center-Pacific in order to request satellite and Gateway services forI MEF units conduction training, exercises and real world contingencies.This documentation also enables all I MEF/Major Subordinate Command(MSC)/Marine Expeditionary Unit (MEU) level frequency managers the ability tounderstand the processes of spectrum-dependent; intelligence, surveillanceand reconnaissance functions; and electronic warfare capabilities.

b. lAW Enclosure (1) subordinate units will submit SARs and/or GARs viathe Major Subordinate Element 5-6 / MSC 0-6 chain.

c. Enclosures (5) through (8) are provided as formats for submission asapplicable lAW Enclosure Cl)

4. Command. This policy letter is applicable to all Marine Corps unitswithin the I MEF sphere of influence for satellite communications resources.

5. Certification. This policy letter is effective from the date signed.

Distribution List: I, II

2

2400G-6

I Marine Expeditionary Force Supplement to the MARFORPAC Satellite AccessRequest and Gateway Access Request Policy

1. Joint Integrated Satellite Communications (SATCOM) Tool (JIST) InAccordance With (lAW) reference (a) all Satellite Access Requests (SARs) mustbe submitted via the JIST. It is a web-based database for entering, tracking,and validating SARs that resides on the Secure Internet Protocol RoutingNetwork (SIPRflet) For a JIST account, contact your respective G-6. TheJIST website is located at the following URL: https://JISTjsme . disa. smil .mil/JIST/pages.

2. Joint Staff (JS) SATCOM Database (SDB) . The JS SOB is defined as adatabase that contains predetermined Department of Defense SATCOMrequirements. All personnel responsible for submitting and validatingSatellite Access Requests (SAR5) should be familiar with SDB requirements andthe technical assessment process. Information training modules areavailable. Contact Marine Forces Pacific (MARFORPAC) Information EnvironmentDirectorate Integrations for more information.

a. All SARs must have a valid SDB entry.

b. Once a new requirement is submitted and validated in SOB ManagementTool by the JS, the user can begin using the SDB entry on requests forSATCOM.

c. If individual SOB entry details have changed, the SOB entry must beupdated, along with the new changes used with the SDB waiver submission.

d. Until approved, an SOB waiver is required. For more informationregarding SOB waivers, see paragraph 7. Reasons for SOB waivers include:

(1) SATCOM mission does not have a current approved United StatesPacific Command (USPACOM) SOB entry.

(2) SATCOM access exceeds approved bandwidth thresholds identifiedwithin the SDB entry.

(3) Mission parameters (terminal type, antenna size, number of users,etc.) for SATCOM access are outside the parameters of the SOB entry.

(4) Overall multiplier exceeds the number of simultaneous networksestablished by the requirement.

3. Chairman of the Joint Chiefs of Staff (CJCS) SATC0M Priorities. Allpersonnel involved with drafting, submitting, or validating SAR5 should befamiliar with the CJCS SATC0M Priority table. The SATCOM priorities areestablished by the JS and are used to determine access to orbit satellitesystems and rescoral priority from anomalies. Additional informationregarding the SATCOM priorities can be found in reference (b) . A MARFORPACSATCOM priority quick reference is provided in Enclosure (2)

4. çirements. SAR/GAR5 sent to I MEF G-E for review and validation mustsupport a legitimate PACOM and MARFORPAC requirement or that of a MARFORPAC

Enclosure (1)

2400G-6

subordinate command, otherwise MARFORPAC Information Environment Divisioncannot:

a. Approve the use of a MARFORPAC 8DB designed to support MARFORPACoperational and training requirements in support of operation plans andcontingency plan.

b. Adeauately determine or validate the mission priority.

S. SAR/GAR Submission, Review, and Validation

a. Submitting units are responsible for the accuracy of documentssubmitted to include, but not limited to, all information provided throughJIST and appropriate communication diagrams.

(1) Submissions that reach I MEF G-G and require correction willdelay the review and validation process.

(2) Incorrect or incomplete documents will be returned for correctionand may restart the submission lead time requirement.

b. Submitting units are responsible for tracking of SAR/GAR status toinclude separate correspondence related to processing and Satellite AccessAuthorization (SAM/Gateway Access Authorization release.

c. SARs must contain two points of contact (POC5) who are reachable 24hours a day. One should be familiar with the mission and SAR process and theother should be capable of reaching the terminal POC (example: a NetworkOperations Center)

d. The following information is required in the remarks section of theSAR if not specially provided for in the SAR format:

(1) Mission description: access request submissions are to be asdetailed as possible in order to readily identify actual requirements and thetrue nature of the mission.

(2) Access requests submission in support of a deployment orcontingency must reference a TASKORD/DEPORD/EXORD/OPORD in order to determineappropriate mission priority.

(3) Operational impact if not supported; users/requesters mustprovide a realistic and substantive assessment of operational impact ifrequest cannot be supported or is pre-empted by a higher priority mission.Simply stating the commander cannot exercise Command and Control is not anacceptable operational impact as units are encouraged to exercise theirPrimary Alternate Contingency and Emergency plan.

(4) Concurrence comments from SAR drafters and validators providingsupport recommendations, priority concurrence, and revalidation of therequirement when needed. When providing comments in JIST, validators mustinclude the date that comments were made with the initials of individualproviding comments.

Enclosure (1)2

2400G-6

e. Special instructions for respective SAR formats (Ultra High Frequency(UHF), Super High Frequency (SHF) (military and commercial) , and ExtremelyHigh Frequency (EHF)) and GARs are provided elsewhere in this policy.

f. Special instructions for Marine Expeditionary Units (MEU5) MEUswill submit all SAR/GAR5 via I MEF G-6 up to the time of departure fordeployment. This includes the first exercise while underway, in order tomeet the submission timelines. Once underway, all submissions will be viathe assigned Combatant Command (COCOM)

6. Routine SAR/GAR5 Submission Timeline. Routine SAR/GAR5 are defined asthose SAR/GAR5 that align with CJCS priority 3B or lower (exercises, non-crisis, and non-contingency)

a. Releasable Routine SAR5. Releasable routine SARs must be received atI MEF G-6 Not Later Than (NLT) 33 calendar days plus eight business daysprior to mission start date. This allows I MEF 0-S three full business daysin advance of the MARFORPAC policy requirement in order to review foraccuracy and prevent unnecessary returns for corrections prior to beingverified and validated to USPACOM. (For any submission received at I MEF G-6after 1200 Pacific Standard Time or Pacific Daylight Time, as applicable, thenext business day will be considered the first review day.)

Note: No routine SAR review at I MEF or MARFORPAC will be conducted onweekends or holidays in accordance with reference (i)

b. United States Forces Korea (USFK) Validation. See MARFORPAC Policyand add three full business days for submission to I MEF 0-6.

c. Non-releasable Routine SARs. See MARFORPAC policy and add three fullbusiness days for submission to I MEF G-6. For more information regardinghandling of classified SARs refer to paragraph (10)

d. Routine SARs, regardless of releasability, will not be reviewed orvalidated at I MEF G-6 or MARFORPAC during non-duty hours. The onlyexception to this is for COtS priority 33-to-31 requirements that includeoperational tasking. Subordinate commands should allow sufficient processingtime for SATCOM missions and be familiar with I MEF 0-6 and MARFORPAC normalduty hours. A pictorial aid is provided in Enclosure (3)

7. Timeline for SARs Requiring 5DB Waivers. SARs requiring SDB waiversrequire additional coordination and processing.

a. Understanding that SARs requiring 5DB waivers must be received atUSPACOM 45 calendar days prior to requested start of mission, SARs requiring5DB waivers must be received at I MEF 0-6 eight business days in advance ofUSPACOM policy lead time requirement to allow adequate time for review foraccuracy and prevent unnecessary returns for corrections.

b. If the SOB waiver timeline is not met, an Exception to Policy (ETP)request is required. This is the case even if submitted prior to thestandard lead time for the SAR.

Enclosure (1)3

2400G-6

8. Failure to Meet SAR/GAR5 Submission Timelines. Failure to submit a SARlAW this policy does not constitute emergency action by I MEF G-6 orMARFORPAC.

a. Automatic Denial

(1) Due to the volume of requests submitted on a daily basis throughUSPACOM to the respective Regional Satellite Support Center (RSSC) and thecascading effects of late submission on the RSSC’s ability to plan globalSATCOM missions, routine SARs submitted to PACOM within 14 days of missionstart date will automatically be denied regardless of the ETP. The onlyexception to this is for CJCS priority 33-to-31 requirements that includeoperational tasking.

(2) In order to allow for I MEF G-6 review and validation, routineSARs must be received at I MEF G-6 NLT eight full business days in advance ofUSPACOM policy lead time requirement.

(3) Upon identification of a catastrophic, documented SIPRNet or JISTfailure, the submitting unit must immediately coordinate with I MEF C--S if aSAR is submitted NLT 25 days of mission start. Failure to identify the issuedoes not absolve the submitting unit from providing required documents (ETP,SDB waiver1 etc.) for the late submission.

b. ETP. An ETP request is required when BAR/CARs fail to meet thesubmission timelines provided in this policy and are to be treated as the“EXCEPTION”. ETP requests will be handled on a case-by-case basis at I MEF G6 and will be reviewed by I MEF C-S Operations, who has the authority to denyETP requests for late submissions. ETPs will only be considered for TEEP’devents and priority missions. (i.e. MEUs, Special Purpose Marine Air-GroundTask Force, Task Forces, Crisis Response, etc.)

(1) Approval authority for ETPs ultimately resides with the USPACOMJ65 director.

(2) I MEF C-S will not draft or submit ETP requests unless thefailure to meet the submission timeline was due to delay at I MEF C-S. Allother ETP requests are required to be drafted by the submitting unit.

(3) when requesting ETP, I MEF units will use the provided ETP Form(see enclosure (4))

(4) Requests for ETP must be digitally signed, on SIPRNet, by an 0-6prior to being sent to I MEF G-6. Digital signature must be able to bevalidated on SIPR. If the ETP is signed “By direction”, a By Direction Letterfrom an 0-6 must accompany the ETP. (Scanning digitally signed Non-SecureInternet Protocol (NIPR) documents cannot be processed)

(5) Requests for ETP will be submitted to I MEF C--S via SIPR email.A copy of the ETP form is available via the I MEF C--S SIPR SharePoint.

Enclosure (1)4

24000-6

9. Crisis or Contingency SAR/GAR5 Submission Timeline. Crisis orContingency SAR/GAR5 are defined as those SAR/GARs that align with CJCSpriority 3 or higher. These SAR/GARs are afforded exemption from normalsubmission timeline stipulations, as they support mission requirements thatare either emergency event driven, or deemed to be critical by the COCOM orhigher.

a. Crisis or Contingency SAR/GAR5 are to be submitted as soon aspossible, once an order has been issued.

b. Crisis or Contingency SAR/GAR5 will be reviewed at I MEF as soon aspossible. I MEF G-6 personnel can be contacted via cell phone 24 hours aday. The MARFORPAC Regional Network Operational Support Center (RN0SC) canbe reached at DSN 315-477-8593/1812 or COM 808-477-8593/1812. Both the I MEFG-6 staff and the MARFORPAC RNOSC will notify appropriate personnel.

c. SAR/GAR5 with a CJCS priority of 3 or higher must be accompanied by adirective order (i.e., TASKORD/DEPORD/EXORD/OPORD)

(1) The order must be referenced in the remarks and sent via email byI MEF G-6 personnel to the MARFORPAC 06 SATCOM organizational mailbox COMB)MARFORPACG6SATCOMOPSusmc.smi1.mil and the RNOSC emailRNOSC. PAC®usmc . smil . mil.

(2) In the event of a routine mission requires an increase inpriority, the change SAR must be accompanied by a directive order.

(3) SAR/GAR5 that request a priority 3 or higher will not be sent toUSPACOM it not accompanied by initiating directive until the directive orderis provided.

d. SARs for recurring or standing priority 3 and above requirements mustbe submitted lAW the routine SAR/GAR timeline.

10. Classified SAR Handling. All classified SARs with the exception of UHFand EHF SARs should be identified with “REL TO USA, ACGU” in the caveat fieldlAW reference Cc)

a. Requests that cannot be handled ACGU (Australia, Canada, UnitedKingdom, and the United States) must provide a valid classificationreference. SAR5 that are not in compliance with reference Cc) will bereturned for action.

b. Unclassified SARs do not require release caveats.

Enclosure (1)5

2400G-6

PACOM

Complete and corraci requests must be received by:

I MEF Ge Requires (3) Business Days to processMARFORPAC Requ:res (4) Business Days to processPACOM NLI 33 Days (‘45 Days) Pñor to mission stadRSSC NLT 3D Days Prior to mission start

“Missions requiring an SDS Waiver adds (15) days to thesubmission timelino, and still must be received by theservicing RSSC NLT 30 days prior to mission stert

-AEHF Gateway missions more than 2048k-NCW-RBSI (GATR)

GM Published1-5 days prior

to mission sted

2 DISA PAC

______

GIG Services DISA PAC

I______________ (Resource Allocation) CONEX

RSSC PAC SM Published I5-lodays poorto mission start

IF at any point in the approval process, the SAR/GAR is rejected, it is muted back to theOriginating Unit, Timelines must still be met.

Figure - 1 SAR/GAR Submission Flowchart

11. Special Instructions for UHF SARs

a. Date Time Group (DTG) on UHF tactical SATCOM (TACSAT) SARs must besubmitted using the following format due to planning tool requirements:dd0000z mmm yy - dd2359z mmm yy.

b. classification and Declassification Guidance. Classification anddeclassification of UHF BARs shall be conducted lAW reference (d)

(1) All UHF SARs must be classified at a minimum of CONFIDENTIAL.UHF BARs can be classified higher, but must reference and include aTASKORD/DEPORD/EXORD/OPORD that justifies the requirement for higherclassification.

(2) All UHF BAR line items will be marked UNCLASSIFIED unless arequirement exists for higher classification. An exception to this is theterminal information.

Enclosure (1)

liku Request

MCTSSAKu sm Manage

Ku BPNAllocation

6

2400G-6

(3) EAR declassification date must be at least one year and one dayfrom the end of requested access period. The format for declassificationdate is dd mmm yyyy (ex. 17 AUG 2017)

(4) “Derived From” field must be populated with UHF SATCOM SCG ID# 06-021.1; (27 Nov 07)

c. Operational Area Location. The area in JIST titled ‘OP Area Location’must match the geographic region in which the ground terminal will beemployed.

Note: For Southern California, select ‘PAC’ unless selecting ‘CONUS’ isadvantageous for providing a more desirable antenna take-off angle. In thiscase, comments explaining the selection must be provided in the SAR remarkssection.

d. Terminal Information

(1) All terminal Information contained under line 14 of a UHF EARmust be classified at a minimum of CONFIDENTIAL.

(2) Terminal latitude and longitude information must be accurate, orthe SAR will be rejected for correction.

e. Multiple Access Channels

(1) lAW reference (e) , TACSAT terminal equipment must be DemandAssigned Multiple Access (DANA) and Integrated Waveform (1W) compliant. AllEARs for DANA/lW compliant terminals must include the statement “All radiosare 1W/DANA compliant”.

(2) Pre-assigned DAMA and 1W slots will be assigned, if available,with the understanding that higher priority mission networks will preemptlower priority networks.

(3) Technical waivers are required when the terminals are notcompatible with the DANA and 1W waveforms. Program Offices requiringtechnical waivers will submit waivers in memorandum format to theconsolidated systems SATCOM exoert (C-SEE) via I LIEF 0-6.

f. CJCS 1W Mandate. lAW reference (f), 1W has been identified as theJoint standard TACSAT waveform. SATCOM mission planners at RSSC have beendirected to exhaust 1W resources prior to assigning other TACSAT waveforms.

g. Dedicated S KHz and 25 KHz TACSAT channels. Dedicated TACSATchannels are becoming increasingly limited in number, and are thereforereserved for priority 3 missions and above, and units intending to employdata controllers, such as High Performance Waveform. Requests for dedicatedTACSAT resources must provide justification within the remarks section of theEAR that specifically describe the requirement for a dedicated channel.

Enclosure (1)7

2400G-6

12. special Instruction for SHF SARs (military bands) . The term militarySATCOM frequency bands refers to X band, Ka band, and Network CentricWaveform (NCW)

a. DTG. The DTG on SHF SARs must be submitted using the followingformat: ddl600z mmm yy — dd2300z mmm yy.

b. NCW Missions (Network on the Move (NOTM)) . Due to issues within JISTfor SHF NCW SARs, RSSC has identified SAA mission-building complications forNCW type mission, to include NOTM. This has necessitated RSSC to adapt withavailable tools to create an SAA to meet user requests.

(1) NOTM networks are often supported by an additional Frequency-Division Multiple Access (FDMA) mission for Defense Information SystemsNetwork (DISN) services. When a Tactical Entry Point is required to supporta NOTM network with Gateway resources, a SHF FDMA SAR must be submitted inconjunction with a separate 51W NCW SAR.

(2) SHF FDMA SAR would be submitted to request Gateway resourcesutilizing a SATCOM terminal such as a Very Small Aperture Terminal Large(VSAT-L) and a MD-l366 modem. In the remarks section of the SAR, the usermust reference the NCW mission JIST ID it is supporting.

(3) SHF NCW SAR will identify the same VSAT-L SATCOM terminal as wellas the requested NOTM terminals. The VSAT-L terminal in this SAR willidentify the NCW Ruggedized Modem. In the remarks section of the SAR, theuser must reference the FDMA mission JIST ID that is supporting the NCWmission.

(4) Do not add NCW network information into the Time-DivisionMultiple Access (TDMA) section of JIST, as this format is not supported atthis time.

c. If no GAR is reauired (ex: no DISN services needed or user willconnect to a Regional Hub Node (RHN) or Adelaide teleport in Australia) put acomment in the remarks section of the main SAR entry page indicating “no DISNservices needed — no GAR needed due to connection to Adelaide teleport.

d. Units must provide justification if they are unable to operate in allof the Wideband Global SATCOM -approved modulations and waveforms foridentified modems or modem/terminal combinations. Additionally, units mustprovide justification if their multiband terminal is unable to operate in oneof its bands. RSSCs ability to resource wideband services is impaired whenunits cannot operate in the entire frequency range due to equipmentlimitations.

13. special Instruction for Commercial SARs

a. DTG on Commercial SARs must be submitted using the following format:ddlGOoz mmm yy - dd2JOOz mmm yy.

Enclosure (1)5

2400G-6

b. If no GAR is required (ex: no DISN services needed or user willconnect to a RUN or Adelaide teleport in Australia) put a comment in theremarks section of the main SAR entry page indicating “no DISN services needed— no GAR needed due to connection to Adelaide teleport.”

c. Ku Bandwidth Request (Enclosure (5)) must be submitted to I MEF G-6via NIPR before the request will be processed in JIST. Continental UnitedStates (CONUS) Missions not requiring a CAR only require a Ku BandwidthRequest, and do not require a JIST submission.

d. Terminal Block Up Converter/Low Noise Block model and part numbermust be provided for each terminal listed in SAR.

e. For Outside the Continental United States (OCONUS) TDMA Ku missions,SAR submitters must select IP mission type vice TDMA in the SAR drop downmenu.

f. For CONUS TDMA Ku missions only a Ku Bandwidth Request is required.

14. special Instructions for EHF SARs.

a. DTG on EHF SARs must be submitted using the following format:ddl600z mmm yy - dd2300z mmm yy.

b. All networks require an active SAA regardless of the networkprecedence.

c. Guidelines for Point-To-Point (PTP) calls are as follows:

(1) Low Date Rate. Units may conduct P3 PTP calls without a SAA.However, users are reminded to conduct PTP calls in the least robustmodulation mode operationally supportable (DPSK 4+108, 2+54, or 1+27) . Thiswill prevent unnecessary loss of communications, due to preemption, whileconducting the PTP call.

(2) Medium Date Rate (MDR) / Extended Date Rate (XDR) . Units mayconduct unfenced P3 PTP calls (256k and below) without a SAA when logged ontoMDR/XDR on a first come/first served basis. Units are not authorized to moveMOR/XDR antennas to conduct FTP calls unless they are designated as theprimary antenna controller lAW an approved SAA. FTP calls will last nolonger than 24 hours with the exception of contingencies, such as equipmentfailures or satellite and Gateway outages. PTP calls exceeding 24 hours forusers not in a contingent status will be torn down by RSSC or 4th SpaceOperations Squadron (4 SOPS) . PTPs that require an extension beyond 24 hoursmust be coordinated within the service chain of command and have a valid SARin the queue. P3 unfenced resources will be monitored, and if oversaturationoccurs, FTP calls will be at risk for teardown by the RSSC or 4 Sops.

(3) MDR/XDR. Units may conduct fenced FTP calls only with anapproved SAA.

Enclosure (1)S

2400G- 6

(4) EHF resource violations are a serious offense for authorizedusers and cause unnecessary communications to be outages for authorizedusers. Users found violating El-iF resources through activities, such asunauthorized spot beam movement, improper access to EHF resources without avalid SAA, or repeat/excessive use of P3 PTP will result in the terminationof EHF privileges.

(5) If no GAR is required, put a comment in the remarks section ofthe main SAR entry page annotating the reason.

(6) EHF PTP Gateway missions that are 2048K and below do not requirean SDB waiver. Gateway missions above 2048K do require an 5DB waiver andmust be submitted lAW waiver timelines. (see paragraph 7)

15. special Instructions for GARs. All missions requiring DISN services orGateway support will be submitted in approved Defense Information systemsAgency (DISA) Headquarters formats as an email attachment sent to I MEF G-6.C-AR forms with detailed instruction and examples for completing GARs arelocated on the SIPRNet at the following URL:https://disa.deps.smil .mil/org/dodin/DGOC/PP/CQNEX/default.aspx

16. Special Instructions for World Wide Reach Back (WWRB)

a. Ku Band missions. A Ku Bandwidth Request (Enclosure 5), a WWRBRequest (Enclosure (6)) and an Exercise Support Request (ESR) (Enclosure (7))are required to be submitted to I MEF G-6 via NIPR email NLT 14 days prior toMission start Date.

b. K Band missions. Refer to normal SHF submission guidelines.

17. Global Broadcast service (GBS) . GBS instructions will be handled via5EPCOR.

18. Long term missions. Priority 4 or lower missions will not be validatedfor periods greater than 40 days. Users must submit additional requests viaJIST in support of follow-on or extended access periods. Exception to thispolicy applies to priority 4A, 4B, and 4C missions, however, these missionsmust be validated by the exercise JTF/CTF via assigned communications officerin order to support a defined exercise period. For SARs seeking satelliteaccess for periods greater than 40 days, exercise task order and additionaldocumentation are required at time of request to MARFORPAC.

19. Active Missions/Changes to Active Missions

a. Access modifications, extensions and changes to active missions aresubject to satellite resource availability and will be handled on a case-by-case basis. The RSSC, DISA Contingency & Exercise Branch, and GBS Helpdeskwill coordinate modifications to existing access with the sponsoringvalidating authority, and applicable Gateways. The validating authoritiesare responsible for limiting excessive or ongoing mission changes. Multiplechanges slow down the planning process and impact the availability of alreadylimited resources. Architectural changes to SARs that are made afterissuance of an BAA and require the R5SC to re-plan, will void USPACOM

Enclosure (1)10

24000-6

validation. As such, change SARs are subject to delays in service, periodadjustments, a partial denial of service, or rejection with a denial ofservice.

b. Mission duration changes of 24 hours or less may be requested by IMEF G-6 and/or MARFORPAC via email to the RSSC. Requests for an early starttime must be received by RSSC at least 48 hours prior to mission start time.Recuests for delayed end time must be received by RSSC at least 24 hoursprior to mission end time. Requests which are received by RSSC within 48hours of start time or 24 hours of end time will be considered untimely andwill be processed according to mission priority and satellite availability.

c. Mission duration changes of more than 24 hours require the submissionof a change SAR. Extensions to active missions will not exceed 10 days or atotal of 40 days of service. Missions requiring extensions for greater than10 days, or for a total of 40 days of service, will require submission of anew SAR.

d. Satellite accesses must be activated lAW parameters outlined in theSAA.

(1) Failure to acquire. Failure to acquire the satellite andactivate the mission within 48 hours may result in a cancellation message.

(2) Late access. If a unit is unable to establish connection by therequested start date, the unit must report the reason for the delay andanticipated start date to the chain of command and satellite control.Failure to report delays may result in loss of support and possible missioncancellation.

(3) Failed attempts for satellite controllers or resource controllersto reach the provided 24 hour POCs may result in mission cancellation andresource re-allocation.

e. Early end of mission. Any mission that ends earlier than therequested time frame must be reported to the chain of command and satellitecontrol. Failure to report end of missions may result in non-support offuture missions. Users must submit an After Action Report (AAR) within 72hours of mission cancellation or prior to submission of the next SAR,whichever comes first.

20. Electromagnetic Interference (EMI) . EMI reporting instructions will behandled via SEPCOR to include Joint Spectrum Interference Resolution Online,Space Support Request, and Primary Monitoring Event List.

21. After Action Report. USPACOM policy requires all units to submit AARsas they provide important information regarding sufficient satellite/gatewayresources, Gateway services, etc. AARs must be submitted no later than 10days after mission completion. AARs will be submitted utilizing the JIST AARtool. In the event of a JIST outage or the JIST AAR tool is not functioningproperly, AARs will be submitted to MARFORPAcG6SATCOMOPS@usmc.smi1.mil viathe chop chain that is reflected within JIST. Failure to submit AARs may

Enclosure (1)11

2400G-6

result in delay and possible denial of future access requests. WidebandMILSATCOM AARs constitute an exception to this policy and will be handled lAWreference (g)

Enclosure (1)12

MARFORPAC SATCOM Priority Quick Reference

z

HC

mC-U

n

nVIVI

C

n0zHamanVI

PRI 1 Strategic Order (Essential to National Survival)

SATCOM JOINT STAFF MARFORPAC SARPRIORITY DEFINITION INTERPRETATION CATEGORY

1A System Control/Orderwire18 Executive Support181 Presidential Support182 Secretary of Defense Support183 Secretary of State/Envoy and Emissary

Support/Diplomatic Negotiations1C Strategic and Threat Warning/Intelligence10 National and Strategic Nuclear Force Direction

RequirementsiF SECDEF Directed COCOM Emergency Operations

Authority (Other than Executive Support)

PRI 2 Tasked Plan Execution (OPLAN, CONPLAN, functionalplan (FUNCPLAN))

2A OCS SupportRelates exclusively to the support provided to thechairman and vice chairman of the JCS in the executionof their duties as senior military advisors to the SECOEF.

28 Combatant Commander OperationsRelates exclusively to the efforts required of theCOCOM in peace and war to facilitate the execution ofthe functional or geographic mission. Includes combatservice support.

2C JTF or CIT Operations Direct Task ForceCommunicationsDoes not include internal communications of task forcecomponents.

2D Component Operations (Theater Forces)Communications internal to a component, includingcomponents that are task force participants.

mCC

mVI

C

2E Tactical Warning and IntelligenceRelated to sensors, personnel, and associated supportthat collect and disseminate time-sensitive intelligenceto U.S. combatants.

Enclosure (2)

MARFORPAC SATCOM Priority Quick Reference

Supports the routine transit and processing of DODmateriel.

0zH fl

m Ln2

0CH2m

PRI 3

SATCOM JOINT STAFF MARFORPAC SARPRIORITY DEFINITION INTERPRETATION CATEGORY

Essential Operational Support (Operations notassociated with an OPLAN, CONPLAN, FUNCPIAN)

3A Humanitarian Support /Defense Support of CivilAuthoritiesResponse to peacetime crises, disasten NationalSpecial Security Events.

3B Combatant Commander Operations.Operations not directly related to executing a taskedplan, but essential for operational support.

3C 1ff CT OperationsJTF and CFF communications not directly related toexecuting a tasked plan, but essential for operationalsupport. Does not include internal componentcommunications.

3D Component OperationsInternal component communications, including taskforce participants, not directly related to executing atasked plan, but essential for operational support.

3E Intelligence and WeatherIntelligence, information gathering, threatidentification, and weather collection activities thatare not directly associated with a higher priorityactivity.

3F Diplomatic Post SupportRoutine communications support to US diplomaticfacilities and personnel overseas.

3G Space Vehicle SupportRelates to launch and recovery support to spacevehicles.

3H EMI Activity ResolutionEMI will be assigned the priority of the missionaffected_or_311,_whichever_is_higher

mpC

mLfl

C

31 Logistics

4’ Enclosure (2)

MARFORPAC SATCOM Priority Quick Reference

CCHam

PRI 6 Research, Development, Test, and Evaluation andGeneral

BA Electromagnetic Interference ActivityTesting/Resolution

68 DOD-Sponsored TestingN/A TO MARFORPAC

6C DOD-Sponsored Demonstrations60 DOD Administrative Support6E DOD Quality of Life Initiatives

PRI 7 Miscellaneous7A DOD Support to Law Enforcement (Non-JTF support)78 Civil Non-Federal Agency Support7C Non-US Support as approved by the Authorized

Organization7D Other

N/A TO MARFORPAC

PRI 4 Training

SATCOM JOINT STAFF MARFORPAC SARPRIORITY DEFINITION INTERPRETATION CATEGORY

4A OCS Directed Exercise4B Pre-deployment Exercise Training (45 days out) EXAMPLE: MEU CERTEX,

Reserved for forces to exercise and train priority 1, 2, TX (WITH MFP UNITor3 requirements within 45 days of an operational PARTICIPATION)deployment.

4C COCOM Sponsored EXAMPLE: BALIKATAN,Specific training tasks associated with supported and COBRA GOLD, ULCHIsupporting commands; imminent follow-on FREEDOM GUARDIAN,deployment, or operations in support of homeland KEY RESOLVE, RIMPAC,security/defense . TALISMAN SABER

40 Major Command: Air Force, Major Command-Army MEF & MSC HQ LEVEL.Echelon 2 sponsored training performed in the name (Example: MEF-EX, DAWNof a Service’s maior command. Bill?, STEEL KNIGHT)

4E Joint Forces Training (Multiple Categories) Forces NOT NAVY & MCengaged in sanctioned joint training. TRAINING

4F Unit-sponsored Unit-level training. BELOW THE MSC FIQ ORREGIMENT LEVELTRAINING

5A58

Service Secretaries

sc

PRI 5 Very Important Person Support

SDCOCOM TravelOther Travel

Service Chiefs N/A TO MARFORPAC

3 EnciDsure (2)

MARFORPAC Routine SAR/GAR Submission Timeline Calendar

SUN MON TUE WED THUR FRI SAT

30 1-Dec

SM DUETOI MEF I MEF SAR REV

(01 FEB START) 5DB WAIVER REQUIRED

Pr,P,f,28-Nov 2:

7

5DBWAWER REQUIRED DAY 1

SAR DUETO MFPI MEF SAR REV

/((,

SUB WAIVER REQUIRED 506 WAIVER REQUIREDDAY 3

SOB WAIVER REQUIRED

‘fi/

MFPSAR1 MFPSARRW 15ETOPAcO SARDUETOIMEF IMEFSARREV

1Z 13 14

!Lc’ 4 5DB WAIVER ROUTINE DAY 1REQUIRED (Dl FEB START) ROUTINE

19 20 21

r,I

IMEFSARREV

18

I MEFSAR REV

J4%fJ

ROIThNE ROUTINE

29Wr_iirrr%rrrj,iI MEF SAR REV

DAY 1SM DUE TO P MEFw Eflr’r’arr,/_

11

W/ETP(O1FEBSTART)

LtEPTSA //////,

IMEFSARREVDAY 3

W/ ETP

16

/ti

MFPSARREV

15

ff 22 23 24 25

1-Febf 29 30 31

MISSIONSTART

ROUTINE SAR REVIEW AT MFP (WEEKEND OR HOLIDAY)

ROUTINE SAR REVIEW AT! MEF (WEEKEND OR HOLIDAY)

—...--—

DUETOW/ EW

17

MFP SAR REVDAY 4a

MFPSAR REVflAJ__ - -

NOT ACCEPTSM

Enclosure (3)

a___

Satellite Access Request(SAR)Exception to Policy (ETP) Form

REQUESTING UNIT

EXERCISE/EVENT NAME:

JIST 10* SAR START DATE: TEEP EVENT (YIN)

I I I I

UNIT POC RANK / NAME (LAST, FIRST)

UNIT POC PHONE NUMBER UNIT POC SIPR EMAIL

I I

TO BE FILLED OUT BY UNIT POC

REASON FOR LATE SUBMISSION

ENCLOSURE ( q)

MARFORPAC

SatelliteException

Access

to Policy

Request (SAR)(ETP) Form

JIST ID#

I IOPERATIONAL IMPACT IN THE CASE OF DENIAL

ACTIONS TAKEN TO PREVENT LATE SUBMISSIONS

1/)ENCLOSURE (

MARFORPAC

JIST 104*

Satellite Access Request (SAR)Exception to Policy (ETP) Form

I I

TO BE FILLED OUT BY 0-6 PROVIDING SIGNATURE

I understand that lAW the USPACOM satellite access request/gatewayaccess request (SAR/GAR) policy , the requesting unit is required torequest for an Exception to Policy (ETP) that will allow a late SAl? tobe considered for review and processing at USPACOM J6. ACKNOWLEDGE

I understand that due to our failure to meet the required timeline,the SAR is subject to delay in service, period adjustment, partialdenial of service or rejection with a denial of service. ACKNOWLEDGE

0-6 REMARKS (NOT REQUIRED)

0-6 DIGITAL SIGNATUREMust be signed by 0-6 prior to reaching MARFORPAC

ENCLOSURE (L/

Attach ETP Form to JIST logbook

Unit

Please send This completed document tomartin. manolona(Thusmc.milscott.tatum ctr( usmc. mu

For classified missions, please send this document tmartin manolona

- ctr(usmc. Sm mit

Cc all unclassified bandwidth requests to:

Civilian Andre Coleman: andre.cdeman@usmc.mil

from:

To:

SNCO or abovE POChWonnationName:Rank:

Follow up on your request! Contact the Bandwidth Manager if you do not receivean acknowledgement that your request was received within forty-eight (48) hours.

After the Bandwidth Manager has received the request, a confirmation of receipt wilt besent to the requesting unit. Once the request has been approved, the unit will receive aSatellite Access Authorization (SM) containing alt pertinent information. Please keep inmind that all SAR forms requesting DOD/DISA TELEPORT SERVICES Will need to be

also processed through JIST so that the respective RSSC can generate the SM,

Phone:

E-Mail:

Name:

Rank:

UDlInk I

Commercial Ku-Band Satellite Access Request (SAR)

Cell: 7604374080 CommercIal: 760-725-1758, 6077 DSN: 365-1758, 6077

Phone:

E-Mail:

TDMAFDMABOTH

Vendor Information: TCS 24x7 MSOC: 8fl482-7762 I 410-2804841 I-DIRECTE-mail: msoc@telecomsys.com NOV41 SOW

PDQA DIAGRAM Info: When conducting FDMA operations, please the diagram tab with your Comm archIbctii”MI-duplex circuit links and the data rates for each lint..

Transmit Data Rate:Receive Data Rate:

Aggregate Rate: 01t When conduflDMMop.mtons, ple.s. II In the below section It conducting TDMA operations ONLY, planesleave the above (FDMA) section L_ -— — .

Number of Caen: I Size: j__________________

Terminal Number Terminal NumberLocation (Let/Long or city): Location (La/Long or city):

System Name: System Name:System Version: System Version:

Antenna Size/Type: Antenna Size/Type:MSC: MSC:

BUC LU (KIt): BUG LO (KHz):For MRT I BUC Power For MRT euc Power

config. files LNB Powec config. files LNB Power:LNB Reference: LNB Reference:

Terminal Number Terminal Number:Location (LauLong or cIty): Location (Lfl’Long or city):

System Name: - System Name:System Version: - - System Version:

Antenna Size/Type: - Antenna Size/Type:- MSG: MSC:

BUCLOØG1ForMRT BUCPq’E. F0rMRT BUG Power:

config.file& LNBPoWe config.Ftes LNBPowec1148 R$.j LNB Reference:

Addifionalfiequanhl :‘- ‘

Enclosure (5)

0 I—s

0 Ca ci II CD

WWRB REQUEST

TERIMINAL #2 INFO TYPE:TERMINAL #2 SERIAL NUMBERLATS & LONGS:MODEM TYPE(S):MODEM SERIAL NUMBERBUG / LNB INFORMATION:

TX FREQ RANGE:RX FREQ RANGE:

LNB 10 MHZ REQUIRED:LNB DC POWER REQUIRED:LNB LO:BUC:BUC LO:10 MHz REFERENCE REQUIRED:DC POWER REQUIRED:

MOBILE / FIXED:PVC INFORMAITON:IP ADDRESSJDHCP

TERIMINAL #3 INFO TYPE:TERMINAL #3 SERIAL NUMBERLATS & LONGS:MODEM TYPE(S):MODEM SERIAL NUMBERBUG I LNB INFORMATION:

TX FREQ RANGE:RX FREQ RANGE:

LNB 10 MHZ REQUIRED:LNB DC POWER REQUIRED:LNB LO:BUG:BUG LO:10 MHz REFERENCE REQUIRED:DC POWER REQUIRED:

MOBILE / FIXED:PVC INFORMAITON:IP ADDRESS/DHCP

2 Enclosure (6)

WWRB REQUESTTERIMINAL #4 INFO TYPE:TERMINAL #4 SERIAL NUMBERLATS & LONGS:MODEM TYPE(S):MODEM SERIAL NUMBERBUC/LNB INFORMATION:

TX FREQ RANGE:RX FREQ RANGE:

LNB 10 MHZ REQUIRED:LNB DC POWER REQUIRED:LNB LO:BUG:BUC LO:10 MHz REFERENCE REQUIRED:DC POWER REQUIRED:

MOBILE I FIXED:PVC INFORMAITON:IP ADDRESSIDHCP

-‘*;;

TERIMINAL #5 INFO TYPE:TERMINfl #5 SERIAL NUMBERL4TS & LONGS:MODEM TYPE(S):MODEM SERIAL NUMBERBUG! LNB INFORMAflON:

TXFREQ RANGE:RX FREQ RANGE:

LNB 10 MHZ REQUIRED:LNB DC POWER REQUIRED:LNB LO:BUC:BUG LO:10 MHz REFERENCE REQUIRED:DC POWER REQUIRED:

MOBILE I FIXED:PVC INFORMAITON:IP ADDRESSIDHCP

3 Enclosure (6)

-ECCS Service Request (ESR) (vi .3)

Document Overview

The ECCS Service Request (ESR) document is used to request network and phoneservices for the ECCS Rapid Response Kit (RRK). See the ECCS RRK ElectronicTechnical Manual (ETM) for instructions on filling this form out and submitting it.

NOTE: This document is only used for requesting CBS services; a SANGM will haveto be submitted to request Satellite services (SAA) and Black Core connection (GAA).

Table of Content

1. Mission Information I2. CBS Station I3. Convergence Network 24. NIPRNeUVoIP Services 25. SIPRNeUVoSIP Services 36. Point of Contact 37. Submit ECCS GAR 4

Version ControlVersion Date_Intials Change

1.0 20180116 AEE Initial Request

1. Mission Information1.1. Unit:1.2. Mission Dates: StartOlick here to enter a date. End:Click here to enter a date.1.3. Mission Type: flReal World: DExercise: STraining:1.4. ECCS Kit: DRRK: Eother1.4.1. ECCS Kit Number: 007

2. CBS Station2.1. ECCS CBS: I MEF D II MEF LI III MEF

Enclosure (7)

3. Convergence Network3.1. Primary Communications EquipmentEVSAT-S: Dinternet Access:NOTE: The CBS will support both Hawkeye Ill Lite and Internet connections for allmission, this option is to identify which communication path the CBS should be setup forby default. To change comm paths during the mission contact the CBS operator.

3.2. Convergence VolP Access3.2.1. Primary Troubleshooting VoIP Phone:

MAC Address

4. NIPRNeUVoIP Services4.1. NIPRNet AccessEves: ENo:4.1.1. Number of NIPRNet Devices (Laptops, VTC, etc.)7

4.2. NIPRNet VTC AccessEYes: NNo:4.2.1. VTC Model:4.2.2. VTC Protocol/Ports:

4.3. Voice over IP (VolP) AccessEYes: ENo:4.3.1. VoIP Phone MAC address and Model

MAC Address Phone Model

Enclosure (7)

EWes: lThNo:MAC Address Phone Model

3.2.2. Alternate Troubleshooting VoIP Phone: Eyes: flNo:Phone Model

2

5. SIPRNeUVoSIP Services5.1. SIPRNet AccessDYes: flNo:5.1.1. Number of SIPRNet

5.2. SIPRNet VTC AccessDYes: ENo:5.2.1. VTC Model:5.2.2. VTC Protocol/Ports:

Devices (Laptops, VTC, etc.)

5.3. Voice over Secure IP (VoSIP) AccessDyes: DNo:5.3.1. VoSIP Phone MAC address and Model

MAC Address

6.2. Mission POC:6.2.1. Name:6.2.2. Primary Email:6.2.3. Alternate Email:6.2.4. SIPRNet Email:6.2.5. Commercial Phone:6.2.6. Alternate Commercial Phone (mobile):6.2.7. DSN Phone:6.2.8. VoSIP Phone:

Enclosure (7)

6. Point of Contact6.1. Mission Planner6.1.1. Name:6.1.2. Primary Email:6.1.3. Alternate Email:6.1.4. SlPRNet Email:6.1.5. Commercial Phone:6.1.6. Alternate Commercial Phone (mobile):6.1.7. DSN Phone:6.1.8. VoSIP Phone:

3

6.3. Alternate POC:6.3.1. Name:6.3.2. Primary Email:6.3.3. Alternate Email:6.3.4. SIPRNet Email:6.3.5. Commercial Phone:6.3.6. Alternate Commercial Phone (mobile):6.3.7. DSN Phone:6.3.8. VoSIP Phone:

6.4. Alternate POC:6.4.1. Name:6.4.2. Primary Email:6.4.3. Alternate Email:6.4.4. SIPRNet Email:6.4.5. Commercial Phone:6.4.6. Alternate Commercial Phone (mobile):6.4.7. DSN Phone:6.4.8. VoSIP Phone:

7. Submit ECCS ESRa. Save file with RRK number (or unit name) and mission dates.

Enclosure (7)4