A.02_Appendix_A-G.pdf

DD FORM 2772, SEP 1998 REPLACES MT FORM 352-R, WHICH IS OBSOLETE. Adobe Professional 8.0

MEMORANDUM OF UNDERSTANDING

BETWEEN

U.S. ARMY CORPS OF ENGINEERS

Portland District

Lock & Dam Cascade Locks, Oregon, 97014

AND

(Company Name) (Location/Project Name)

(Street Address) (City, State, Zip Code)

PURPOSE: To create a Memorandum of Understanding (MOU) between the Army Corps of Engineers, Portland District, and the (Company Name). To establish an interoperability agreement authorizing personnel of (Company Name) at (Project Name) Lock & Dam to use radio frequencies assigned to the Army Corps of Engineers.

This MOU establishes permission for (Company Name)to use Corps of Engineers frequencies for purpose of communicating with Corps of Engineers security personnel in accordance with Local, State, and Federal policies. As a result of this agreement, (Company Name) personnel will be authorized to operate on the Corps of Engineers designated frequencies listed below.

AUTHORIZED FREQUENCIES:

Frequency ___________________________ (MHz)

Frequency ___________________________ (MHz)

It is understood (Company Name) will be responsible for the acquisition and maintenance of necessary radio equipment needed to operate on radio frequencies owned by the Corps of Engineers. Use is intended strictly for communications between (Company Name) and Corps of Engineers. No (Company Name) internal communications are permitted. (Company Name)will follow all technical standards and operating procedures for the proper use of Army Corps frequencies at all times. Cloning of radios may be allowed at the discretion of the COR.

POINTS OF CONTACT: Primary points of contact for any technical and/or operational purposes:

Army Corps of Engineers: ____________________________ _______________________ Printed Name Phone Number

(Company Name): ____________________________ _______________________ Printed Name Phone Number

This Memorandum of Understanding will become effective on the date of last signature, and will remain in effect until terminated by one or both parties. This MOU may be modified by mutual agreement of the Parties. Either party may cancel this agreement upon 90 days written notice to the other party.

PARTIES TO THE AGREEMENT

This Memorandum of Understanding is agreed upon this _________ day of ________ 20_____.

CORPS OF ENGINEERS:

Signature: _____________________________________________

Title: __________________________________________________

Address: _______________________________________________

Phone: ________________________________________________

(Company Name):

Signature: _____________________________________________

Title: __________________________________________________

Address: _______________________________________________

Phone: ________________________________________________

Appendix G: REGULATORY GUIDANCE

Regulatory Compliance:

˗ Oregon Department of Public Safety Standards and Training (DPSST) ˗ State of Washington Professional Licensing for Private Security Guards ˗ U.S. Army Regulations and other regulations listed in section 15 of this PWS ˗ 29 Code of Federal Regulation (CFR) 1910, Occupational Safety and Health Standards for General

Industry ˗ U.S. Army Corps of Engineers (USACE) Safety Manual (EM 385-1-1, dated 30 November 2014)

