ATTACHMENT 1 Sample TO PWS Amendment 0003.docx

DOCX document 25 KB Posted

Attached to
Meter Data Management System (MDMS) Federal contract opportunity
Solicitation number
W912DY24R0001
Issued by
Department of the Army Corps of Engineers Engineering Support Center Huntsville

About this file

This document is a Performance Work Statement (PWS) for a Meter Data Management System (MDMS) Operations and Maintenance Task Order. The primary objectives are to: (1) deliver dependable meter data, (2) use industry standards to normalize data and establish facility energy consumption, (3) provide tools to enable facility and energy managers to identify energy reduction opportunities, (4) support continual advancement and optimization, (5) keep the system compliant with policies and regulations, and (6) use system engineering techniques to reduce sustainment cost and complexity. Key tasks include acquiring and implementing a COTS software solution, migrating the MDMS enterprise environment to a commercial cloud vendor, implementing system engineering and quality control processes, providing energy engineering expertise, and performing operations and maintenance support. The PWS includes detailed requirements, labor estimates, and schedules for each task. The related federal contract opportunity is a solicitation (W912DY24R0001) for the Army Corps of Engineers to operate, enhance, and sustain the Army's centralized MDMS.

View the file

Other files for this federal contract opportunity

Show all 19

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT

Meter Data Management System (MDMS) Operations and Maintenance Sample Task Order (TO) XX Version XX

XXXX

XXX

1.0 BACKGROUND

Regarding the purpose of metering, Department of Defense Instruction 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.”

1.1 OBJECTIVE

The primary objective of this Sample Task Order is to accomplish the MDMS 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.

1.2 SCOPE OF WORK

1.2.1 Schedule - The order of tasks issued in section 1.2 do not reflect the order of execution of tasks. In addition it is expected that tasks will be worked concurrently if possible.

1.2.2 Task 0001 Acquire and Implement the COTS Software Solution

1.2.3 Task 0002 Maintain the MDMS Authorization

1.2.4 Task 0003 Migrate MDMS enterprise environment from Defense Information Systems Agency – Oklahoma City to a Commercial Cloud Vendor.

1.2.5 Task 0004 Implement and Sustain System Engineering and Quality Control Processes

1.2.6 Task 0005 Energy Engineering

1.2.7 Task 0006 Operations and Support – Sustainment

1.2.8 The MDMS Enterprise System at the beginning of this task Order is MDMS Version 2 with OSIsoft PI. MDMS Version 2 will be running at 118 installations at the start of this task order, while OSIsoft PI will be running at 2 installations.

2.0 Task 0001 Acquire and Implement the COTS Software Solution

2.1 The Contractor shall implement OSIsoft PI System as provided by the Government and maintain the license for the Government.

2.2 The Contractor shall include in the proposal the implementation strategy for implementing OSIsoft PI at all garrisons and sunsetting MDMS V2.

2.3 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

2.4 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B.

2.5 The Contractor shall recommend and then implement functional MDMS capabilities at the energy manager, garrison, major command, and enterprise level. The proposal shall at a minimum identify:

2.5.1 The user tools to be provided at each level and the justification for each tool.

2.5.2 The user tools required to manage the MDMS program by providing insight into system health and reliability; support data calls; and support programmatic decision making, coordination, control, analysis, and visualization.

2.5.3 The geospatial tools used to support a Common Operating Picture (COP) for MDMS situational awareness and the geospatial tools used for advanced analysis.

2.5.4 The contractor shall be responsible for a) sustainment of the meter Army Common Installation Picture geospatial feature database, b) submission of the meters feature and metadata to the Army Installation Atlas, c) development and sustainment of the Quality Assurance Plan for this feature.

2.5.5 Any other improvements or enhancements that are cost effective, reduce sustainment footprint, increase reliability, or reduce sustainment costs.

2.5.6 All capabilities not included above but required by relevant DOD, Army, or federal policy, law, regulation, or instructions.

2.6 The Contractor shall provide in the proposal a training approach for the new functionality.

2.7 The Contractor shall provide as part of the proposal a system architect drawing as well as any other relevant drawings for the proposed MDMS solution.

2.8 Customization of the implementation of the COTS software will only be allowed if determined that (a) COTS cannot meet technical requirements, (b) custom development does not increase sustainment costs, (c) does not increase or create dependence on specialized or costly labor, (d) does not increase implementation timelines, and (e) does not create a dependency that would provide an unfair advantage to Contractor.

