Atch__24_-_AFSC_Energy_Metering_Requirements_24_June_2016.pdf

AFSC Energy Metering Requirements Documentation

24 June 2016

Prepared by: 402 MXSS/MXREI Coordinated with: Energy Managers at Tinker and Hill AFB

U. S. AIR FORCE

Robins AFB, GA

TABLE OF CONTENTS

1 INTRODUCTION 3

1.1 Purpose 3

1.2 Scope 3

1.3 Topology 4

2 AF FORM 332 PROCESS 9

2.1 AF 332 Data Content 9

2.2 Submittal of AF 332 9

3 BASE COMMUNICATION SQUADRON COORDINATION 10

3.1 Acquisition of New Cabinets, Switches, and Patch Panels 10

3.2 Final Connection to the Communication Switch 10

3.3 IP Addresses 10

4 ACCEPTANCE TESTING 11

5 MISCELLANEOUS 11

5.1 Hazardous Material 11

5.2 Handling Process and Requirements 12

5.3 Physical Environment 12

6 NETWORK DESIGN DETAILS 12

6.1 Government Furnished Equipment 12

6.2 Building Level Design Detail 12

7 INTEGRATED MASTER SCHEDULE 12

8 LIFE CYCLE SUPPORTABILITY 12

9 RELIABILITY, MAINTAINABILITY & AVAILABILITY 12

APPENDIX 13

1 INTRODUCTION

1.1 Purpose

A Telecommunication System Installation Plan (TSIP) was documented for the energy metering efforts at Robins. It was expanded to include equipment either in use or planned for use at Tinker and Hill. The TSIP included a pilot at Robins AFB. The pilot would include the acquisition, installation and integration of electric, natural gas, chilled water and potable water meters. The documentation would include a complete design package for the implementation of the targeted buildings, as well as the “as built” documentation requirement for the installation.

In the interest of time, the TSIP was modified to reflect the AFSC energy metering requirements at the three ALCs.

The purpose of this revised TSIP is to provide a list of communication devices (See Appendix A) and meters (See Appendix B) that are required to support ALC process level metering. The document also provides schematics that describe the function and integration of the components. If approved to operate on the AFCEC CEVLAN, the proposed process level metering components could effectively integrated in to the AFCEC system. The proposal is additive and takes nothing away from the existing AFCEC system.

Our goal is to address facility level and process level meter requirements using a single meter platform that automatically reads meters and provides the data needed to make sound economic decisions. Based on the large existing and planned UESC and ESPC projects, time is of the essence.

1.2 Scope

In order to support review by and approval of the local 78th Communication Squadron, specific hardware and implementation strategies had to be provided. However, in most cases, approved equivalent hardware devices could be substituted. The computer hardware and software aligned as closely as possible with the AFCEC solution to help facilitate integration and implementation.

Our proposed design accommodates facility level and process level metering. A list of utilities targeted at the facility and process level are shown in Appendix C. A list of data required from each of the metered utilities or processes is shown in Appendix D.

To date, the initial pilot, which included the acquisition, installation and integration of electric, natural gas, chilled water and potable water meter has not been implemented. The initial focus has shifted away from the proposed pilot to installation of facility level electric and natural gas meters.

1.3 Topology

The network topology of the ALC Metering System consists of a facility level, hub and spoke design. A Meter Communication Gateway creates the hub element in the design. Each facility would be equipped with one or more Meter Communication Gateways which provides the central point of connection to all metering elements. Figure 1.4-1 illustrates the hub and spoke network topology and standard configuration implemented for the metering system.

Figure 1.4-1: Typical Facility Level Metering System Network Topology

In Figure 1.4-2, a complete network topology diagram is provided for the first three buildings to be metered in the pilot. This approach is repeated for each of the facilities addressed. In Figure 1.4-2, we illustrate how our components could interface with the Air Force Civil Engineering Center (AFCEC) Advanced Meter Reading System (AMRS) servers and associated equipment.

Although proposed meters and communication devices have been tested with AMRS in a lab setting, the AMRS system has not been officially deployed at Robins. Therefore, the latest version of AMRS would have to be delivered and installed by AFCEC in collaboration with the RAFB Communication Squadron. AMRS would be connected to the RAFB CEVLAN and the Meter Communication Gateway(s) installed at each building would be connected to CEVLAN to provide network connectivity across the system.

