M6785423R4907_Attch 5_PESHE_10MAR2014.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

Naval Enterprise Networks Program Management Office

PMW-205

NEXT GENERATION ENTERPRISE NETWORK

Programmatic Environment, Safety, and Occupational Health Evaluation (PESHE)

VERSION: 1.1

DATE: 10 MARCH 2014

Program Executive Office Enterprise Information Systems

Program Manager, Naval Enterprise Networks 1325 10th Street, SE, Suite 301

Washington, DC 20374

Distribution Statement D: Distribution authorized to the Department of Defense (DoD) and United States (U.S.) DoD contractors only (Administrative Use) (Oct 2008). Questions concerning technical content or any other requests for this document shall be referred to the Naval Enterprise Networks Program Manager, Program Executive Office – Enterprise Information Systems, 1325 10th Street, SE, Suite 301, Washington, DC 20374.

Handling and Destruction Notice: Comply with Distribution Statement and destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational Program Management Office Health_Evaluation_(PESHE)_ v1.1_10 March 2014

Not to be disclosed outside the Government except IAW the referenced non-disclosure agreement ii

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational iii

Revision Number Revised By Revision Date Revised

1.0 Initial Version Signed by the PM 10-24-11

1.1 Logistics Team Update Program information and content in

support of FTD/FDD March 2014

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational iv

EXECUTIVE SUMMARY

The Next Generation Enterprise Network (NGEN) Programmatic Environment, Safety, and Occupational Health Evaluation (PESHE) serves as the primary Environmental Safety and Occupational Health (ESOH) management tool. It has been developed in accordance with the Defense Acquisition Guidebook (DAG), Department of Defense (DoD) Instruction (DoDI)

5000.02 and Secretary of the Navy Instruction (SECNAVINST) 5000.2E ESOH requirements.

The specific PESHE focus areas are:

• ESOH Risk Management;

• ESOH Regulatory Compliance;

• Pollution Prevention (P2) and Hazardous Materials (HM) Management (HMM);

• Safety and Occupational Health (OH); and

• National Environmental Protection Act (NEPA)/Executive Order (EO) 12114

Each focus area is discussed in further detail in this PESHE as they are essential components of the overall NMCI system. ESOH compliance issues are being addressed in alignment with both the United States Navy (USN) Government-Owned/Contractor-Operated (GO/CO) approach and the United States Marine Corps (USMC) Government-Owned/Government-Operated (GO/GO) approach. Further, ESOH compliance issues were incorporated into the Continuity of Services Contract (CoSC) and have been incorporated into the NGEN Contract as appropriate.

NGEN is the follow-on Contract under which HP Enterprise Services (HP) provides network services to Department of the Navy (DON). NGEN is currently transitioning from CoSC which is set to end on 30 September 2014.

Per the Under Secretary of Defense for Acquisition, Technology and Logistics (USD (AT&L)), NGEN is currently an Acquisition Category IA Major Automated Information System (ACAT IA MAIS) Program. The Program was initiated successfully at MS C on 05 June 2013. NGEN will also follow the Two-Pass, Six-Gate review process of the acquisition improvement initiative set forth in Secretary of the Navy Instruction 5000.2E (SECNAVINST 5000.2E).

