02-MACC_Gen_Rqmts-EMCS.pdf

ENERGY MANAGEMENT AND CONTROL SYSTEM (EMCS)

14 DEC 2017

1. Installation

1.1 Install all components, software, and programming necessary to incorporate the into the SAFB Johnson Controls Metasys Extended Architecture (MEA) Building

Automation System (BAS) Energy Management and Control System (EMCS).

1.2 Installing additional BAS components, software, and programming, including but not limited to controllers, integrators, and network automation engines, media converters, patch cords, and LAN cabling which may be necessary to integrate the new into the existing BAS shall be included as a part of this contract at no additional cost.

1.3 A JCI MS-NAE55xx-x Network Automation Engine (NAE) shall be installed complete with battery, transformer, and enclosure. NAE shall be capable of supporting two BACNet MS/TP (RS-485) trunks.

1.4 The NAE shall include one Ethernet port; 10/100 Mb; 8-pin RJ-45 connector, two optically isolated RS-485 ports; 9600, 19.2K, or 38.4K baud; pluggable and keyed 4 position terminal blocks, two RS-232-C serial ports, with standard 9-pin sub-D connectors, that support all standard baud rates, two USB serial ports, standard USB connectors support an optional, user-supplied external modem

1.5 Provide for each piece of equipment where appropriate:

1.5.1 Start/stop control of supply and return fans, pumps, VAVs, etc.

1.5.2 Current status of supply and return fans, pumps, VAVs, etc.

1.5.3 Zone temperature control.

1.5.4 Supply and return water temperatures and pressures.

1.5.5 Cold deck, hot deck, zone, discharge air, return air, and mixed air temperature control.

1.5.6 Current cold deck, hot deck, zone, discharge air, return air, outside air, and mixed air temperatures.

1.5.7 System static pressure control.

1.5.8 Discharge and return air CFM tracking control.

1.5.9 Supply CFM, return CFM, discharge static pressure, and system static pressures.

1.6 All BAS binary control points shall be configured for a maintained binary output (relay contact closure).

1.7 The chiller shall control all pumps, valves, and other ancillary equipment necessary for it to operate. (Only applicable to chillers.)

1.7.1 In BAS control mode, leaving water set point and maximum operating capacity shall be adjustable via the BAS.

1.7.2 In local control mode, chiller start and all set point functions shall be operated from the chiller control panel.

1.8 Label new devices and panels.

1.9 Check, test and commission system

FA440718R0002

Attachment 2

2. ENERGY MANAGEMENT AND CONTROL SYSTEM (EMCS) EQUIPMENT

COMPATIBILITY

2.1 It is the policy of Scott AFB that every new building or building renovations of significant size incorporate DDC as the means of HVAC control. The Scott AFB Civil Engineering Squadron sets policies and procedures for managing, operating, repairing, and maintaining installed equipment for Energy Management And Control System (EMCS). The complete system must consist of a single EMCS that monitors and controls mechanical equipment in all facilities containing centralized heating systems or air-conditioning units of 10-ton capacity or larger. The Air Force goal for EMCS expansion is to have a single EMCS at each base, to monitor and control facility energy consumption and utility metering. The existing base wide EMCS system is a Johnson Controls Inc. Metasys Extended Architecture Direct Digital Control (DDC) building automation system (BAS).

2.2 Equipment or Materials of equal quality, form, fit, and function: References in this statement to any brand name equipment or materials to be installed shall be regarded as establishing a standard of quality and shall not be construed as limiting competition. The contractor may submit for testing and approval, equipment or materials of equal quality, form, fit, and function as those listed in this statement of work.

2.2.1 To assure that all DDC controllers to be substituted for those listed in this statement of work are capable of communicating seamlessly with the existing Johnson Controls MEA BAS, the contractor will install and commission one controller of each type.