The illustration shown in Figure 1.4-2, schematically identifies each piece of equipment to be installed as part of the pilot. Each building would require one or more Meter Communication Gateways and one or more utility meters attached to their corresponding Meter Communication Gateway. The number of gateways and meters shown in Figure 1.4-2, represents the actual number of planned gateways and meters as identified on the Meter Location Drawings that are provided within the Technical Drawing Package created for the Robins Metering Project.

Figure 1.4-2: B81, B82 and B83 Topology

NOTE: *B83 has one natural gas meter. However, the closest gateway box is in B82. Therefore, we are depicting it in building 82 in the figure above.

Figure 1.4-3 provides a functional block diagram of the Meter Communication Gateway. The gateway provides a facility level hub for the system and marks the point of demarcation between the TCP/IP CEVLAN network and the point-to-point RS-485 serial interfaces used to connect to each meter. Highlighted in this functional diagram are the major gateway components, which include the E-Mon interval data recorder and two (2) Perle IOLAN SDS4 T Device Servers. Figure 1.4-3 also shows the functional interconnects to meters and the network connection to CEVLAN. It is our understanding that AFCEC is testing similar E-Mon interval data recorders and Perle devices in their laboratory. Equivalent hardware that has been approved for use on the network could be substituted as necessary.

*(B83)

Figure 1.4-3: Meter Communication Gateway Functional Block Diagram

As illustrated in Figure 1.4-3, each Meter Communication Gateway was configured with two (2) Perle IOLAN SDS4 T Device Servers. The IOLAN is an Ethernet to serial device server and provides a single RJ-45 connector for making a 100Base-T Ethernet connection. Within our proposed meter system, the IOLAN is intentionally the sole element that is connected to the Robins CEVLAN. All other metering system components are connected to the IOLAN’s four (4) RS-485 serial ports. Thus, the IOLAN serves as the demarcation boundary between the TCP/IP CEVLAN Network and the point-to-point RS-485 Serial interface to the metering components. Figure 1.4-4 provides a photograph of the Perle IOLAN SDS4 T and identifies the various indicators and connectors.

Figure 1.4-4: Perle IOLAN SDS4 T

As shown, the IOLAN SDS4 provides four (4) independent RS-485 serial ports that can be used to make connection to the various metering elements. A configuration capability within the IOLAN allows these RS-485 ports to be configured as two-wire, half duplex or four-wire, full duplex interfaces. For the metering elements designated for use at Robins, each of the four (4) ports is configured as a two-wire, half duplex interface with the 10-Pin RJ-45 connector pinout shown in Table 2 below.

Table 1: 10-Pin RJ-45 Connector Pinout

Pin EIA‐485Half Duplex

1 ‐

2 ‐

3 TxD+/RxD+ 4 ‐

5 TxD‐/RxD‐

6 ‐

7 GND

8 ‐

9 ‐

10 ‐

Figure 1.4-5 provides a physical drawing of the Meter Communication Gateway and illustrates the manner in which various meter components are connected to the gateway.

Figure 1.4-5: Meter Communication Gateway With Typical Meter Connections

As stated earlier, each buildings would use one or more Meter Communication Gateways as shown in Figure 1.4-3.

In developing the metering system architecture, several locations lacking CEVLAN connectivity were identified and a solution to address these locations was developed. This solution was the addition of a FIPS-140-2 compliant, 900MHz, unlicensed radio to the Meter Communication Gateway. Figure 1.4-6 provides the functional block diagram of the Meter Communication Gateway that is equipped with this radio.

Figure 1.4-6: Wireless Meter Communication Gateway Functional Block Diagram

The radio selected for use within the Meter Communication Gateway was the AvaLAN AW900FS and it functions as a wireless TCP/IP network extender. The radio network consists of a single radio physically connected to the CEVLAN network and serves as the radio system base station. Each base station radio can be configured to connect to up to 16 client radios. Once configured, the radios transparently transfer TCP/IP network traffic between the base and client radios at up to 1Mbs. No additional network configuration is required to enable use of the wireless radios and the data is transferred using AES 256 encryption and the radios are FIPS-140-2 compliant.

With the addition of the radio within the Meter Communication Gateway, an Ethernet switch is required to allow connection to the two IOLAN that are collocated inside the gateway. A Cisco IE-2000-8TC-B has been selected because of its industrial temperature rating and fanless design. The Cisco IE-2000-8TC-B is an eight (8) port, managed Ethernet switch and is functionally similar to the default Cisco 3750 edge switches that are commonly found at RAFB.