The PESHE is a living document and requires periodic updates to support changes in Program strategies, direction, organization and schedules. Additionally, this may include updates at the Gate reviews, Final Transition Decision (FTD/ Full Deployment Decision (FDD), and throughout the system life cycle to manage ESOH risks. This version has been developed to address programmatic changes included in the NGEN Acquisition Strategy (AS) update of 19 April 2012, and in accordance with current DoD and DON policies and guidance. Based on a preliminary assessment and association with the NMCI September 2010 environment, the overall NGEN ESOH risks are low/green. ESOH regulatory and statutory compliance, P2 & HM management, system safety, OH, and NEPA/EO 12114 issues are all being closely monitored through the organizations and processes outlined in this plan.

For the USMC, NGEN is a subset of a larger Marine Corps Enterprise Network (MCEN) and as such Marine Corps policy, directives and guidance exist to manage, control and support enterprise wide operation of the MCEN. In order to support the enterprise wide operation of the MCEN, NGEN ESOH activities will be managed based on the following order of precedence:

Applicable DoD and/or SECNAV directives, instructions, regulations, and/or publications, Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational v

Marine Corps Orders and Instructions, Marine Administrative Messages (MARADMINS), USMC Total Lifecycle Management policies and procedures, USMC E-ITSM policies, processes, and procedures, and NGEN Program documentation.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational vi

Table of Contents

1.0 INTRODUCTION AND PROGRAM DESCRIPTION

1.1 System Purpose, Description, and Status Overview

1.2 Schedule

2.0 ESOH MANAGEMENT AND PROGRAM INTEGRATION

2.1 Organizational Structure to Support NGEN

3.0 ESOH RISK MANAGEMENT

3.1 ESOH System Safety Management

3.2 Software System Safety

3.3 Occupational Health

4.0 ESOH REGULATION COMPLIANCE

5.0 P2, GREEN PROCUREMENT, AND HM MANAGEMENT

5.1 Pollution Prevention

5.2 Green Procurement

5.3 HM Management

5.4 Disposal

6.0 NEPA AND EO 12114

APPENDIX A ACRONYMS ............................................................................................... A-1 APPENDIX B LIST OF REFERENCES ................................................................................ B-1

Table of Tables

Table 3.1-1 - ESOH Risk Identification and Management Table 3.1-2 - Hazard Severity Category Table 3.1-3 - Hazard Probability Level Table 3.1-4 - Risk Assessment Matrix

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

1.0 INTRODUCTION AND PROGRAM DESCRIPTION

As described in the NGEN Acquisition Strategy (AS) version 19 April 2012, the DoD and the DON identified NGEN Increment 1 as an ACAT IA MAIS to Congress in the 31 December 2008 Pre-MAIS Annual Report (Pre-MAR). NGEN is currently an Acquisition Category (ACAT) IAM Major Automated Information System (MAIS) program. NGEN will also follow the Two- Pass, Six-Gate review process of the acquisition improvement initiative set forth in

SECNAVINST 5000.2E.

1.1 System Purpose, Description, and Status Overview

During the timeframe of the NMCI contract, the US Strategic Command evolved its Network Operations (NetOps) Concept of Operations (CONOPS) governing warfighting in the cyberspace domain. Some limitations in the ability of NMCI operations to support NetOps CONOPS led the DON to establish overarching objectives for NGEN:

• Achieve command and control of the network

• Ensure the security of that network

• Support the Naval Networking Environment (NNE) vision

• Comply with DON FORCEnet1 standards

NGEN Increment 1, awarded on 22 November 2013, is the first increment of the acquisition program that is the follow-on to NMCI. In its complete form, NGEN will provide secure, net-centric data and information technology services and support to the USN and USMC. NGEN is in the process of expanding through migration of legacy networks such as the Outside the Continental United States (OCONUS) Navy Enterprise Network (ONE-NET) where approved and funded. To the maximum extent practicable, NGEN Increment 1 incorporates Commercial off the Shelf (COTS), Government off the Shelf, (GOTS) products and Non-Developmental Item (NDI) products. NGEN Increment 1 includes the capabilities of NMCI/CoSC, with increased Government operational and design control of the networks, and requisite Information Assurance (IA) enhancements to meet evolving security requirements. The system is the largest DoD centrally managed IT network, supporting approximately 400,000 seats representing over 800,000 users across the globe. It provides comprehensive, end-to-end information services through a common computing and communication environment.

1.2 Schedule

The NGEN Program level schedule lists Gates/Milestones, critical reviews, segment awards, key acquisition documents and test events required for transition to NGEN Increment 1. This PESHE has been developed consistent with DoD and DON policies and guidance to support the upcoming NGEN Increment 1, FTD/FDD decision which is currently scheduled for Q4 FY14.

The PESHE development schedule is captured in the logistics portion of the Program Integrated Master Schedule (IMS).

1 FORCEnet is the operational construct and architectural framework for Naval Warfare in the Information Age which integrates warriors, sensors, networks, command and control, platforms and weapons into a networked, distributed combat force, scalable across the spectrum of conflict from seabed to space and sea to land.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

2.0 ESOH MANAGEMENT AND PROGRAM INTEGRATION

The integration of ESOH considerations throughout the NGEN life cycle is a requirement of all USN and USMC Government employees, military personnel, support contractors, and vendors to support the NGEN mission and program objectives. The NEN PMO will maintain compliance with all ESOH regulations and all DoD and DON policy requirements. The NEN Program Manager (PM NEN) has directed that all NGEN personnel adhere to the following ESOH principles:

• Facilitate a program that is committed to ensuring that all programs are designed so that operation and deployment, maintenance and ultimate disposal meet all ESOH laws, regulations, policy directives, and relevant international agreements

• Empower NGEN staff, including contractors, in order to ensure the appropriate integration of ESOH management practices into all relevant activities, as well as keeping senior leadership informed of the ESOH risks to Program cost, schedule and performance

• Ensure effective integration of ESOH considerations into the Systems Engineering (SE) process to assist in accomplishing the overall program mission to field an effective product that meets all applicable ESOH requirements

This PESHE serves as a management tool for the NGEN Program. It serves as a planning document in support of the contract performance statement of work, and will be used up through FTD/FDD and beyond to record analyses, capture results, and report the current status of the ESOH Program. Top level preliminary activities that have already been performed include incorporating ESOH strategy information into program documentation such as the AS, the Systems Engineering Plan (SEP) and the Life Cycle Sustainment Plan (LCSP). In addition, statutory and regulatory ESOH requirements are addressed in the NGEN Contract Performance Statement of Work as well as manpower and resource estimates.

ESOH risks will be tracked and managed if they have unexpected, negative cost, schedule or performance impacts. ESOH risk or issue tracking will be based on the receipt of applicable information including but not limited to safety reports, environmental tracking and report data, facility reports, ESOH incident reports, OSHA reports, occupational health data, and any Material Safety Data Sheets (MSDS) associated with IT support systems such as site generators, electrical transformers, etc.

NGEN will apply the safety methodology contained in Military Standard (MIL-STD) 882E, DoD Standard Practice for System Safety, to update the PESHE with details regarding the management of ESOH hazards and associated risks.

2.1 Organizational Structure to Support NGEN

Based on a 28 January 2010 Charter, NGEN utilizes a Working-level Integrated Product Team (WIPT) structure in accordance with DoDI 5000.02, the Defense Acquisition Guidebook, and the Office of the Assistant Secretary of Defense (OASD) Rules of the Road for IPTs. The NGEN Program also participates in the DON Network Alignment Overarching IPT (NA-OIPT) and the DoD NGEN Oversight Committee. NGEN’s IPT construct allows for full participation from appropriate DON and DoD organizations at the appropriate levels. The IPT composition depends on the program phase and experts; field activities; the Prime Contractor and industry partners;

customers and users; resource sponsors; and T&E communities.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

2.1.1 Working Integrated Product Teams and Working Groups

The NGEN WIPTs are Acquisition, Cost, Logistics, Systems Engineering (including IA), and T&E. Each WIPT shall assist the NEN PM as follows:

• Review strategies and program plans for alignment with DoD and DON policy objectives

• and vision for IT programs and network. Provide recommendations for improved

• alignment

• Validate that Program technical and programmatic issues are properly addressed and

• resolved to support NGEN goals

• Recommend potential tailoring of MS C documents for policy and goal alignment

• Establish and execute plans of action and milestones for WIPT operations

• Apply the principles of Integrated Process and Product Development (IPPD) to enable

• and support execution of the NGEN program

• Coordinate with the Risk Management team to ensure that critical risk areas are identified and appropriate mitigation strategies are implemented

3.0 ESOH RISK MANAGEMENT

The PM NEN and the Risk Management Team are responsible for accepting or rejecting all risk candidates as part of the overall Risk Management Process for the NGEN Program. The enterprise risk and issue registry tool utilized by the NGEN Program to register risks is called Risk Exchange. Risk Coordinators are assigned to collect and assess all program risks, including ESOH-specific risks. Risks will be categorized as Program-level risks if they meet the cost, schedule or performance thresholds delineated in the NEN Risk Management Plan (RMP), v 4.0, signed 20 May 2013.

3.1 ESOH System Safety Management

The NEN PMO uses the system safety methodology contained in MIL-STD-882E, DoD Standard Practice for System Safety, to assess and manage ESOH hazards and associated risks.

ESOH information will be stored in the SE portion of the NEN portal in a folder entitled “NGEN Safety Management.” All Safety Incident Reports, safety issues, etc. will be managed via this workspace. Any hazard mitigations that result in a baseline change will need to be processed via an Engineering Change Proposal, per the NGEN Configuration Management Plan (CMP). The MIL-STD-882E ensures the proper identification of ESOH hazards and their associated risks using the steps as described in Table 3.1-1 below:

Step Action 1 Document the approach 2 Identify the hazard 3 Assess the risk 4 Identify the risk mitigation measures 5 Reduce the risk to the an acceptable level 6 Verify the risk reduction 7 Accept the residual risk at the appropriate authority level 8 Continue to track hazards and residual risk

Table 3.1-1 - ESOH Risk Identification and Management

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

MIL-STD 882E provides for classification of hazards according to the severity of the potential mishap (Table 3.1-2 - Hazard Severity Category) and the probability of occurrence of the hazard (Table 3.1-3 - Hazard Probability Level). These are included in the tables below. Additionally, NGEN will ensure proper, formal risk acceptance at the appropriate authority level as outlined in Table 3.1-4 – Risk Assessment Matrix.

Table 3.1-2 - Hazard Severity Category

DESCRIPTION CATEGORY SEVERITY DEFINITION

NEGLIGIBLE IV Minimal or No Impact

SAFETY (S) – Could result in injury (non-fatal) or occupational illness, but no lost work day, equipment/property loss/damage >$2K, but < $10K Environmental (E) – Minimal environmental damage not violating law or regulation

Occupational Health (OH) – Dose of a substance or induced stress levels with lost work time and no job impairment

MARGINAL III

Minor Effect Minor Reduction in technical performance or supportability, but will not change program approach, additional activities required to get program schedule; budget or unit production cost increase <5% of budget

S – Could result in injury or occupational illness that may result in hospitalization of at three or more personnel, equipment/property loss/damage >$100K, but <$200K E – Mitigatible (reversible) environmental damage (>$100K, but <$200K) without

OH – Dose of substance or induced stress levels leading to illness with one or more lost work days

CRITICAL II

Unacceptable Effect Significant degradation in technical performance or major shortfall in supportability;

mitigation may or may not be available; may affect program critical path and success; budget or unit cost increase <10% of budget

S – Could result in permanent partial disability, injuries, or occupational illness that may result in hospitalization or at three or more personnel, equipment/property loss/damage >$200K but <$1M E – Reversible environmental damage OH – Dose of a substance or induced stress levels leading to permanent partial disabling illness and/or 3 or more people hospitalized

CATASTROPHIC I

Unacceptable Effect Severe degradation in technical performance; cannot meet key performance parameters and/or technical/supportability thresholds; program success will be affected; no alternatives exist;

budget or unit production cost increase >10% of budget

S -Could result in death, permanent total disability, loss exceeding $1M, or irreversible severe environmental E- Damage that violates law or regulation.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

Table 3.1-3 - Hazard Probability Level

Table 3.1-4 - Risk Assessment Matrix

3.1.1 The NGEN Program fully endorses system safety management principles based on the MIL-STD-882E, and establishes the following ESOH objectives:

• Safety will be designed into the system, equipment, and workplace processes

• Design for minimization or elimination of hazard risk

• Use historical data and lessons learned from other systems

• Minimize risk with new technologies, materials, or designs

• Identify and determine causes for hazards and failure modes

• Assess hazard severity and probability of occurrence

• Determine hazard control requirements to reduce risk to acceptable levels

• Incorporate engineering controls to control and mitigate risk

• Identify and quantify any residual risk hazards by ensuring risks are accepted by the appropriate management decision authority

• Verify implementation of control measures

DESCRIPTION LEVEL SPECIFIC INDIVIDUAL ITEM

NOT LIKELY

(Improbable) E So unlikely, it can assumed that occurrence may not be experienced;

probability of occurrence <0.0001%

LOW LIKELYHOOD

(Remote) D Unlikely but possible to occur in life of an item;

probability of occurrence < 0.1%, but >0.0001%

LIKELY

(Occasional) C Likely to occur sometime in the life of an item;

probability of occurrence,<1%, but >10%

HIGHLY LIKELY

(Probable) B Will occur several times in the life of an item;

probability of occurrence <10%, but >1%

NEAR CERTAIN

(Frequent) A Likely to occur often in the life of an item;

probability of occurrence >10% in that life

RISK ASSESSMENT MATRIX

Frequency of

Occurance Risk Severity

IV (Negligible) III (Marginal) II (Critical) I (Catastrophic) A

(Frequent) IVA IIIA IIA IA

B (Probable) IVB IIIB IIB IB

C (Occasional) IVC IIIC IIC IC

D (Remote) IVD IIID IID ID

E (Improbable) IVE IIIE IIE IE

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

• Provide warning devices

• Develop safety operating procedures and training

• Evaluate changes in design, configuration, and mission requirements to ensure safety is met and risks are eliminated or controlled to acceptable level

3.2 Software System Safety

The objective of a software safety program is to meet or exceed all requirements of MIL-STD- 882E; applicable considerations of the Standardization Agreement 4404; and USN standards pertaining to software development, integration, testing, deployment, and maintenance.

The software safety analysis effort focuses on identification of software hazards through derivation of the software safety requirements, preliminary safety analyses, system and subsystem hazard analyses, as well as identification of safety critical items and safety critical functions. Most of the software used by NGEN is COTS, GOTS, and NDI and has been commercially developed for IT business systems; therefore software system safety issues are not foreseen.

3.3 Occupational Health

The NGEN OH Program will also be a component of the NGEN ESOH Management Program and will be in accordance with (IAW) Occupational Safety and Health Administration (OSHA) (Parts 1904.0 and 1910), DoD, and DON requirements. Efforts will focus on identifying health hazards, evaluating exposure levels to personnel, and implementing any required mitigation measures for operators and maintainers throughout the NGEN life cycle. Additionally, related Human Systems Integration (HSI) efforts will be integrated with the NGEN safety and OH aspects. Additional information about HSI initiatives can be found in the NGEN HSI Plan (HSIP). Early introduction of HSI in all NGEN increments and phases of the acquisition process will help optimize performance by ensuring that OH is fully and continuously considered as part of the total NGEN system.

4.0 ESOH REGULATION COMPLIANCE

Compliance issues will be identified and resolved as soon as possible in order to mitigate any potential cost or schedule risks. All NGEN personnel are required to identify any potential environmental impacts or compliance-related aspects, and to integrate ESOH risk reduction into all of their processes. To minimize cost and schedule risks, NGEN will ensure changes are reviewed IAW applicable ESOH laws and regulations, policy directives, and international agreements to identify and changes that may impact the Program.

The NEN PMO will address issues aimed at achieving and maintaining environmental policy compliance. Environmental issues for this Program are addressed as an integral component of the risk management process. As the Program progresses towards Final Transition Complete, the details of the system and services will be fully reviewed for compliance with all applicable ESOH regulations. At this time it is anticipated that NGEN will have a low ESOH compliance risk. Future PESHE updates will discuss any specific regulatory compliance matters as additional ESOH compliance-related data becomes available.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

Host installations will retain programmatic responsibility for the above mentioned items, and NGEN service providers will be tasked with compliance. As outlined in the Performance Statement of Work, and in support of ESOH regulation compliance, the Service Provider is required to develop a Hazard Analysis Report that identifies potential ESOH hazards for the NGEN environments in accordance with MIL-STD-882E, Standard Practice for Systems Safety.

(NGEN Contract CDRL A048 – Hazard Analysis Report).

The Service Provider is also required to develop and provide to the Government a Safety and Health Risk Assessment that determines the severity and likelihood of occurrence for safety and health risks in NGEN operational and maintenance environments (CDRL A049 – Safety and Health Analysis Report).

5.0 P2, GREEN PROCUREMENT, AND HM MANAGEMENT

5.1 Pollution Prevention

Pollution prevention (P2) is reducing or eliminating waste at the source by modifying production processes, promoting the use of non-toxic or less-toxic substances, implementing conservation techniques, and re-using materials rather than putting them into the waste stream. A P2 Program eliminates the creation of pollutants through increased efficiency in the use of raw materials, energy, water, or other resources, reducing the overall life cycle costs of the system. P2 is typically targeted at those aspects of the system’s design that necessitate the use of HM, and thus focuses on manufacturing, maintenance, and operations that expose personnel to HM or generate waste; however, it also includes efforts to eliminate or reduce HM contained with the system hardware. As NGEN is a commercial IT network, significant P2 issues are not anticipated.

Procedures for pollution prevention may differ between the USN and USMC as they are each responsible for their own compliance.

5.2 Green Procurement

NGEN competitive segments will comply with the Under Secretary of Defense (USD) “Updated Green Procurement Policy;” Assistant Secretary of the Navy (Research, Development and Acquisition) (ASN (RDA)) “Updated DoD Green Procurement Policy;” and Assistant Secretary of the Navy for Installations and Environment (ASN (I&E)), ASN(RDA) and DON Deputy Chief Information Officer (CIO) “Department of the Navy Strategy for Green IT Electronic Stewardship and Energy Savings Strategy.” This compliance includes requirements for 95 percent or greater of electronic equipment particularly laptops, desktops, etc. to be procured from Electronic Product Evaluation Assessment Tool (EPEAT) silver-rated and registered products per EO 13423.

5.3 HM Management

One of the goals of HM management is the elimination or reduction (where elimination is not feasible) of HM in processes and products throughout the network’s life cycle. This effort includes HM contained within and associated with operations, maintenance, and disposal of NGEN, including any possible hazardous waste generation.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

HM management objectives include the following:

• Select a system design approach and technologies not requiring HM whenever possible as well as eliminating/minimizing the release of pollutants

• Eliminate the use of HM and the generation of hazardous wastes and pollutants in operational, maintenance, and disposal processes and procedures

• Substitute an equivalent material that is less hazardous than HM, e.g. ESOH friendly alternatives

• Avoid the use of highly toxic chemicals such as: lead, mercury, cadmium, beryllium, hexavalent chromium, etc

• Use a centralized control and tracking method for indentifying an equivalent material that is less hazardous

Because NGEN is a COTS/GOTS/NDI-based IT system, no significant HM risks are foreseen.

5.4 Disposal

In August 2002, the DoD CIO directed the Defense Logistics Agency (DLA) and Defense Information Systems Agency (DISA) to develop a single property disposal process for DoD IT equipment. To accomplish this task, DLA and DISA established the DLA/DISA Business Initiatives Council (BIC) working group (WG). The WG, in collaboration with the Military Services, developed a proposed single IT property disposal process. The DLA/DISA BIC WG single property disposal process was approved by the DoD BIC.

The single property disposal procedures were implemented on 5 May 2003 thereby eliminating duplicate disposal channels for IT and other DoD property. NGEN IT equipment will be processed using established Defense Logistics Agency (DLA) Disposition Services (formerly known as the Defense Reutilization and Marketing Service (DRMS)) procedures. For additional information please visit DLA Disposition Services Website at http://www.dispositionservices.dla.mil.

Some specific disposal types included in this process are critical equipment and batteries for IT equipment. HM however is not included in this process and is subject to local HM procedures.

Procedures for disposal may differ between the USN and USMC as they are each responsible for their own compliance.

5.4.1 Demilitarization and Disposal Planning

Government policies, regulations, and instructions [e.g., 1) DoD 4160.21-M-1, Defense Materiel Disposition Manual, August 18, 1997; and, 2) Executive Order (EO) 13423, Strengthening Federal Environmental, Energy, and Transportation Management, January 24, 2007] require the demilitarization and disposal of all Global Information Grid (GIG) Hardware (HW), Software (SW), and electronic components at the end of service life.