2.2.1.1 The Contractor shall provide all labor, equipment, materials, tools, software, programming, and transportation necessary to install, commission and operate the proposed substitute controller in a temporary “test bench” location as directed by the 375 CES Personnel. The controller will be installed complete with all proposed sensors, relays, transducers, etc.

2.2.1.2 The Contractor shall provide all labor, equipment, materials, tools, software, programming, and transportation necessary to temporarily add the proposed controller and its associated points to the existing Metasys network and database. Network access restrictions found elsewhere in this document apply.

2.2.1.3 EMCS Operations personnel will evaluate the performance of the proposed equipment and may at their discretion, contract with a third party company or agency to advise and assist them in determining the compatibility of the proposed equipment.

2.2.1.4 The EMCS System Manager shall be the final authority as to whether the proposed controller(s) meet the compatibility requirements of this statement of work.

2.2.1.5 The government accepts no liability for damages to the proposed controller(s), tools or test equipment supplied by the contractor.

2.2.1.6 The contractor assumes full responsibility for any damages to the existing Metasys networks caused by the installation of the proposed controller(s).

2.2.1.7 The Contractor shall provide all labor, equipment, materials, tools, software, programming, and transportation to restore the existing Metasys network and database to “pretest” conditions.

2.3 Absolutely no wireless devices, controllers, sensors, or other components may be installed.

2.4 No external connections to the EMCS network such as internet or dial in/out modem, exist or may be created.

FA440718R0002

2.5 All DDC controllers installed must be capable of communicating seamlessly with the existing Johnson Controls Ethernet protocol Metasys Extended Architecture (MEA) building automation systems (BAS).

2.5.1 To assure compliance, all heating, ventilation, and air conditioning (HVAC) equipment must have DDC controllers which communicate via BACNet Master-Slave/Token-Passing protocol (MS/TP) and are fully comply with ASHRAE’s BACNet "Protocol Implementation Conformance Statement" (PICS) and “BACNet Interoperability Building Blocks (BIBBs) requirements.

2.5.2 The EMCS System Manager may approve Johnson Controls proprietary N2 compatible devices in lieu of BACNet devices on a case by case basis.

2.6 Our standard BACNet buss baud rate is 38400. The EMCS System Manager must pre-approve any deviations from this baud rate.

2.7 All equipment and materials supplied shall conform to their respective manufacturer’s specifications and shall be the standard products of manufacturers regularly engaged in their production. All equipment and materials supplied shall be new items. No used, reconditioned or rebuilt equipment or materials shall be installed.

2.8 If the DDC controllers installed require software other than Johnson Controls CCT, HVACPro, GX-9100, XTM Configurator, DX Commissioning, or N2 Device Loader for programming and commissioning, the contractor shall provide and install a minimum of six copies of the required programming and commissioning software on computers designated by the EMCS Operations personnel.

2.8.1 The programming and commissioning software shall be licensed for use by the 375th Civil Engineering Squadron, Scott AFB, IL.

2.8.2 All original media, documentation, manuals, pamphlets, etc. which accompanied the software at purchase will become the property of the Government and will be stored in the EMCS control room in building 60.

2.8.3 The software must be capable of, and configured to allow the computer on which it is installed to program and commission its controller from any location in the EMCS network.

2.9 If the DDC controllers installed require software other than Johnson Controls CCT, HVACPro, GX-9100, XTM Configurator, DX Commissioning, or N2 Device Loader for programming and commissioning, the contractor shall provide a minimum of 40 hours of “hands on” classroom training in the use of the software to ten 375 CES personnel. The training will be given in two consecutive five day sessions on site at Scott AFB with five personnel in each class. At a minimum, the course shall include instruction in how to:

2.9.1 Access and read existing control strategies.

2.9.2 create control strategies for custom programs,

2.9.3 build side loops

2.9.4 Download and test existing configurations.

2.9.5 Download and test custom program’s configurations

2.9.6 Manually and automatically tune control loops

2.9.7 troubleshoot control programs

2.9.8 troubleshoot and repair controller hardware