[http://www.usace.army.mil/SafetyandOccupationalHealth.aspx] ˗ NERC Critical Infrastructure Protection (CIP) regulations, particularly CIP-004, CIP-006, and CIP-007 ˗ Manufacturers’ operation/maintenance specifications for materials supplied by the Contractor.

Other Regulations:

˗ Army Regulation 190-56, The Army Civilian Police and Security Guard Program, dated 15 March 2013 ˗ Army Regulation 190-11, Physical Security of Arms, Ammunition, and Explosives dated 5 September

˗ Army Regulation 190-14, Carrying of Firearms and Use of Force for Law Enforcement and Security

Duties, dated 12 March 1993 ˗ Army Regulation 600-85, The Army Substance Abuse Program, dated 28 December 2012 ˗ Army Regulation 25-2, Information Assurance dated 24 October 2007 (Rapid Action Revision 23 March

2009) ˗ Army Regulation 380-67 Personnel Security Program ˗ Army Regulation 190-51 Security of Unclassified Army Property (Sensitive and Non-sensitive) ˗ ST 19-085, Department of the Army Civilian Security Guard Field Training Manual ˗ TSP 191-AS-0001 Active Shooter Response ˗ TSP-191-SG-001, Department of the Army Civilian Security Guard Oregon Department of Public Safety

Standards and Training (DPSST) ˗ State of Washington Professional Licensing for Private Security Guards ˗ Revised Code of Washington (RCW) 18.170 Security Guards ˗ RCW 9.41 Firearms and Dangerous Weapons ˗ Washington Administrative Code (WAC) 308-18 Private Security Guard Companies and Private Security

Guards ˗ Homeland Security Presidential Directive 12: Policy for a Common Identification Standard for Federal

Employees and Contractors ˗ Army Directive 2011-08, Army Implementation of Homeland Security Presidential Directive 12 ˗ 29 Code of Federal Regulation (CFR) 1910, Occupational Safety and Health Standards for General

Industry (OSHA) ˗ EM 385-1-1, USACE Safety and Health Requirements, dated 30 November 2014 ˗ National Institute of Justice (NIJ) Ballistic Resistance Standard 0101.06 ˗ Executive Order 12564, Drug Free Federal Workplace ˗ US Army Public Health Command - Work/Rest/Water Consumption Table, CP-033-0811 ˗ 18 USC 922(g)(9) Domestic Violence Offender Gun Ban (aka Lautenberg Amendment to the Gun Control

Act of 1968) ˗ Privacy Act of 1974, 5 U.S.C. § 552a ˗ USACE Radio Frequency Memorandum of Understanding ˗ ER-25-1-111 Information Management Radio/Satellite Transmission systems and Frequency Management

Policy, dated 14 May 2015 ˗ NERC Critical Infrastructure Protection (CIP) regulations, particularly CIP-004, CIP-006, and CIP-007 ˗ FAR 52.212-4 Contract Terms and Conditions – Commercial Items ˗ Army Training Support Package TSP-191-SG-0001 ˗ ASTM F 2413-11 (Standard Specification for Performance Requirements for Protective (Safety) Toe Cap

Footwear ˗ ANSI/ISEA Z89.1-2014 Industrial Head Protection http://www.usace.army.mil/SafetyandOccupationalHealth.aspx http://www.usace.army.mil/SafetyandOccupationalHealth.aspx

DEPARTMENT OF THE ARMY ER 25-1-111

U.S. Army Corps of Engineers

CECI-PID-IP Washington, DC 20314-1000

Regulation No. 25-1-111

Information Management

RADIO/SATELLITE TRANSMISSION SYSTEMS

AND

FREQUENCY MANAGEMENT POLICY

14 May 2015

1. Purpose. This regulation establishes and implements policy and guidance for the governance of the U.S. Army Corps of Engineers (USACE) Transmission Systems (i.e. HF/VHF/UHF, microwave, satellite, etc.) and Frequency Management practices.

2. Applicability. This policy applies to all U.S. Army Corps of Engineers (United States and its Possessions (US&P)) elements. Sites minimally supported by ACE-IT are still required to abide by these policies since this regulation is based on DoD policies/ directives and Army regulations as defined. Systems and/or equipment requiring frequencies to operate must be coordinated with the Radio Systems Design Branch as described in section 6 (regardless of intended operations in federal or unlicensed frequency bands). Examples include: HF Single Sideband; VHF/UHF land mobile radios (LMR); maritime radio systems; Geostationary Operational Environmental Satellite (GOES) radios; wireless paging systems; frequency-dependent survey equipment; point-to-point microwave systems, Very Small Aperture Terminal (VSAT) satellite systems and services. All radio equipment operating primarily in federal bands requires adherence to federal rules and regulations for military, civil works, and emergency operations missions. Additionally, all long-haul satellite services (i.e. VSAT) are to be obtained from the Defense Information Systems Agency (DISA) via ACE-IT Radio Systems Design Branch.

3. Distribution Statement. This document is approved for public release. Distribution is unlimited.

4. References.

a. DoD Land Mobile Policy Memorandum. 3 Aug 01

b. JP 6-0, Joint Communications System, 10 June 2010. http://www.dtic.mil/doctrine/ new_pubs/jointpub_communications.htm

c. DoD Directive 4650.1, Policy and Procedures for Management and Use of the Electromagnetic Spectrum, 9 Jan 2009. http://www.dtic.mil/whs/directives/corres/pdf/465001p.pdf

This Regulation supersedes ER 25-1-111, dated 30 April 2012

ER-25-1-111

14 May 15

d. DoD Directive 5100.35, Military Communications Electronics Board, 10 Mar 1998.

http://www.dtic.mil/whs/directives/corres/pdf/510035p.pdf .

e. AR 5-12, Army Use of the Electromagnetic Spectrum, 15 Feb 2013.

http://www.army.mil/usapa/epubs/pdf/r5_12.pdf.

f. AR 25-13, Telecommunications and Unified Capabilities, 25 Mar 2013.

http://www.apd.army.mil/jw2/xmldemo/r25_13/main.asp.

g. Manual of Regulations and Procedures for Federal Radio Frequency Management- (Redbook), May 2014 Revision of the May 2013 Edition. www.ntia.doc.gov/osmhome /redbook/redbook.html.

h. Military Communications Electronics Board MCEB Pub 7, Standard Frequency Action Format (SFAF), 31 Dec 2003. https://acc.dau.mil/adl/en-US/283278/file /43444/MCEB%20Pub%207.pdf .

i. Military Communications Electronics Board MCEB Pub 8, Standard Spectrum Resource Format (SSRF). http://www.disa.mil/Services/Spectrum/Enterprise-Services/MCEB-Pub-8.

j. Military Communications Electronics Board Pub 1.

k. USACE Campaign Plan FY13-18 (Goal 4: Prepare for Tomorrow).

l. ER 1110-2-248 Engineering and Design Requirements for Water Data Transmission Using GOES/DCS, 13 Mar 1981. http://www.publications.usace.army.mil/Portals/76/ Publications/EngineerRegulations/ER_1110- 2-248.pdf.

m.. Asst. Sec. of Defense/NII DoD CIO Memorandum, Base and Long-Haul Telecommunications Equipment and Services, 10 May 07.

5. Introduction.

a. The ACE-IT Radio Systems Design Branch has the missions of coordinating, facilitating and processing of requisitions to obtain and maintain authorized radio frequency assignments through/from the appropriate authoritative federal agencies. Frequencies are approved and forwarded from the National Telecommunications and Information Administration (NTIA), part of the Department of Commerce, to the Army Spectrum Management Office (ASMO).

Approved USACE frequency assignments are then managed by ACE-IT Radio Systems Design Branch and coordinated with the DoD’s Joint Spectrum Center (JSC), the organization that has oversight of Army frequency management activities. The JSC specifies the hardware/software and procedures for the transmittal, receipt and usage of radio frequency items. In addition, the Radio Systems Design Branch continuously collaborates with the ASMO and other federal, state and local agencies regarding frequency related matters.

b. All frequencies, radio/satellite equipment and associated service needs must be coordinated through the ACE-IT Radio Systems Design Branch. Members of this branch perform a wide range of wireless services with a single streamlined process. These services range from radio/satellite repair to major infrastructure improvement projects.

6. Policy.

a. This policy implements governance of IT systems discussed in Paragraph 2 above. It is effective immediately unless an exemption is obtained from the CIO’s office.

b. All radio equipment will be P25 capable & JF12 compliant as mandated by the DoD Land Mobile Policy Memorandum, Dtd. 3 Aug 01 and AR 25-12, Army Use of the Electromagnetic Spectrum. The purpose for operation, whether military or civil, is irrelevant as the equipment will be operating primarily in federal bands and must adhere to the federal regulations. Since USACE is an Army Command, equipment purchased for the organization is part of the Army’s inventory. Compliance is required regardless of the type of funds used to purchase the equipment. All Army-acquired equipment operating primarily in federal bands requires adherence to federal rules and regulations for military, civil works, and emergency operations missions.

c. Frequency authorizations are obtained through Army channels, not the Federal Communications Commission (FCC). Authorizations can only be given if the equipment is properly certified.

d. The P25-compliant radios ensure future compatibility with both digital and analog systems.

There is a growing need to communicate with other agencies (i.e. local law enforcement, Homeland Security, FEMA, etc.). The P25 standard will support that compatibility requirement and also proactively align USACE for future NTIA digital compliance initiatives.

e. To allow for the appropriate engineering analysis/coordination and to obtain the necessary clearance for a new frequency assignment, frequency requests will be submitted to ACE-IT via an ACE-IT Enterprise Service Desk (ESD) ticket prior to the proposed operational date and prior to procurement of equipment. Based on AR 5-12, funds for the research, development, production, purchase, lease or use of frequency-dependent items will not be released by the obligating authority until supportability has been established. No frequency- dependent "off-the-shelf" or other non-developmental system shall be purchased or procured without this supportability determination. Supportability will be determined by ACE-IT Radio Systems Design Branch.

f. In accordance with AR 25-13, Telecommunications and Unified Capabilities, all VSAT Services must be procured through DISA. Commercial wideband services are procured by DISA under a contract vehicle. All services and agencies are required to procure their long-haul communications services through DISA unless a waiver is granted by the Office of the Secretary of Defense (OSD). The only permitted method to obtain VSAT equipment and services is to open a ticket with the ACE-IT ESD. A Radio Systems Design Branch Subject Matter Expert (SME) will be assigned to coordinate the effort.

Other specialized radio systems are also required to adhere to these policies:

(1) Geostationary Operational Environmental Satellite (GOES): New requests for assignment of radio frequencies for operation of the GOES Data Collection Platforms (DCP) shall be submitted to ACE-IT Radio Systems Design Branch.

(2) Ship Radio Authorization (SRA) is a license authorizing vessels to use transmitting and receiving equipment aboard a ship for communications. This is required by international treaty. Maritime Mobile Service Identity (MMSI) is a series of 9 digits which are transmitted over the radio that uniquely identifies the ship's station. Requests and renewals of SRAs and MMSIs for Corps of Engineers vessels shall be submitted by the ACE-IT Radio Systems Design Branch. Upon deactivation or disposal of a land or vessel station, a request for cancellation of the SRA and MMSI must be submitted to ACE-IT Radio Systems Design Branch for upward processing.

g. No other IT solutions and/or services or changes to any part of its architecture will be authorized unless a waiver from the CIO’s office has been granted.

h. Exemptions/waivers to portions of this policy can be granted by the office of the CIO. A complete business case is required to request an exemption. For frequency management and radio/satellite systems information please contact CEIT-EDT-R Chief, gregory.s.formosa@usace.army.mil (412) 395-7410. For policy guidance please, contact the CEIT-PMP, Project Manager, janice.m.dewitt@usace.army.mil (412) 395-7411.

FOR THE COMMANDER:

Appendix A - List of Acronyms MICHAEL D. PELOQUIN

COL,EN

Chief of Staff

ER 25-1-111

APPENDIX A

List of Acronyms

ACE-IT Army Corps of Engineers Information Technology AR Army Regulation ASMO Army Spectrum Management Office CIO Chief Information Officer DCP Data Collection Platforms DISA Defense Information Systems Agency DoD Department of Defense ER Engineering Regulation ESD Enterprise Service Desk FCC Federal Communications Commission FEMA Federal Emergency Management Agency GOES Geostationary Operational Environmental Satellite ITPM Information Technology Project Manager JSC Joint Spectrum Center LMR Land Mobile Radio MCEB Military Communications-Electronics Board MMSI Maritime Mobile Service Identity NTIA National Telecommunications and Information Administration OMB Office of Management and Budget OSD Office of the Secretary of Defense RF Radio Systems and Frequency Management SME Subject Matter Expert SRA Ship Radio Authorization VSA Very Small Aperture Terminal USACE United States Army Corps of Engineers US&P United States and its Possessions

A-1

ER 25-1-111

THIS PAGE INTENTIONALLY LEFT BLANK

A-2

Month February Year

City

Describe The Case

(B1) (B2) (B3) (C) (D) (F)

USACE Office Overseeing Work

Enter the number of days the injured or ill worker was:

Using these categories, check ONLY the most serious result for each case:Job Title

(e.g., Welder)

US Army Corps of Engineers

USACE PRIME CONTRACTOR

Pr im e or

S ub

(P o r S

Company Name

(A)

Ag e

G en de r

(E) Where the event occurred (e.g. Loading dock north end)Date

Employee Began

Work on Job

Covered by

Contract

Monthly Record of Work-Related Injuries/Illnesses & Exposure

In accordance with the provisions of EM 385-1-1, Section 01 Program Management, Paragraph 01.D Accident Reporting and Recording, sub-paragraphs 01.D.05, you (the Prime Contractor) shall provide a monthly record of all exposure and accident experience incidental to the work (this includes exposure and accident experience of the Prime Contractor and its sub-contractor(s). As a minimum , these records shall include exposure work hours and a record of occupational injuries and illnesses that include the data elements listed below. Definitional criteria for each data element is found in 29 CFR Part 1904. If the maintenance of OSHA 300 Logs are required by OSHA, most of this information can be obtained from those logs. If data on log provided below is revised after it is submitted to USACE, Contractor shall provide a revised report to the GDA. You must complete the USACE ENG Form 3394, Report of Accident Investigation Report for all recordable accidents. If you're not sure whether a case is recordable, call your local Safety and Occupational Health Office for help.

Project Title

Describe injury or illness, parts of body affected, and object/substance that directly injured or made person ill (e.g. Second degree burns on right forearm from acetylene torch)

Check the "injury" column or choose one type of illness:

Contractor Name

USACE PORTLAND DISTRICT

Security Services for the Bonneville Dam, The Dalles Dam & John Jay Dam State

Contract Number

USACE Command

Date of injury or onset of illness

Classify the caseIdentify the person

(G) (H) (I) (J) (K) (L) (1) (2) (3) (4) (5) (6)

0 0 0 0 0 0 0 0 0 0 0 0 Type of Contract (Choose One):

Construction Opn & Main. Civil Works Eng. Services Military Programs Dredging Other Rsch. & Dev.

Emerg. Opns.

Other

Ordinance/Expl. Cleanup Environmental Other

For Government Use Only TYPE OF WORK ACTIVITY (Choose One):

Environmental Remed.

Superfund

Date

Exposure Hours Month

__1_ of _1_

Page

Job transfer or restriction

Enter the number of days the injured or ill worker was:

Remained at work

Using these categories, check ONLY the most serious result for each case:

Al l o th er

Ill ne ss es

Death

Job Title (e.g., Welder)

Sk in

D is or de r

R es pi ra to ry

C on di tio n

Po is on in g

H ea rin g

Lo ss

(M)

Pr im e or

S ub

(P o r S

Company Name Ag e

G en de r Where the event occurred (e.g. Loading dock north end)Date

Employee Began

Work on Job

Covered by

Contract

(mo./day)

FUSRAP

IRP

Year to Date

Days away from work

Signature

Certification of Record

Name of Person Submit. RecordFUDS

Describe injury or illness, parts of body affected, and object/substance that directly injured or made person ill (e.g. Second degree burns on right forearm from acetylene torch)

Check the "injury" column or choose one type of illness:

On job transfer or restriction (days)

Away from work (days)

In ju ryOther record-able cases

Date of injury or onset of illness cari.adamonis Typewritten Text cari.adamonis Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text X alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Rectangle alfred.garcia Rectangle alfred.garcia Rectangle alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Rectangle alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text alfred.garcia Typewritten Text