The Service Provider will Demilitarize and dispose of HW and SW at cleared Contractor or Government facilities in accordance with sub-paragraphs Executive Order (EO) 13423, Strengthening Federal Environmental, Energy, and Transportation Management, January 24, 2007, DoD 4160.21-M-1, Defense Materiel Disposition Manual, August 18, 1997, DoD 4160.28- M, DoD Demilitarization (DEMIL) Program, April 7, 2011, Defense Reutilization and http://www.dispositionservices.dla.mil/turn-in/usable/index.shtml

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

Marketing Service DRMS-I 4160.14, Operating Instructions for Disposition Management, 11 September 2009, DON Strategy for Green IT Electronic Stewardship and Energy Savings, April 23, 2009, FAR 52.245-1 (only applies to GFP), and DoD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), February 28, 2006.

The Service Provider will dispose of classified and unclassified hard drives, in accordance with DON CIO Message Processing of Electronic Storage Media for Disposal 281759Z 12 AUG12.

The service provider(s) shall maintain accountability records for assigned Government Furnished Property (GFP) within the NGEN Configuration Management System (CMS) in accordance with the Service Provider’s Configuration Management Implementation Plan (CMIP) and the Asset Management Implementation Plan (AMIP).

As upgrades and improvements are introduced, any hardware having reached the end of its useful life shall be disposed of IAW all applicable DON IT equipment disposal procedures. For current IT equipment disposal procedures please see DLA Disposition Services website listed above. The DLA Disposition Services website also provides a turn-in guide for disposition of unclassified computer hard drives.