FA440718R0002

3. PROGRAMMING AND COMMISSIONING

3.1 Personnel

3.1.1 TRAINING AND CERTIFICATIONS: The contractor shall possess, and all contractor employees performing work under this contract must have ready access to, the original manufacturer's most current manuals, bulletins, data sheets, etc. for all equipment and software installed, serviced and maintained under this contract. The contractor’s employees must follow the specified maintenance and repair procedures outlined in this literature.

3.1.2 Metasys Training: All contractor personnel performing work for the Johnson Controls BAS shall be trained and certified by Johnson Controls Inc. to perform this work. The contractor must have a working knowledge of JCI custom programming languages and be able to analyze and modify custom programming in JCI servers, workstations, and DDC controllers. The contractor must be able to create and modify dynamic graphics for Metasys controlled HVAC systems. Within seven (7) calendar days after contract award, the contractor shall provide training and certification documentation. Information on courses offered by Johnson Controls can be found at http://www.johnsoncontrols.com/cg-gls/.

3.1.3 Fiber Optic Training: The contractor must have on staff, personnel certified in the installation, repair and troubleshooting of single mode and multi-mode fiber optic cabling systems. Certification shall be through the Fiber Optic Association (FOA) or another nationally recognized university or telecommunications organization. In the event of a malfunction in the Metasys network, the personnel certified for installation, repair and troubleshooting of single mode and multi-mode fiber optic cabling systems must be available to perform the troubleshooting and repairs. Within seven (7) calendar days after contract award, the contractor shall provide training and certification documentation.

3.1.4 LAN Training: All contractor personnel performing work on the Johnson Controls Metasys MEA LAN must be trained and experienced in the installation, configuration, and troubleshooting of local and wide area networks and their components.

3.1.5 CCNP: The contractor must have on staff, personnel certified by Cisco Systems Inc.

as a Cisco Certified Network Professional (CCNP). In the event of a malfunction in the Metasys network, the CCNP must be available when needed for consultation with the contractor personnel performing the repairs. Within seven (7) calendar days after contract award, the contractor shall provide training and certification documentation.

3.1.6 Privileged Access Agreement Requirement: IAW DoD 8570.01-M para. C2.1.4. As a condition of privileged access to any information system, PERSONNEL PERFORMING IA FUNCTIONS described in this Manual must satisfy both preparatory and sustaining DoD IA training and certification requirements (see Chapters 3, 4, 5, 10, and 11). Additionally, personnel with privileged access must complete a “Privileged Access Agreement,” a sample of which is shown in DoD 8570.01-M Appendix 4, DoD Components may expand the requirements of this agreement to meet their needs.

3.1.6.1 Contractor personnel assigned IA responsibilities shall be required to access the Scott AFB NIPRNet to perform required IA training.

3.1.6.2 IAW DoD 8570.01-M para. C1.4.4.5. Contractors must secure at their own expense the appropriate background investigation to be granted NIPRNet access to perform their IA functions.

FA440718R0002

Attachment 2 http://www.johnsoncontrols.com/cg-gls/

3.1.6.3 IAW DoD 8570.01-M para. C3.2.4.8.5. All personnel must agree to release their certification qualification(s) to the Department of Defense.

3.1.6.4 Required IA training must be completed before access to the Scott AFB EMCS is granted.

3.2 REQUIRED PROGRAMMING AND COMMISSIONING: All work requirements in facilities connected to the Scott AFB EMCS shall include the required programming and commissioning necessary to integrate the new equipment into the existing Johnson Controls Metasys® network. This includes but is not limited to programming the controller, mapping all points into the existing Johnson Controls Metasys® system to be displayed and controlled from the existing workstations, and creating dynamic graphical representations of the HVAC equipment associated with this work. Graphics shall display current status, temperatures, pressures, and set points of covered HVAC equipment. Set points must be adjustable from both graphic and text views by 375 CES Personnel with the with appropriate password level access to adjust set points.

