ATTACHMENT_VII.Performance_Work_Statement.pdf

Attachment VII

PERFORMANCE WORK STATEMENT (PWS) Meter Data Management System (MDMS) 2/21/2019

US Army Engineering and Support Center - Huntsville Alabama Version 1 Rev 1.1

1.0 BACKGROUND.

Section 543(e)(1) of the National Energy Conservation Policy Act [42 U.S.C. 8253(e)(1)], as amended by the Energy Policy Act of 2005 (EPAct 2005) and the Energy Independence and Security Act of 2007 (EISA 2007) requires

“By October 1, 2012, in accordance with guidelines established by the Secretary …, all Federal buildings shall, for the purposes of efficient use of energy and reduction in the cost of electricity used in such buildings, be metered. Each agency shall use, to the maximum extent practicable, advanced meters or advanced metering devices that provide data at least daily and that measure at least hourly consumption of electricity in the Federal buildings of the agency. Not later than October 1, 2016, each agency shall provide for equivalent metering of natural gas and steam, in accordance with guidelines established by the Secretary …. Such data shall be incorporated into existing Federal energy tracking systems and made available to Federal facility managers.”

The “guidelines established by the Secretary” in 42 U.S.C. 8253(e)(1), coordinated with each agency (e.g., Department of Defense [DoD]), taking into consideration expected savings and costs of metering, maintenance, and training, establishes priorities for types and locations of buildings to be metered and establishes exclusions based on cost-effectiveness.

Section 3(f)(ii) of Executive Order (EO) 13693, Planning for Federal Sustainability in the Next Decade (19 Mar 2015) adds the requirement to install water meters and collect data to improve water conservation and management.

DoD’s guidelines for complying with the metering requirements of the law are incorporated in UFC 1-200-02 High Performance and Sustainable Building Requirements, which references the metering requirements of Department of Defense Instruction (DoDI) 4170.11 (March 16, 2016) as amended by DOD Utilities Meter Policy, 16 April 2013. Together, the DoD policies require advanced metering each applicable building for each utility serving the building (electricity, steam, natural gas, and water), wherein an advanced metering system (AMS) must automatically and reliably collect and analyze regular interval data from advanced meters and distribute information to key stakeholders.

DoD directs all Components (e.g., Army, Navy, Air Force) to install sufficient advanced meters to capture 60% of electricity use and natural gas use with a goal of 85% at the Component level by the end of Fiscal Year 2020.

MDMS is the Army’s implementation of DoD’s AMS requirement, the requirements of which are described in Army Directive 2014-10 (Advanced Metering of Utilities, June 4, 2014), Energy and Water Goal Attainment Responsibility Policy for Installations (ASA-IEE Memorandum, Jan 13, 2017), and Sustainable Design and Development Policy Update ( ASA-IEE Memorandum, Jan 17, 2017). To the requirements of the law and DoD, the Army adds 1) the requirement to also meter district chilled water and hot water serving buildings, 2) the requirement for advanced meters to report 15-minute interval data for all utilities to the Army’s MDMS at least hourly, 3) the requirement to install all meters in compliance with Army Metering Program Guidance (HNC UMCS-MCX, Revision 8, May 2016), and 4) the requirement to also meter, where practical, building subsystems according to ASHRAE 189.1-2014 Section 6.3.3 for Water Consumption and Section 7.3.3 for Energy Consumption.

2.0 OBJECTIVE

Regarding the purpose of metering and AMS, DoDI 4170.11 states that “while meters themselves do not constitute a direct energy conservation measure, it is expected that the management of data collected through metering will lead to energy and cost savings. Meter data should be collected, assimilated, interpreted, and made available to facility and energy program managers. This information should serve as the foundation to establishing facility energy efficiency relative to other facilities in the building inventory. It should also serve to identify and confirm opportunities for energy reduction or increased energy efficiency through improved operation procedures, best practices, or energy conservation and retrofit projects.”

Thus, the primary objective of this contract is to implement the chosen COTS in order to operate, enhance, and sustain the Army’s centralized MDMS in order to accomplish the primary mission of

(1) delivering dependable meter data, (2) use industry standards to normalize data and establish facility energy consumption relative to other facilities, (3) provide tools in an easy-to-use interface to enable facility and energy program managers to identify and confirm opportunities for energy reduction, (4) support continual advancement and optimization in capabilities and technologies, (5) keep the system in accordance with applicable laws, policies, executive orders, regulations, instructions, and guidance, and (6) continually use system engineering techniques to reduce system sustainment cost and complexity.

3.0 SCOPE & AUTHORITY