To preclude disclosure of classified data, NGEN service providers and users are required to handle and dispose of classified hard disk drives IAW appropriate DON security directives/procedures as well as local command procedures.

Additional details regarding demilitarization and disposal can be found in the NGEN Asset Management Plan (AMP).

6.0 NEPA AND EO 12114

NEPA, as amended, is a procedural law requiring Federal agencies to fully disclose and consider environmental information in agency decision making. NEPA mandates specific procedures that must be followed by Federal agencies to determine potential environmental impacts that may result from implementation of a proposed action and to diligently address alternatives for minimizing potential environmental impacts, while still accomplishing the agency’s mission. In addition, EO 12114, Environmental Effects Abroad of Major Federal Action, requires an environmental analysis for major actions conducted outside the United States (the global commons or within the territory of another nation) to determine whether there is a potential for significant environmental impacts.

A Categorical Exclusion (CATEX) to NEPA/EO 12114 was signed by the NGEN PM on 28 December 2010; therefore no Environmental Assessment or Environmental Impact Statement (EIS) is required. Five categorical exclusions were identified and each was addressed in the CATEX letter as follows:

• CATEX #3 – Routine use and operation of existing facilities, laboratories, and equipment.

• CATEX #7 – Routine procurement of goods and services conducted IAW applicable procurement regulations, executive orders, and policies.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