3.2.1 All programming and commissioning necessary to integrate the new equipment into the existing Johnson Controls Metasys® network shall be done by competent technicians skilled in the setting and adjustment of the BAS equipment used in this project. Technicians are to be factory trained and certified by Johnson Controls for this work and experienced in the type of HVAC systems associated with this project. Information on courses offered by Johnson Controls can be found at http://www.johnsoncontrols.com/cg-gls/.

3.2.2 Programming Equipment: Only government owned computers or storage devices may be connected to the EMCS network. Contractor owned netbooks, laptop, notebook, desktop or other computers, hard drives, portable flash memory device such as thumb drives etc. shall not be used. All custom programming, graphics, database additions, etc. must be created on site on EMCS network workstations or transferred to a EMCS network workstations via CD/DVD.

3.2.3 Graphic representations of all mapped points shall be created for viewing via the existing ADS/ADX server and network workstations.

3.2.4 All new devices, controllers, monitoring and control points, etc shall be viewable via the Johnson Controls Metasys® BAS server in “All Items” navigation tree and existing user views associated with building .

3.2.4.1 Add all mapped points from new to the existing EMCS database. Points will be created in the “All Items” navigation tree as well as the existing SAFB and user views associated with building .

3.3 Point names shall conform to requirements in the “Point Naming Conventions” below.

4. SYSTEM SOFTWARE FEATURES

4.1 All necessary software to form a complete operating system as described in this specification shall be provided.

4.2 The software programs specified in this specification shall be provided as an integral part of the DDC controller and shall not be dependent upon any higher level computer for execution.

4.3 CONTROL SOFTWARE DESCRIPTION:

4.3.1 Equipment Cycling Protection: Control software shall include a provision for limiting the number of times each piece of equipment may be cycled within any one-hour period.

FA440718R0002

Attachment 2 http://www.johnsoncontrols.com/cg-gls/

4.3.2 Heavy Equipment Delays: The system shall provide protection against excessive demand situations during start-up periods by automatically introducing time delays between successive start commands to heavy electrical loads.

4.3.3 Powerfail Motor Restart: Upon the resumption of normal power, the DDC panel shall analyze the status of all controlled equipment, compare it with normal occupancy scheduling, and turn equipment on or off as necessary to resume normal operation.

4.3.4 All programs shall be executed automatically without the need for operator intervention, and shall be flexible enough to allow operator customization.

4.3.5 Dynamic Data Access: A single process shall be able to incorporate measured or calculated data from any and all other DDC panels on the local area network. In addition, a single process shall be able to issue commands to points in any and all other DDC panels on the local area network.

4.3.6 Historical Data and Trend Analysis: A variety of Historical data collection utilities shall be provided to automatically sample, store, and display system data in all of the following ways:

4.3.7 Continuous Point Histories: Standalone DDC panels shall store Point History Files for all analog and binary inputs and outputs.

5. CONTROL EQUIPMENT AND DEVICES

5.1 The control system shall include all necessary and specified control equipment properly installed in accordance with specifications and drawings

5.2 NETWORKING/COMMUNICATIONS:

5.2.1 All network devices shall be capable of communicating directly with the existing Johnson Controls Inc. MEA Server via the existing Ethernet protocol Metasys Extended Architecture network.

5.2.2 All Ethernet devices shall be installed in a locked cabinet to prevent tampering. Keys to all cabinets will be provided to the EMCS System Manager at the beginning of the warranty period.

5.2.3 The equipment controllers shall be capable of communicating directly with the NAE via the ASHRAE’s BACNet protocol network.

6. DDC Controllers

6.1 METASYS EQUIPMENT CONTROLLERS (MEC) i.e.: Field Equipment Controllers (FECs), Input/output Modules (IOMs), Variable Air Volume Modular Assemblies (VMA), Networked Thermostats (TECs), Networked Sensors (NSs), and Local Display Modules (DISs).

