Note: Additional references and guidance links provided at the end
SSRA Frequently Asked Questions (FAQs)
SSRA Guidance Document
DoDI 4650.01 Management and the Use of Electromagnetic Spectrum
DoDI 4650.01 requires system developers of spectrum dependent (S-D) systems and equipment to identify and mitigate regulatory, technical, and operational spectrum supportability (SS) and electromagnetic environmental effects (E3) risks during the development process. The instruction also requires that the resulting spectrum supportability risk assessment (SSRA) be updated to provide increasing levels of detail as the item's design matures. The SSRA constitutes the basis for milestone decision authority determinations of spectrum supportability and provides increasing levels of detail regarding a system’s regulatory, technical, and operational requirements in Initial, Detailed, and Updated SSRAs.
SSRAs are required to determine and document if adequate spectrum is available to support system operation in DoD, Allied, and Coalition operations. SS and E3 risks and the steps that need to be taken to mitigate the risks are to be identified in the SSRA and provided to the Military Department (MILDEP) Spectrum Management Office (SMO) who will review the SSRA and forward their recommendations to the Service Chief Information Officer (CIO) for approval. A statement on the spectrum supportability of an acquisition is then forwarded to the milestone decision authority (MDA). Program Manager (PMs)/Materiel Developers (MATDEVs) should consult, as early as possible, with their respective MILDEP SMO regarding the application and tailoring of the SSRA, and to ensure that all user requirements are met.
The detail and scope of each SSRA depends upon the system’s entry point into the DAS, the complexity of the system, knowledge of the S-D systems to be acquired or integrated, and the intended operational EME. In general, each PM/MATDEV is required to prepare and submit an SSRA when the acquisition includes or incorporates an S-D system or equipment, including commercial items (CI) and non-developmental items (NDI) that are S-D.
To summarize:
- SSRAs are used to manage SS and E3 risks through systems engineering processes
- SSRAs are required for each milestone decision, updated for FRP and system upgrades
- Each has a regulatory, technical, operational, and E3 component
- Complex “system-of-systems” may require more than one SSRA
They include the conduct/results of Electromagnetic Interference (EMI)/Electromagnetic Compatibility (EMC)/ Electromagnetic Vulnerability (EMV) assessments, and other E3 assessments, as required by MILDEP SMO.
|
Defense Acquisition System (DAS) Phase |
Materiel Solution Analysis |
Technology Development |
Engineering and Manufacturing Development |
Production and Development |
Operations and Support |
| MS |
Event |
Milestone (MS) A |
MS B |
MS C |
Request Authorization to Operate - other than Testing |
|
| ESC |
Required USG and HN Coordination |
Stage 1 Conceptual |
Stage 2 Experimental |
Stage 3 Developmental |
Stage 4 Operational |
Stage 4 (Note-to-Holder) |
| SSRA |
Required SSRA for Each Event |
Prepare SSRA |
Prepare/Update SSRA |
Prepare/Update SSRA |
Prepare/Update SSRA |
Prepare/Update SSRA for specific missions, new HN deployments, system mods, etc. |
A description of each component:
Regulatory Component - addresses the ESC stage and status and the relative status of the acquisition with respect to the radio services authorized within the U.S. tables of allocation (TOAs) and intended Host Nation (HN) insights from the ESC and HNC processes.
Tasks for Regulatory Component of SSRA (Table)
Technical Component - focuses on candidate technologies and required technical parameters, such as system type, platform type, bandwidth requirements, etc, and initial quantification of potential mutual interactions that may require further study.
Tasks for Technical Component of SSRA (Table)
Operational Component - evaluates all S-D systems anticipated to be in the operational environment to determine if operational performance requirements, as specified in the requirements documents (ICD, CDD, CPD, etc), or acquisition documents are met. Frequency-distance (F-D) separations, and/or tactics, techniques, and procedures (TTPs) to mitigate risks to acceptable levels should be identified.
Tasks for Operational Component of SSRA (Table)
E3 assessment for SSRA, as a minimum, should address, EMC and EMI to determine the potential for interactions between the proposed system and its anticipated operational EME. The assessment also includes an EMV analysis to determine the possible effect on operational performance as a result of any EM interaction.
- Analyses of additional E3 disciplines (e.g. HERP, HERF, HERO, EMP, ESD, lightning, etc) may be required; contact the MILDEP SMO for guidance.
- Navy systems will require E3 analyses for all applicable E3 disciplines. S-D systems intended for use by more than one Service or on multiple platforms, systems, or vehicles must be analyzed for all possible uses and users.
E3 Assessments for SSRAs
Submission of SSRAs
SSRAs are to be prepared, updated, and submitted for approval to the appropriate Service review authority prior to each acquisition MS and readiness reviews.
1st Submission of SSRA
- Prior to MS A, when applicable, with the components described earlier.
- Evaluates the acquisition’s spectrum needs vs national and international spectrum regulatory requirements and availability as well as the ESC stage and status of possible candidate S-D systems.
- Operational requirements, as stated in the Joint Urgent Operational Needs Statement (JUONS) or ICD, and the potential for technical issues, including E3, are to be assessed.
2nd Submission of SSRA
- Prior to MS B.
- Increase details in the Regulatory, Technical, Operational, and E3 components of the first SSRA based on new data and program maturity.
- Discuss impact to system operation; potential risks and mitigation measures.
- Operational EME should support early tailoring and development of E3 test requirements in the request for proposal and other acquisition documents during the Development Stage of the DAS.
3rd Submission of SSRA
- Prior to MS C.
- Components of the second SSRA are updated with more detailed spectrum and E3 analyses.
- A Stage 4 ESC is required for this SSRA for ALL of the S-D items that are part of the acquisition program.
- Operational EMEs should be refined; spectrum and E3 risks reduced to acceptable levels through mitigation measures and/or TTPs.
4th Submission of SSRA
- Prior to Full Rate Production (FRP).
- Components of the third SSRA should be updated with completed spectrum and E3 analyses.
- This SSRA addresses final guidance from the ESC and, when applicable, HNC processes as well as changes to U.S., Federal, or civil regulations impacting the system’s frequency bands.
- Risks should have been reduced to acceptable levels.
Updated SSRAs - SSRAs are to be updated as follows:
- For production and fielded systems to reflect changes to the S-D system or equipment spectral output, its operational deployment, HN regulations, or modifications and upgrades of the integrated system, family of systems (FoS) or system of systems (SoS).
- For readiness reviews
- System is ready for operational deployment.
Risk Management
Risk management is an essential and integral part of technical program management throughout the life cycle. In general, risk can be classified into a program risk based on likelihood and consequence, or a performance or safety risk based on the probability or frequency of occurrence, and its severity. A standard format for evaluating and reporting risk assessment findings can facilitate a common understanding of program risks at all levels of an organization. Stop-light matrices are often used to illustrate the level of risks identified within a program.
A sample matrix to illustrate the impact of a risk is shown in the table below. The impact or consequence of the potential risk may be reported as low, moderate, or high, as represented in the matrix with the colors green for minimal or minor impact, yellow for moderate, and red for significant or severe impact.
| Level |
Impact |
| 1 |
Minimal or no consequence to technical performance |
| 2 |
Minor reduction in technical performance or supportability, can be tolerated with little or no impact on program; same approach retained. |
| 3 |
Moderate reduction in technical performance or supportability with limited impact on program objectives; workarounds available |
| 4 |
Significant degradation in technical performance or major shortfall in supportability; may jeopardize program success; workarounds may not be available om may have negative consequences. |
| 5 |
Severe degradation in technical performance; Cannot meet supportable threshold; will jeopardize program success; no workaround available. |
Likelihood of Risk Occurrence
The likelihood of occurrence of the risk should also be quantified. A suggested scheme is shown in Table IV where green denotes little or no likelihood of occurrence, yellow denotes a likely occurrence, and red denotes a highly likely or near certain occurrence.
| Level |
Likelihood of Occurrence |
Probability of Occurrence |
| 1 |
Not Likely |
<20% |
| 2 |
Low Likelihood |
20-40% |
| 3 |
Likely |
40-70% |
| 4 |
Highly Likely |
70-90% |
| 5 |
Near Certainty |
>90% |
Risk Classification Logic
The red, yellow, and green categories for describing the spectrum and E3 issues are shown below.
RED
-
No certification or approved J/F 12 in the Military Communications Electronics Board (MCEB) archived database
- Operating in the incorrect or non-allocated frequency band or significant SS issues are known to exist for this system/equipment
-
E3 or, as a minimum, EMC and EMI studies not completed, planned or anticipated; known mitigation measures will impact operational deployment and/or use in EME
-
HNC process not started; operational and/or developmental use may be extremely limited and/or not permitted at all
-
System will not likely receive HN spectrum support, or may be allowed to operate after lengthy bi-lateral negotiations with individual HNs
|
YELLOW
-
No certification or approved J/F-12 in the MCEB archived database, however similar equipment has been approved and is in the database
-
System is operating in properly allocated frequency spectrum and ESC can be anticipated
-
Requires minimal actions for ESC, i.e. Note-to-Holder or updated certification request
-
E3/EMC studies funded/planned or completed with mitigation measures identified that will not adversely impact operations
-
Minimum spectrum issues are known to exist for this equipment
-
Operational and/or developmental use is anticipated to be supportable
-
May receive HN spectrum support, but with numerous geographic, temporal, spectrum, or operational restrictions; spectrum use in a band may be restricted to a limited number of channels
|
GREEN
-
Approved J/F-12 exists in the MCEB archived database (minimum Stage 2 for MS B)
-
Requires no actions for spectrum support
-
E3/EMC studies completed and compatible operations confirmed or acceptable mitigation measures identified that will not impact operations
-
No SS issues are known to exist for this equipment in the intended operational area
-
Operational and/or developmental use is or will be supportable
-
High likelihood of receiving HN spectrum support to operate with few, or a minimum number of, possible spectrum or operational restrictions
|
For SSRA Format/Content guidance, please see Appendix A of the Joint Service Guide for the Development of an SSRA
References
https://acc.dau.mil/CommunityBrowser.aspx?id=334074#7.6.4.1
http://www.dtic.mil/whs/directives/corres/pdf/465001p.pdf
https://acc.dau.mil/CommunityBrowser.aspx?id=491776 (SSRA Guidance Document)
Understanding the E3 Assessment- http://ifiamps.wordpress.com/category/spectrum-supportability-risk-assessments-ssra/
SSRA Slideshow - http://www.afcea.org/events/jwc/13/documents/SSRAEngagementTheater.pdf
Compatibility (EMC) and preventing EMI for S-D systems and equipment.