Figure 1.4-7: Photograph of Typical Meter Communication Gateway With 900Hz Radio Option

2 AF FORM 332 PROCESS

AF Form 332s were prepared for the initial three buildings. Additional AF Form 332’s will be required and submitted prior to installation of meter hardware.

2.1 AF 332 Data Content

The details of the information required in all building AF Form 332’s is as follows:

- Drawings and/or photos necessary to clearly illustrate the work to be accomplished. Specifically identify any work to be accomplished and whether it will be performed by the contractor or by the government.

- Network equipment and distribution installations and all necessary support work. This information includes, but is not limited to, new/improved electrical power service, new switch installations, new switch cabinets, new patch panels, communications grounding improvements, lead paint and/or asbestos abatement work and quantities, and any necessary access control changes.

- Detailed information on routing plans including, but is not limited to, trenching, conduit, and entry or exit locations required in external walls.

2.2 Submittal of AF 332

The AF Form 332 and accompanying documentation shall be submitted by Facility Engineer at each building.

3 BASE COMMUNICATION SQUADRON COORDINATION

3.1 Acquisition of New Cabinets, Switches, and Patch Panels

An initial survey of the buildings indicated that in most cases the existing infrastructure switches do not have sufficient open ports to accommodate the connections required by the Robins Metering System. To remedy this need, the 402 MXSS agreed to provide the funds to acquire switches, patch panels and cabinets through the BOS agreement. This equipment will not be purchased or installed by the meter installation subcontractor. Work orders in ITSM will be submitted by 402 MXSS personnel, as required.

3.2 Final Connection to the Communication Switch

Final connections will be completed under an ITSM work order submitted by the complex Unit Communication Security Officer (UCSO).

3.3 IP Addresses

Communication Squadron will provide a list of available IP addresses for the buildings.

4 ACCEPTANCE TESTING

Acceptance testing will be conducted at the facility level by making a local, direct Ethernet connection to each Meter Communication Gateway. Figure 4-1 illustrates the concept of direct meter level validation and verification.

Figure 4-1: Meter Validation and Verification

A government representative or contractor will need to use a specially configured laptop and Ethernet switch to connect directly to the two Perle IOLAN Serial Device Servers in the gateway. The laptop must be equipped with meter manufacturer’s software to facilitate the programming, configuring and testing of the meters attached to the gateway. The Perle IOLAN devices will be configured to use a predetermined static IP address as required for operation on CEVLAN at the given facility. Correspondingly, the laptop will be configured to use a static IP address within the network domain required to emulate a connection to CEVLAN. Once verified and validated at the gateway level, the final system level verification and validation will occur via CEVLAN using AMRS.

5 MISCELLANEOUS

5.1 Hazardous Material

Hazardous material handling is anticipated to be minimal. The installation subcontractor may come in contact with hazardous material when penetrating the walls or trenching. Hazardous materials must be disposed of properly.

5.2 Handling Process and Requirements

In this section document the handling procedures for hazmat materials to be removed, stored and disposed of as part of the ITS effort. Outline the necessary State and/or Federal regulations governing such procedures. Update final quantities at the completion of the project.

5.3 Physical Environment

This section describes current power, grounding, air conditioning, suitability and apparent constraints of building space, patch cords and their compatibility with existing wiring. It should identify the requirements for improvements to support the new and/or modification to the existing network gear.

6 NETWORK DESIGN DETAILS

6.1 Government Furnished Equipment

The infrastructure edge switches will be provided by the government.

6.2 Building Level Design Detail

The Robins metering project does not impact building level network design. The Robins metering system connects to specific edge router ports that are provisioned within the CEVLAN.

7 INTEGRATED MASTER SCHEDULE

A detailed implementation schedule is required, but TBD at this time.

8 LIFE CYCLE SUPPORTABILITY

The Robins Metering Project uses a Meter Communication Gateway that serves as the point of demarcation between the CEVLAN and the point-to-point meter connections. Within the gateway, two (2) Perle IOLAN Device Servers connect directly to the CEVLAN designated edge switch ports and the RS-485 serial ports of the IOLAN connect to the metering components. Since the Meter Communication Gateway serves as the terminal point of TCP/IP connectivity, Robins CE is responsible for the lifecycle support and sustainment of the Robins facility level metering equipment from the point of the network connection to the IOLAN and throughout the balance of the system.