The U.S. Army Engineering and Support Center, Huntsville (CEHNC), is a Major Subordinate Command under the U.S. Army Corps of Engineers. CEHNC is the Army Program Management Office responsible for managing the execution of the Army Central Metering Program (AMP) and is available to support other Federal agencies in their compliance with the National Energy Conservation Policy Act using this same contract. Scope of services as may be purchased through the award of task orders under this contract may include the following: (a) Furnishing a commercial off-the-shelf (COTS) software as a single MDMS Enterprise solution to be the Army’s standard for its meter data analyses; (b) provide operator training for use of the software; (c) provide administration, operation, and maintenance of the MDMS Program’s COTS solution, to include installation level interfaces of gateway devices, software upgrades as required for internet security; (d) provide system security engineering to support the secure configuration and sustainment of the MDMS, to include devices that must interface with the MDMS in accordance with Army and Department of Defense (DoD) requirements; (e) develop the appropriate Risk Management Framework (RMF) packages or the Army’s current accreditation process; (f) maintain the current accreditation package’s artifacts to include periodic reviews in accordance with the MDMS continuous monitoring requirements and no less than annually for accuracy and change management controls to support Federal Information Security Management Act (FISMA) reporting and continuous authorization under RMF; (g) develop Networthiness and/or Asses-Only packages for submission to Network Enterprise Technology Command (NETCOM) or through Enterprise Mission Assurance Support Service (eMASS) for review and approval; (h) operate a call center technical support for software and hardware trouble shooting issues; (i) and provide secure and complete solutions for enabling legacy system compatibility with the Army-wide MDMS. Task orders under this contract may include any node above the meter that assist in delivering dependable meter data. Installation and maintenance of meters or control systems are outside the scope of this contract as they pose a life-safety risk. This base contract vehicle is not in itself a deliverable as those will be addressed in individual task orders, rather this vehicles seeks to define the scope, authority, and range of functional and technical requirements that may be executed under this vehicle.

4.0 GENERAL REQUIREMENTS

4.1 Principal Contract Requirements - The requirements in the following sections of this base contract shall be applied to any task order issued (whether mentioned in the task order or not) under this contract vehicle. Each task order will be negotiated after contract award, and the task order proposal shall include all ancillary costs associated with this base contract. Additional requirements described in each task order, once awarded, may compliment, emphasize, or add to any requirements or processes mentioned in this paragraph so long as they are within the scope of the contract described in Section 3. Task orders may include multiple tasks. The Government reserves the right to expand any requirements of any task order so long as the requirement does not force the Contractor to perform outside the scope of what would be considered reasonably within the bounds of this services contract. The Government also reserves the right to absolve the Contractor of requirements under this paragraph ONLY by noting such release in the verbiage of the task order.

4.2 Performance Metrics – All Key Performance Metrics for Quality Assurance associated with requirements in this contract shall be documented in the Quality Assurance Plan for each specific executed task order. The PRS will document Performance Metrics that will be required for every task order.

4.2.3 Quality Assurance – Quality control under this section shall apply to all task orders awarded under this contract. The verbiage of the task order may require additional quality control requirements above and beyond those mentioned in the base contract. The Contractor shall submit a quality assurance plan for the MDMS program within thirty (30) days of award. Individual quality assurance plans should be submitted with each task order.

4.2.4 Quality Management Plan. The Contractor will be required to provide their current Quality Management Plan (QMP) after the base contract is awarded which clearly depicts how the Contractor will minimize errors prior to submittals and final submissions. It will explain how Quality Control (QC) will be implemented to deliver products consistent with contract requirements for the full scope of the contract and all task orders. The QMP must list the names, qualifications, authority, and responsibilities of all members of the Quality Control Team and define and describe the processes in sufficient detail for the entire life cycle of the products expected to be delivered. The government will not prescribe the quality management organization used by the Contractor or it’s processes, but will hold the Contractor responsible for its effectiveness once implemented. Quality management will be provided at all times on all deliverables, and shall be supported for the length of one year after the final deliverable has been submitted to the government. The Contractor is required to implement the controls and processes as defined in the QMP submitted. The government may require the QMP to be updated to address specific task order requirements.

5.0 ROLES AND RESPONSIBILITIES

The Contractor shall furnish a fully staffed team with proven demonstrated relevant experience to operate, enhance, and sustain the US Army’s Meter Data Management System. These individuals will identify themselves as contractors, if applicable, and meet all other personnel requirements. Tasks will be awarded under this base contract, which will be based on defined requirements and negotiated to the quantities of labor hours and Other Direct Costs (ODCs) needed to perform the requirements.

5.1 Labor Rates - All labor CLINs shall be fully loaded to account for hourly base costs, overhead, and any other administrative costs.

5.2 Proposal – The Contractor shall submit with their proposal a rate sheet using the template provided in the Request for Proposal (RFP). The Contractor shall submit a staff, mid-level, and senior rate for each proposed position. No other adjectives shall be used in this contract to described experience level or differentiate between experience levels.

5.3 Teaming Agreements – Teaming Agreements are required for all proposed sub-contractors and are considered binding. Teaming Agreements shall be submitted with the RFP. Rates and responsibilities should be agreed upon before singing of teaming agreements. Teaming agreements can only be breached with KO approval once the prime contractor has documented and proven to the KO’s satisfaction that the sub-contractor either a) has delivered unsatisfactory work or b) the subcontractor is refusing to deliver services at rates agreed upon in the base rate table.