• CATEX #8 - Routine repair and maintenance of NOCs, Security Operations Centers, buildings, facilities, vessels, aircraft and equipment associated with existing operations and activities. (e.g., localized pest management activities, minor erosion control measures, painting, and refitting)

• CATEX # 12 - Routine procurement, management, storage, handling, installation, and disposal of commercial items, where the items are used and handled IAW applicable regulations. (e.g., consumables, electronic components, computer equipment and pumps)

• CATEX #36 - Acquisition, installation, and operation of utility (e.g., water, sewer, electrical) and communication systems, (e.g., data processing cable and similar electronic equipment) which use existing rights of way, easements, distribution systems, and/or facilities.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

For Official Use Only - Contains Acquisition Sensitive Information A-1

APPENDIX A

ACRONYMS

Acronym Description

ACAT Acquisition Category AMP Asset Management Plan AMIP Asset Management Implementation Plan AS Acquisition Strategy ASN (I&E) Assistant Secretary of the Navy (Installations and Environment) ASN (RDA) Assistant Secretary of the Navy (Research, Development & Acquisition) BAN Base Area Network BIC Business Initiatives Council CATEX Categorical Exclusion CFR Code of Federal Regulations CHENG Chief Engineer CIO Chief Information Officer CMP Configuration Management Plan CMIP Configuration Management Implementation Plan CONOPS Concept of Operations CoSC Continuity of Service Contract CO/CO Contractor-Owned/Contractor Operated COTS Commercial Off-The-Shelf CSIA Cyber Security Information Assurance DAG Defense Acquisition Guide DISA Defense Information Systems Agency DISN Defense Information Systems Network DLA Defense Logistics Agency DoD Department of Defense DoDD Department of Defense Directive DoDI Department of Defense Instruction DON Department of the Navy DRMS Defense Reutilization and Management Service EDS Electronic Data System EIS Environmental Impact Statement EO Executive Order EPEAT Electronic Product Evaluation Assessment Tool ES Enterprise Services ESI Enterprise Software Initiative ESOH Environment, Safety, and Occupational Health FDD Full Deployment Decision FFP Firm Fixed Price FOIA Freedom of Information Act FoS Family of Systems FTD Full Transition Decision FY Fiscal Year

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