9 RELIABILITY, MAINTAINABILITY & AVAILABILITY

All of the meters selected for use in the Robins Metering system were evaluated for a usable service life of at least 15 years. Generally the operating temperature range of the selected meters is -40oC to +85oC.

The Meter Communication Gateway was developed using commercially available components and each component was evaluated with respect to operating temperature. The Perle IOLAN is the component having the lowest operating temperature of +70oC. As the Robins System design has evolved, the Meter Communication Gateways are now located in the controlled environment of the Communication Locations and the +70oC upper operating temperature is not a derating concern. As with the meters, the Communication Gateway components were selected with a 15 year service life requirement.

APPENDIX

Appendix A: Basis of Design Communication Components

Appendix B: Basis of Design Hardware Components

Appendix C: AFCEC and AFSC Metering Requirements

Appendix D: Industrial Metering Requirements

Appendix E: Meter Device Requirements

Appendix F: Information System Requirements

Appendix A: Basis of Design Communication Components

Device Function Interface Notes

Perle IOLAN SDS4T

Transparent Serial to

Ethernet Server

Physical Interfaces:

RS‐485 Serial (x4)

Ethernet

Provides a transparent RS‐485 to Ethernet Terminal Server.

AvaLAN AW900FS 900MHz

900MHz Radio Physical Interfaces:

Ethernet

900MHz Encrypted RF

FIPS‐140‐2 compliant 900MHz RF LAN Bridge Radio. One radio connects to the CEVLAN Network and up to 16 client Radios can then attach to the RF LAN Extension.

Appendix B: Basis of Design Hardware Components

Meter ALC Utility Interface Notes

ION 8650

Electricity Meter

WR

OC

Electricity + 3 Pulsed Inputs

Physical Interfaces:

RS‐485 Serial

Ethernet

Pulse Input (x3) Protocols:

MODBUS TPC

MODBUS RTU

MV‐90

Compatible

Other protocols

High‐end electricity meter that can be equipped with three optional inputs. The inputs can receive pulsed signals from other meters and produce a totalized, interval time stamped record.

NEXUS 1262/1272

OO Electricity Physical Interfaces:

RS‐485 Serial

Ethernet Protocols:

MODBUS TPC

MODBUS RTU

MV‐90

Compatible

Other protocols

High‐end electricity meter. Power quality measurement capable.

Elster A3

N/A Electricity Physical Interfaces:

RS‐485 Serial Protocols:

ANSI C‐12.21

C&I electricity meter widely used across utility industry. Meets requirements for most metering applications.

Onicon System‐10 BTU Computer and F‐3500

Flow Meter

WR

OC

OO

Chilled Water Physical Interfaces:

RS‐485 Serial

Ethernet

Pulse Output Protocols:

MODBUS TPC

MODBUS RTU

The System 10 BTU Computer provides an interface for the F‐3500 Thermal Mass Flow Meter and two temperature transducers to provide a complete Chilled Water Metering Package.

Basis of Design Hardware Components (Continued)

Onicon F‐5100 Thermal

Mass Flow Meter

WR

OC

OO

Natural Gas Physical Interfaces:

RS‐485 Serial

Pulse Output Protocols:

MODBUS

RTU

The F‐5100 is used to measure the flow of Natural Gas. The Thermal Mass Flow measurement technique eliminates the need for ancillary temperature and volume correctors required by other meter types.

Sensus T2 Flow Meter

WR Potable Water Physical Interfaces:

Pulse Output Protocols:

None

At Robins AFB there is a large installed base of Sensus T2 and similar potable water meters.

These meters produce a Form A contact closure that must be received and totalized by a separate metering device.

Spirax/Sarco VLM‐10

WR

OC

OO

Steam Physical Interfaces:

RS‐485 Serial

Pulse Output Protocols:

MODBUS TCP

MODBUS

RTU

Other protocols

Vortex Flow Meter used for Steam System Metering.

CDI‐5200

WR Compressed Air Physical Interfaces:

Pulse Output Protocols:

None

Specialized ultrasonic meter for compressed air.

Currently widely deployed at RAFB.

Basis of Design Hardware Components (Continued)

Badger M2000

OC

OO

Potable Water/Industrial Waste Water

Physical Interfaces:

RS‐485 Serial

Pulse Output Protocols:

MODBUS

RTU

Electromagnetic Flow Meter slated for Industrial Waste Water Metering.

WattNode