5.4 Resumes – Resumes submitted in the proposal shall include commitment letters and are considered binding. A contractor shall only submit commitment letters for employees that will either

a) fulfill a key position designated in section 5 or b) fulfill positions described in the contractor’s technical proposal. Employees with submitted resumes shall work a majority of their hours on this contract at the agreed rates as long as they are employed by the contractor or sub-contractor within the government requirements. A contractor found submitting resumes solely for the intent of winning award without displaying intent to use those resumes on the award are subject to forfeiture of the award.

5.5 Staff Changes - Contractor shall secure written approval from the Contracting Officer and the Project Manager for proposed staff and/or changes to the roles and responsibilities with respect to specific task orders. Acceptable professional requirements for key positions are established below.

5.6 Position Experience – Staff level positions shall require 3-8 years of related experience, mid-level requires 9-14 years of related experience, and senior requires a minimum of 15 years of related experience. Postgraduate degrees may be counted as experience equal to the length of the program.

Ex: A two (2) year masters counts as two (2) years. Undergraduate degrees may not be counted towards experience. The Contractor shall use the rate that matches the experience of the employees executing task under specific task orders. Proposals on task orders shall include a crosswalk between employees, their positions and rate level, and hours being executed per requirement on specific task orders. The designated Contracting Officer Representative (COR) or Contracting Officer KO) for this vehicle shall approve all resumes for fulfillment of positions included on the binding labor rate table.

No position shall be proposed unless it is on the binding labor rate table. Additional considerations will be given for DOD and DOA experience. Additional considerations will be given for resumes submitted with proposals for positions outside the 4 required positions in Section 5.7.

5.7 Required Positions – The Contractor will provide for program and project support at all levels of the Army Command structure, the following are required roles or responsibilities:

5.7.1.1 Program Manager (Key Personnel). The Program Manager (PgM) shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The PgM shall have nine (9) or more years of demonstrated recent relevant experience in a program/project management or supervisory capacity, a minimum of five (5) or more years of recent relevant experience in the functional area of the program to be managed, a minimum of five (5) years of demonstrated recent relevant PMP experience in agile project management. An identified alternative individual shall also be designated to act for the PgM when the PgM is not available. There shall be only one (1) Program Manager position on this contract. Requirements should be properly delegated to project managers if required. Additional considerations will be given for individuals with DOD or DOA experience.

5.7.2 Technical Director (Key Personnel). The Technical Director serves as the Contractor’s technical lead, manages the technical team, provides technical oversight, and is a point of contact on technical matters. The Technical Director shall have at least nine (9) years of demonstrated recent relevant experience leading technical teams in fielding Information Technology projects. The Technical Director shall have a Bachelor’s degree in engineering, information technology, or related degree from an accredited university or college. The Technical Director shall have at least three (3) years of demonstrated recent relevant experience managing a technical team using Agile Project Management methods and will be responsible for managing and leading sprint meetings. The Technical Director shall have a thorough understanding of a) Army IT and IA policies, procedures, and regulations and b) Army IT and IA organizational structures and responsibilities. The Technical Director shall demonstrate a thorough understanding of sustainment responsibilities for a large-scale DOD system across many DOD Information Networks (DoDIN’s.). There shall be only one Technical Director position on this contract. Additional considerations will be given for DOD and DOA experience.

5.7.3 Senior Energy Engineer (Key Personnel). The Senior Energy Engineer is responsible for technical oversight of all areas of the contract that deal with the energy calculations, standards, policies, or criteria. The Senior Energy Engineer shall have demonstrated recent relevant experience with Government or industry processes, procedures, standards, methodologies, or tools as relative to the assignment. The Senior Energy Engineer shall at least fifteen (15) years of experience in energy engineering (energy systems design, facility energy modeling, auditing, energy studies, commissioning, and validating and executing energy conservation projects). The person shall have a Bachelor’s degree from an accredited university in either mechanical or electrical engineering. The person shall have at least three (3) years of demonstrated recent relevant experience in facility energy modeling and have strong background in mathematical modeling. The Senior Energy Engineer must have a thorough background in DOD, Army and Federal Energy and Sustainability laws, policies, executive orders, regulations, instructions, and guidance. There shall be only one Senior Energy Engineer on this contract. Additional considerations will be given for licensed Professional Engineers (PE). Additional considerations will be given for DOD or DOA experience. Additional considerations will be given for a Certified Energy Managers (CEM). A PE license will be considered superior to a CEM certification.