A-2

GIG Global Information Grid GO/CO Government-Owned/Contractor-Operated GO/GO Government-Owned/Government-Operated GOTS Government Off-The-Shelf GPR Government Purpose Rights HAZMAT Hazardous Material HM Hazardous Materials HMMP Hazardous Materials Management Program HSI Human Systems Integration HSIP Human Systems Integration Plan HW Hardware IA Information Assurance IAW In Accordance With IDE Integrated Data Environment IF Infrastructure IMS Integrated Master Schedule IPPD Integrated Process and Product Development IPT Integrated Product Team IT Information Technology ITIL V3 Information Technology Infrastructure Library Version 3 ITSM Information Technology Service Management LAN Local Area Network LCSP Life Cycle Sustainment Plan LOE Level of Effort MAGTF Marine Air-Ground Task Force MAIS Major Automated Information System MAR MAIS Annual Report MARADMINS Marine Administrative Messages MARCORSYSCOM Marine Corps Systems Command MCEITS Marine Corps Enterprise Information Technology Services MCHS Marine Corps Common Hardware Suite MCNIS Marine Corps Network and Infrastructure Services MCNOSC Marine Corps Network Operations and Security Command MCSELMS Marine Corps Software Enterprise License Management Systems MD Management Domain MITSC MAGTF IT Support Centers MIL-STD Military-Standard MS Milestone MSDS Material Safety Data Sheets NDI Non-Developmental Item NEN Naval Enterprise Networks NEPA National Environmental Protection Act NetOps Network Operations NGEN Next Generation Enterprise Network NII Networks and Information Integration

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

A-3

NMCI Navy/Marine Corps Intranet NNE Naval Networking Environment NOC Network Operations Center OCONUS Outside Continental United States OEBGD Overseas Environmental Baseline Guidance Document OH Occupational Health OIPT Overarching Integrated Product Team ONE-NET OCONUS Navy Enterprise Network OPNAVINST Office of Chief of Naval Operations Instruction OSD Office of the Secretary of Defense OSHA Occupational Safety and Health Administration P2 Pollution Prevention PEO Program Executive Office PEO-EIS Program Executive Office - Enterprise Information Systems

PESHE Programmatic Environment, Safety, and Occupational Health Evaluation

PM Program Manager PMO Program Management Office POA&M Plan of Actions and Milestones PSI Product Support Integrator PSM Product Support Manager RFP Request for Proposal RMB Risk Management Board RMP Risk Management Plan S&OH Safety and Occupational Health SDS System Design Specification SE Systems Engineering SE&I Systems Engineering & Integration SECNAVINST Secretary of the Navy Instruction SEP Systems Engineering Plan SoS System of Systems SPAWAR Space and Naval Warfare Systems Command SW Software SYSCOM Naval Systems Command T&E Test and Evaluation USD Under Secretary of Defense USD (AT&L) Under Secretary of Defense for Acquisition Technology and Logistics USMC United States Marine Corps USN United States Navy WG Working Group WIPT Working Integrated Product Team

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

A-4

APPENDIX B

LIST OF REFERENCES

[1] U. S. Government, United State Code, National Environmental Policy Act (NEPA),Title

42 – The Public Health and Welfare, Chapter 55 – National Environmental Policy, Sec.

4321. Congressional Declaration of Purpose [Page 761-789], http://frwebgate1.access.gpo.gov/cgi-bin/TEXTgate.cgi?WAISdocID=4U4Y0H/1/1/0&WAISaction=retrieve.

[2] U. S. Government, Executive Branch, United States Code, National Fire Protection Association (NFPA) Codes and Regulations, Title 50 – War and National Defense, Chapter 15 – National Security, Sec. 401. Congressional Declaration of Purpose [CITE:

50USC401] [Page 48-63], http://frwebgate4.access.gpo.gov/cgi-bin/TEXTgate.cgi?WAISdocID=283274338491+11+1+0&WAISaction=retrieve.

[3] U. S. Government, Legislative Branch, United States Code, Resource Conservation &

Recovery Act (RCRA), Title 16 – Conservation, Chapter 54 – Resource Conservation, Chapter 54 – Resource Conservation, Subchapter V – Resource Conservation and Development Program, Sec. 3452. Resource Conservation and Development Program, [CITE: 16USC3452], [Page 2067], http://frwebgate2.access.gpo.gov/cgi-bin/TEXTgate.cgi?WAISdocID=d98rcY/3/1/0&WAISaction=retrieve.