6.1.1 Controllers shall support all the necessary point inputs and outputs to perform the specified control sequences in a totally standalone fashion.

6.1.2 Controllers shall have a library of control routines and program logic to perform the sequence of operation in accordance with the original building design specifications.

6.1.3 Each controller shall automatically and continuously maintain a history of the associated zone temperature to allow users to quickly analyze space comfort and equipment performance for the past 24 hours. A minimum of six samples per hour shall be stored.

FA440718R0002

6.1.4 Each controller shall automatically and continuously auto-tune its control loops for optimum performance and efficient energy use.

6.1.5 Each controller shall perform its own limit and status monitoring and analysis to maximize network performance by reducing unnecessary communications.

6.1.6 Each MEC shall operate as a standalone controller capable of performing its specified control responsibilities independently of other controllers in the network. Each MEC shall be a microprocessor-based, multi-tasking, real-time digital control processor.

6.1.7 Each MEC shall have sufficient memory to support its own operating system and data bases including:

6.1.7.1 Control Processes

6.1.7.2 Energy Management Applications

6.1.8 Powerfail Protection: All system set points, proportional bands, control algorithms, and any other programmable parameters shall be stored such that a power failure of any duration does not necessitate reprogramming the MEC.

6.1.9 Operator interface (O/I)

6.1.9.1 The O/I to any MEC point data or programs shall be through the DIS or a laptop computer connected to any MEC on the network.

6.1.9.2 FECs and NCEs shall include and directly support the use of a DIS that shall be connected to the MEC directly at the controller. The capabilities of the DIS shall include, but not be limited to, the following:

6.1.9.2.1 Display temperatures

6.1.9.2.2 Display status

6.1.9.2.3 Display set points

6.1.9.2.4 Display control parameters

6.1.9.2.5 Override binary output control

6.1.9.2.6 Override analog set points

6.1.9.2.7 Modification of gain and offset constants

7. Naming Conventions

7.1 PURPOSE: To standardize point names to make information easily understandable by all personnel and to facilitate alphabetically grouping and sorting items in lists. The following naming conventions will be followed for all points added to the base EMCS.

7.2 All device, folder, point and extension names will be in the format

BUILDING.SYSTEM.POINT

7.3 The building is a four-digit number. Where appropriate, the number may be followed (never preceded) by one or more letters i.e. 0040N.AH-1.OCC-C. Buildings at Scott AFB are often referred to as P3, P150, etc but the P will cause the building to be sorted after 3650 in a list. Likewise, building 150 would sort before building 40. Therefore, all building numbers less than 1000 will be preceded enough zeros to achieve a 4 digit number.

FA440718R0002

7.4 The system is the name of the equipment system or PC group in which the point resides. The system name may be letters and numbers as appropriate. For grouping and sorting purposes, where numbers are used all systems of the same type will use the same number of digits. For instance, if there are likely to be more than 9 air handlers, the air handlers will be numbered AH01, AH02…AH18, AH19… The contractor is responsible for verifying and following the existing system name format in use in the facility where the work is to be performed.

7.5 The point is the individual point label and will end in a dash followed by a function descriptor i.e. OCC-C, DA-T. See list below for a list of acceptable point names and descriptors. If none of the listed names or descriptors is adequate for a particular point, the short names used by Johnson Controls HVAC Pro may be used or contact 375 CES/CEOFC at

618.256.2528 for approval of a substitution.

7.6 “Periods” will be used to separate the building, system, and point identifiers.

7.7 Dashes will be used within each system name where appropriate for clarity but must be consistent for all systems of the same type in the facility. For instance, if the format AH1-3 is used for one air handler, it must be used for all the rest of the air handlers in the facility. If the format AH-13 is used for one air handler, it must be used for all the rest of the air handlers in the facility. The contractor is responsible for verifying and following the existing system name format in use in the facility where the work is to be performed.