3 Phase Electricity Meter for

Submetering

Physical Interfaces:

RS‐485 Serial Protocols:

MODBUS

RTU

A 3‐Phase submeter for industrial process metering.

E‐Mon Interval Data

Recorder

WR

OC

OO

Multiple (Interval Data Recorder)

Physical Interfaces:

RS‐485 Serial

10/100 Base T Ethernet

Pulse Output

Pulse Input (x8)

Protocols:

MODBUS TCP

MODBUS

RTU

MV‐90

Compatible

The E‐Mon IDR accepts pulse inputs from various meter sources and creates a totalized interval data recorded for each meter that is connected. Large non‐ volatile memory stores data when power is removed.

TransData SSR6000

Interval Data Recorder

N/A Multiple (Interval Data Recorder)

Physical Interfaces:

RS‐485 Serial

10/100 Base T Ethernet

Pulse Input (x8)

Protocols:

MV‐90

Compatible

Other protocols

The TransData SSR6000 IDR accepts pulse inputs from various meter sources and creates a totalized interval data recorded for each meter that is connected. Large non‐ volatile memory stores data when power is removed.

Appendix C: AFCEC and AFSC Metering Requirements

AFCEC Robins Tinker Hill Facility Level Meters

Electricity X X X X

Natural Gas X X X X

Potable Water ‐ X X X

Steam ‐ X X X

Chiller Water ‐ X X X

Industrial Waste Water ‐ X X X

Hot Water ‐ X X X

Compressed Air ‐ X X X

Fuel Oil ‐ X ‐ ‐

Propane ‐ X ‐ ‐

Process Level Meters

Electricity ‐ X X X

Natural Gas ‐ X X X

Potable Water ‐ X X X

Chiller Water ‐ X X X

Industrial Waste Water ‐ X X X

Hot Water ‐ X X X

Compressed Air ‐ X X X

Equipment/Life Meter ‐ X X X

Appendix D: Industrial Metering Requirements

Targets Units of

Measure Consumption Billing

IE/Process

Optimization EA Life Cycle Cost

Primary Electricity kWh X X X kW X X X kVAR X X

Iac X

Vac X

Submetered Electricity kWh X X X kW X X X kVAR X X

Iac X

Vac X

Natural Gas CFM X X X

BTU X X

Potable Water GPM X X X

Steam lbs/hr X X

Chilled Water GPM X

TEMP X

DELTA TEMP X

BTU X X X

Industrial Waste Water GPM X X

Hot Water GPM X X

TEMP X X X

BTU

Compressed Air CFM X X

PSI X X

Fuel Oil GPM X X X

BTU X X

Propane CFM X X X

BTU X X

Life Meter kWh X X X kW X X X kVAR X X X

Iac X X

Vac X X

Hours X X

Oil Temp X X

Vibration X X

Appendix E: Meter Device Requirements

Meter Device Requirements MD1 General Requirements for Meters (All Types) All meters shall meet applicable building codes, local/state/federal regulations, industrial, adhere to UFGS specifications.

MD2 General Metering Requirements for Electricity Meters Quantities Measured:

Total KWH (Total Energy), Real Power (Total of Phases), Total Reactive Power, Historical Peak Demand Power, Rms Voltage For Each

Rms Current For Each Phase

Rms Voltage For Each

Rms Current For Each Phase

Power Factor For Each PhaseRms Current For Each PhaseShall meet ANSI

C12.20 (0.5% Accuracy)

Shall meet ANSI C12.1 (Environmental)

Shall provide optical ports for calibration and test

Shall provide a non‐volatile data storage for a minimum of 6 months of continuous storage

Shall provide an alarm feature for power outage

Shall provide an alarm feature for a tamper event

Shall support a resettable demand read feature to allow 30 day demand recording

Absolute minimum for all electricity meter types is 15 min energy and demand data

MD3 General Requirements for Natural Gas Meters (Note: Not all NG meters provide all quantities) Quantities Measured

Flow in Cubic Feet

Temperature

Pressure

Volume Corrected Cubic Feet

BTU

Absolute minimum for all Natural Gas meter types is 15 min volumetric flow data with pressure

MD4 General Requirements for Steam Meters (Note: Not all Steam meters provide all quantities)Flow in Cubic Feet

Temperature

Pressure

BTU

Absolute minimum for all Steam meter types is 15 min volumetric flow data with pressure and temperature

