1: Collect & Review Baseline Documentation
Baseline Development / Collect & Review Baseline Documentation
Not Started

Inputs Needed

  • Critical functions from the Site-Level Planning module and the facilities that house them

Outputs

  • Documentation on facilities and critical loads required for Baseline Development: Action 2, Risk Assessment: Action 1, and Solution Development: Action 2
  • Documentation on redundant systems required for Baseline Development: Action 3 and Solution Development: Action 2
  • Points of contact for data and identified data gaps

Overview

This action identifies and consolidates sources of information used to establish the site’s critical energy and water requirements and baseline conditions of energy and water systems. In Site-Level Planning, data collection focused on establishing critical missions and functions and the status of site-wide planning for emergencies and business continuity. In Baseline Development, data collection focuses on the facilities that carry out those critical functions and the energy and water systems that supply and provide redundancy to critical loads.

In-Depth

Information Classification Considerations
Some of the data gathered through the Baseline Development process may be considered classified or sensitive. Prior to starting data collection, the resilience planning team should seek guidance from designated information security personnel. Some organizations have documented guidelines on topics that may be treated as potentially classified. These can include details on critical missions, functions, facilities, or other assets, particularly when specific vulnerabilities and the locations of those assets are identified or disclosed.

Data collection for Baseline Development focuses on energy and water end-use data, as well as the design operation and maintenance of both onsite redundant and primary supply systems. Energy and water use data for the site and specific facilities can be identified from central sources as an initial step and reviewed in more detail once critical loads in those facilities are identified in Action 2. Similarly, general data on redundant systems at the site (e.g., where they are, system capacity, age) can be gathered from central data sources, then examined more carefully once it is understood which redundant systems support critical loads.

Leveraging Data Collection Efforts

Data collection for the TRN is designed to inform risk assessment and enhance resilience through stakeholder interviews, audits, and documentation review. These data collection efforts could also serve other related site priorities, beyond risk and resilience. For example, a single facility audit could not only be used to identify energy and water efficiency opportunities but also the status of redundant energy and water systems. This would meet both federal facility audit requirements and establish whether the redundant systems in place represent risk to the site. Be sure to coordinate with other site planning teams during data collection to achieve related site goals when possible. Other FEMP resources on facility auditing, cybersecurity assessment, and laboratory benchmarking may be used to guide these related data collection efforts.

Use the Baseline Development Action 1 worksheet to identify sources of documentation required and how the data will be used. Note who the primary data owners are and verify with them that the documentation is the most recent, available, and accurate. Add relevant data sources to the checklist as needed. Items with an asterisk (*) are key inputs to the TRN Risk Assessment model and should be prioritized for data collection.

Information Classification Considerations
Some of the data gathered through the Baseline Development process may be considered classified or sensitive. Prior to starting data collection, the resilience planning team should seek guidance from designated information security personnel. Some organizations have documented guidelines on topics that may be treated as potentially classified. These can include details on critical missions, functions, facilities, or other assets, particularly when specific vulnerabilities and the locations of those assets are identified or disclosed.