5.7.4 Senior Information Security Engineer (ISSE). (Key Personnel) The Senior ISSE is responsible for the design, development, implementation, and/or integration of a DOD IA architecture, system, or system component for use within CE (computing environment), NE (network environment), and/or enclave environments. The Senior ISSE must meet the Department of Defense Directive (DoDD) 8570.01 “Information Assurance Training, Certification, and Workforce Management” and DoD 8570-M “Information Assurance Workforce Improvement Program” requirements. The Senior System Security Engineer shall have a Bachelor’s degree in engineering or an information technology field and a minimum fifteen (15) years demonstrated recent relevant experience in the cyber security or information technology sector. The ISSE shall have five (5) years of experience in performing information assurance (now called cybersecurity) and security engineering in the process control industry. The ISSE shall have a minimum of five (5) years of demonstrated recent relevant experience in performing information assurance and security engineering in the information technology industry for systems or networks and must have at least three (3) years demonstrated recent relevant experience performing information assurance and security engineering in the Department of Defense to include demonstrated recent relevant experience with the RMF process. The security engineering effort shall include identification, development, and implementation of the Information Assurance (IA) Controls, to include technical, procedural, and documentation requirements as described in DoD and Army requirements and guidelines. Additional considerations will be given for a Certified Information Systems Security Professional - Information Security Systems Engineer (CISSP-ISSE).

5.8 Certifications – All Contractor personnel shall maintain all certifications, access, documentation, security clearances, and professional licenses required to fulfill their responsibilities or to gain access to systems critical to fulfilling their responsibilities.

5.9 Contractor Man-hours Reporting -

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor will report ALL Contractor manpower (including sub-Contractor manpower) required for performance of this contract. The Contractor is required to completely fill in all the information in the format using the following web address: https://cmra.army.mil/Login.aspx. Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data. For internal Army analysis, the reports and queries from the database shall not contain proprietary data.

5.10 Qualified Personnel – All contract personnel shall have and maintain all certifications, approvals, clearances, and pathways established (including all requirements for IAT Level I, II, or III designations and Common Access Cards) sufficient for the management of the hosting solution. This shall include employees of vendors providing authorized cloud services.

5.11 Position Technology Refresh – Due to the high rate of evolution of technologies that may be required under this contract vehicle the contractor shall, in (Year 3), have the opportunity to propose new positions required because of the emergence of new technologies and specific skills required to support the potential new technologies. No positions in the award base rate table may be re-proposed or renegotiated.

6.0 SOFTWARE

The contractor shall support the program by operating, enhancing, and sustaining software applications required to meet the MDMS mission and provide a user experience that enables users to meet the MDMS objectives defined in section 2 in a secure matter in alignment with DOD and DOA policies. .

6.1 COTS – The Contractor shall operate, enhance, and sustain the COTS software that serves as the data infrastructure within the MDMS Enterprise solution and is the Army’s standard for meter data analyses. Approval for customization of COTS software integration shall be signed by the COR and communicated in writing by the COR. Configuring, extending functionality to include interfaces with COTS API, writing functions, and writing formulas with COTS provided tools is not considered customization. If the contractor uses the COTS API the contractor must show that the functionality does not exist natively within the COTS solutions or the contractor must prove through a ten year life cycle cost analysis that extending functionality/interfaces with the API is cheaper to the government than using included interfaces. The chosen COTS solution for MDMS is OSIsoft PI. The government has already made a significant capital investment in the COTS solution under the current contract and is not seeking to invest or recompete another COTS solution at the time of award. This does not prevent the government from replacing the COTS solution during the execution of this award if requirements, performance, or funding require moving to a new COTS solution. All code whether custom developed or within the COTS tool is the property of the government. This contract does not support development of a non-COTS tool.

6.2 User Interface/User Tools – The Contractor shall provide user interfaces that deliver required functionality to meet program objectives and meet Quality in Use Integrated Measurement (QUIM) metrics as defined in the PRS. The Contractor shall use International Organization for Standardization (ISO) Standard 9241 as guidance for best practices. The Contractor shall maintain support and compliance for all browsers supported in the Army Gold Master Windows baseline.

6.3 Functionality/Capability – The Contractor shall provide functionality and capabilities that support the MDMS mission in meeting its objectives as described in Section 3. The contractor shall work with the government product delivery team, proponents, users, and stakeholders to document required functionality, changes, and upgrades and delivery those functional requirements as needed.

6.4 Performance – The Contractor shall meet performance metrics for software as defined in the PRS and within the QASP associated with individual task orders

6.5 Test Environment – The Contractor shall furnish, maintain, operate, and sustain a development and test environment to (1) build new functionality, (2) test functionality, (3) debug existing functionality, (4) simulate operating conditions, & (5) test interoperability of MDMS components.

6.6 Documentation – The Contractor shall properly document all software and code in order to (a) maintain portability, (b) decrease learning curves, and (c) enhance troubleshooting capabilities through available reference. Software documentation should meet the following objectives:

1. Conceptual – To help understand goals, principles and methods involved in completing a process or task.

2. Instruction – To learn how to complete a procedure

3. Reference – To Search for details when something has been forgotten or when something unexpected happens.

6.7 Version Control – The Contractor shall provide quality version control tools to organize and control revisions in a logical way.