[4] U. S. President, Executive Order no. 12114. “Environmental Effects Abroad of Major

Federal Actions.” Code of Federal Regulations (CFR), 1979 Comp.

http://www.archives.gov/federal-register/codification/forward.html.

[5] U. S. Department of Defense, Operation of The Defense Acquisition System, Department of Defense Directive (DoDD) 5000.02D. Washington, DC: DoD, May 12, 2003, http://www.dtic.mil/whs/directives/corres/pdf/500002p.pdf.

[6] U. S. President, Executive Order no. 13423 “Strengthening Federal Environmental, Energy, and Transportation Management” Code of Federal Regulations (CFR), 1979 Comp. http://edocket.access.gpo.gov/2007/pdf/07-374.pdf.

[7] U. S. Department of Defense, Department of Defense Regulation Storage and

Warehousing Facilities and Services, DoD 4145.19-R-1, Headquarters Department of the Army, Washington, DC: 15 Jun 1978, http://www.dtic.mil/whs/directives/corres/pdf/414519r.pdf

[8] U. S. Department of Defense, Department of Defense Standard Practice for System Safety, MIL-STD-882E. Washington DC: DoD, 11 May 2012.

[9] U. S. Department of Defense, Department of Defense Design Criteria, Human

Engineering, MIL-STD-1472F. Washington DC: DoD, 23 August 1999, http://www.hf.faa.gov/docs/508/docs/milstd14.pdf.

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

B-2

[10] U. S. Department of Defense, Undersecretary of Defense, Memorandum for the Secretaries of The Military Departments: “National Aerospace Standard (NAS 411), “Hazardous Material Management Program,”19 Jan 1995, https://acquisition.navy.mil/rda/content/view/full/6583.

[11] U. S. Department of the Navy, Independent Logistics Assessment Handbook, Department of the Navy Guide for Conducting Independent Logistics Assessments, NAVSO-P 3692.

DON, September 2006.

[12] U. S. Navy, Office of the Chief of Naval Operations, Environmental Readiness Program

Manual, OPNAVINST 5090.1C. Washington, DC: DON, CNO, 30 Oct 07, http://doni.daps.dla.mil/ Directives/05000%20General%20Management%20Security %20and%20Safety%20Services/05-00%20General%20Admin%20and%20 Management%20Support/5090.1C%20 %20Instruction%20and%20Chapters.pdf

[13] U. S. Navy, Office of the Chief of Naval Operations, Navy System Safety Program

Policy, OPNAVINST 5100.24B. Washington, DC: DON, CNO, 6 Feb 2007, http://doni.daps.dla.mil/ Directives/05000%20General%20Management%20Security %20and%20Safety%20Services/05-100%20Safety%20and%20Occupational%20Health %20Services/5100.24B.PDF.

[14] Department of the Navy, Secretary of the Navy, DASN(RD&A)ALM, Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System, SECNAVINST 5000.2E, Washington DC: 01 September 2011 http://doni.daps.dla.mil/Directives/05000%20General%%20and%20Safety%20 Services/05-00%20General%20Admin%20and%20Management%20Support/5000.2E.

pdf.

[15] Department of the Navy, Secretary of the Navy, ASN (I&E), Environmental Planning For the Department of the Navy Actions, SECNAVINST, Washington DC: 26 April 2004, http://doni.daps.dla.mil/Directives/05000%20General%20Management%20Security%20a nd%20Safety%20Services/05-00%20General%20Admin%20and%20Management%20 Support/5090.6A.pdf.

[16] U. S. Navy, Commander, Naval Sea Systems Command, “Naval Lithium Battery Safety

Program,” NAVSEAINST 9310.1B, 13 Jun 1991, http://www.navsea.navy.mil/ NAVINST/09310-001B.pdf.

[17] U. S. Department of the Navy; Commander, Space and Naval Warfare Systems

Command, Logistics Planning Guidance (LPG) and Preferred Formats, 19 Nov 2007, http://www.delreysys.com/lpg/.

[18] U. S. Department of the Navy; Commander, Space and Naval Warfare Systems

Command, Navy Occupational Safety and Health (NAVOSH) Program for Space and Naval Warfare Systems Command (SPAWAR), http://enterprise.spawar.navy.mil/docs/5100_15.pdf.

http://doni.daps.dla.mil/

Naval Enterprise Networks NGEN_Programmatic_Environment_Safety_and_Occupational

B-3

[19] U. S. Department of the Navy, Headquarters Marine Corps, Commandant of the Marine

Corps, Marine Corps Occupational Safety and Health (OSH) Policy Order, MCO 5100.8, 15 May 2006, http://www.marines.mil/news/publications/Documents/MCO%205100.8.pdf.

[20] U.S. Navy, Next Generation Enterprise Network (NGEN), NGEN Risk Management Plan, Version 4.0, Washington DC: Department of Navy, PEO-EIS, 20 May 2013.

[21] U.S. Department of Defense, Defense Technical Information Center, http://www.dtic.mil/descriptivesum/Y2012/Navy/0602131M_2_PB_2012.pdf.

1.0 INTRODUCTION AND PROGRAM DESCRIPTION 1

2.0 ESOH MANAGEMENT AND PROGRAM INTEGRATION 2

3.0 ESOH RISK MANAGEMENT 3

4.0 ESOH REGULATION COMPLIANCE 6

5.0 P2, GREEN PROCUREMENT, AND HM MANAGEMENT 7

6.0 NEPA AND EO 12114 9

APPENDIX A ACRONYMS A-1

1.0 INTRODUCTION AND PROGRAM DESCRIPTION