7.8 More than one system name may be used if necessary for clarity but should be avoided if possible.

7.9 Building, system, Point, and extension names will be upper case.

7.10 Engineering units, descriptions, etc. will be title case.

7.11 All static pressure values will be given in 2 decimal point precision

7.12 All CFM values will be given in whole numbers.

7.13 All other numeric point values will be given in 1 decimal point precision

0003.HWCW.HWP1-S On Hot Water Pump 1 Status

1700.CHLRS.MCQUAY.CHLR1-S Off Chiller Status

1600.AH-1.SF-C On Air Handler 1 Command

1700.AH3-1.DA-T 55.3 Deg F 1700 Air Handler 3-1Discharge Air

Temp

1900.AH-1.SA-P 1.46 In Wc AHU-1 Static Press

7.14 All point names will end with one of the following:

-C For all binary output (Command) points

-S For all binary status points

-SPT For all analog set points

FA440718R0002

-T for all temperature values

-P For all pressure values

-A or -mA

For all amperage values

-RH For all relative humidity values

-FLO For all gas or liquid flow values

-HZ For all hertz values

-RPM For all rounds per minute values

-HP For all horse power values

-POS Position

7.15 The following point names will be used:

OCC Occupied mode. [ OCC-C, OCC-S]

CHLR# For chillers where # is the number of the chiller. (CHLR1-C)

CH$ For chilled water points where $ is the letter describing the point

CHS For chilled water supply (water leaving chiller evaporator) [CHS-SPT]

CHR For chilled water return (water entering chiller evaporator) [CHR-T]

CHP For chilled water pump (CHP1-S)

CW$ For condenser water points where $ is the letter describing the point

CWS For condenser water supply (water entering chiller condenser or leaving tower) [CWS-FLO]

CWR For condenser water return (water leaving chiller condenser or entering tower) [CWR-P]

CWP For condenser water pump (CWP1-C)

CTF# For cooling tower fans where # is the number of the tower or cell. (CT1-C, CT2-1-HZ]

DPR Damper (DPR-C, DPR-POS)

CLG Cooling valve, solenoid (CLG-C, CLG-S)

HTG Heating valve, solenoid, relay (HTG-C, HTG-S)

FILTER Filter (FILTER-S)

LL Low Limit (LL-S, LL-SPT)

FA440718R0002

SD Smoke Detector (SD-S)

SF# For supply fans where # is the number of the air handler, roof top unit, etc.

(SF1-C)

RF# For supply fans where # is the number of the air handler, roof top unit, etc.

(RF1-S)

DA Discharge Air (DA-T)

DASTC Discharge Air Static Pressure

MA Mixed Air (MA-T)

OA Outside Air (OA-T)

RA Return Air (RA-FLO)

EA Exhaust Air (EA-FLO)

RM Room where only one room is referenced (RM-T)

ZN Zone where a group of rooms are referenced (ZN-T)

ECON Economizer (ECON-S, ECON-C)

SDWN Shutdown Command (SDWN-C)

Appendix A – STATEMENT OF ACCEPTANCE OF RESPONSIBILITIES

EMCS

INFORMATION SYSTEM PRIVILEGED ACCESS AGREEMENT AND ACKNOWLEDGMENT

OF RESPONSIBILITIES

Date: __________

1. I understand that I have the necessary clearance for privileged access to the Energy Management and Control

(EMCS). I will not introduce or process data or software for the IS that I have not been specifically authorized to handle.

2. I understand the need to protect all passwords and other authenticators at the highest level of data they secure. I will not share any password(s), account(s), or other authenticators with other coworkers or other personnel not authorized to access the EMCS. As a privileged user, I understand the need to protect the root password and/or authenticators at the highest level of data it secures. I will NOT share the root password and/or authenticators with coworkers who are not authorized EMCS access.

3. I understand that I am responsible for all actions taken under my account(s), root, or otherwise. I will not attempt to “hack” the network or any connected information systems, or gain access to data to which I do not have authorized access.