6.8 Management Information System (MIS) – The Contractor shall provide a dashboard, visualization tools, and reports within the COTS solution to provide the Government with metrics to understand and conceptualize the operational health of the MDMS system, statistical usage of the help desk, and the effectiveness of the program to meet objectives.

6.9 Geospatial Integration – The Contractor shall integrate the COTS solution with COTS geospatial tools in order to (a) provide a common operating picture for installations, (b) identify spatial relationships between time-stamped meter data and installation assets, and (c) provide a tool for enhanced analytics involving space-time relationships.

6.10 COTS User Roles – The Contractor shall provide tools to dynamically and trustfully manage user roles, permissions, groups, security, and authentication in compliance with applicable federal, Department of Defense, and Department of the Army Information Assurance & Cyber Security regulation, policies, instructions, and practices.

6.11 New Functionality Capability – The Contractor shall be able to deploy new functionality quickly within the COTS suite of tools without requiring development of new code.

7.0 SYSTEM HOSTING

The Contractor shall provide system hosting in a DoD-approved hosting environment with minimal dependencies on entities outside the Contractor’s team. The environment shall support mature Infrastructure as a Service & Software as a Service capabilities for the Contractor and Government technical teams. The hosting environment must be agile, responsive, and easy to reconfigure server, network, and environment specs. Authorized Cloud Service Providers through the Federal Risk and Authorization Management Program (FedRAMP) are approved provided they prove the ability to meet all applicable Army and DoD Information Assurance and Information Technology regulations, standards, policies, and best practices and enable the MDMS to maintain its RMF accreditation.

7.1 Requirements Identification – The Contractor shall initially and periodically conduct requirements analysis in regards to the MDMS hosting solution to determine the needs or conditions to meet for successful mission execution and sustainment of the MDMS hosting solution.

Requirements should be documented, actionable, measurable, testable and related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

7.2 Document – POC List – The Contractor shall develop and maintain a point of contact list for persons serving as a focal point of information attributed with the successful sustainment of the MDMS solution.

7.3 Cybersecurity inherited controls identification – The Contractor shall identify common controls that are employed at the hosting, facility, installation organizational level or serve multiple information systems that are, or should be, referenced as inherited controls in MDMS RMF artifacts and properly documented in eMASS through the RMF process for the MDMS solution.

7.4 Credentials/CAC - The Contractor shall ensure that the MDMS hosting solution meets all applicable DoD Information Assurance and Information Technology regulations, standards, policies, and best practices. Access to the MDMS hosting solution should be available only to properly credentialed individuals who have met IAT Level I, II, or III depending on their position requirements and functions. All users must be properly authenticated according to DoD and DA requirements.

7.5 Ports, Protocols, and Services Management (PPSM) Compliance – The Contractor shall be compliant with DoD Instruction 8551.01 (Ports, Protocols, and Services Management). The Contractor shall use approved standard procedures to control the use of protocols in the Internet protocol suite and associated ports. The Contractor will request PPS changes, updates, and modifications through the NETCOM defined process. The Contractor will ensure new PPS are properly documented and submission of a Component Service Level Assessment (CLSA) is submitted through the Army PPSM Technical Advisory Board (TAG) as needed for a new PPS where required.

7.6 Computer Network Defense (CND) Service Provider Requirement – The contractor shall coordinate and develop MOA with CND service provider, or to achieve waiver.

7.7 Maximum Use of Available Enterprise Service – The Contractor shall ensure maximum use of available Enterprise Services.

7.8 Quality Assurance on Services Received – The contract shall provide within 60 days of award a Quality Assurance Plan to ensure quality of products and services received from the MDMS hosting provider.

8.0 BILLING

The Contractor shall provide tools to support Energy Mangers to automate tenant billing. The billing tools should be available within the COTS system. The MDMS requirements define tools/reports to be given to installation Resource Management (RM), tenants, and users by energy managers. RM handles actual billing through their systems. MDMS does not need to interface or replace actual billing functionality handled by installation RM.

8.1 – The Contractor shall enable MDMS user to produce reimbursable tenant billing documentation that complies with all applicable Army regulations and policies to include but not limited to Army Regulation (AR) 420-41.

8.2 – The Contractor shall incorporate tools to show a tenants meter readings, meter reading dates, current month usage, and usage compared against same month last year.

8.3 – The Contractor shall implement functionality so that once the initial tenant billing report is set-up for a tenant by a MDMS user, the MDMS shall automatically update the report (bill) each month by the 10th of the following month.

8.4 – The Contractor shall implement functionality to implement levelized billing

8.5 – The Contractor shall provide templates within the MDMS of applicable contract forms to include but not limited to those included in AR 420-21.

8.6 – The Contractor shall provide functionality to provide convenient means for MDMS users to produce a utility bill in an electronic format.

8.7 – The Contractor shall provide functionality to provide an Energy Manager with the ability to produce multiple tenant billings reports for a designated time frame.

