SSRA engagement theater oct2015
•Download as PPTX, PDF•
1 like•553 views
The document discusses requirements and guidance for conducting Spectrum Supportability Risk Assessments (SSRAs) for spectrum-dependent systems. Key points include: - SSRAs are required by DoD Instruction 4650.01 to identify and mitigate spectrum supportability risks early in acquisition. - The process, format, and required components of an SSRA are defined in the Joint Services Guide for Development of an SSRA and DI-EMCS-81543. - An SSRA must address regulatory, technical, operational, and electromagnetic environmental effects (E3) components to analyze risks and recommend mitigations. It is reviewed at acquisition milestones.
Recommended
Recommended
More Related Content
Similar to SSRA engagement theater oct2015
Similar to SSRA engagement theater oct2015 (20)
Recently uploaded
Recently uploaded (20)
SSRA engagement theater oct2015
- 1. UNCLASSIFIED UNCLASSIFIED Spectrum Supportability Risk Assessment (SSRA) ENGAGEMENT THEATER SSRA Requirements For Spectrum Dependent Systems
- 2. UNCLASSIFIED UNCLASSIFIED Bottom Line Up Front • SSRAs and Equipment Spectrum Certification (ESC) are two separate processes. • The Requirements are established in Department of Defense Instruction (DODI) 4650.01, January 9, 2009 • The SSRA form and format are provided in the Data Item Description (DID) DI-EMCS-81543; dtd 20120120 • The SC form and format are provided by El-Cid, Stepstone, and SCS • Additional Content guidance is provided in the Joint Services SSRA Guide and service specific documents 2
- 3. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED A Process, Not an Event Risk Identification Risk Analysis Risk Mitigation Planning Risk Management Implementation Risk Tracking Spectrum Supportability Risk Assessment 3
- 4. UNCLASSIFIED UNCLASSIFIED SSRA Requirements and Guidance • Equipment Certification and SSRA Requirements are drawn from: DoD Instruction 4650.01, Policy and Procedures for Management and Use of the Electromagnetic Spectrum – Establishes policy, assigns responsibilities, and provides instructions for management and use of the electromagnetic spectrum – Requires the submittal of an SSRA • Enclosure 3, 2.b: “At a minimum, electromagnetic interference (EMI) and electromagnetic compatibility assessments shall be made…” • Enclosure 3, 2.d: “ DoD Components' S-D system developers are encouraged to initiate the SSRA in order to help identify regulatory, technical, and operational risks while completing the appropriate stage of certification of spectrum support.” • Each SSRA submission requires ALL 4 Components; an increase in what is depicted in DoDI 4650.01, Enclosure 3, Table 1. • Acquisition Milestone requirements for SSRA and Frequency Allocation are specified in the Defense Acquisition System – DoD Instruction 5000.02 “Operation of the Defense Acquisition System,” Table 2 • Guidance on the preparation of an SSRA is provided in the “Joint Services Guide for Development of an SSRA” • Suggests format and content for an SSRA • Expands on E3 assessment for an SSRA • Expands on risk management • Service Specific Requirements and Guidance
- 5. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED All electric or electronic systems shall be designed to be mutually compatible with other equipment in the expected operational EM environment (DoDD 5000.01, DoDI 3222.03) E3 Control shall be planned for and incorporated in all DoD acquisitions (DoDI 3222.03) Estimates or obligation of funds for the development or procurement of C-E systems should be withheld pending assurance of the availability of frequency support by the NTIA (OMB Circular A-11, NTIA Manual) DD Form 1494 (Application for Frequency Allocation) shall be used to initiate and obtain spectrum certification (DoDI 4650.01, DFARS 235.071) Law and Associated Regulations – OMB Circular A-11 – NTIA Manual – DFARS 235.071 DoD Policy – CJCSI 3170.01, CJCSI 6212.01 – DoDD 5000.01 Enclosure 1, Para. E1.1.10 – DoDI 5000.02 – DoD Instruction 3222.03, 25 Aug 2014, DoD E3 Program – DoD Instruction 4650.01, 09 Jan 2009, Management and Use of Radio Frequency Spectrum Policies 5 E3/SS Policy DoDI 5000.02: Relevant E3/SS Changes: Table 3, Regulatory Requirements Applicable at Milestone (MS) B and C Enclosure 4, Table 2-1/2-2: Spectrum Supportability required for Major and ACAT II and lower programs DoDD 5000.01: E1.1.10. Information Superiority. Acquisition managers shall provide U.S. Forces with systems and families of systems that are secure, reliable, interoperable, compatible with the electromagnetic spectrum environment, ... [Encl 12] 11. SPECTRUM SUPPORTABILITY. For all electromagnetic spectrum-dependent systems, PMs shall comply with U.S. and host nation spectrum regulations…
- 6. UNCLASSIFIED UNCLASSIFIED Ser vi ceSpect r um M anagem ent O f f i ce( s) Joi nt / Nat i onal SSD Pr ocess NTI A ( SPS) M CEB ( ESG PW G ) Pr ogr amOf fi ce or Pr ocur ingAct i vi t y ( Pr ogr am of Recor d, COTS,NDI , Non- Pr ogr am ofRecor d) Spect rum Support abi l i ty Det ermi nat ion Approval Spect rum Support abi lit y Ri sk Assessment Program O f f i ce or Procuri ng Act i vi t y CJSCI 3170.01 CJSCI 6212.01 DOD 4630 series E3 and spectrum supportability must be addressed in CDD/CPD/TEMPs/ISPs DODD 5000.01 DODI 5000.02 Acquisition Managers shall provide systems that are secure, reliable, interoperable, and compatible with the electromagnetic spectrum environment For all electromagnetic spectrum-dependent systems, PMs shall comply with U.S. and host nation spectrum regulations. DODI 3222.03 DODI 4650.01 DOD Electromagnetic Environmental Effects Program Policy for the Management and Use of the Electromagnetic Spectrum Acquisition & Capabilities Regulations and Directives All derived from Title 47 US Code (statutory requirement) 1/15/2016 6
- 7. UNCLASSIFIED UNCLASSIFIED JCIDS /Acquisition System Spectrum Supportability (SS) Business Processes
- 8. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED 8 DoDI 5000.02: Operation of the Defense Acquisition System Frequency Allocation
- 9. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED 9 Spectrum Supportability Risk Assessment DoDI 5000.02: Operation of the Defense Acquisition System
- 10. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED “Policy and Procedures for Management and Use of the Electromagnetic Spectrum” Proper management required for operations involving spectrum dependent systems Spectrum Supportability Risk Assessments • Required on all Spectrum-Dependent (S-D) systems. • Includes increasingly detailed regulatory, technical, and operational assessments (to include EMC) • Assessments and Mitigation Plans are Reviewed by CIO or designate at MS A, B, and C, to determine supportability • Procedures specified at high level, recommended risk assessment tasks included as attachment • Certification in U.S. and Host Nations handled separately – doesn’t hold up risk assessments • PROBLEM: Format and Content requirements not specified 10 I DoD Instruction 4650.01 09 January 2009
- 11. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED Spectrum Supportability Risk Assessments Para 4 Policy e. For all S-D systems, DoD Components shall determine if there will be sufficient spectrum to support operation of the system during its life cycle. In order to affect design and procurement decisions, DoD Components shall: (1) Identify spectrum-related risks as early as possible via spectrum supportability risk assessments. (2) Review these assessments at acquisition milestones. (3) Manage the risks throughout the system’s lifecycle.” Enclosure 2, Responsibilities P5. HEADS OF THE DoD COMPONENTS. The Heads of the DoD Components shall: b. Develop procedures to implement the policies in section 4 of the front matter of this Instruction to include: (4) Procedures to identify and mitigate, as early as possible, spectrum supportability risks using spectrum supportability risk assessments. 11 I DoD Instruction 4650.01 09 January 2009
- 12. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED Spectrum Supportability Risk Assessments Enclosure 3, Procedures P2. SPECTRUM SUPPORTABILITY RISK ASSESSMENTS (SSRAs) a. DoD Components’ S-D system developers shall identify and mitigate regulatory, technical, and operational spectrum supportability risks using suggested tasks in the appendix to this enclosure. DoD Components’ S-D system developers shall increase the detail of these risk assessments as the S-D system’s design matures. b. DoD Components’ S-D system developers shall assess the risk for harmful interference with other S-D systems and/or harmful radiation-related effects. At a minimum, electromagnetic interference (EMI) and electromagnetic compatibility assessments shall be made (Reference (g)). c. DoD Components’ S-D system developers shall manage spectrum supportability risks with other developmental risks through systems engineering processes (Reference (i)). d. DoD Components' S-D system developers are encouraged to initiate the SSRA in order to help identify regulatory, technical, and operational risks while completing the appropriate stage of certification of spectrum support. e. Complex “family of systems” or “system-of-systems” may require more than one SSRA. (but still one overarching SSRA for the FoS or SoS) 12 I DoD Instruction 4650.01 09 January 2009
- 13. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • Program objectives: – Operational EMC for all DoD systems – Built-in EMC vice after-the-fact remedies – Common DoD-wide philosophies, approaches, and TTPs to preclude unacceptable degradation from E3. • Requires E3 control planning in all DoD acquisitions • E3 and SS issues must be resolved to acceptable risk before proceeding to next phase of acquisition • Assigns functional responsibility to OSD, Joint Staff, DISA, DSO, Services, DoD agencies, etc. 17 I DoDI 3222.03 – DoD Electromagnetic Environmental Effects (E3) Program (25 Aug 2014)
- 14. UNCLASSIFIED UNCLASSIFIED • Identify Regulatory, Operational, and Technical spectrum supportability (SS) and electromagnetic environmental effects (E3) Issues and assign risk level • For each identified risk, there should be a risk mitigation measure identified • Submitted through channels identified by each service – Process typically includes Service Spectrum Management Office, with Chief Information Officer (CIO) review/approval and Spectrum Supportability Determination (SSD). • SSRA required when the acquisition includes a S-D system or equipment, including commercial item (CI) and non- developmental item (NDI). • Initiate the SSRA while completing the appropriate stage of equipment spectrum certification (ESC) process SSRA Basics
- 15. UNCLASSIFIED UNCLASSIFIED • Complex “system-of-systems” (SoS), “family-of-systems” (FoS), and/or Platforms require: – One SSRA for the SoS/FoS/Platform to include ALL, imbedded S-D equipment – Individual SSRAs are required for each S-D Equipment (Exception: S-D equipments, with Stage 4 approval, are “Grandfathered” in; unless, the S-D equipment is receiving an upgrade/modification that affects its EM characteristics.) – Regulatory, Technical, Operational, and E3 Components are REQUIRED for each SSRA • Contact Service, SMO early for guidance – What spectrum/frequency band(s) should be used – What SSRA(s) is/are required • Detail and scope of each SSRA depends on: – the item’s entry point into the Defense Acquisition System (DAS) – its complexity – the intended operational environment – the maturity of the design SSRA Basics (Continued)
- 16. UNCLASSIFIED UNCLASSIFIED Joint Services Guide • SSRA Content Guidance • Components – Regulatory Content – Technical Contents – Operational Contents – E3 Assessment – Risk Assessment • Submission Requirements • Guidance on Risk Classification • Format Guidance
- 17. UNCLASSIFIED UNCLASSIFIED • Front Cover • Introduction • Executive Summary • Regulatory Component of SSRA • Technical Component of SSRA • Operational Component of SSRA • E3 Assessment for SSRA • Conclusions • Recommendations • References SSRA Report Format Joint Guidance Document Sept 2011/DI-EMCS-81543
- 18. UNCLASSIFIED UNCLASSIFIED Joint Services Guide for Development of an SSRA Final Draft, Sept 2011 Joint Services Guide
- 19. UNCLASSIFIED UNCLASSIFIED • Addresses: – ESC stage and status applicable to the DAS phase of the acquisition, – HNC (Host Nation Coordination) Status • With respect to the radio services authorized within the tables of allocation (TOAs) of the U.S. and intended Host Nation (HN) • Responses in HNSWDO from the HNC processes. SSRA Components Overview Regulatory Joint Services Guide
- 20. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • Service Spectrum Management Office • J/F-12 Data from processed ESC Requests – Frequency Assignment data (JSC Databases) – MCEB/SPS Comments – Resident at Service Spectrum Management Office – JDAWS at the Defense Spectrum Office – Stepstone/EL-CID/SCS searches • NTIA Manual – ITU Tables – Other web based allocation table resources • Host Nation Status available in HNSWD-O from the DSO – InternaInternational Comments – Normally requires a completed, Stage 4, Spectrum Certification. – Check www.efis.dk for operations in Europe Data Requirements & Sources Regulatory Component
- 21. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • ESC Request Submission does not ensure compliance with all regulatory requirements nor does it allow operation of systems…discuss frequency assignments versus ESC Requests. • Make sure the planned spectrum use is allocated for the intended function…radio service and station class • Look at all three ITU regions, not just US Allocations • Be wary of the "age" of HSNWDO data (not real-time enough). • For MS A look at existing systems with similar technical attributes • Coordinate as early as possible with your service SMO • Some of the Suggested Tasks for the Technical Component have Regulatory implications and may be addressed in this section. • Early and often discussions with the DoD Component SMO will save Time and Money and reduce Risk. Lessons Learned
- 22. UNCLASSIFIED UNCLASSIFIED • Identify other military and civilian and non-U.S. systems likely to be co-site or in close proximity by querying DoD or national system databases • Identify undesired interactions that may require further study using initial and measured technical parameters for candidate system and the technical parameters of S-D systems expected to be in operational environment. • Determine acceptable received EM levels to ensure that coexistence is feasible. • Evaluate system performance and effect on other S-D systems that may operate co- frequency or adjacent frequency expected in the intended environment. • Quantify, using tests or M&S, the impact of changes to the operational “signals-in- space” RF parameters to co-site EMC. • Determine potential link degradation and blockage due to atmospheric conditions, terrain and building obstructions within intended deployment areas • Generate recommendations to mitigate potential technical issues. SSRA Components Overview Technical Joint Services Guide
- 23. UNCLASSIFIED UNCLASSIFIED • Identify and quantify interactions with non-DoD, other Federal, and commercial users in the environment. • Identify/update spectrum risks and recommendations for mitigation of technical issues. • For non-communications systems (radar, passive sensors, etc.), determine the appropriate operational degradation as a function of the level of received environmental and co-site EMI. • Address how limitations or restrictions identified in the ESC/HNC process are being mitigated and/or resolved for each S-D equipment. • Assessment: – Identify/update spectrum risks and recommend mitigation techniques of Technical issues. Joint Services Guide SSRA Components Overview Technical
- 24. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • System Technical Parameters – Parametric Data from Spectrum Certification, DD Form 1494’s, J/F-12s – Data Sheets from Developer(s) – Program Office/Systems Engineering Note: Many technical parameters not available early in program • RF Modeling – Propagation – Interference Analyses – Selectivity Curves – Antenna Coupling • Co-site/Intersite data/modeling – Platform vs. EME at Key Locations • Discuss with Program/Systems Engineering Personnel • Detailed Modeling Data Likely not available for MS A Data Requirements & Sources
- 25. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • Tends to overlap with the other DoDI 4650.01 defined Tasks as well as the E3 Assessment (AF, Navy) • Understand what technical standards apply • May also need to considered other regional/national/international standards for systems looking to operate outside the US Lessons Learned
- 26. UNCLASSIFIED UNCLASSIFIED • Identify: – The S-D equipments that are incorporated, supported by the Acquisition, – The operational performance requirements, as specified in the Operational Needs Statement (ONS) or Joint Urgent Operational Needs Statement (JUONS) or, and the acquisition documents (e.g. ICD, CDD, CPD, or information support plan (ISP)), – The S-D systems anticipated to be in system’s operating environment, – Assess the capability to meet or exceed the requirements • Assessment: Identify/update risks and develop tactics, techniques, and procedures (TTPs) to mitigate operational issues. SSRA Components Overview Operational Joint Services Guide
- 27. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • JCIDS Documents – ICD, CDD, CPD, ISP, CONOPs – Systems description information • Facilities Requirements Documents (if applicable) – May Provide EME • Discussion with Program/Engineering personnel on impact to operations of identified EM issues • Consider impact of identified regulatory issues – Operational impact if you can't radiate or have no approved HNC/ESC Data Requirements & Sources
- 28. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • Understand the intent; not a CONOPs or simply a description of how the system operates – What other systems will/are operating in the same physical/spectral space? – Will geospatial separation be required for frequency use management for simultaneous operation with other systems? • EX: Simultaneous employment of UAVs using common control frequency band • EX: Flying an aircraft with a new 225-400 MHz transmitter which plans to utilize four 5 MHz wide sub-bands within the 225-400 MHz band - what will be the impact to operation of existing 225-400 MHz users? Lessons Learned
- 29. UNCLASSIFIED UNCLASSIFIED • Determine the potential for EMC and EMI interactions between the proposed system, other systems, and its anticipated operational EME. • Quantify the potential EMI between the candidate system and S-D systems used by other DoD units in the operational environment. • Determine the effect on overall system performance as a result of any EM interaction. • Perform additional E3 analyses (e.g. EMV, EMP, HERP, HERF, HERO, lightning, etc) as required by the MILDEP SMO. • Assessment: Identify/update spectrum risks and recommend mitigation techniques of E3 issues. SSRA Components – E3 Assessment Note: Not specifically called out in 4650 Joint Services Guide
- 30. UNCLASSIFIED UNCLASSIFIED • E3 Requirements – Program Office • E3 Test Data – Program Office – EMI Test Plans/Reports – EMC Test Plans/Report • Other E3 Analyses • MIL-HDBK-237 Data Requirements & Sources
- 31. UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED UNCLASSIFIED • Overlap between Regulatory, Technical, and Operational Components and the E3 Assessment • See MIL-HDBK-237 for E3 Assessment Guidance Lessons Learned
- 32. UNCLASSIFIED UNCLASSIFIED Risk Management 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% Sample Likelihood of Risk Occurrence Matrix Common method used to depict the likelihood of occurrence LikelihoodofOccurrence 5 4 3 2 1 Joint Services Guide Impacts of Potential Risks
- 33. UNCLASSIFIED UNCLASSIFIED Regulatory Component Risk Categories Examples • 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 Y • Requires minimal actions for ESC, i.e. Note-to-Holder or updated certification request • Minimum spectrum issues are known to exist for this equipment • 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. • No certification or approved J/F-12 in the Military Communications Electronics Board (MCEB) archived database • 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. • Approved J/F-12 exists in the MCEB archived database (minimum Stage 2 for MS B) G • Requires no actions for spectrum support • No SS issues are known to exist for this equipment in the intended operational area • High likelihood of receiving HN spectrum support to operate with few, or a minimum number of, possible spectrum or operational restrictions. Y R G
- 34. UNCLASSIFIED UNCLASSIFIED Technical Component Risk Categories Examples • Potential link degradation and blockage due to atmospheric conditions or terrain and building obstructions • System’ will affect other S-D system operating cofrequency or adjacent frequency • Correctable received interference level between the system and other spectrum-dependent systems • Correctable operational degradation as a function of the level of received environmental and co-site interference. • Correctable intra-platform EMC among co-sited platform emitters • Candidate technologies not fully developed • Initial EMC analyses indicate adverse electromagnetic interactions • Systems non compliant with U.S. or international spectrum standards • Unacceptable received interference level between the system and other spectrum-dependent systems • Unacceptable operational degradation as a function of the level of received environmental and co- site interference. • Unacceptable intra-platform EMC among co-sited platform emitters • Robust technologies; successfully deployed already • EMC analyses indicate no adverse electromagnetic interactions • Systems fully compliant with U.S. or international spectrum standards • No received interference level between the system and other spectrum-dependent systems • No operational degradation as a function of the level of received environmental and co-site interference. • No intra-platform EMC among co-sited platform emitters Y R G
- 35. UNCLASSIFIED UNCLASSIFIED Operational Component Risk Categories Examples • System is operating in properly allocated frequency spectrum and ESC can be anticipated • Expected interference as part of the DoD response to conventional and non-conventional missions is well understood and mitigation plans are in place. • Operating in the incorrect or non-allocated frequency band or significant SS issues are known to exist for this system/equipment • system experiences or causes interference as part of the DoD response to conventional and non- conventional missions. • Unacceptable frequency-distance separation requirements between a transmitter and a receiver that must be maintained to achieve compatibility. • The number of anticipated SDE being deployed by US/Coalition forces in close proximity cannot be satisfied from the spectral resources forcing sharing or scheduleing of operations which could adversly affect operations. • Requires no additional actions for spectrum support • Frequency-distance separation requirements between a transmitter and a receiver are acceptable to achieve compatibility. • System does not experience or cause interference as part of the DoD response to conventional and non-conventional missions. Y R G
- 36. UNCLASSIFIED UNCLASSIFIED E3 Assessment Risk Categories Examples • E3/EMC studies funded/planned or completed with mitigation measures identified that will not adversely impact operations • The mechanisms of any unacceptable level of EMC and EMI interactions determined, via test or analysis, between the proposed system, other systems, and its anticipated operational EME are well understood and corrective actions planned. • 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 • Unacceptable level of EMC and EMI interactions determined via, test or analysis, between the proposed system, other systems, and its anticipated operational EME. • Unacceptable results of additional E3 analyses (e.g. EMV, EMP, HERP, HERF, HERO, lightning, etc). • E3/EMC studies completed and compatible operations confirmed or acceptable mitigation measures identified that will not impact operations • No unacceptable level of EMC and EMI interactions determined, via test or analysis, between the proposed system, other systems, and its anticipated operational EME. Y R G
- 37. UNCLASSIFIED UNCLASSIFIED Data Item Description (DID) DI-EMCS-81543 “SPECTRUM SUPPORTABILITY RISK ASSESSMENT (SSRA)” CONTACT MILDEP SMO FOR GUIDANCE SSRA Report Format
- 38. UNCLASSIFIED UNCLASSIFIED • Front Cover • Introduction • Executive Summary • Regulatory Component of SSRA • Technical Component of SSRA • Operational Component of SSRA • E3 Assessment for SSRA • Conclusions • Recommendations • References SSRA Report Format Joint Guidance Document Sept 2012
- 39. UNCLASSIFIED UNCLASSIFIED •SSRA Supporting Document/Report, • SSRA Executive Summary of the SSRA Supporting Document/ Report approved by the PM/MATDEV and submitted to the MILDEP SMO, • Cover or Transmittal letter, signed by the PM/MATDEV, and used to transmit the SSRA Executive Summary to the MILDEP SMO, requesting a Spectrum Supportability Determination. SSRA Documentation
- 40. UNCLASSIFIED UNCLASSIFIED 1. Front Cover – Title of the document – Month and year of publication – Acquisition milestone or readiness review it supports & date – Name(s) of the principal author(s) – Program office or sponsor’s name and address – Distribution statements, as required, and – Security classification markings, as required SSRA Report Format (Cont)
- 41. UNCLASSIFIED UNCLASSIFIED 1/15/2016 Signature Page Issues: • Who Signs? • In What Order? • Can Contractors?
- 43. UNCLASSIFIED UNCLASSIFIED 2. Introduction – A description of the purpose of the report and programmatic decision and/or readiness review it supports. – A detailed system description including the following: • Physical components (vehicle or platform mounted, stand alone, etc.) • Materiel readiness level (MRL), where applicable • Purpose of system and concept of operations • Subsystem description and block diagrams SSRA Report Format (Cont) Legend: MRL = materiel readiness level VM = vehicle mounted SA = stand alone PM = personnel mounted Table A-I System Description (SAMPLE) System Component MRL (where applicable) System Description (SA, VM, pm, other (specify)) #1 #2 etc Army Only
- 44. UNCLASSIFIED UNCLASSIFIED 1/15/2016 • Could have a lot more System Description, but don’t go overboard!
- 45. UNCLASSIFIED UNCLASSIFIED 1/15/2016 49 • Tables and pictures are always helpful
- 46. UNCLASSIFIED UNCLASSIFIED 3. Executive Summary – Cover Page – Introduction – Summary of Spectrum and E3 Issues SSRA Report Format (Cont) Table A-II Summary of Spectrum and E3 Issues (SAMPLE) Issue Likelihood of Occurrence (See Table IV) Impact of Risk (See Table III) Regulatory issue # 1 - ESC status Regulatory issue #.2 - HNC status Technical spectrum issue Operational spectrum issues E3 issues NONE/MINIMAL MODERATE SIGNIFICANT/SEVERE RECOMMENDED MITIGATION MEASURES: Regulatory issue #1 (ESC status): Regulatory issue #2: (HNC status): :Technical spectrum issue: Operational spectrum issue: E3 issues Insert colors, as applicable
- 47. UNCLASSIFIED UNCLASSIFIED Click to edit Master title style 1/15/2016 Spectrum Supportability Risk Assessment for the Battle Force Tactical Network (BFTN) • Too much Acquisition Status and summary (IMHO) • Not focused on the Spectrum and/or EMI issues and mitigation
- 48. UNCLASSIFIED UNCLASSIFIED Click to edit Master title style 1/15/2016 Spectrum Supportability Risk Assessment for the Battle Force Tactical Network (BFTN) • EMC and EMV “well documented”, but no mention whether its good or bad! • Content is a bit thin Executive Summary (Cont)
- 49. UNCLASSIFIED UNCLASSIFIED 4. Regulatory Components Include results of tasks described earlier (suggested summary table) SSRA Report Format (Cont) Table A-III Summary of Regulatory Information (SAMPLE)(1) Nomenclature J/F 12 # Stage/Status(2)(3) US&P(4) OCONUS(5) NOTES: (1) For a FoS or SoS, include all S-D systems that are or will be integrated into the FoS or SoS. (2) Provide the Stage as 1, 2, 3, or 4; indicate status as Approved, (with date) or In-Process (at Equipment Spectrum Guidance Permanent Working Group awaiting MCEB guidance, etc). (3) For a FoS or SoS, include, as a note, the acquisition program under which the S-D system is being procured and POC information. (4) Provide a YES/NO or Probability (High, Medium, Low) of obtaining necessary frequencies for non- degraded operation. Provide MCEB guidance, operating conditions and/or restrictions. Include in table as notes. (5) Provide a YES/NO or Probability (High, Medium, Low) of obtaining necessary frequencies for non- degraded operation regarding OCONUS, HN approval status. Provide expanded status (which CCMDs have it) and guidance where the system or similar system has HN approval. Identify countries and the guidance, or restrictions. Information may be obtained from the MILDEP SMO as a result of the ESC/HNC processes.
- 51. UNCLASSIFIED UNCLASSIFIED • Essentially a listing of whether or not the system has an approved allocation in the countries in which it must operate • Hard to quantify the mitigation, ie, whether coordination will be done in time for operations
- 52. UNCLASSIFIED UNCLASSIFIED 5. Technical Component Describe technical parameters of system (suggested summary table) SSRA Report Format (Cont) Table A-VI System Spectrum Requirements vs. Availability (1)(2)(3)(4)(5) (SAMPLE) System Nomenclature and/or J/F 12# Freq Range Throughput Required/ Available BW/Required Available Power Output Antenna Gain Factor NOTES: (1) Availability may be a known quantity or an estimated quantity based on previous operation of the same or similar systems performing the same type or similar functions. (2) Where table input may require lengthy or long explanation, use Note and include the information following the table as a note. (3) For a FoS or SoS, include all S-D systems that are, or will be, integrated into the FoS or SoS. (4) Cite source document for requirement. (5) Cite security classification of data, where applicable.
- 54. UNCLASSIFIED UNCLASSIFIED . Operational Component – Include a statement of the program requirements, how they are being met, and a description of the intended operational deployment of the system (see suggested table format) SSRA Report Format (Cont) Table A-VII System Description and Deployment (SAMPLE) System Component Anticipated HNs MRL Deployment (SA, VM, pm, Other (specify)) Training Requirements NOTES: Legend: MRL = materiel readiness level VM = vehicle mounted SA = stand alone pm = personnel mounted HN = host nation Include results of tasks described earlier along with a POA&M for cases of non-compliance where the likelihood of being able to perform the operational mission is at risk.
- 55. UNCLASSIFIED UNCLASSIFIED 6. Operational Component (continued) – Identify and quantify system’s ability to perform satisfactorily in operational environment • Propagation considerations (jungle, urban, desert, at sea, space, etc.) • Kind and quality of data/information transmitted • Desired/required ranges • Operational scenarios considered – Include a POA&M for resolving non-compliance and risk if unable to perform operational missions because of: • Intra-system EMC • Inter-system EMC – Describe the mitigation measures and impact if: • Spectrum is unavailable • System is unavailable SSRA Report Format (Cont)
- 56. UNCLASSIFIED UNCLASSIFIED 7. E3 Assessment for SSRA - Include the results of the E3 tasks described earlier along with recommendations for mitigation of the E3 risks SSRA Report Format (Cont) Table A-VIII Summary of E3 Issues Issue Green/ Yellow / Red (see Risk Categories in Table V) E3 Issue #1 E3 Issue #2 E3 Issue #3, etc NOTES: Insert colors, as applicable
- 57. UNCLASSIFIED UNCLASSIFIED Click to edit Master title style 1/15/2016
- 58. UNCLASSIFIED UNCLASSIFIED Problem: Doesn’t describe mitigation measures!
- 59. UNCLASSIFIED UNCLASSIFIED 8. Conclusions – Include a summary of risks, impact or potential degradation to – System’s operational requirements and mitigation measures SSRA Report Format (Cont) Table A-II Summary of Spectrum and E3 Issues (SAMPLE) Issue Likelihood of Occurrence (See Table IV) Impact of Risk (See Table III) Regulatory issue # 1 - ESC status Regulatory issue #.2 - HNC status Technical spectrum issue Operational spectrum issues E3 issues NONE/MINIMAL MODERATE SIGNIFICANT/SEVERE RECOMMENDED MITIGATION MEASURES: Regulatory issue #1 (ESC status): Regulatory issue #2: (HNC status): :Technical spectrum issue: Operational spectrum issue: E3 issues Insert colors, as applicable
- 62. UNCLASSIFIED UNCLASSIFIED 9. Recommendations - Provide recommendation as to whether the SSRA should be forwarded by the MILDEP SMO to their Service CIO for approval and forwarded to the MDA. 10. References - Copies of DD Form 1494 or information page for each S-D item in system/platform - Copies of E3 Assessment Reports, when requested. - Source documents for performance requirements - DoDI 4650.01 (latest version) - DoDD 3222.3 (latest version) - MILDEP Spectrum and E3 policy regulations SSRA Report Format (Cont)
- 63. UNCLASSIFIED UNCLASSIFIED • The SSRA Will Do, Provides: – A formally documented SS risk assessment, with mitigation measure(s) identified, to achieve a SS Determination from the FMO, CIO/G6, or OSD(NII) (depending on ACAT and/or level of Interest) – Details of the following, for each piece of S-D system: • J/F 12’s • Status of HN Coordination • Provide/discuss known SS and E3 issues and assigns RISK • Discuss potential operational impact of known SS and E3 deficiencies • Provide program risk (R/Y/G) for each system, a risk summary, and mitigation plans to reduce or eliminate YELLOW and RED issues • Provide an overall, Program assessment for acquisition Milestones Summary
- 64. UNCLASSIFIED UNCLASSIFIED • What the SSRA will not do: – Not a substitute for the ESC process; the SSRA is separate from the ESC process and the resulting MCEB issuance of a J/F 12. – May not provide detailed E3 assessments but it will identify what EMC/EMI assessments are planned and/or have been conducted, identify risks, and the status of mitigation plans. Summary (Cont)
- 65. UNCLASSIFIED UNCLASSIFIED • ARMY Joe Reza (915) 593-6881 jose.reza@usaec.army.mil • NAVY/CNO Mark Johnson (703) 601-1414 david.m.johnson4@navy.mil • NAVAIR Mike Squires (301) 342-1660 mike.squires@navy.mil • NAVSEA Doug Knapman (202) 781-2049 douglas.knapman@navy.mill • SPAWAR PACIFIC Dave Hilton (619) 553-2666 david.r.hilton@navy.mil ATLANTIC Wayne Lutzen (843) 218-5723 wayne.lutzen@navy.mil Points of Contact • JSC Training: Matt Grenis (410) 293-9264 matthew.z.grenis.civ@mail.mil Brian Farmer (703) 864-7023 bfarmer@emcmanagement.com • AIR FORCE Pabon Soto USAF AFMC AFLCMC/EZAC jose.pabon_soto.1@us.af.mil • AFSMO Colonel David Bosko (301) 225-3743 afsmo.cc@workflow.us.af.mil • ASMO Richard DeSalvo (301) 225-3763 richard.desalvo@disa.mil • NMSC Tom Downie (703) 325-2750 tom.downie@navy.mil
- 66. UNCLASSIFIED UNCLASSIFIED https://acc.dau.mil/ The Acquisition Community Connection (ACC) https://acc.dau.mil/e3
- 67. UNCLASSIFIED UNCLASSIFIED Sign up and be part of the Spectrum and E3 Compliance Community! Within the various Spectrum and E3 Compliance SIA web pages, you will find a variety of information on requirements, guidance, organizations, etc. associated with the proper consideration of E3 and spectrum management considerations for weapon systems and other DoD equipment in the acquisition cycle. If you are not presently a Spectrum and E3 SIA member, please feel free to sign-up! “Spectrum & E3 Compliance” home page: acc.dau.mil/e3 or acc.dau.mil/spectrum Spectrum & E3 Training: acc.dau.mil/learn JSC Spectrum & E3 Document Library: acc.dau.mil/library Lessons Learned acc.dau.mil/LessonsLearned
Editor's Notes
- This lesson will present information about SSRA purpose and scope, policy and guidance, defining and classifying risk, and SSRA entry points into the DAS process required for S-D equipment and systems. An SSRA is an assessment performed by PMs and MATDEVs of any program that is acquiring or incorporating S-D systems or equipment. The purpose is to identify and assess an acquisition’s potential to affect the required performance of the newly acquired system or other existing systems within the operational EME. As risks to SS and E3 are identified, the MILDEP SMO is provided with planned steps to mitigate the risks. PM/MATDEVs should consult, as early as possible, with their respective MILDEP SMO regarding the application and tailoring of the SSRA.
- The following references address SSRA requirements: DoD Instruction 4650.01, Policy and Procedures for Management and Use of the Electromagnetic Spectrum DoDI 5000.02 Table 2 DI-EMCS-81543, SPECTRUM SUPPORTABILITY RISK ASSESSMENT (SSRA) Joint Services Guide For Development Of A Spectrum Supportability Risk Assessment (SSRA)
- 5
- Spectrum supportability and E3 risks and the steps that must be taken to mitigate these risks are identified in the SSRA Report and provided to the MILDEP SMO who will review the SSRA and forward their recommendations to the Service CIO for approval. The actual approval process depends on service policies dictated primarily by program size. A statement on the SS of an acquisition is then forwarded to the MDA. PM/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, including: All portions of the SSRA are completed using the most current information and updated at each submission in the DAS. The amount and type of information available will be determined by what required studies/analysis have been accomplished and where it has entered the Acquisition Process. When preparing the SSRA, be sure to identify risks and recommend mitigation strategies for ALL testing and fielding frequencies.
- There are a wide variety of E3 and spectrum supportability actions that must be addressed throughout the acquisition cycle of any system developed by the DoD. This chart provides a general overview of many of those task. Note that this is an generic example, idealized to show actions through all milestones and phases. Individual programs will vary based on where they enter the acquisition system and specific program requirements and priorities. ACAT Level determines CIO approval (or below)
- 8
- 9
- 10
- 11
- 12
- AR 5-12 is the reference document/regulation. 2013 is current version. We updated much of the SSRA input and next publication is expected for publication in next 30-60 days. I thought we would get it signed in the spring; delayed due to higher priority ARs like IA-Cyber. Listing the AR and suggesting to look for the 2015 update is best COA and contacting us for Army template/guide is also suggested. Prefer that you coordinate with us when you engage with any Army PMO so that we have SA and if time permits, make someone available to dial in for a training session or available to answer a question.
- 17
- SSRA requires engineering studies to ensure that each S-D system/equipment is compatible with all other S-D systems/equipment in the EME. The assessment must consider the following concerns: Does the assessment ensure that adequate spectrum is available to support system operation in DOD, Allied, and Coalition operations (assessment determines and documents adequate spectrum availability)? Are sufficient spectrum resources available to support the operational use of an S-D system/equipment? What are the potential impacts of the acquisition on other newly acquired or existing systems within EME have been identified? Have risks been assessed from regulatory, technical, and operational spectrum, and E3 perspectives to identify issues before assigning risks?
- An SSRA is composed of four components and an executive summary. The four components are the Regulatory, Technical, Electromagnetic Environment Effects (E3), and Operational components. The Regulatory component assess whether frequency management regulations are complied with and spectrum is available for operations in the host nation. The Technical/E3 components combined provide an assessment of the ability of the platform or system to operate without intersystem co-site and intrasystem intersite interference. The Operational component assesses the performance of the system in its actual operating environment. These components are combined as needed to form a single risk assessment for the applicable system or platform to meet the successive MS review requirements. The Executive Summary provides a synopsis of the overall assessment for the system/platform S-D equipment at that MS point in the acquisition review cycle. The linking of the SSRA requirement with the program MS approval process ensures that spectrum availability issues are addressed throughout the program lifecycle. The SSRA is the principle means by which the DoD determines whether sufficient spectrum is available for the S-D equipment associated with a proposed system/platform.
- So, DoDI 4650.01 doesn’t provide a lot of specific guidance so how exactly do we do an SSRA?
- 1st Submission of SSRA 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 JUONS or ICD, and the potential for technical issues, including E3, are to be assessed. 2nd Submission of SSRA 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 of E3 test requirements in the request for proposal and other acquisition documents during the Development Stage of the DAS. 3rd Submission of SSRA 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 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.
- The regulatory component of the SSRA addresses the ESC stage and status and the acquisition status relative to the radio services authorized within the TOAs of the U.S. and intended HNs; it includes an identification of ITU registrations for other space stations registered in the frequency band being sought for operation; and includes additional spectrum insights from the ESC and HNC processes of mature systems. A table format is suggested for summarizing the ESC and HNC information and results of the regulatory tasks to be included the Regulatory Component of the SSRA. ESC: Identify the ESC stage and status for all S-D systems being developed or integrated by the acquisition. HNC: Determine countries for likely operational deployment Fielding Plan JUONS, ONS, Etc. Determine internationally recognized radio service. Identify portions of tuning range supported by HN’s TOA. Determine the regulatory status (primary, secondary, etc) assigned by the HN's TOA. Obtain comments on the same/similar systems submitted for ESC and HN spectrum certification. Identify all military, civil, and non-U.S. in-band, adjacent-band and harmonically-related systems likely to be co-site or in close proximity by querying DoD or NTIA databases. Consult with the Service, SMO regarding changes to U.S., Federal, or civil telecommunication regulations impacting the system’s frequency bands. Determine if the system meets appropriate military, U.S., national, and international spectrum standards for bandwidth and transmitter characteristics. NTIA and WRC: Quantify impacts of changes to U.S. or HN spectrum regulations Assessment: Identify/update spectrum risks and recommend mitigation techniques of regulatory issues.
- Recommended primary data sources for the Regulatory component are listed in the slide. Regulatory data comes from the available J/F-12s (SPS/MCEB comments), HNSWDO (like system data and metrics) and the NTIA Redbook (frequency allocations and services etc. For example, the data for the Regulatory component analysis are ITU Tables that come from the NTIA manual, international comments on US military systems come from HNSWDO, freq assignment data comes from JSC databases, US mil system data comes from the SCS, etc.
- - Though this area seem to be perceived as a difficult part by the preparers of SSRAs it is in reality probably the easiest. The difficulties come into play when programs intentionally try to use portions of the spectrum that are not allocated for the radio service the program plans on using it for. - It appears that program people do not know where to look to check for regulatory compliance. Some seem to feel that as long as they are doing DD1494 (J/F-12 certification) actions they are meeting all regulatory requirements. They need to check frequency allocation tables, preferably in their earliest system design phase, to ensure they are targeting a band that is properly allocated for the radio service their device will operate in. They also need to know to do this looking at not just the US allocations but for all three ITU regions and it is advisable that they go to www.efis.dk if they are going to operate in Europe. This site is the best site to check individual national allocation tables for all ERO member nations. They can also spend a little time checking for other allocation tables for nations in other parts of the world.
- The Technical Component of the SSRA should contain a description of the technical parameters of system’s components (e.g. receivers, transmitters, antennas) and include the results of technical tasks previously presented in this lesson. A table format is the suggested format for presenting this information in an SSRA. The Technical component of the SSRA focuses on candidate technologies and available technical parameters, such as system type, platform type, bandwidth requirements, etc, to generate initial quantification of potential mutual interactions. For example, if sufficient data is available, an analysis may determine frequency-distance (F-D) relationships required to preclude EMI based on generic interference-to-noise (I/N) ratios and potential interactions that will require further study. Use of M&S tools is appropriate. As technologies mature and technical parameters are defined, potential mutual interactions can be better determined. The detailed analysis can use measured minimum carrier-to-interference ratios to determine F-D relationships to preclude EMI. Specific capabilities, such as automatic power control, which may affect the F-D curves, should be included.
- The Operational component of the SSRA should contain a statement of the program requirements, how they are being met, and a description of the intended operational deployment of the system. It should also include the results of the Operational tasks presented in this lesson along with a POA&M for cases of non-compliance where the likelihood of being able to perform the operational mission is at risk. The suggested format for presenting this information is a table format. The operational performance requirements should be met for conventional and non-conventional (i.e. disaster relief) missions. From an EMC analysis (modeling and simulation (M&S) tools available), Quantify the potential EMI between the candidate system and the S-D systems used by other DoD units in the operational environment, Express the results in operational terms, e.g., the frequency-distance (FD) separation requirements between a transmitter and a receiver that must be maintained to achieve EMC. Refine the analysis, M&S, as the acquisition progresses through the DAS.
- The E3 assessment for the SSRA should include the results of the E3 tasks outlined in the Joint Guidance Document along with recommendations for mitigation of the E3 risks. A table or stop-light chart similar to that shown herein may be used to illustrate/ summarize results of the risk assessment using standard DoD risk logic. Quantify intra-platform EMI among co-sited emitters and receivers for complex SoS or platforms in terms of the possibility and influence of: Inter-modulation Transmitter Harmonic Interference Transmitter Spurious Output Interference Transmitter Noise Interference Receiver Desensitization Interference Using tests or M&S tools, refine the E3 analysis; quantify the mutual EMI between the candidate system and S-D systems used by other DoD units in the operational environment. Identify/update E3 risks and develop recommendations for mitigation of risks.
- 36
- 37
- 38
- 39
- 40
- The following guidance (suggested form, format, and content) is provided for the 3 Services: For the Army: There are three levels of documentation: SSRA Supporting Document/Report, SSRA Executive Summary of the SSRA Supporting Document/Report approved by the PM/MATDEV and submitted to the MILDEP SMO, Cover or Transmittal letter, signed by the PM/MATDEV, and used to transmit the SSRA Executive Summary to the MILDEP SMO, requesting a Spectrum Supportability Determination. For the Navy: Compile a single SSRA Report containing all supporting SSRA components (regulatory, technical, operational, and E3) along with an Executive Summary. This product will be referred to as the SSRA and will be submitted for approval within the Department of the Navy under cover letter signed by the PM. For the Air Force: Compile a single SSRA Report containing all supporting SSRA components (regulatory, technical, operational, and E3) along with an Executive Summary. The SSRA during the lifecycle of the S-D system may require tailoring to address issues from the MDA in making the determination for that particular milestone or phase of acquisition.
- Executive Summary The Executive Summary, which is meant to be an abridged version of the SSRA Report, should contain the following: A cover page (see A.1 above); however, the name and logo should apply to the PM/MATDEV required to submit the SSRA. Introduction (see A.2 above). A summary of spectrum and E3 issues. This should be a summation of A.4 through A.7, which follows below, the summarized conclusions should be here and presented in a Stop-Light chart format. The impact of the risks on the ability to obtain SS including a brief summarization of the important aspects from the Conclusions section. The summarized conclusions should be here and presented in a Stop-Light chart format . Recommendation: If all risks can be mitigated, the suggested recommendation should read as follows: “The (insert PM/MATDEV) recommends that the (insert Program name) receive a Spectrum Supportability Determination to support (insert review).
- The Regulatory component of the SSRA should include the results of the regulatory tasks outlined in paragraph 2.1 and Table II of this the Joint Guidance document. A suggested table format for summarizing the ESC and HNC information is shown in Table A-III. This information is relatively easy to find by engaging the appropriate service Spectrum management Office.
- The Technical component of the SSRA shall also include the following: (1) A list of other U.S. military, U.S. civil, and non-U.S. in-band and adjacent-band and harmonically-related systems likely to be co-site or in close proximity. (2) The undesired interactions of S-D systems expected to be in the candidate’s operational environment including plans to address non-compliant systems. (3) The expected system performance and effect on other S-D systems that may operate co-frequency or adjacent frequency expected to be found in the intended operational environment. (4) The acceptable received EM levels between the subject system and other S-D systems to ensure neither is significantly degraded and that coexistence is feasible. (5) Potential link degradation and blockage due to atmospheric conditions or terrain and building obstructions within intended deployments areas. (Note: The overall system performance includes link availability, with and without EMI, while taking into account the effects of the environment (e.g. considering path loss, rain attenuation, humidity, climate, temperature, and water/oxygen absorption)). For non-communications systems (e.g. radar, passive sensors, etc.), the operational degradation shall be presented as a function of the level of received environmental and co-site EMI. (6) Recommendations to mitigate potential technical issues (e.g. implementation of channelization plans, advanced narrow-beam antennas, (active, spot and contoured-beam, etc.), as well as passive radio frequency components (filters, diplexers, couplers, etc.). (7) Identification and quantification of interactions with non-DoD, other Federal and commercial users in the environment. (8) Identification of spectrum risks and recommendations for mitigating issues. (9) Address how limitations or restrictions identified in the MCEB J/F-12 recommendations are being mitigated and/or resolved for each S-D equipment
- The Operational component shall also include the following where the likelihood of being able to perform the operational mission is at risk: (1) The operational performance requirements, as specified in the acquisition documents (e.g. initial capabilities document, capability development document, capability production document, or ISP) or operational needs statements and whether the requirements will be met or exceeded. (2) A list of the expected complement of S-D systems (DoD, non-DoD, Federal and commercial) anticipated to be in the system’s operating environment. (3) Quantification in operational terms (e.g. frequency-distance separation between transmitter and receiver that must be maintained to achieve EMC) of the performance of the candidate system and other S-D systems used by other DoD units in the operational environment. (4) Operational spectrum risks and recommendations, including tactics, techniques, and procedures for mitigation of operational risks.
- The E3 component of the SSRA shall include the following along with recommendations for mitigation of the E3 risks. a. Identification of EMC and EMI interactions between the candidate system, other systems, and its anticipated operational EME including the possible effect on overall system operational performance as a result of any EM interaction. b. Quantification of intra-platform EMI among co-site emitters and receivers for complex SoS and platforms in terms of the possibility and influence of: (1) Inter-modulation (2) Transmitter Harmonic Interference (3) Transmitter Spurious Output Interference (4) Transmitter Noise Interference (5) Receiver Desensitization Interference c. Quantification of the mutual EMI between the candidate system and S-D systems used by other DoD units in the operational environment. d. Quantification of potential E3 (including hazards of electromagnetic radiation to personnel (HERP), volatile materials (HERF), and ordnance (HERO), electromagnetic pulse (EMP), lightning, electrostatic discharge (ESD), etc) as may be contractually required by the MILDEP SMO or E3 authority.
- The conclusion shall contain a summary of the spectrum and E3 risks identified and the impact on SS and potential degradation to the system’s operational performance. The results may be summarized in a table or stop light chart (see Table VI). The conclusion shall also indicate whether the system meets all user requirements.
- Considering that all spectrum and E3 risks with potential to affect the required performance of the system or other systems within the operational EME, and that their associated mitigation measures have been identified, indicate whether the SSRA should be forwarded by the MILDEP SMO to their Service CIO for approval and forwarded to the MDA. References Provide at least the DoD Information page or DD Form 1494 for each S-D system, subsystem, or equipment that is, or will be, integrated within a platform, FoS, or SoS. Copies of E3 Assessment Reports, when requested. DoDI 4650.01 (latest version) DoDD 3222.3 (latest version) MILDEP Spectrum and E3 policy regulations Source documents for performance requirements
- Feel free to contact us!
- ACC stands for Acquisition Community Connection. The ACC is an electronic, interactive forum where the AT&L workforce meets to share knowledge, lessons learned, and best practices. The ACC supports the AT&L workforce by providing a collection of collaborative spaces including: Communities of Practice (CoPs) Special Interest Areas (SIAs) Collaborative Workspaces Each of the many CoPs, SIAs, and workspaces is dedicated to a specific DoD acquisition topic, such as contracting, program management, risk management, etc.
- Spectrum and E3 Compliance SIA on the ACC DAU Compliance with SS requirements and control of E3 can be critical performance parameters for platforms, systems, and equipment acquired by the DoD. If these technical areas are not given the proper level of attention during the acquisition process, fielded systems will suffer from some level of operational degradation up to, and including, catastrophic failures or unacceptable operating restrictions. Within the various Spectrum and E3 Compliance SIA web pages, you will find a variety of information on requirements, guidance, organizations, etc. associated with the proper consideration of E3 and spectrum management considerations for weapon systems and other DoD equipment in the acquisition cycle. If you are not presently a Spectrum and E3 SIA member, please feel free to sign-up! The DAU Spectrum and E3 SIA are located at: https://acc.dau.mil/e3 or https://acc.dau.mil/spectrum. In addition, the DAU JSC E3 Training and class descriptions and JSC E3 document library can be found at https://acc.dau.mil/learn and https://acc.dau.mil/library, respectively.