1.1 System Purpose, Description, and Status Overview

1.2 Schedule

2.0 ESOH MANAGEMENT AND PROGRAM INTEGRATION

2.1 Organizational Structure to Support NGEN

2.1.1 Working Integrated Product Teams and Working Groups

3.0 ESOH RISK MANAGEMENT

The PM NEN and the Risk Management Team are responsible for accepting or rejecting all risk candidates as part of the overall Risk Management Process for the NGEN Program. The enterprise risk and issue registry tool utilized by the NGEN Program to re...

3.1 ESOH System Safety Management

3.1.1 The NGEN Program fully endorses system safety management principles based on the MIL-STD-882E, and establishes the following ESOH objectives:

3.2 Software System Safety

3.3 Occupational Health

4.0 ESOH REGULATION COMPLIANCE

5.0 P2, GREEN PROCUREMENT, AND HM MANAGEMENT

5.1 Pollution Prevention

5.2 Green Procurement

5.3 HM Management

5.4 Disposal

5.4.1 Demilitarization and Disposal Planning

6.0 NEPA AND EO 12114

N65236-USMC-BTI-PESHE-0001

BTI PESHE

Marine Corps Systems Command

Emergency Response Systems

Base Telecommunication Infrastructure

Programmatic Environment, Safety, and

Occupational Health Evaluation

Program Manager Information System & Infrastructure

Product Manager Emergency Response Systems

Prepared by:

August 2016, Version 1.0

Space and Naval Warfare Systems Center Atlantic

P.O. Box 190022

North Charleston, South Carolina 29419-9022

DISTRIBUTION STATEMENT D: Distribution is only authorized to Department of Defense (DoD) agencies and

U.S. DoD contractors only for Administrative or Operational Use. Request for authorization to distribute this document to others shall be sent to Space and Naval Warfare Systems Center (SPAWARSYSCEN) Atlantic, Charleston, SC.

Unclassified/For Official Use Only ii

THIS PAGE INTENTIONALLY LEFT BLANK

iii

Record of Changes

Date Revision Reason for Change Description

December 2012 V0.01 NSWC Draft Version

July 2013 V0.02 Incorporated MCSC Changes

July 2016 V0.03 Incorporated MCSC Changes

August 2016 V1.0 MCSC Initial Release iv v

Marine Corps Systems Command (MCSC)

Program Manager Information Systems & Infrastructure (PM IS&I)

Product Manager Emergency Response Systems (PdM ERS) Base Telecommunications Infrastructure (BTI)

Programmatic Environment, Safety and Occupational Health Evaluation (PESHE)

Prepared by:

Liza Brown

BTI Systems Engineer

Information Systems & Infrastructure

Marine Corps Systems Command, Quantico, VA

Date

Concurrence by:

Joseph Murgo

Product Manager, Emergency Response Systems

Andy Mittura

Assistant Product Manager – Engineering, ERS

Carroll CIV Thomas W

Assistant Program Manager – Engineering, PMM110 Information Systems & Infrastructure

Approved by:

Harry G. Oldland – Program Manager vi vii

TABLE OF CONTENTS

Executive Summary ..................................................................................................................... ix

1 Introduction and Purpose .................................................................................................. 1-1

1.1 Program Overview ....................................................................................................... 1-1

1.1.1 Mission Need and Major Program Objectives ....................................................... 1-1

1.1.2 System Description ................................................................................................ 1-1

1.1.3 Acquisition Strategy/Type of Acquisition ............................................................. 1-4

1.1.4 Program Master Schedule ...................................................................................... 1-5

1.2 Program ESOH Goals .................................................................................................. 1-6

2 Approach for Integrating ESOH Considerations into the Acquisition and Systems

Engineering Processes ........................................................................................................ 2-1

2.1 ESOH Risk Management – Program ESOH Organization, Roles and

Responsibilities ............................................................................................................ 2-1

2.1.1 Government ESOH Responsibilities...................................................................... 2-2

2.1.2 Contractor ESOH Responsibilities ........................................................................ 2-2

2.1.3 Customer Responsibilities ..................................................................................... 2-2

2.1.4 ESOH Responsibilities of Key Program Authorities ............................................. 2-2

2.2 Approach to Identify and Manage ESOH Risks .......................................................... 2-2

2.2.1 Hazard Risk Assessment ........................................................................................ 2-2

2.2.2 ESOH Risk Management Strategy – Risk/Hazard Identification, Tracking, and

Mitigation .............................................................................................................. 2-4

2.2.3 Risk Acceptance/Close Out Methodology ............................................................. 2-4

2.3 ESOH Integration into the Acquisition Strategy ......................................................... 2-5

2.4 ESOH Integration into the Systems Engineering Strategy .......................................... 2-5

2.5 Approach for Integrating ESOH into Test and Evaluation Planning and Reporting ... 2-5

2.6 ESOH Integration into Demilitarization/Disposal Planning ........................................ 2-5

2.7 ESOH Integration into Key Program Documents ........................................................ 2-6

3 National Environmental Policy Act / Executive Order 12114 Compliance ................... 3-1

3.1 NEPA Strategy ............................................................................................................. 3-1

3.2 NEPA Compliance Schedule ....................................................................................... 3-1

3.3 Categorical Exclusion .................................................................................................. 3-5

4 Management of Hazardous Materials .............................................................................. 4-1

4.1 Hazardous Material and Hazardous Waste Management Program ............................. 4-1

4.2 HAZMAT Use Summary ............................................................................................. 4-1

4.2.1 Locations and Quantities of HAZMAT in the System .......................................... 4-2

4.2.2 Special HAZMAT Training, Handling, and Storage Needs ..............................