8.8 – The Contractor shall provide the ability to produce a report for a tenant to budget upcoming fiscal year (FY) energy costs based.

8.9 - The Contractor shall provide the ability to implement tenant billing according to virtual meters. A virtual meter is an algorithm-defined meter which calculates consumption based on the sum or difference between physical MDMS meters or estimates consumption using engineering estimates that can be defined and configured by the installation energy/utility manager.

9.0 METER DATA

The Contractor shall be able to track, record, and report utility consumption with respect to time in typically one-hour intervals (with ability for select meters at fifteen (15) minute intervals) and for a minimum of three (3) years, with the ability to archive consumption data up to twenty-five (25) years to be retrieved later as needed. Utilities include but are not limited to electricity, gas, steam, chilled water, heating hot water, potable water, irrigation water, garrison master meter, renewable, and production meters.

9.1 Parsing & Cleaning Time-Stamped Meter Data – The Contractor shall be able to parse and clean time-stamped meter data delivered from the installations in the most efficient method possible or whatever is deemed the best technical solution to provide reliable time-stamped energy data to user.

9.2 Historian Database – The Contractor shall provide the ability through the MDMS COTS solution to successfully parse meter data into coordinated universal time (UTC) in a time-stamped historian database stored as EPOCH 1970 milliseconds. The Contractor shall store time-stamped data in a non-relational database optimized for handling time series data.

9.3 Compress Data – The Contractor shall provide the ability through the MDMS COTS solution to compress time-stamped meter data using a sliding door algorithm.

9.4 Read Records – The Contractor shall provide the ability to read 100,000 records per second from the time-stamped historian database.

9.5 Meter Data – The Contractor shall store the time-stamped data in a non-relational database optimized for handling time series data.

9.6 Meter Metadata – The Contractor shall store static data that provides context to time-stamped meter data in an enterprise relational database. Examples of metadata include but are not limited to meter make, model number, and serial number, meter resolution, max reading, GPS coordinates, building zone/transformer/circuit served, size of PTs and CTs, max service capacity, etc.

9.7 Meter Data Standardization and Transfer – The contract shall implement technology and data standards that ensure data always remains in the same format and type from the IP meters/building point of contacts to the enterprise. Data should not be transformed by type, format, or storage type as it moves through the enterprise. Data logging should be used to ensure that a meter reading is only handled one time and is not resent multiple times through the enterprise.

9.8 Frequency & Scalability – The Contractor shall provide the ability for meter data to change in frequency and scale depending on the appropriate level for facility and time periods. The MDMS solution should be scalable in granularity (Interval, Hourly, Daily, Monthly, Quarterly, & Annually) and scalable by units appropriate for context or report or tool (kWh, MWh, Btu, MBtu, MMBtu, gal, kgal, Mgal).

9.9 Estimation/Interpolation of missing or erroneous data – The Contractor shall implement to estimate or interpolate missing or erroneous meter data.

9.10 Utility Privatization (UP) – The Contractor shall obtain and import UP Meter data into MDMS by secure file transfer protocol (SFTP) whenever UP provided data is available.

9.11 Standards – The Contractor shall support the MDMS Program & AMP Program in developing and publishing data, communication, implementation, and design standards.

9.12 Meters Army Common Installation Picture Geospatial Feature – The Contractor shall be responsible for collecting, maintaining, and submitting meter geospatial features to the Army Information Atlas for the entire Army enterprise. The contractor shall develop and maintain a Quality Assurance Plan for meter features.

10 ENERGY ENGINEERING

The contractor shall configure the COTS software solution to at a minimum do the following energy engineering/analysis functions within COTS environment.

10.1 Normalization – Report meter consumption data normalized by square footage, weather, occupancy, and other pertinent variables (e.g., per student trained, per widget produced, per soldier deployed, etc., as related to the mission of the facility/installation).

10.2 Benchmarking – Benchmark facility energy use against self (historically weather normalized) and against Energy Use Intensity (EUI) targets by Army CAT Code (ASHRAE Standard 100 Facility Type) and ASHRAE climate zone according to Tables 1 through 3 of Sustainable Design and Development Policy Update (ASA-IEE Memorandum, Jan 17, 2017). Historical EUI data from all facilities will be used to periodically update the EUI targets within the referenced tables.

10.3 MDMS Data Export – Export MDMS data for external analysis activities such as calibrating or comparison with building energy simulation modeling tools, conducting remote energy audits, and conducting traditional ASHRAE Level 1, 2, and 3 audits. The time granularity for these tools should be scalable (lowest interval [typically fifteen (15) minute], hourly, daily, weekly, monthly, quarterly, and annually).

10.4 Project Milestone – Benchmark energy conservation measure projects or implemented behaviors and provide reports to quantify savings for implemented projects or behaviors.

10.5 Management of Condition-Based, Key-Event Notification/Alerts – Set conditions where the MDMS COTS solution notifies designated role-based users when a condition has passed a defined threshold. The conditions can be set for a number of opportunities to include but not limited to facility energy use, system health, condition-based maintenance, faulty meter reporting, and network health.