MD5 General Requirements for Chilled Water Meters (Note: Not all Chilled Water meters provide all quantities) Flow in Cubic Feet

Temperature

Pressure

Absolute minimum for all Chilled Water meter types 15 min volumetric flow data with pressure and temperature entering and leaving

MD6 General Requirements for Potable Water Meters

Flow in Cubic Feet

Absolute minimum for all Potable Water meter types 15 min volumetric flow data

MD7 General Requirements for Hot Water Meters

Flow in Cubic Feet Temperature

Absolute minimum for all Hot Water meter types 15 min volumetric flow data

MD8 General Requirements for Compressed Air Meters

Flow in Cubic Feet, Temperature, Pressure

MD9 General Requirements for Industrial Waste Water Meters

Flow in Cubic Feet

Absolute minimum for all IWW meter types 15 min volumetric flow data

MD10General Requirements for Equipment Usage Meter

Run time, Energy Consumption, Oil Life, Vibration Analysis

Support of the Robins Life Meter.

MD11Allowed Meter Types By Utility:

Meter types for Steam: Thermal Insertion, Vortex Shedding

Meter types for CW: Thermal Insertion, Venturi

Meter types for PW: Thermal Insertion, Venturi, Turbine

Meter types for CA: Thermal Insertion, Venturi, Turbine, Orifice

Meter types for NG: Volume, Turbine, Venturi, Orifice

Meter types for IWW: Venturi, Orifice

MD12All meters deployed on the system shall provide for a human readable display.

Support manual reading of all meters.

Appendix F: Information System Requirements

Req# Requirement Comments

IS1 Shall meet all information technology and cybersecurity requirements levied on a Platform IT Solution of this type.

IS2 Shall support the hierarchical grouping of meters to support analysis of meter data according to the following:

Command [AFSC]

Installation [e.g. Robins, Tinker, Hill, Kirkland, etc]

Energy Source [e.g. Electrical Substation, Chilled Water Plant, Steam Plant, Potable Water Well, Sewer Line]

Distribution [e.g. Electrical Transformer, Steam Distribution Loop, Chilled

Water Loop, etc]

Tenant Organization [e.g. ALC, ANG, etc]

Facility (e.g. BLDG]

Process Area [e.g. Paint/Depaint, Avionics, Software, Engine, Admin, Warehouse, etc]

Work Cell [e.g. Dock, Manufacturing Cell]

Circuit [e.g. Electrical circuit designation, Steam Distribution Loop, Chilled

Water Loop, etc]

Equipment Type

Equipment Model

Equipment Serial Number

User Defined (5 fields)

The goal is to have the appropriate database fields to allow meters to be hierarchically grouped across the enterprise. Having this data associated with each meter will allow analytics to be applied iaw logical grouping. The user defined fields allow for the expansion of logical grouping beyond those presently identified. These grouping might relate more closely to process areas.

IS3 Shall support billable and non‐billable meters Billable meters shall be used to generate billing reports and will be used by CE and the Complexes to generate, verify reimbursable billing.

Non‐billable meters will not be used to generate billing reports and will be used by A4 to analyze industrial process energy.

IS4 Shall support a wide variety of meter types for all primary and secondary energy sources:

Electricity

Natural Gas

Chilled Water

Steam

Compress Air

Hot Water

Potable Water

Fuel Oil

Propane

Industrial Waste Water

It is required that a variety of meter types be supported, from simple pulse flow meters to more complex volume correcting gas meters. The system shall be able to be extended to provide native support for the meters required to cost effectively and accurately meter the quantities of interest.

IS5 Shall support existing legacy meter infrastructure, where cost effective and beneficial. Examples include: Elster A3, L+G S4E, Schneider ION 8600/8650, Mercury Gas Meter Recorders, Transdata Solid State Recorders, and other meters currently installed.

The system should allow reading from as many existing meters as is possible including switch gear panel meters, existing process and facility meters.

IS6 Shall support metering of industrial process streams including: Potable Water

Industrial Waste Water

The system should allow input from pulse meters for a variety of metered quantities. Typical use would be for various fluid flows.

IS7 Shall support local administration of the system to include: Add/Delete/Edit

Meters Add/Delete/Edit Users and User Roles Add/Delete/Edit Custom

Reports

Local administration of the system at the user level is required to allow for the dynamic addition of meters to support process metering needs and to allow for management of the user base.

IS8 Data contained in the metering system shall be made available to authorized users via the NIPRNET.

