nossainst_8020_22.pdf

NOSSA INSTRUCTION 8020.22

From: Commanding Officer, Naval Ordnance Safety and Security Activity

Subj: EXPLOSIVES SAFETY SITE APPROVAL DOCUMENTATION

REQUIREMENTS, SUBMITTAL, REVIEW, APPROVAL, AND OVERSIGHT (U)

Ref: (a) OPNAVINST 8020.14/Marine Corps Order P8020.11

(b) NAVSEA OP 5, Volume 1, Seventh Revision

Encl: (1) Guide for Preparing an Explosives Safety Site

Approval Request

(2) Site Plan Evaluation Form and Guidelines

(3) Reserved (planned for later revision of instruction)

(4) Glossary of Terms

(5) Table of Contents

1. Purpose. To assign responsibilities and establish minimum procedures for: submitting an explosives safety site approval request (ESAR); maintaining Activity-level explosives safety site approval (ESA) administrative records; and monitoring deviations and compensatory measures involving an ESA, to facilitate the Naval Ordnance Safety and Security Activity’s (NOSSA) effective review, oversight, and verification of ESAs.

In accordance with references (a) and (b), this instruction is applicable to Navy and Marine Corps Activities/Installations as defined in reference (b), paragraph 8-1.2.1.

2. Cancellation. This is a new instruction. It augments and updates the requirements in reference (b) and NAVFACINST

11010.45 for the preparation and submittal of ESARs to NOSSA for review and approval. Where this instruction and NAVFACINST

11010.45 conflict in regard to minimum requirements, this instruction takes precedence. Activities generating and reviewing ESARs should refer to their chain of command instructions for additional requirements. Additional requirements may include, but are not limited to, Naval Facilities Engineering Command (NAVFAC) Business Management System (BMS) B-2.1.8 Site Approval-Explosives Safety; Marine Corps Order (MCO) P8020.10B; and applicable Navy Regional instructions.

NOSSAINST 8020.22

3. Background. Historically, the ESA process has been a partnership between the Navy/Marine Corps Activity/Installation;

Commander, NAVFAC; Commander, Marine Corps Systems Command (MARCORSYSCOM); NOSSA; and the Chief of Naval Operations (CNO).

The requirements for an ESAR are specified in reference (b).

4. Roles and Responsibilities. This section outlines the roles and responsibilities for the generation, review, approval, and oversight of ESAs.

a. Shore (Host) Activity/Command. The Commanding Officer (CO) of a Navy or Marine Corps Shore (Host) Activity/Command is responsible for explosives safety at that Activity/Command. The CO may delegate authority to the lowest level of competence commensurate with the subordinate’s assigned responsibilities, in accordance with reference (b), paragraph 1-4.3.2. The CO is responsible for ensuring an ESA is obtained for new construction; modification of existing structures; or change of function that involves explosives safety quantity distance (ESQD) arcs or explosives safety criteria, prior to beginning construction or conducting explosives operations. At a minimum, the following reviews and approvals are required at the Shore (Host) Activity/Command-level, as well as the following ongoing oversight actions, after an ESA is granted.

(1) The Shore (Host) Activity/Command CO shall:

(a) Provide approval of the ESAR package via a CO-to-CO NOSSA letter, or assign written by-direction signature authority to the Public Works Officer (PWO) for review and approval of ESARs within WebSAR, the Department of the Navy’s (DON) web-based automated site submission module. If the ESAR is approved at the PWO level, via WebSAR, then a serialized transmittal letter on Shore (Host) Activity/Command letterhead is not required by NOSSA. However, Navy Region or Marine Corps chain of command may require Shore (Host) Activity/Command approval letter or transmittal letter.

(b) Accept the risk of loss, via a CO-to-CO NOSSA letter, of facilities and/or assets, in the case of accidental detonation, in the following instances: [Note this authority cannot be delegated to the PWO.]

1. Explosives operating facilities sited without lightning protection.

2. Facilities/assets sited as single potential explosion site (PES) at less than intermagazine distance (IMD) (K11) separation, such as loaded combat aircraft at a Combat Aircraft Loading Area (CALA).

(c) At Marine Corps Activities, ensure that a planner is assigned to support the development of any ESARs consistent with the duties defined in 4.c.(1) of this instruction.

(2) The Shore (Host) Activity/Command PWO shall:

(a) Assign a planner to the Site Approval Development Team (SADT) (see 4.a.(4) for role of the SADT).

(b) Provide Activity-level ESAR review and approval in WebSAR. All ESARs must be signed/approved by the PWO (or Assistant/Deputy PWO), if delegated signature authority by the Shore (Host) Activity/Command CO. If the PWO does not have by-direction signature authority from the Shore (Host) Activity/Command CO, then a Command approval letter, signed by the Shore (Host) Activity/Command CO, must be included in the ESAR package. PWO approval and signature for the ESAR signifies the following conditions have been met:

1. The project has been approved by the Shore (Host) Activity/Command CO and any required Regional planning boards.

2. All maps are accurate and up-to-date, with current existing field conditions validated by a site visit, and generated using the Navy’s GeoReadiness or Marine Corps’ GeoFidelis geographic information system (GIS) (i.e., enterprise mapping system), and meet the requirements listed in enclosure (1).

3. Building functions described in the ESAR are consistent with the real property inventory, internet Naval Facilities Assets Data Store (iNFADS).

4. All applicable existing land-use restrictions, such as ESQD arcs, Hazards of Electromagnetic

Radiation to Ordnance (HERO) zones, air field safety zones, and munitions response program sites are noted in the ESAR.

(c) Have in place a written process to monitor the design and construction phases of the project as follows:

1. Ensure construction does not begin until the ESA has been received from NOSSA.