10.6 Enterprise Analytics – Assist the US Army with analytics to prioritize opportunities at the enterprise level.

10.7 Query/Research Tools – Provide the ability for power users/analyst to conduct dynamic custom research, validate opportunities or suspected trends, and conduct custom data calls within the COTS environment using COTS-native tools that relate, contextualize, group, and transform data.

10.8 Trend Analysis – Analyze trends in data for relationships and, based on these findings, make recommendations that can be used to improve data filtering and missing/erroneous data interpolation/estimation methods, and improve, enhance, and extend MDMS forensic and predictive capabilities over the contract term. Some of these recommendations may be executed as task orders under this contract. Some of the findings may also be included within the Technical Training (5.x.x) scope of services.

10.9 – Commissioning – The contractor shall provide continuous commissioning meter analysis tools to assist energy mangers in continuous commissioning efforts in metered facilities.

10.10 – Remote Auditing – The contractor shall provide the ability to implement or conduct remote energy audits as a lower-cost equivalent to engineer performed audit in terms of energy savings projections. The remote auditing tools shall be able to identify inefficient building systems and projects a range of costs for an energy-efficient replacement from a facility level meter. Remote Building Analytics (RBA) or remote audits are not considered to be an equivalent or replacement of ASHRAE Level 1, 2, or 3 walk through surveys.

10.11 – Advance Analytics – The contractor shall provide advance analytical tools as required to support the MDMS mission. These tools could include but not be limited to advanced applied statistics applications commonly used by scientist, machine based learning modeling tools, or any other tool or technique beyond those of traditional business intelligence tools.

11 INTERFACES

The contractor shall be responsible for ensuring the program has the ability to interface quickly and cost-effectively with a variety of devices, standards, protocols, formats, and external data sources as maintain interoperability as a key indicator of mission success.

11.1 COTS Interfaces - The Contractor shall provide as COTS functionality the ability to quickly and cost-effectively interface with a variety of devices, standards, protocols, formats, and external data sources to ensure the ability to connect with a variety of assets. The COTS solution as a minimum should be able interface with common industrial electronic device communication protocols to include but not limited to Modbus, Lonworks, BACnet, and IP.

11.2 Support Existing Interfaces – The Contractor shall support the following existing, authorized interfaces so long as they are deemed a requirement for executing the mission of MDMS:

A Gateway interface to UMCS/EEDRS SQL B. Gateway interface to Enterprise Hosting Site

C. Gateway interface to RCC/JRSS/TLA DMZ firewall D. Gateway interface to Army boundary router E. VRF assignments F. IP Management

12 Cyber Security/Information System Security Engineering (ISSE) The Contractor shall be responsible for planning and carrying out security measures to assess, document, configure, test, monitor and protect the MDMS. The Contractor shall develop information security plans and procedures, implement protections, test for and mitigate vulnerabilities, monitor and report security breaches, execute contiguous monitoring activities, and sustain MDMS in accordance with the RMF security plan and artifacts

12.1 ISSE Best Practices – The Contractor shall implement ISSE best practices to include but not limited to NIST Special Publication 800-160, ISO 27001, ISO 27034,

12.2 Completion and Government Approval of Scan/Fix/Scan Testing and Analysis. The Contractor shall periodically assess (scan and perform manual checks) its own system using approved IA scanning tools and in coordination with supporting NECs (for installation level system components within the MDMS accreditation boundary). When issues are found (Category (CAT) 1, 2, or 3 vulnerabilities) the Contractor shall fix those issues in accordance with the timeframes associated with the severity of the finding, either provided by ARCYBER, ACSIM, IAPM or the DAA, and rescan the system to ensure all issues have been fixed and/or properly and acceptably mitigated. CAT 1 issues (and CAT 2s) that cannot be fixed are to be reported to the Government immediately along with a valid reason the vulnerability cannot be fixed, initiate an action to mitigate the vulnerability, and submit a plan to fix the vulnerability in the future (submit in POA&M format). The DAA has to approve having CAT 1s on a system. The goal is for the system to maintain a proper IA posture. The scan/fix/scan should find and fix all issues before a formal assessment, as part of an approved change to the system, or as required by DoD/Army policy. The scan/fix/scan data and analysis shall be provided to the government. If the system is hosted at a Government Datacenter, the Contractor will coordinate all scanning activities with the hosting facility.

12.3 Technical QA – The Contractor shall develop and submit an ISSE Quality Assurance Plan within 30 days of award.

12.4 ISSE Code review - The Contractor ISSE shall be responsible for all existing code. The Contractor shall analyze scan results of the code for vulnerabilities and mitigate all vulnerabilities or properly document government approved deviations.

12.5 Vulnerability identification, analysis, and mitigation – The Contractor shall conduct vulnerability analysis to identify and mitigate security vulnerabilities within the MDMS.