4. I understand my responsibility to appropriately protect and label all output generated under my account

(including printed materials, magnetic tapes, floppy disks, compact disks, and downloaded hard disk files).

5. I will immediately report any indication of computer network intrusion, unexplained degradation or interruption of network services, or the actual or possible compromise of data or file access controls to the EMCS System

Manager, EMCS contract quality assurance evaluator or contract manager. I will NOT install, modify, or remove any hardware or software (i.e., freeware/shareware and security tools) without written permission and approval from the EMCS System Manager.

FA440718R0002

6. I will not install any unauthorized software (e.g., games, entertainment software) or hardware (e.g., sniffers).

7. I will not add/remove any users’ names to the Domain Administrators, Local Administrator, or Power Users group without the prior approval and direction of the EMCS System Manager.

8. I will not introduce any unauthorized code, Trojan horse programs, malicious code, or viruses into the EMCS local area network.

9. I understand that I am prohibited from the following while using the DoD IS:

a. Introducing Classified and/or Controlled Unclassified Information (CUI) into the EMCS environment.

b. Accessing, storing, processing, displaying, distributing, transmitting, or viewing material that is abusive, harassing, defamatory, vulgar, pornographic, profane, or racist; that promotes hate crimes, or is subversive or objectionable by nature, including material encouraging criminal activity, or violation of local, state, federal, national, or international law.

c. Storing, accessing, processing, or distributing Classified, Proprietary, CUI, For Official Use Only

(FOUO), or Privacy Act protected information in violation of established security and information release policies.

d. Obtaining, installing, copying, pasting, transferring, or using software or other materials obtained in violation of the appropriate vendor’s patent, copyright, trade secret, or license agreement.

e. Knowingly writing, coding, compiling, storing, transmitting, or transferring malicious software code, to include viruses, logic bombs, worms, and macro viruses.

f. Engaging in prohibited political activity.

g. Using the system for personal financial gain such as advertising or solicitation of services or sale of personal property (e.g., eBay), or stock trading (i.e., issuing buy, hold, and/or sell directions to an online broker).

h. Fundraising activities, either for profit or non-profit, unless the activity is specifically approved by the organization (e.g., organization social event fund raisers and charitable fund raisers, without approval).

i. Gambling, wagering, or placing of any bets.

j. Writing, forwarding, or participating in chain letters.

k. Posting personal home pages.

l. Any other actions prohibited by DoD 5500.7-R (Reference (y)) or any other DoD issuances.

10. Personal encryption of electronic communications is strictly prohibited and can result in the immediate termination of access.

11. I understand that if I am in doubt as to any of my roles or responsibilities I will contact the EMCS System

Manager for clarification.

12. I understand that all information processed on the EMCS is subject to monitoring. This includes email and browsing the web.

13. I will not allow any user who is not cleared access to the network or any other connected system without prior approval or specific guidance from the EMCS System Manager.

14. I will use the special access or privileges granted to me ONLY to perform authorized tasks or mission related functions.

15. I will not use any US Air Force owned information system to violate software copyright by making illegal copies of software.

16. I will ONLY use my PRIVILEGED USER account for official administrative actions. This account will NOT be used for day to day network communications.

17. I understand that failure to comply with the above requirements will be reported and may result in the following actions:

FA440718R0002

a. Revocation of IS privileged access.

b. Counseling.

c. Adverse actions pursuant to the Uniform Code of Military Justice and/or criminal prosecution.

d. Disciplinary action, discharge or loss of employment.

e. Revocation of Security Clearance.

18. I will obtain and maintain required certification(s), according to DoD 8570.01-M and the certification provider, to retain privileged system access.

INFORMATION SYSTEM NAME EMCS

IAT’s NAME

IAT’s SIGNATURE

Date

EMCS SYSTEM MANAGER NAME

EMCS SYSTEM MANAGER SIGNATURE

Date

FA440718R0002