Meeting this requirement is based on ALC understanding of the capabilities to be afforded by the adoption of ICSNET2.0.

IS9 Shall provide for secure web presentment of information. Tailored based on user login Support export of presented information in a usable, common data format

Use of a tailorable web presentment framework to allow for individual users to have an actionable dashboard interface is needed to maximize the effectiveness the system.

IS10 Shall support near‐real‐time communication in response to Outages, Voltage

Anomalies, Reactive Power Anomalies

The system administrator shall be able to configure the communication engine to issue messages sent via sms or email to a managed distribution lists. Distribution list should be assignable to the logical groups defined within the system. For example a distribution list for facilities in general might be created and a separate distribution list for a specific type of machine might exist. If a voltage anomaly is reported that affects a facility and a specific piece of equipment, then a message would be issue to both distribution lists.

Information System

Information System Requirements (Continued)

IS11 Shall support near‐real‐time voltage and demand monitoring and reporting of anomalies that violate preset thresholds

Near real‐time voltage and demand monitoring allows the system to monitor voltage and demand using meters suitable equipped and becomes a data stream that the distribution engineering community can use to detect issues in the distribution network. Demand monitoring, when coupled with communication, also becomes part of a

Demand Side Management strategy to allow quick response to curtailment signals.

IS12 Shall provide storage for not less than 24 months of meter data for the maximum number of meters

The system's storage should be sufficient to allow for historical analysis.

IS13 Shall provide for meter data collection and storage for not less than 2000 meters

IS14 Shall support 15 minute interval data for all meter types and support Time of

Use (TOU) meter data collection and rates.

IS15 Shall provide the ability to input not less than five (5) TOU rate structures for each utility and to apply these rate structures to meters based on individual meter and/or system hierarchical groupings

The goal is to have meter data directly aligned to the base's utility billing structure to allow a certified billing structure which exactly mirrors the installations billing structure. Date will also be used to: 1.

Performance Management (quality, statistical process control, waste, cost, throughput). 2. Process Optimization (continuous improvement, trade‐off decisions). 3. Identifying potential improvement initiatives.

4. M&V (energy consumption for baselines of production in energy/production output level, in‐progress initiatives, proposed initiatives and results of completed initiatives). 5. Predictive maintenance. 6. Energy cost allocation, billing, auditing, and procurement. 7. Energy and water baselines.

IS16 All data shall have a time stamp applied by the metering device Meter times shall not be applied based on server read time to ensure that temporal accuracy is met in an auditable manner. In this system the meter/recording device is the device of record and the information system is the collector of this data. Once collected into the information system and validated, then the data present in the information system becomes the historical data of record. Allows billing on the same rate structure as the installation.

IS17 Shall have the ability to generate reports that normalize energy usage to weather data

IS18 Shall have the ability to generate reports that normalize energy usage to production data

IS19 Shall provide a real‐time read capability to allow users to read meters on demand.

For meters capable of such, shall allow for the real‐time streaming of meter data quantities in a manner to allow for real‐time analysis of the metered quantities. In particular, the ability to make use of the waveform capture capabilities of the ION 8600 meter.

IS20 Shall provide for the trending of energy use on daily, monthly, and yearly basis by hierarchal groups.

Trending on Facility, Installation, Work Cell, Individual piece of equipment.

IS21 Shall use GIS data to allow for visualization of energy consumption by facility. Map view presentment of energy intensity data.

IS22 Shall capture and report peak demand usage for all utilities by hierarchical group.

IS23 Shall support decision making within a demand response program. Requires robust, near real‐time notification engine with multiple distribution lists all local administered at the base level. Data needs to be easily visible by many different people and offices.

Information System Requirements (Continued)

IS24 Shall support ICSNET2.0 and allow for database replication to support enterprise level energy analysis at the enterprise level.

Data from the base internal CEVLAN is replicated via one‐way optical router to a database server located on the NIPRNET. Once on the

IS25 Shall support TOU enabled Solid State Recorders for measurement of pulsed

IS26 Shall support TOU enabled Solid State Recorders for measurement of analog signal types: 4‐20ma, 0‐20VDC, 0‐5VDC

IS27 Shall provide a report of the communication status of all meters active on the system.

IS28 Shall support use of approved wireless technologies to allow for wireless collection of meter data.

Use of wireless technology to allow for the collection of meter data in areas that do not support wired infrastructure.