12.6 Product review for compliance with Army and DoD policy – The Contractor shall conduct a periodic product review of all MDMS components for compliance with Army and DoD Information Assurance policies. All new products must be reviewed before implementation.

12.7 Security Technical Implementation Guide – The Contractor shall ensure all MDMS devices/systems are configured to DoD and Army IA standards. The Contractor shall monitor for STIG changes that effect MDMS components and implement those configuration changes.

12.8 Security Content Automation Protocol (SCAP) and Assured Compliance Assessment Solution (ACAS) scanning – The Contractor shall conduct SCAP and ACAS vulnerability scanning where authorized. The Contractor shall analyze scan results of the code for vulnerabilities and mitigate all vulnerabilities or properly document government approved deviations.

12.9 Information Assurance Vulnerability Alert Compliance – The Contractor shall ensure compliance with all Information Assurance Vulnerability Alerts through the United States Computer Emergency Readiness Team – (US-CERT).

12.10 Configuration Control Board (CCB) Support and Participation – The Contractor shall support and participate in CCB meetings and activities and support the CCB in facilitating systematic proposal, justification, evaluation, coordination, approval, or disapproval of configuration changes and the implementation of approved configuration changes.

12.11 Configuration Management Process – The Contractor shall establish a process to (1) identify change, (2) manage that change, (3) ensure that the change is being properly implemented, (4) report the change to others who may have interest, and (5) record the change for historical reference .

12.12 Information System Security Officer (ISSO) Appointment – The Contractor shall appoint an ISSO to provide oversight to ensure established cybersecurity policies and procedures are followed.

Those policies include but are not limited to DoDI 8500.01, AR 25-2.

12.13 Policy enforcement at the system level – The Contractor shall be responsible for cybersecurity policy enforcement at the system level. Policy enforcement should be included in the Quality Assurance plan described in 4.2.3.

12.14 Cybersecurity technical representative in meetings – The Contractor shall provide a cybersecurity/ISSE representative in all technical meetings to include design meetings.

12.15 ISSE PPSM technical input/review – The Contractor shall provide the technical review and input for system security as is relates to PPSM compliance.

12.16 Information Security Policy & Concurrency – The Contractor shall establish a process for identifying and reviewing new or changing Information Security policies and implementing policy changes. This should be included within the Quality Assurance plan implemented described in 5.6.8.

In addition the Contractor shall be responsible for any additional artifacts or documentation required due to policy changes.

12.17 Training and Certification Requirements – All Contractor personnel fulfilling ISSE Cybersecurity or System Administration roles must meet the Department of Defense Directive (DoDD) 8570.01 “Information Assurance Training, Certification, and Workforce Management” and DoD 8570-M “Information Assurance Workforce Improvement Program” requirements for each position.

12.18 Standardize templates/document formats – The Contractor shall develop standardized template and document formats for ISSE tasks, where they do not currently exist to include documents to support Configuration Management submission.

12.19 Risk Management Framework Accreditation – The Contractor shall maintain the MDMS RMF accreditation to include all services associated with sustaining the accreditation packages. The Contractor shall be responsible for developing, managing, and updating RMF documentation and artifacts.

12.20 Enterprise Mission Assurance Support Service (eMASS) Access, Credentials, and Training – The Contractor shall be responsible for (a) ensuring appropriate Contractor access to eMASS, (b) employees have the proper credentials for accessing eMASS, and (c) employees are properly trained on the eMASS tools. All Contractor personnel responsible for fulfilling IA/RMF/eMASS roles must meet the Department of Defense Directive (DoDD) 8570.01 “Information Assurance Training, Certification, and Workforce Management” and DOD 8570-M “Information Assurance Workforce Improvement Program” requirements for each position.

12.21 eMASS Sustainment – The Contractor shall be responsible (a) input of relevant information into eMASS, (b) Profile Management & Sustainment, (c) review and verification of eMASS artifact.

12.22 eMASS Authorization – The Contractor shall be responsible for supporting the Information System Security Managers(s) and Authorizing Official (AO) by coordinating and providing follow up on associated tasks related to MDMS risk management and authorization activities.

12.23 Army/DOD Cybersecurity Policy & RMF Process SME – The Contractor shall provide SME in regards to Army and DoD Cybersecurity Policy and Army and DoD RMF processes.

12.24 APMS Support – The Contractor will provide Army Portfolio Management System (APMS) data input

13 ASSET METADATA MANAGEMENT

The contractor shall manage data that provides context to meter interval data and provide one version of the truth to users no matter how they access MDMS data.

13.1 Asset Management – Provide tools to dynamically import and manage associated metadata that can provide context to meter readings in a variety of methods to include hierarchical structure and/or model based structure. The tool shall be able incorporate any dataset that can provide context to meter data or support the mission of the MDMS. The tool should provide the ability for a user to add new data types and categories and to manage the hierarchical relationship between datasets within the user interface and without developing new code. The tool should provide the ability to group data by multiple factors in a single query.