3.0 Task 0002 Maintain the Risk Management Framework (RMF) Authorization

3.1 The Contractor shall maintain the MDMS RMF Authorization.

3.2 The Contractor shall include in the proposal a plan to maintain the RMF authorization At a minimum the plan shall include:

3.2.1 Position and/or responsibilities required by DOD, Army, of Federal policy, law, regulation, and instruction to fulfill this requirement.

3.2.2 Site applicable DOD, Army, or Federal regulation, law, policy, or instructions.

3.2.3 The Contractor’s approach for future reauthorization and annual self assessments.

3.3 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

3.4 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B.

4.0 Task 0003 Migrate to Cloud

4.1 The Contractor shall migrate MDMS from DISA to an approved DOD commercial cloud provider.

4.2 The Contractor shall provide in the proposal an implementation plan to migrate MDMS from DISA to an approved DOD commercial cloud provider. The plan at a minimum shall include:

4.2.1 Evaluation of cybersecurity and .mil network requirements.

4.2.2 Identify and Quantify sustainment requirements.

4.2.3 Evaluate all applicable Software as a Service (SaaS), Infrastructure as a Service (IaaS), and Platform as a Service (PaaS) options from each approved DOD provider studied by the contractor.

4.2.4 Define what services the Government should inherit from each provider as well as services that can be managed by the Cloud Service provider.

4.2.5 Identify whether Machine Learning /AI or other technologies provided by Cloud Service Provider can be of benefit to the Government.

4.3 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

4.4 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B.

5.0 Task 0004 System Engineering

5.1 The Contractor shall implement a system engineering process to reduce system sustainment costs and system complexity and support the objective described in section 1.1.

5.2 The Contractor shall include in the proposal a plan to implement and sustain their system engineering process.

5.3 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

5.4 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B.

5.5 The Contractor shall provide whitepapers and proposals for improvements to the overall AMP program as inefficiencies or bugs are discovered.

6.0 Task 0005 Energy Engineering

6.1 The Contractor shall serve as the Energy Engineering subject matter experts for the MDMS to ensure the system provides functional requirements based on sound Energy Engineering principals and science.

6.2 The Contractor shall provide, as part of the proposal, an implementation plan to ensure the MDMS system is providing functional tools based on sound Energy Engineering principals and science. At a minimum the proposal shall include:

6.2.1 How to model and benchmark facilities.

6.2.2 Commissioning Tools.

6.2.3 Energy Engineering Functions that should be included as features in the MDMS tool.

6.2.4 Site relevant Federal, DOD, and Army policies, regulations, instructions and laws.

6.2.5 Site relevant Industry best practices.

6.3 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

6.4 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B.

7.0 Task 0006 Operation & Maintenance

7.1 The Contractor shall provide continuing Operation and Maintenance support for MDMS,

7.2 The MDMS Enterprise System for the terms of this Task Order is MDMS Version 2 and OSIsoft PI until Task 0001 and Task 0003 are completed. At that point MDMS V2 will be sunsetted. The amount of garrisons to support for V2 and OSIsoft PI whenTask0001 and Task0003 are completed will be determined by the Contractor’s proposed implementation strategy developed in Task 0001.

7.3 The Contractor shall in supporting the database of record for meter data and meter metadata propose a database management plan. The Contractor shall also proposes a plan for enterprise management of the Army Common Installation Picture (CIP) geospatial to include submission of geospatial meter data to the Army Information Atlas (AIA) and for developing a Quality Assurance Plan for submitting data to AIA.

7.4 The Contractor shall provide a detailed labor effort breakout for this task in the format provided in Appendix A.

7.5 The Contractor shall provide a detailed schedule for this task in the format provided in Appendix B

7.6 The Contractor shall provide as part of the proposal an Operation and Maintenance plan. At a minimum the proposal shall include:

7.6.1.1 Program Management Philosophy and Strategy

7.6.1.2 Support for Data Calls

7.6.1.3 Program Outreach and Support

7.6.1.4 Support for adding value driven functionality

8.0 Schedule

The period of performance of this task will be part a) the time to complete Tasks 0001 and Task 0003, and part b) 1 year of sustainment once Task 0001and Task 0003 are completed. Tasks 0002, 0004, 0005, and 0006 are perpetual and will be included throughout the period of performance. The Contractor shall in the proposal break out the labor for each task separately for part a and part b using the provided format in Appendix A and shall provide the schedule for the period of performance described in Appendix B.

File details come from the government source that posted it. Updated .