2. Ensure all personnel who monitor the design and construction phases of the project, or make decisions in regards to change-orders or de-scoping, have been familiarized with the requirements of the ESA and specific aspects of the project that involve explosives safety criteria.

3. Ensure construction is completed per conditions of the ESA. Any changes to the project, that affect ESQD or explosives safety criteria, require re-submittal of the ESAR, via the chain of approval for NOSSA/Department of Defense Explosives Safety Board (DDESB), depending on the extent of the changes to the project.

(d) After turnover of the facility to the user, provide the following continued ongoing oversight:

1. Ensure facility and associated ESQD arc data is maintained in the Navy or Marine Corps GIS/enterprise mapping system.

2. Ensure that new construction, modifications of existing structures, or changes of function within 110% of the inhabited building distance (IBD) of the sited facility, is not approved without first obtaining an ESA.

3. Ensure that new construction or modification of facility components covered by explosives safety criteria, such as barricades, substantial dividing walls, protective construction (including windows, doors, and other hardened building components), and electrical/grounding/bonding/ lightning protection systems (LPS), is not implemented without first obtaining an ESA.

(e) By 1 October 2011, have a documented process in place to evaluate repair, maintenance, and construction work performed within 110% of the IBD of any PES, to determine if an ESAR is required, per reference (b), paragraphs 8-1.2.1. and

8-1.2.2. The Shore (Host) Activity Explosives Safety Officer (ESO) shall make the final Activity-level decision whether an ESAR is required. The ESO may allow for Public Works Department (PWD)-level determination of whether an ESAR is required, through the use of enterprise geospatial data from the GIS/enterprise mapping system and checklists, provided ESO oversight of the process is maintained. A permanent record of the evaluation will be maintained by the Activity.

(3) The Shore (Host) Activity/Command ESO shall:

(a) Provide explosives safety oversight. For the purpose of this instruction, the ESO is the ESO designated in writing to support the Shore (Host) Activity/Command. Per reference (b), paragraph 1-4.4.1., an ESO must be designated in writing by all Shore (Host) Activity/Command and Operational (generally Tenant) Activity/Command COs whose missions directly involve or support ammunition and/or explosives operations. This designation may be accomplished by a memorandum, Inter-Service Support Agreement (ISSA), Memorandum of Agreement (MOA), Memorandum of Understanding (MOU), or instruction as defined in reference (b), paragraph 1-4.3.5. The ESO may belong to the Region, Operational (generally Tenant) Activity/Command, or any Department other than the Department responsible for the conduct of ordnance operations (i.e., Weapons/Ordnance, Security, etc.).

(b) Participate, as an active member, in the SADT (see 4.a.(4)) to facilitate the preparation of the ESAR.

(c) Monitor the PWD work reception process and make the final Activity-level decision on whether proposed projects within 110% of IBD require an ESA, per reference (b), paragraphs 8-1.2.1. and 8-1.2.2. The ESO may allow for PWD-level determination of whether an ESAR is required through the use of enterprise geospatial data from the GIS/enterprise mapping system and checklists, provided ESO oversight of the process is maintained. A permanent record of the evaluation will be maintained by the Activity.

(d) Provide Activity-level review and approval of ESARs. All ESARs must be signed by the ESO. ESO approval and signature on an ESAR signify the following conditions have been met:

1. Explosives operations associated with the request are described accurately, to include, but not be limited to, the following: the type of explosives operations to be conducted in the facility/area being sited, the Class/ Division(s) (C/D) and net explosives weight (NEW) of explosives to be used in the facility and nearby facilities, and any explosives operations with K18 intraline distance (ILD) arcs that encumber the construction site that must be conducted concurrent with construction, including risk-mitigation procedures.

2. Explosives limits for the surrounding PESs are accurate, and all encumbering PESs are listed in the ESAR and depicted on the ESQD map.

3. Facility/operation will meet all applicable explosives safety criteria.

4. All exposed sites (ESs) within 110% of IBD are listed in the ESAR and depicted on the ESQD map.

5. Any compensatory measures (i.e., administrative measures) used when ESQD requirements cannot be met are included in the ESAR; are agreed upon by affected Commands; will be incorporated in the appropriate Standard Operating Procedures (SOPs); and will be noted in the Activity’s Explosives Safety Information System (ESIS) database.

6. All existing deviations (Waivers, Exemptions, or Secretarial Certifications) affecting, or affected by, the ESAR are listed in the request.

(e) After the ESAR is approved by NOSSA, maintain a permanent administrative record of the ESA, to include:

1. Copies of all ESA packages for the Activity.

The copies may be either paper or electronic. The ESO may delegate maintenance of ESA records to the PWD or other suitable office at the Activity, providing the ESO maintains oversight and overall responsibility for the records.

2. A current copy of the Activity’s ESQD map.

At a minimum, the ESO shall review the map annually and validate all PESs are shown and ESQD arcs are accurate, and forward any required changes to NAVFAC or appropriate Public Works Department for update.

3. An explosives safety database that meets the minimum data requirements of this instruction. At a minimum, the ESO shall review the database annually, and prior to submitting an ESAR for approval.

4. All ESQD maps used for planning and decision making, including the Activity Fire map, are updated to include all changes approved in the ESA.

(f) Provide ongoing oversight to ensure that all compensatory measures and administrative controls used to meet ESQD requirements are incorporated into all applicable Activity SOPs, prior to starting explosives operations.

(g) Provide oversight for facilities, to ensure facility components covered by explosives safety criteria, such as barricades, substantial dividing walls, electrical grounding and bonding systems, and LPSs are maintained and not modified without an ESA, until the explosives limits are removed from the facility.

(4) The SADT shall:

(a) At a minimum, include the ESO, a planner from the Activity/Installation PWD, and a technical representative from the Operational (generally Tenant) Activity/Command that will be conducting the explosives operations being sited. As required, the team may also include representatives from NAVFAC components responsible for facility design. In cases where protective construction is required, a representative from the Naval Facilities Engineering Service Center (NAVFAC ESC) responsible for developing a basis-of-design for protective construction and review of protective construction design drawings may be required. For complex projects involving facilities or operations that cannot meet ESQD and involve determination of a reduced maximum credible event (MCE), compensatory measures, or protective construction, NOSSA shall be notified, through the Shore (Host) Activity/Command chain of command, to determine if a representative from the NOSSA Facilities Certification Branch Code N54 should be included on the SADT in an advisory role. The team will be typically led by either the planner or the ESO.

(b) Be responsible for the development of the ESAR.

(c) Review any changes to the ESAR during review, endorsement, and approval process, to assure that the operational use of the facility is not compromised by the proposed project changes.

b. Operational (generally Tenant) Activity/Command. The Operational (generally Tenant) Activity/Command is the Command(s) performing the explosives operations that result in the requirement for an ESA. The Operational (generally Tenant) Activity/Command CO is responsible for explosives safety for operations under his/her Command. The Operational (generally Tenant) Activity/Command CO may delegate authority to the lowest level of competence commensurate with the subordinate’s assigned responsibilities, in accordance with reference (b), paragraph 1- 4.3.

(1) Operational (generally Tenant) Activity/Command CO shall:

(a) Assign the appropriate technical representatives to the SADT, to define the operational requirements for the facility and/or operation being sited.

(b) Endorse any compensatory measures used to meet ESQD requirements. Endorsement of compensatory measures is the Operational (generally Tenant) Activity/Command CO’s acceptance of responsibility that the compensatory measures shall be incorporated into all applicable Command SOPs. All compensatory measures and associated SOPs shall be maintained, until a request to cancel the ESA is approved by NOSSA.

(c) Obtain the endorsement from any other Commands that must comply with the compensatory measures used to meet ESQD requirements. All Commands operating under compensatory measures to meet ESQD requirements must maintain these controls and applicable SOPs in place, until a request to cancel the ESA is approved by NOSSA.

(2) Operational (generally Tenant) Activity/Command Technical Representative shall:

(a) Participate as a member of the SADT and:

1. Provide the team developing the ESAR with the details of the proposed explosives operations and facility requirements.

2. If required under reference (b), paragraph 8-1.2.5.f., develop a hazards analysis or mishap risk assessment for proposed explosives operations.

c. NAVFAC. NAVFAC provides Activity-level and DON-wide support for planning, site approval, design, and construction.

At Marine Corps activities, Activity-level planning support may be provided by a Marine Corps planner under the command of the Shore (Host) Activity/Command CO. Where NAVFAC is the service provider, NAVFAC will determine the echelon level within NAVFAC that will provide service.

(1) During the development of an ESAR, NAVFAC shall provide Activity-level planning support, to include:

(a) Development of a comprehensive ESAR package for submittal to the ESO and PWO for Activity-level approval.

(b) Request the participation of the appropriate members of the SADT, to include, at a minimum, the ESO, and Operational Shore (Host) Activity/Command Technical Representative.

(c) Lead the SADT and facilitate team discussions.

At some Activities, the ESO may be the team leader for SADT. In situations were the ESO leads the SADT, the planner shall provide technical leadership for planning functions.

(d) Ensure ESQD maps are properly updated by field verification and discussions with the Activity ESO and the GIS Analyst.

(e) Ensure consistency with all Shore (Host) Activity/Command and Operational (generally Tenant) Activity/Command planned development.

(2) Provide engineering support, such as:

(a) Design, or facilitate the design of, any engineering controls, such as substantial dividing walls, barricades, and protective construction, such as explosion-resistant windows. Obtain endorsement from Department of Defense (DoD) design authority (NAVFAC ESC or U.S. Army Corps of Engineers (USACE), if design is not a DDESB Technical Paper 15 (TP-15)-approved design and provide design to the SADT lead for inclusion in the ESAR.

(b) Design, or facilitate the design of, fire protection systems, electrical grounding and bonding systems, and LPSs. Provide design drawings and zone-of-protection diagrams to the SADT lead for inclusion in the ESAR.

(3) Provide technical review and endorsement of ESARs submitted by Navy Activities:

(a) Provide technical review of the ESAR, using enclosure (2), independent of the package developer. The technical review shall include a review of the accuracy of the mapping, basic application of explosives safety criteria from reference (b), Chapters 5-8, and consistency with the Regional Shore Infrastructure Plan (RSIP) and other Regional and Activity-level land-use and planning guidance.

(b) Endorse the ESAR to NOSSA. Reviewer must have taken AMMO-36 within the last 5 years, demonstrated technical proficiency (as defined by the Asset Management Business Line Coordinator) in the generation and review of ESARs, and have signature authority from the CO of the NAVFAC, Echelon IV or higher.

d. MARCORSYSCOM (PM AMMO). MARCORSYSCOM is responsible for explosives safety within the Marine Corps. MARCORSYSCOM PM AMMO is responsible for managing the explosives safety program.

MARCORSYSCOM shall:

(1) Provide interpretation/clarification, for Marine Corps Activities, on questions of explosives safety criteria in support of ESARs/ESAs.

(2) Provide clarification, for Marine Corps Activities, for issues regarding ESAs during Explosives Safety Inspections (ESIs) and Ammunition and Hazardous Materials (AMHAZ) Handling Review Boards.

(3) Provide technical review, using enclosure (2) of the ESAR submitted by the Activity, independent of the package developer. The technical review shall include a review of the accuracy of mapping, application of explosives safety criteria from reference (b), Chapters 5-8, and consistency with Activity Master Plans. Review for consistency with Activity Master Plans may be delegated to a lower level of endorsement.

(4) Endorse ESAR to NOSSA. Reviewer must have taken AMMO-36 within the last 5 years.

e. NOSSA. NOSSA is responsible for the technical requirements for explosives safety, to include ESAs. NOSSA shall:

(1) Provide the requirements for ESAs through this instruction to facilitate ESAR submittal, review, endorsement, approval, and oversight.

(2) Provide interpretation/clarification on questions of explosives safety criteria in support of ESARs/ESAs.

(3) Provide clarification for issues regarding ESAs during ESIs and AMHAZ Handling Review Boards.

(4) Review and approve ESARs for the DON:

(a) Set the priority for review of ESARs, based on first-come, first-served basis, unless accompanied by an expedited request letter from the Shore (Host) Activity/Command CO or guidance from Senior Navy or Marine Corps leadership.

(b) For ESARs that require DDESB approval:

1. Review and endorse ESARs to DDESB.

2. Support the review and approval of ESARs at the DDESB. NOSSA is the single point of contact (POC) with the DDESB. Direct communication by telephone, facsimile, or electronic mail with DDESB staff members is not authorized, except in the circumstances permitted in reference (b), paragraph 1-3.4.2.

3. Provide DON approval and include any DON-specific criteria restrictions to ESAs approved by the DDESB.

(c) For ESARs that can be approved at the DON level:

1. Review and approve these ESARs, noting any special requirements of, or stipulations to, the approval.

2. Review and approve the storage of less than 300 pounds NEW of C/D 1.2.2, C/D 1.3, and C/D 1.4 in locations such as ready-for-issue magazines and aircraft life support shops (ALSS); or less than 300 pounds NEW of C/D 1.3 or C/D 1.4 material necessary for ship’s security and safety-at-sea. This review and approval will be provided by the NOSSA Explosives Safety Support Offices Atlantic (ESSOLANT) or Pacific (ESSOPAC), as permitted by reference (b), paragraph 8-1.2.1.

(5) Transmit approved ESAR to endorsing NAVFAC or MARCORSYSCOM for continuing action.

(6) Evaluate ESA submissions, using enclosure (2), and provide constructive comments to Customers, to facilitate improvements in ESARs, in order to reduce the time required for ESAR review/approval.

(7) Maintain WebSAR as the DON process for submitting ESARs, to include providing for DON Regional and Marine Corps-required endorsement chains.

(8) Maintain ESIS database template, make the template available to Activities via the NOSSA Restricted Web Site, and maintain Summary Database for ESIS.

5. ESA Documentation.

a. An ESA is comprised of the entire package, including the ESAR and its enclosures, endorsements, and approvals required to construct and operate explosives facilities or operations.

(1) All facilities must be constructed and operated per the constraints outlined in the ESA. If changes are made that deviate from the ESA, such as changes in facility location, method of construction, or systems covered by explosives safety criteria, or in operations that increase the hazards associated with the operation, the facility/operation must be resited by submittal of a new ESAR.

(2) A copy, either paper or electronic, of the complete approved ESA must be maintained at the Activity. The complete package must, at a minimum, contain a copy of:

(a) Original ESAR;

(b) All attachments, including site map, to the original ESAR;

(c) NAVFAC or MARCORSYSCOM endorsement;

(d) NOSSA endorsement or approval;

(e) DDESB approval letter, and NOSSA transmittal letter, if the ESA required DDESB approval;

(f) Complete copies of any preliminary approval packages; and

(g) If the facility was sited with a temporary building number, a copy of an e-mail, addressed to NOSSA Code N54, notifying NOSSA of the permanent building/facility number, must be maintained in the record.

b. All ESARs shall be prepared following the format specified in enclosure (1).

c. By 30 June 2011, all ESARs must be generated using Naval Enterprise Data:

(1) Navy GeoReadiness and Marine Corps GeoFidelis GIS/enterprise mapping system for all maps;

(2) Navy and Marine Corps facility (real property) inventory, iNFADS;

(3) ESIS database maintained by the Shore (Host) Activity/Command ESO.

d. After 1 December 2011, a current copy of the Activity’s ESIS database must be submitted with each ESAR that sites a new facility or changes the explosives limits or the function of a facility within 110% of IBD of any PES.

e. An ESA is in effect until an ESAR to remove explosives limits is approved. If a facility is approved and not constructed, the associated arcs are in effect until an ESAR to remove the explosives limits and arcs is submitted to, and approved by, NOSSA. Note that for an ESA that will remove arcs from existing facilities with the construction of new facilities, the arcs for the existing facilities may remain in place until the new facility is built, as permitted by the ESA.

Note that for an ESA that will demolish an ES to permit construction of the new facility, the old ES may be retained until the new facility is built. If the new facility will not be built and the Activity plans to retain existing facilities, the Activity must request to retain the siting of the existing facilities when requesting NOSSA remove the arcs for the facility that will not be built.

f. If a facility is not built within 10 years of the date the ESAR was approved, the Shore (Host) Activity/Command must notify NOSSA Code N54, via a letter, requesting NOSSA revalidate the ESA against any significant changes in explosives safety criteria, prior to the start of construction.

g. Requests for expedited review of ESARs, from Navy Activities, must be in the form of a separate Shore (Host) Activity/Command CO-to-CO NOSSA letter, include a rationale for need for expedited review, and be signed by the CO of the requesting Shore (Host) Activity/Command, with a mandatory copy to the Regional Engineer. Signature authority for requests for expedited review should not be delegated to the PWO. Expedited review is a request on the part of the Shore (Host) Activity/Command CO to place the ESAR in front of other Navy ESARs for action by NOSSA and the DDESB. Therefore, expedited review should be reserved for urgent, emergent requirements and not serve as a substitute for prior planning on the part of the Activity. NOSSA will set the priority for requests for expedited review from multiple Navy Activities.

h. Requests for expedited review of ESARs, from Marine Corps Activities, must be included on the Shore (Host) Activity endorsement letter. MARCORSYSCOM will coordinate the expedited review with NOSSA and the DDESB.

6. ESQD Maps and Data.

a. ESQD maps are any maps that show ESQD arcs. Typical ESQD maps include site-specific maps for ESARs, planning maps, and Fire maps.

(1) After 30 June 2011, all maps showing ESQD arcs used for submittal of ESARs, making decisions in regards to explosives safety, and/or Fire maps shall:

(a) Only be generated using official GIS/enterprise mapping system (Navy GeoReadiness or Marine Corps GeoFidelis).

(b) Be reviewed and approved by the cognizant ESO.

If the map uses standardized ESQD arc display formats, such as showing all IBD arcs or a composite IBD arc, ESO review of the standard display of the arcs is sufficient. The date the ESO reviewed the map (or standard arc layer) must be noted on all maps.

(c) Be clearly labeled with:

1. Name of Activity;

2. Title/description of map;

3. Measurable scale and North arrow;

4. Dates prepared, revised, data reviewed by ESO; and

5. Name and contact information of the preparer of the map.

b. ESQD maps will be provided in electronic format, such as PDF, must have a scale of even 100-foot increments (e.g., 1”:100’, 1”:200’, 1”:300’, 1”:400’, etc.), and shall be saved to scale.

c. ESQD maps submitted as part of an ESAR shall be prepared following the format in enclosure (1).

7. ESIS.

a. Starting 1 December 2011, following the spiral schedule in paragraph 7.b. at a minimum, all Shore (Host) Activity/ Command ESOs must maintain an ESIS database listing all PESs and any ES within 110% of IBD of any and all PESs. ESO may delegate implementation and maintenance of the ESIS database to an appropriate supporting office, but shall maintain oversight of the function. The ESIS shall be maintained as an MS Access database using the template provided by NOSSA, available on the NOSSA Restricted Web Site or by contacting NOSSA at inhdnossa-facilitiescertification@navy.mil.

b. Starting 1 December 2011, implementation of the ESIS database may be conducted on a spiral basis as follows:

(1) By 1 December 2011, list all PESs with sited explosives limits for the Activity.

(2) By 1 March 2012, with each submittal of an ESAR, list all PESs and their sited explosives limits for the Activity; for all PESs encumbered by or encumbering the facility/operation being sited, provide all fields associated with those facilities, and list all ESs encumbered by the facility/operation being sited.

(3) By 1 December 2012, all fields for all PESs and all ESs within 110% of IBD of any and all PESs must be completed and a copy of the database submitted to NOSSA Code N54.

c. After the 1 December 2012 submission of the ESIS from the Activity to NOSSA Code N54, Activities will be required to submit updated copies of the ESIS to NOSSA Code N54 on the following schedule.

(1) A copy must be submitted with each ESAR that sites a new facility or changes the explosives limits or the function of a facility within 110% of IBD of any PES.

(2) Upon request, a copy must be submitted to NOSSA Code N54 one month before the AMHAZ Handling Review Board for the Activity’s Region.

(3) Upon request, a copy must be submitted to both NOSSA Code N54 and the cognizant ESSO 30 days before an ESI.

d. A data dictionary and instructions on how to populate the ESIS database will be provided with the template database and will be available on the NOSSA Restricted Web Site.

8. WebSAR.

a. Unless approved in writing by NOSSA in advance, all ESARs must be submitted using WebSAR.

b. If mandatory DON Regional or Marine Corps endorsements are required, the DON Regional ESOs and MARCORSYSCOM shall provide the WebSAR Helpdesk (inhdnossa-WebSAR@navy.mil) with the required POC information. The DON Regional ESOs and MARCORSYSCOM will be responsible for monitoring their respective endorsement chains.

c. All Commands involved in the ESA process are responsible for maintaining/updating their Command’s personnel contact information within WebSAR, through the WebSAR Helpdesk.

9. Automated Site Planning Tool (ASPT) (ESSv6).

a. By 1 December 2010, all DON ESARs generated using an ASPT must be generated using ESSv6, or latest approved version, and using Naval Enterprise Data:

(1) Navy GeoReadiness and Marine Corps GeoFidelis GIS/enterprise mapping system for all maps;

(2) Navy and Marine Corps facility (real property) inventory, iNFADS;

(3) ESIS database maintained by the Shore (Host) Activity/Command ESO.

b. Army and Air Force tenants on DON Activities must use Naval Enterprise Data, as described in 9.a. for ESARs generated using ASPT. Air Force tenants may use the Air Force-endorsed ASPT, ASHSii.

10. Safety Assessment for Explosives Risk (SAFER). Per reference (b), paragraph 8-1.5.2., request for site approval using the SAFER model will be submitted as a normal ESAR, following the guidelines in enclosure (1), unless other guidance is provided by NOSSA.

11. Subsequent Revisions. Enclosure (3) is reserved for later revisions of this instruction.

12. Glossary of Terms and Table of Contents. Enclosure (4) lists definitions of basic terms used in this instruction.

Enclosure (5) is a table of contents for the instruction, enclosure (1), and enclosure (2).

13. Technical Guidance. For ESA technical guidance, contact NOSSA Code N54 at inhdnossa-facilitiescertification@navy.mil.

14. Records Management. Records created as a result of this instruction, regardless of media and format, shall be managed in accordance with SECNAV Manual 5210.1.

mailto:inhdnossa-facilities_certification@navy.mil

15. Forms. NAVFAC 11010/31 Part I, NOSSA 8020/22 Part II Division A, and NOSSA SPE Forms are automatically generated by the NOSSA WebSAR application available at https://nossa.nmci.navy.mil/nrws2/.

Distribution:

Electronic only via NOSSA Restricted Website https://nossa.nmci.navy.mil/nrws2/

Enclosure (1)

Guide for Preparing an Explosives Safety Site Approval Request (ESAR)

This guide is to be used by the Site Approval Development Team (SADT) to prepare Explosives Safety Site Approval Requests (ESAR) for submittal to the Naval Ordnance Safety and Security Activity (NOSSA) for endorsement/approval. The Guide is designed to be used with WebSAR, the Department of the Navy’s (DON) web-based automated ESAR submission module, and is formatted to follow the WebSAR data entry sequence and the Main Check List screen. If minor formatting changes are incorporated into WebSAR between revisions of NOSSAINST 8020.22 and this Guide, guidance will be provided by NOSSA, via WebSAR or separate communication, on any changes required in ESAR format and data requirements. WebSAR is accessed through the NOSSA Restricted Web Site: https://nossa.nmci.navy.mil/nrws2/

Specific notes are inserted in the appropriate ESAR sections where there are different requirements for:

Construction Worker Authorization (CWA) within K18 intraline distance (ILD) of potential explosion sites (PESs), or

Requests for Final Explosives Safety Site Approval (FESA), where a preliminary explosives safety site approval (ESA) was granted

Following is a list of documentation required for submission of an ESSAR. This list parallels the Main Check List in WebSAR.

Explosives Safety Site Approval Request (ESAR) Category

Required Documentation K

C W A

Q D

E S A R f o r

N e w

P E S w i t h o u t

P r o t e c t i v e

C o n s t r u c t i n

E S A R f o r

N e w

P t h

P r o t e c t i n s t r u c t i

E S A R f o r

N e w t h o u t

P r o t e c t i n s t r u c t i

E S A R f o r

N e w

E S w i t h

P r o t e c t i v e

C o n s t r u c t i

R m o v e

E x p l o s i v s

L m i t s f r o m

P

F E R

E S

1. Project Title and

CATCODE

X X X X X X X

2. Project Description X X X X X X X

3. Project Siting Rationale

X X X X X X X

4. NAVFAC 11010/31 Part I Section A

X X X X X X X

5. NOSSA 8020/22 Part II Division A

X X X X X X X

6. Paired PES/ES Relationship Form

(1) X X (2) (2) (6)

7. Maps

a. Location Map X X X X X X X

b. Site Map (3) X X X X X X

8. Previous Approvals A/R A/R A/R A/R (4) A/R

9. Building Layout A/R A/R A/R A/R A/R

a. Structural Drawing X X A/R

b. Structural Specification

(5) (5) A/R

c. Lightning Protection Drawing or documentation of exception, per NAVSEA OP 5, Vol 1, para 6-3.1.

X X A/R

d. Electrical and Grounding System Drawing

X X A/R

Required Documentation K

C W

E S A R f o r

N e w

P t h o u t

P r o t e c t i n s t r u c t i

E S A R f o r

N e w

P E S w i o t e c t i v e

C o n s t r u c t i

E S A R f o r

N e w t h o u t

P r o t e c t i n s t r u c t i

E S A R f o r

N e w

E S w i o t e c t i v e

C o n s t r u c t i m o v e

E x p l o s i v e s

L i m i s f o m

P

F E R

E S

e. Barricade Drawing A/R A/R A/R A/R A/R

f. Other Drawings A/R A/R A/R A/R A/R

10. Other Documents A/R A/R A/R A/R A/R A/R A/R

11. Activity (Host) Command Approval/Transmittal Letters

A/R A/R A/R A/R A/R A/R A/R

12. NAVFAC or MARCORSYSCOM Endorsement Letter

X X X X X X X

12. Approval Letters X X X X X X X

13. NOSSA Required Approvals/Endorsements

A/R A/R A/R A/R A/R A/R A/R

X-Required A/R-As Required

(1) List of PESs with K18 encumbrances on work site.

(2) List of all PESs that have ESQD encumbrances on exposed site

(ES).

(3) Site map that shows K18 explosives safety quantity distance (ESQD) arcs that encumber work site.

(4) Include ESA(s) that set the current explosives limits.

(5) If protective construction not previously approved by Department of Defense Explosives Safety Board (DDESB), design drawing must be endorsed by Naval Facilities Engineering Service Center (NAVAFAC ESC) (or Army Corps of Engineers (USACE) equivalent) and may require site-specific engineering analysis.

(6) Submit Paired PES/ES Relationship forms for all of the facilities being sited. For the PES/ES pair(s) that violate ESQD criteria and require SAFER siting, note “SAFER siting requested”, following the guidelines in paragraph 6.i.(3)(b) of this document.

Additional project specific guidance may be provided by NOSSA.

Note, all documents, other than the Part I and Part II Forms, included in the ESAR, acted on by NOSSA, will have an Attachment Number noted on the tab page of the consolidated document. All attachments will automatically be referenced on the Part II form. The WebSAR Submitter will not have to label attachments;

WebSAR will automatically number and label all attachments.

1. Project Title and Category Code (CATCODE): Enter the five-digit CATCODE number from NAVFAC P-72 (DON Facility Category Codes) for the primary facility. In the case of a multi-use facility, enter the CATCODE of the predominant use. The project title is the nomenclature from NAVFAC P-72, or a local description of the project. Name the special area if the project is not located at the primary Activity.

2. Project Description: Briefly describe the proposed project.

Address the type of explosives operations that will be conducted and Class/Division (C/D) of explosives that will be handled at the proposed facility. Describe the proposed facility. This may include type of construction materials, special construction features such as hardening, shatterproof windows, electromagnetic radiation shielding, etc.

3. Project Siting Rationale:

a. State the reason for the proposed project location, including building relationships, strategic, operational, functional and/or time constraints which dictate or influence location of the facility. Specifically address the rationale for the site, if these constraints supersede other locations that may have posed less risk to personnel, facility, or strategic assets. State any economic factors which may influence the project location. Discuss any feasible alternatives and the reasons for rejecting these alternatives.

b. If construction workers will be within K18 ILD of a PES, then the ESAR must describe how the risk to construction workers from encumbering PESs will be managed. If construction activities have the potential to impact explosives operations, such as construction work concurrent with explosives operations, the Activity/Installation must describe how the risk to the explosives operations will be managed. If concurrent explosives operations and construction work must take place, the Activity/Installation must provide a justification of why concurrent operations are required.

c. Questions: These questions are used to determine if the project should be routed to either of NOSSA’s Explosives Safety Support Offices, Atlantic (ESSOLANT)/Pacific (ESSOPAC).

(1) Is this an ESAR that only involves the storage of C/D 1.2.2, C/D 1.3, and C/D 1.4 material (less than 300 pounds net explosives weight (NEW)), as in ready-for-issue magazines and aircraft support shops (ALSS), to meet operational requirements, or handling 300 pounds NEW or less of C/D 1.3 and C/D 1.4 material necessary for ship’s security and safety-at-sea? Yes or No.

(2) Does this ESAR involve facilities or rooms within non-explosives facilities (such as aircraft hangars, troop buildings, and manufacturing/operating buildings) that are used for storage and work on aircraft egress devices, signaling devices, life vests, and life rafts? Yes or No.

4. NAVFAC 11010/31 Part I Section A: Refer to NAVFACINST

11010.45 “Site Approval Process”, Section 6.1.1, for specific block instructions for shaded fields.

5. NOSSA 8020/22 Part II Division A (Formerly NAVFAC 11010/31 Part II Division A): The NOSSA 8020/22 Part II Division A Form (see Figure 1) will be used as a summary sheet for the facilities being sited. The NAVFAC 11010/31 Part II Division A Form will no longer be used. The final formatted Part II Division A will not be generated by WebSAR until NOSSA finalizes the project for either endorsement to DDESB or approval by NOSSA. Until the project is finalized by NOSSA, the submitters and reviewers will only see the Part II Division A data entry screen, see Figure 2. For each facility being sited, an individual PES/ES Relationship Sheet shall be attached to the Part II Form Tab using the “Add/Edit PES-ES” button in the upper left-hand corner of the screen (see Figure 2). Specific block instructions for the NOSSA 8020/22 Part II Division A Form are as follows.

a. Block 1a. Auto-filled by WebSAR as PES/ES Forms are attached using the “Add/Edit PES-ES” button. Directions on how to complete the PES/ES Relationship Form can be found in Section 6 of this document.

b. Block 1b. Filled in by WebSAR, when Part II Division A is finalized.

c. Block 2. List any deviations (Chief of Naval Operations (CNO) Waivers, CNO Exemptions, or Secretarial Certifications) that affect the facilities for which an ESA is requested.

Describe the deviation, how it is associated with the proposed facility, and if this ESAR will eliminate the deviation.

d. Block 3. Siting Rationale is auto-filled by WebSAR from the “Project Siting Rationale” response entered earlier.

Figure (1)

Figure (2)

6. Paired PES/ES Relationship Form:

a. The Paired PES/ES Relationship Form will demonstrate that the ESQD required in NAVSEA OP 5, Volume 1, are met. A PES/ES Form will be prepared for each facility for which an ESA is requested, including facilities that are sited as ESs only.

b. If the Activity is using the Automated Site Planning Tool (ASPT), ESSv6, the program will generate the PES/ES Relationship Form automatically as a PDF that can be attached to WebSAR. If the Activity is preparing the ESAR by hand, follow the directions below to prepare the PES/ES Relationship Form.

c. Each PES/ES Relationship Form shall be titled with a header that includes the name of the Activity/Installation, the facility number, and the WebSAR number. The footer shall contain the revision date, page number in the format of Page X of Y, and the attachment number. See Figure (3) for an example for siting a PES, and Figure (4) for siting an ES.

d. (CWA) Provide a PES/ES Relationship Form for each individual work location. List the work location in Section II.

List all PESs with K18 intraline distance (ILD) encumbrances on the work location. Alternatively, for a large number of work locations, substitute a list of work locations, with unique identifiers (i.e., Site A, Site B, etc.), type of work to be performed, associated risk control measures to project construction workers, and impacted PES. If a list is used, then all locations must be shown and labeled on the ESQD map and all encumbering K18 ILD arcs shown.

e. (FESA) If the ESQD relationships have not changed since the preliminary ESA, a PES/ES Relationship Form is not required.

f. Section I:

(1) Activity/Installation: Name of the Activity/Installation where the project is located.

(2) Location: Geographical location, generally City, State.

(3) Date: Revision date (shall be the same date shown on the footer).

g. Section II:

(1) Facility Number: Building number or other facility number. If known, also include the Real Property Unique Identifier (RPUID).

(2) Facility Description: Provide the 3-letter standard description from Table (1), in this instruction, which best identifies the facility. Then provide short name of facility.

Figure (3)

Figure (4)

Table 1. List of Standard Descriptions (PES/ES Types).

AEB AE burn area AGE aboveground electric line AGM aboveground magazine AGT aboveground storage tank AGU aboveground utility AJR airfield, joint-use runway AJT airfield, joint-use taxiway ALS anchorage, explosives-loaded ALU anchorage, explosives loading/unloading AMR airfield, military-use only runway AMT airfield, military-use only taxiway ASC anchorage, scuttling site BND activity/installation boundary CAF facilities for combat a/c alert forces CAP combat aircraft parking area (CAPA)/combat aircraft loading area (CALA) EBP explosives barge/pier ECA aircraft explosives cargo parking ECM earth-covered magazine ELP explosives loading pier/wharf EOL explosives operating location FMA flight-line munitions holding area GRD guard shelters HAS hardened aircraft shelter HDY yard, railroad or truck holding HLA helicopter landing pad, loading/unloading ae HLL helicopter landing pad, loading/unloading HPM high-performance magazine IBD inhabited building distance facility IDS intentional detonation site ILD intraline distance facility IS1 inert storage-IB separation required IS2 inert storage-K18 separation required IS3 inert storage-no separation required IST inert storage KFT Korean flow through (HAS) KTV Korean tab vee (HAS) MCC multi-celled cubical complex MLP missile launch pad MSC main shipping channel NAA non-applicable area NAF non-applicable facility NEA non-explosives-loaded aircraft NLP non-explosives anchorage/pier NTR this road is not a public traffic route

OSM open storage module PLA passenger load/unload area PTR public traffic route distance RAF recreation area facility RAM ready service aboveground magazine REM round earth-covered magazine RIG ready service igloo RLF related facility RMD ready service module RMG ready service magazine RSL ready storage locker RSM ready service magazine TBV tab vee or tab vee modified (1st generation aircraft shelter) TVM tab vee maintenance (HAS) UGU underground utilities 2GM 2nd generation maintenance (HAS) 1GN 1st generation aircraft shelter 2GN 2nd generation aircraft shelter 3GN 3rd generation aircraft shelter

(3) Required Inhabited Building Distance (IBD): Enter the appropriate IBD for the explosives limits requested. For PESs such as earth-covered magazines (ECMs) with different IBDs out the front, side, and rear, list each distance, and label front, side, or rear as appropriate.

(4) Required Public Traffic Route Distance (PTRD):

Enter the appropriate PTRD for the explosives limits requested.

For PESs such as ECMs with different PTRDs out the front, side, and rear, list each distance, and label front, side, or rear as appropriate.

(5) Required ILD: Enter the appropriate ILD for the explosives limits requested. For PESs such as ECMs with different ILDs out the front, side, and rear, list each distance, and label front, side, or rear as appropriate.

(6) 1.1: C/D 1.1 explosives limits requested.

(7) 1.2.1: C/D 1.2.1 explosives limits requested. A maximum credible event (MCE) must be specified. If greater than 450 pounds, state “no MCE limit”

(8) 1.2.2: C/D 1.2.2 explosives limits requested.

(9) 1.2.3: C/D 1.2.3 explosives limits requested. An MCE and hazardous fragment distance (HFD)(parenthetical) must be specified.

(10) 1.3: C/D 1.3 explosives limits requested.

(11) 1.4: For 300 pounds or less, specify the requested limits. For more than 300 pounds, specify specific limit or mission-essential quantities (MEQ).

h. Section III: Show all facilities within 110% of IBD of the PES being sited. Address any facilities outside of IBD that encumber the facility being sited as follows:

(1) If the facility is a PES, and the ILD arc from the PES with the largest NEW at the Activity/Installation is less than the IBD for the facility to be sited, then no facilities outside of IBD must be listed. In the first line of Section III, provide the following statement:

“Maximum sited explosives limits at any facility at the Activity/Installation is XXXXX pounds of C/D 1.1 (or appropriate C/D) with an unbarricaded ILD of YYY feet. This distance is less than the ZZZZ feet of the IBD for this facility; therefore, only facilities within IBD are shown.”

(2) If the facility is a PES, and the unbarricaded ILD arc from the largest PES at the Activity/Installation is larger than the IBD for the facility to be sited, demonstrate that the facility is not encumbered by an intermagazine distance (IMD) or ILD ESQD arc, in violation of ESQD requirements by one of the following approaches:

(a) Based on the unbarricaded ILD for the PES with the largest NEW for the Activity/Installation, list all facilities out to this distance from the facility being sited.

In the first line of Section III provide the following statement:

“The largest PES for the Activity/Installation is XXXXX pounds of C/D 1.1 (or appropriate C/D) with an unbarricaded ILD of YYY feet. All facilities within YYY feet of the facility sited by this form are listed to demonstrate compliance with ESQD requirements.”

(b) If the PES with the largest NEW is significantly larger then all of the remaining PESs on the Activity/

Installation, such as an explosives handling wharf, then demonstrate that the PES does not violate ESQD requirements, by listing all facilities within IBD of the facility being sited, and listing all facilities with an IMD or ILD greater than the IBD of the facility being sited, as appropriate. In the first line of Section III, provide the following statement:

“The IBD for the facility being sited is XXXXX pounds of C/D 1.1 (or appropriate C/D) with an IBD of YYY feet. All facilities within YYY feet are listed. The majority of the facilities at the Activity/Installation have ILD separation of less than YYY feet, but the largest PES for the Activity/Installation is AAAAA pounds of C/D 1.1 (or appropriate C/D) with an unbarricaded ILD of BBB feet. All facilities with an ILD greater then YYY feet, and within BBB feet of the facility sited by this form, are listed to demonstrate compliance with ESQD requirements.”

(3) (CWA) If the ESAR is a CWA, then only list facilities that have either a K24 remote operation or K18 ILD encumbrances on the work locations, lay-down areas, and trailer locations.

i. Data Element for Section III: For each facility listed as outlined above, there shall be a double-row entry outlined by bold lines. The first row of the entry is the listed facility as the PES to the facility being sited as the ES. The second row is the listed facility as the ES to the sited facility as the PES. See Figures (2) and (3) as examples. For CWAs, only a single-line entry for each encumbering PES is required.

(1) On the first row:

(a) Facility Number: Building number or other facility number. If known, also include the RPUID.

(b) Facility Description: Provide the 3-letter standard description from Table (1) that best identifies the facility. Then provide short name of facility.