A02.12_PWS_Specialized Power and Reliability Consulting_DRAFT.docx

IAC MAC Task Order Performance Work Statement Specialized Power and Reliability Consulting (SPARC), United States Army Corps of Engineers, Power Reliability Enhancement Program P1-17-1455

BACKGROUND

United States Army Corps of Engineers (USACE) Power Reliability Enhancement Program (PREP) provides technical management, staff support, and specialized consultation to Department of Defense (DoD), Joint Chiefs of Staff, and Unified Combatant Commands to improve and assure mission reliability of electric power and mechanical cooling systems and other infrastructure that supports the National Military Command System (NMCS) as well as Command, Control, Communications, Computer, Intelligence, Surveillance, and Reconnaissance (C4ISR) facilities. The tenants of the PREP mission are to ensure the reliability of the electric power and mechanical cooling systems; establish design criteria for C4ISR facilities; perform critical facility assessments; and assist facility managers to remove utility vulnerabilities.

PREP conducts a variety of specialized analyses on critical facilities specifically designed to identify vulnerabilities within utility systems and to provide recommendations to reduce component and system failures resulting in minimized downtime and maximized mission reliability. PREP also maintains a one-of-a-kind comprehensive database supporting a variety of analytical approaches for facility technology updates. The database, managed using Microsoft Access software, has over 1.8 million records, and is documented in both Technical Manual (TM) 5-698-5 and by the Institute of Electrical and Electronics Engineers (IEEE) in the IEEE Standard 3006.8, Design of Reliable Industrial and Commercial Power Systems.

OBJECTIVE AND SCOPE

Objective The primary purpose of this Task Order (TO) is to research, analyze, provide advice, and develop deliverables to advance Information Analysis Center (IAC) Multiple Award Contract (MAC) related scientific and technical information (STI) through the application of knowledge and resources in achieving the requiring activity's mission requirements defined herein.

The specific objective is to improve the reliability of the power distribution and mechanical systems within the C4ISR buildings that support the critical missions executed by War Fighters around the world. The contractor shall assess facility conditions and Operations and Maintenance (O&M) practices. Assessments shall include fault current analysis, arc flash and relay coordination, power quality analyses reporting, mechanical and electrical site condition surveys for determining systems reliability and availability, as well as drafting new or updating existing design criteria that could be adopted and used within all critical facilities to enhance system reliability. A database expansion effort will collect new data for insertion into an existing, large database of failure criteria for most of the typical components that make up an electrical or mechanical utility systems, and which forms the basis by which automated maintenance management systems operate. The goal of this TO is to enhance the situational awareness of DoD facility managers regarding operational status of facilities and expose them to new technologies and automation tools to more efficiently operate, manage, maintain, and repair facilities to maximize mission availability.

Scope IAC MAC Basic PWS References. The work under this TO is within the scope of the following IAC MAC Basic Performance Work Statement Technical Focus Areas: Software Data & Analysis (1.4.2.3.1) and Knowledge Management and Information Sharing (1.4.2.3.4).

Requiring Activity and Partners. The work under this TO is being done principally for the USACE PREP Office at Fort Belvoir, Virginia. Typically, the contractor shall travel to Government critical sites, collect utility system data specific to the study being performed, and return to their home office to complete the analyses, then submit completed reports to PREP.

TASKS

The Contracting Officer (CO) is the only person authorized to direct the contractor or take any actions that would change the TO or commit the Government in any way. The CO will appoint an Alternate Contracting Officer’s Representative (ACOR) in the PREP office who will be the Requiring Activity’s contact. The ACOR will work with the contractor pursuant to the scope of the PWS to meet mission requirements.

Any and all source code, models, prototypes, programming, language, licensure, enterprise-wide rights, software, Contract Data Requirement Lists (CDRLs), manuals, training documents, and other similar products and related data developed, modified, or created under the TO shall be exclusively at the United States (U.S.) Government's expense. Per DFARS 252.227-7014(b)(1), all of these items must be delivered to the U.S. Government with unlimited rights. As such, the Government may use, modify, reproduce, release, perform, display, or disclose the source code in whole or in part, in any manner and for any purpose whatsoever, and it may authorize others to do so. The actual deliverable quantities will be decided by the ACOR and RA upon delegation of each task; estimated quantities are provided for reference.

(Task 1) – Program Management Post Award Orientation. The Post-Award Orientation shall be held within 7 calendar days of the start of performance. Schedule and conduct this meeting, in coordination with the ACOR, Contracting Officer's Representative (COR), and Contracting Officer (CO).

The purpose of the Post-Award Orientation is to: 1) discuss any unique characteristics of the requirement(s); 2) identify stakeholders' roles and responsibilities; 3) review the 30-day transition-in to full performance and 4) establish a common understanding of cost, schedule, and performance expectations (Deliverable 3.1-1: TO Post Award Orientation Slides).

Program Management Plan. Provide a Program Management Plan (PMP) within 15 days after order award and quarterly to the COR and ACOR. The Program Management Plan shall provide a resource-loaded schedule that outlines the steps that will be taken, the timeline to completion, and any associated risks with execution of the order. The PMP will be updated within 15 days of each new project tasking. The update shall specify estimated project start and stop dates as well as a risk mitigation plan and an expenditure plan aligned to key milestones within the project, to include any anticipated Other Direct Costs (ODCs). The update should highlight any interdependencies within the tasks and the projects schedules. Upon acceptance and approval by the Government, the contractor shall meet the cost, schedule and forecasted delivery date of all deliverables by taking all reasonable measures to fulfill the requirement and shall report monthly status updates in the Monthly Status Report (MSR) (Deliverable 3.1-2: Program Management Plan (PMP)).

Monthly Status Report. Submit a MSR. The MSR shall provide detailed status for the project(s) within the PMP as well as capture an overall status of the order. The MSR reports cost, schedule, and performance against PMP requirements and identifies status of funding, planned versus actual expenditures per project, total monthly and cumulative ODC expenditures, status of known risks, risk mitigation efforts, deliverables funded and date they were funded, technical progress made and schedule status per deliverable, the titles, dates and number(s) of deliverables completed, and the deliverables scheduled to be delivered during the upcoming month. The MSR shall report all funding received and shall detail the tasks or projects supported by such funding, and the funding source, if known. Specific MSR format, and any additional content not specified in this section, shall be mutually agreed upon by the contractor and ACOR; this should be established no later than (NLT) the Post-Award Orientation. If the MSR shows that a project is not meeting the performance standards set forth in the Service Summary found in Section 6.0, the contractor shall provide the rationale and circumstances preventing the standards from being met (Deliverable 3.1-3: Monthly Status Report).

Final Technical Report. The Final Technical Reports (FTRs) shall include TO-specific background information, objectives, assumptions, specific data collected, conclusions, analyses conducted, and recommendations. The first report shall be submitted half way through the Period of Performance (PoP). The final FTR is due NLT 45 days prior to the last date of the TO’s PoP. Each report shall be delivered to the ACOR and COR (Deliverable 3.1-4: Final Technical Report).

Redacted TO. Within 30 days of contract award, provide a redacted copy of the awarded TO that is appropriate for public release, which the Government intends to post to a public web site (Deliverable 3.1-5: Redacted TO).

Contractor Acquired Property (CAP) Report. Provide monthly report for all Contractor Acquired Property acquired via Other Direct Cost charging (Deliverable 3.1-6: Contractor Acquired Property Report).

Conferences. Do not expend any resources associated with hosting a conference until the requisite approval to conduct a conference has been obtained by the requiring activity from the appropriate approval authority in accordance with the current DoD Conference Guidance. Approval is required for each individual conference, unless one-time approval is provided for a recurring DoD-sponsored or hosted conference. A "conference" is defined in the Joint Travel Regulations as, "[a] meeting, retreat, seminar, symposium, or event that involves attendee travel. The term 'conference' also applies to training activities that are considered to be conferences under 5 CFR 410.404." The contractor shall be aware of and not incur any prohibited conference expenses per the DoD Conference Guidance. The DoD Conference Guidance can be located at http://dcmo.defense.gov/Products-and-Services/DoD-Conference-Policies-and-Controls. Contractor responsibilities may include coordinating a location for the technical symposium, and providing the venue by reserving and incurring the cost of meeting rooms and required technical equipment as Other Direct Costs (ODCs) under this TO. Additionally, contractors can manage attendee invites and acceptances, badging, security, and providing print outs of briefs to attendees. The contractor shall not expend any funds under this TO for providing food or nutrition for the technical symposiums/conference or for blocking off or reserving lodging for attendees (Deliverable 3.1-7: Conference Planning and Draft Approval Information; Deliverable 3.1-8: Conference Report).

Contractor Manpower Reporting (CMR). Report all contractor labor hours (including subcontractor, independent consultant and wholly owned subsidiary labor hours) required for the performance of services provided under this contract via a secure data collection site. Complete all required data fields at https://www.ecmra.mil. Reporting will be at the order level and must be reported according to the ACOR of this TO. Reporting inputs will be for the labor executed during the period of performance for each Government Fiscal Year (FY), which runs 1 October through 30 September, while the order remains active. While inputs may be reported any time during the FY, all data shall be reported NLT 31 October of each calendar year. Direct questions to the Contract Manpower Reporting Application help desk (Deliverable 3.1-9: Contractor Manpower Reporting (CMR)).

Completion Statements (DD250 & SF298). The DoD requires contractors who supply goods or services under a contract that contains DFARS clause 252.246-7000 to submit a material inspection and receiving report, a form DD250. This form is the receiving document used to record the delivery of goods or services including pertinent information about the TO. Defense Technical Information Center is the central repository for technical reports and comprises reports for the Department of Defense. In order to comply with the contract, the vendor must provide a completed DD250 and SF298 (Deliverable 3.1-10: STI TO Completion Statements).

Task 1 Deliverables Table

(Task 2) – STI Relevance Assessment and Gap Analysis In order to ensure that TO performance builds on the breadth of the DoD’s knowledge base and contributes to it, a Pre-Award Literature Search and an annual STI Relevance and Gap Analysis are performed. The pre-award literature search is performed by the Basic Center of Operations (BCO) functioning in the same technology domain area as the TO, e.g., Defense Systems, Cyber-Security and Information Systems, or Homeland Security and Defense. The results of this literature search are provided to the contractor performing the TO work at the Post Award Orientation. This literature search (conducted against the technical library of the Defense Technical Information Center) provides the TO contractor with the results of previous research done in the same technology area, providing a foundation of knowledge upon which the TO contractor can build.

The annual STI Relevance Assessment and Gap Analysis builds on the pre-award literature search performed by the BCO. In conducting the STI Relevance Assessment and Gap Analysis, the contractor shall do two things: first, for each search term in the pre-award literature search, highlight noteworthy examples of how the STI provided in that literature search significantly contributed to the performance of the TO work. Second, the TO contractor will identify any perceived gaps in the knowledge base as revealed in the literature search (e.g., the task required information on XYZ, but the literature search did not turn up STI on XYZ). This STI Relevance Assessment and Gap Analysis will be provided annually (during the life of the TO) to the BCO that generated the literature search. The identified gaps will show the BCO the areas in which they need to build knowledge, especially as the BCO notices trends across multiple TOs (Deliverable 3.2-1: TO-Specific Annual Gap Analysis).

Task 2 Deliverable Table

(Task 3) – TO Transition Support Transition-In. Facilitate the accomplishment of a seamless transition of requirements. Transition-In services shall begin on the effective date of the award and shall be complete on the date which is 30 days after the effective date when the contractor will assume full responsibility for Tasks 4 and beyond.

Identify points of contact (POCs) for liaison between the Government, the prime contractor (if applicable), and other contracted industry partners to ensure a proper and orderly transition and transfer of services and assets between the parties cited.

Ensure minimum disruption to vital Government business. The contractor shall ensure that there shall be no service degradation during or after transition.

Establish an overview of the transition efforts and describe the activities to transition, which shall include a schedule with milestones by activity.

Support the transition of Government property (if applicable).

Obtain the following from Government personnel:

a. Transition knowledge and information regarding risk or problem areas

b. Modeling capabilities, experiments, methods, and results to date (to include analysis and reporting status) Transition-Out Plan. Develop and execute a Transition-Out Plan that shall facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor or Government personnel at the expiration of the order. Provide a Transition-Out Plan no later than (NLT) 60 days prior to expiration of the order. Identify how the incumbent will coordinate with the incoming contractor and Government personnel to transfer knowledge regarding the following (Deliverable 3.3-1: Transition-Out Plan):

a. Program and project management processes

b. Points of contact

c. Location of technical, program and project management documentation

d. Status of ongoing technical initiatives

e. Appropriate contractor-to-contractor coordination to ensure a seamless transition.

f. Transition of key personnel

g. Identify schedules and milestones

h. Identify actions required of the Government

i. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of the transition via weekly status meetings

j. Transition Out Plan shall include:

1. Coordination with Government representatives

2. Review, evaluation, and transition of current support services

3. Transition of historic data to new contractor systems

4. Transfer of hardware warranties and software licenses (if applicable)

5. Transfer of all necessary business and technical documentation

6. Orientation phase and program to introduce Government personnel, programs, and users to the contractor's team, tools, methodologies, and business processes

7. Disposition of contractor-purchased Government owned assets, including facilities, equipment, furniture, phone lines, computer equipment, etc.

8. Personnel out-processing procedures, turn-in of all Government keys and ID or access cards

9. Transition of modeling capabilities, experiments, methods, and results to date (to include analysis and reporting status)

10. Transition of test method development status, technical approach for developing new test methods, testing status, and results to date (to include analysis and reporting status) Task 3 Deliverables Table

(Task 4) – PREP Database Analysis (IAW IAC MAC Basic Contract PWS 1.4.2.3.1) The purpose of this task is to increase the effectiveness of the PREP database. The PREP Database is a Microsoft Access based collection of reliability and maintenance information for 280 distinct categories of electrical, mechanical, and information technology equipment. This includes items commonly found in facility infrastructure, such as generators, transformers, chillers, pumps, servers, routers, cables, piping, valves, circuit breakers, and many others. Typical sites where data is collected include industrial or commercial facilities, universities and colleges, automotive manufacturing plants, petroleum industry sites, United States Post Office sites, and transportation providers. Based on lessons learned in the past, the Government will exercise strong control over the proceedings under this task in order to avoid wasted effort and to protect the integrity of both the processes used to collect the data and the actual database. The database has been published in commercial and Government standards, and will be made available for use by the contractor for the scope of this task.

The contractor will increase the quantity (i.e., number of unit-years of equipment data) and quality (i.e., number of complete records for a component) of the information. Only complete data records shall be added to the PREP database. A complete record includes component description, failure history data, maintenance records, parts descriptions data, operational periods, and at least five continuous years of recorded data.

The contractor shall protect all information and data collected from industrial plants, universities, manufacturing plants, etc. throughout the data collection and statistical summarization process as proprietary information. The contractor shall establish and strictly follow a methodology to maintain the privacy and confidentiality of the sites that provide data for the data collection effort in order to increase participation and ensure attaining a diverse set of data. The data protection policy must be able to separate collected raw data from the source such that no site specific information is carried forward into the database, but still maintain general attributable information about the type of facility and the data collected. The contractor will provide Non-Disclosure Agreements (NDAs) to participating data collection sites. At no time will site specific information or site participation be included in any reporting to the Information Analysis Center (IAC).

The PREP organization will get full disclosure and may at any point during the course of the project request copies of all collection, summarization, analysis, and incorporation files and reports already completed by the contractor. Upon completion of the project, all raw data collection files, data collection reports, final summarization files, summarization reports, analysis reports, incorporation reports, and the updated database shall be provided to the Government. The goals for the project are to increase the size of the database by approximately 30 percent (600,000 unit-years) and to diversify the data collection such that every component type in the database contains a minimum of eight failures (Deliverable 3.4-1: PREP Database Update).

Collection. Identify candidate sites with equipment items that match equipment categories in the database. The Government will provide a prioritized list of all desired categories and a list of sites that have provided information in the past, as a starting point for the data collection. Enhance the data collection of equipment categories that are weaker in the database. This includes items that have fewer unit-years of information, are unusually common or important components, have few failures on record, or are expected to have changed significantly since the last data collection. Coordinate with sites to collect maintenance records for inclusion (including sites to increase the diversity of sources of data). The Government anticipates that data collection from approximately 200 sites, including approximately 100 short-duration physical surveys, shall be necessary. Data collection may be performed in a variety of collection methods including phone interviews, e-mail questionnaires, and site visits. All data sources and methods shall be utilized with equal consideration (without bias toward computerized records or those not requiring physical surveys) (Deliverable 3.4-2: Collection Summary).

Summarization. Process all of the collected data to create component records in a format consistent with the existing PREP database. If collected data cannot be processed, identify this in the Collection Summary (Deliverable 3.4-2: Collection Summary).

Analysis. Assess the statistical consistency of the new, summarized data for each component type against existing data in the database. At a minimum, this shall include calculation of basic reliability statistics (reliability, inherent availability, operational availability, unit-years, failures, failure rate, mean-time-between-failures, mean-time-to-repair, mean-time-to-maintain, mean-downtime, mean-time-between-maintenance, and hours of downtime per year) for the new data and the combined data. Reliability calculations shall include a Weibull analysis, Chi-squared analysis, and goodness-of-fit analysis. Develop a recommendation for each component type at each site as to whether the data should be merged with the existing PREP database. Include the results and recommendations for each component at each site in the Collection Summary (Deliverable 3.4-2: Collection Summary).

Incorporation. For each component type at each site that is approved by the Government, merge the summarized data into the database tables. This data merger shall include summarization information related to the equipment failure and maintenance statistics, as well as procedural information, such as dates of completion for each phase and contact information of analysts responsible for each phase (Deliverable 3.4-1: PREP Database Update).

Commercial Software Analysis. In the process of completing the collection, summarization, analysis, and incorporation phases, the contractor shall analyze commercially available software packages for statistical analysis and database management. Currently, the database is in Microsoft Access but it would be best to be able to share summary results and perform various analyses over the internet without sharing the underlining data. The Government is open to migrating the database to another software platform if practical and all logistics and security requirements can be met. The statistical analysis software that will be used to merge the new data with old data should be capable of producing basic reliability statistics, Weibull, Chi-squared, and goodness-of-fit analyses of data in the PREP database. The database management software should accommodate the size of the updated PREP database, provide web-based interface, and have a user-friendly front-end. The software analysis should include features, approximate cost, country of the developer, and whether the software is currently allowable on the Government network (i.e., Certificate of Networthiness or DISA Risk Management Framework (RMF)). The statistical analysis and the database management requirements may be accomplished by the same software. Analyze the options for these software tools and provide recommendations for each in a consolidated report (Deliverable 3.4-3: Software Analysis Tools and Recommendations).

Task 4 Deliverables Table

(Task 5) – C4ISR Facility and Information Technology Update Studies and Assessments (IAW IAC MAC Basic Contract PWS 1.4.2.3.1, 1.4.2.3.4) Conduct special studies, as directed by Government, on facilities requiring immediate attention due to the risk of loss of support to their mission. Studies shall assess critical facility conditions and practices. Studies shall include recommendations for the development and implementation of software tools to monitor and report conditions, predict maintenance and capital investment needs, and plan for future sustainment, restoration, and modernization (SRM). Use these studies in concert with the PREP database to assess the performance of facility mechanical, electrical, and related systems and equipment. The typical C4ISR facility is located in the continental United States (CONUS), is 25,000 square feet, contains 10,000 square feet of raised floor area (server room designed for 200 watts/SF power density), and is supported by diesel generators, uninterruptible power supplies (UPS), power distribution units (PDUs), and has chilled water loops and computer room units (CRUs) sized to meet the mission power and cooling requirement on a N+2 basis (i.e., requisite quantity of needed devices with two additional spares/backups). Reports shall include assessments of critical facility conditions and practices, and recommendations regarding knowledge management and Information Technology (IT) tools to better maintain mission readiness.

Although it is not possible to know which facilities will require what special studies, it is anticipated that 70% of the studies will be for facilities located within the continental United States (CONUS). The contractor should plan appropriately because some special studies under this task require working on and around live, electrically energized equipment and rotating devices. Therefore, the contractor should meet all company and local safety requirements, including those in NFPA 70B, the National Electric Code and all posted safety placards and arc flash stickers. Personal Protective Equipment (PPE), gloves, googles, boots, clothing, should be in proper working order.

Site Mechanical and Electrical Condition Assessment. Condition assessments of critical facilities are needed to establish design capacity, system loads, operating condition, and reliability /availability of the utilities and other systems that service a critical mission. Typically they start with creating or confirming the electrical single-line diagrams to document existing conditions. The same is needed for the mechanical systems –drawings, capacities, and maintenance conditions. Condition assessments shall include establishment of accurate electrical and mechanical single-line drawings (with wire sizes and lengths, capacities, etc.), a discussion of single points of failure, equipment condition, load, and capacity, and recommendations for corrections, as needed, to remove single points of failure and address facility issues. Recommendations shall include rough order of magnitude cost estimates. The contractor shall recommend technology updates for the site that shall include the implementation of current technologies and software solutions designed to increase the accessibility of information to the facility managers and maintenance personnel. If any specialized software is used in the evaluation process, the contractor shall make the software available to the Government. (Deliverable 3.5-1: Site Mechanical and Electrical Condition Assessment).

Computational Fluid Dynamics Study. CFD studies help determine the effectiveness of cooling systems and are used to documents conditions within datacenters, looking for hot spots or other problems (air flow, water temperature, air temperatures, etc.). CFD studies shall accurately identify all equipment type and capacities of air handlers, ducts, cooling water amount and temperature, etc., as well as the datacenter configuration strategy (hot isle - cold isle, overhead plenums, in-row coolers, etc.), include an analysis and identification of potential failure modes of critical fluid systems, and make recommendations, as needed, to remove single points of failure and reduce risk of failure. Six Sigma is the preferred software for the execution of this sub-task (Deliverable 3.5-2: Computational Fluid Dynamics Study).

Fault Current Analysis. These analyses model the existing facility electrical distribution system to determine the fault current throughout the system and are performed to ensure the site is safe and compliant with the National Electric Code (NFPA 70). The analysis starts with accurate electrical single-line diagrams which the contractor will have to verify or create for the site. The analysis shall include a protection coordination survey and arc flash analysis. A power quality analysis may be performed. The Fault Current Analysis shall include all site electrical equipment from the commercial feeder cable(s) down to 480 volt panels and all PDUs. The power quality analysis and fault current analysis shall be based on circuit breaker settings, conductor sizes and lengths, electrical component data, and configurations or modes of operation provided to the contractor by the site. Collect all power data on energized equipment to include the opening of panels, switchgear, and switchboards, as is needed to perform the analysis. Visit the designated site to see the facility, review one-line electrical and mechanical drawings, review operations manuals, and assess the site-supplied information to ensure completeness. Use SKM Power Tools and EasyPower with Arc Flash (the Government may direct the use of additional analysis tools) to conduct fault current analysis as a part of this sub-task. The contractor may be directed to purchase and ship replacement breakers to the site if existing circuit breakers are determined to be non-adjustable, failed or failing, or the site lacks sufficient spares. The contractor shall deliver to the PREP office, in addition to the written report, a working model of the fault current analysis with arc flash for each specific site which can be re-run and verified using the corresponding software. (Deliverable 3.5-3: Fault Current Analysis with Arc Flash).

O&M Practices Assessment. Contractor shall assess site operations to recommend benchmark Operations and Maintenance (O&M) practices tailored to the facility based on research of “best-in-class” practices and subject matter expertise. Assessment shall include comparison of existing practices to the benchmark, and recommendations for improvements. In addition, perform a cost benefit analysis for the implementation of an automated Maintenance Management Systems (MMS) which shall consider, as a minimum, comparison of selections and installation costs of an MMS. Assess top rated MMS software packages including IBM Maximo, Trellis, Remedy, and Archibus as candidates for implementation. Implement Government-approved recommendations. Implementation may include purchase and installation of software packages and technology updates for each site assessed, including the computers and software needed to operate. (Deliverable 3.5-4: Operations and Maintenance Practices Assessment).

Information Technology Analysis. The goal for these IT Analyses is to introduce technology to the site that will improve accuracy, speed processes, expand accessibility, consolidate building and configuration information, and save money. Analysis areas may include planning and installation of industrial controls, SCADA systems, geographic information systems (GIS), smart building technology, power usage monitoring, automated maintenance management systems (MMS), UPS system battery cell watch, and Computer-Aided Facility Management (CAFM) systems. Analysis shall include identification of IT shortfalls and recommendations for new technologies and methodologies explicitly tailored toward the mission of that site, including procurement of specific software, hardware, or Special Test Equipment (STE). These analyses shall also include cost benefit analyses for each recommendation. Implement Government-approved recommendations. Implementation may include purchase and installation of software packages, technology updates and hardware. Implementation may also include the purchase and shipment of replacement UPS batteries strings for existing UPS systems supporting critical missions, found to be at or near failure as a result of this analysis. (Deliverable 3.5-5: IT Improvement and Recommendation Technology Update Report).

Power Usage Effectiveness Analysis. The Federal Government has established criteria for Government datacenters that require them to reach specified levels of efficiency, or power usage effectiveness, as measured using a specific methodology. The contractor shall conduct Power Usage Effectiveness (PUE) Analysis on Government datacenters to calculate and report the PUE. Use a standard approach for collecting data from datacenters and use that data to calculate PUE in order to standardize the benchmarking of datacenter efficiencies. A standard approach is necessary for comparison purposes of a site’s before and after implementation of a “fix” and for comparison between different sites in different organizations. Use the following, three-part methodology, upon Government discretion. The three-part methodology is: 1) categorize data center subsystems as either (a) IT load, (b) physical infrastructure, or (c) not included in the calculation; 2) if a subsystem’s power consumption cannot be directly measured because it is shared with non-data center loads, estimate the power using a standardized methodology for that subsystem type; 3) if a subsystem’s power cannot be directly measured because of technical barriers to measurement, estimate the power using a standardized methodology for that subsystem type. To perform data center efficiency calculations, clearly define which power usage constitutes IT load, and which power is physical infrastructure. Create a comprehensive list of the types of devices found in a datacenter and clearly assign them to “IT load”, “Physical Infrastructure”, or “Not Included” categories, for the purpose of data center efficiency calculation. These assignments shall be reviewed and approved by the Government. The contractor may be asked to perform a PUE Analysis and comment on the 65% or 90% design documents for a new facility. (Deliverable 3.6-7: PUE Report).

Task 5 Deliverables Table

(STI rollup with trend analysis due annually to the DoD IAC PMO unless otherwise indicated) Description

(Task 6) – Critical Facility Construction Criteria Development (IAW IAC MAC Basic Contract PWS 1.4.2.3.1, 1.4.2.3.4) Develop or update construction criteria for use in critical facilities, for Government approval, that provides guidance for facility support; system technical guidance; facility management; and Tools, Techniques and Procedures (TTP), including the establishment of policy for the O&M of critical facilities supporting the C4ISR mission. The common objective driving the development of critical facility criteria shall be to maximize the availability of mission systems, reliability of energy management systems, facility sustainment, and facility management in order to reduce the risk to the War Fighter’s mission resulting from facility failures.

USACE PREP is responsible for keeping critical facility construction criteria current, purposeful, and practical with established policy and guidance for critical mission sites. This criteria was created to provide a knowledge base of information consolidated into official publications accessible throughout the C4ISR community. Each criteria is written to address the specific needs of the C4ISR mission within the Department of Defense but also applies to other similar facilities found throughout the Federal Government. It is important that criteria development provide essential guidance in the form of TTPs that keep pace with changing technologies, new software, and any new threats or challenges, including cyber threat. The goal is to update Army criteria and convert them from Army Technical Manuals (TM) format to Unified Facility Criteria (UFC) format, thereby making them applicable to all the Military Services and Agencies.

Analysis of Existing Criteria. Analyze all existing pertinent facility criteria to develop recommendations for categories requiring the creation of new criteria and to identify existing criteria requiring updates. Critical Facility Construction Criteria development categories shall include the following: facility automation; industrial controls and the impact on vulnerability; IT structure and the critical role of datacenter infrastructure reliability; communication system design and sustainability considerations; analysis and evaluation of facility design and the application of countermeasures techniques; technology specific information addressing the fast-changing datacenter world; human factors and how they affect system sustainability; software tools to establish analysis; and modeling and assessment techniques for the facility manager (Deliverable 3.6-1: Critical Facility Criteria Recommendations).

New Criteria Development. Draft new criteria in the format of Unified Facility Criteria for Government directed categories. The new criteria shall reflect the cutting edge of knowledge and practices in the selected category. Conduct research, SME interviews, and practitioner interviews to develop an understanding of what constitutes cutting edge, and present those findings to the Government, before completing a detailed outline for the criteria. Present a development schedule for Government approval. This schedule shall include monthly and ‘milestone’ progress reviews to present critical items such as: table of contents, detailed outline, rough draft, and final draft for Government approval. The final draft of the new criteria shall be submitted to the Government, in accordance with Whole Building Design Guide formatting guidelines (Deliverable 3.6-2: Criteria Research Report; Deliverable 3.6-3: Criteria Development Schedule; Deliverable 3.6-4: Criteria Development Milestone Items; Deliverable 3.6-5: Draft New Unified Facility Criteria).

Existing Criteria Update. Update existing facility criteria as directed by Government. The updates shall reflect the cutting edge of knowledge and practices in the selected category. Conduct research, SME interviews, and practitioner interviews to develop an understanding of what constitutes cutting edge, and present those findings to the Government, before completing a detailed outline for the updated criteria. Present a development schedule for Government approval. This schedule shall include monthly and ‘milestone’ progress reviews to present critical items such as: table of contents, detailed outline, rough draft, and final draft for Government approval. The final draft of the updated criteria shall be submitted to the Government, in accordance with Army Publishing Directorate formatting guidelines (Deliverable 3.6-2: Criteria Research Report; Deliverable 3.6-3: Criteria Development Schedule; Deliverable 3.6-4: Criteria Development Milestone Items; Deliverable 3.6-6: Draft Updated Criteria).

3.6.4 Draft Design Intent Documents for a Specific Project. The object is to create a set of instructions or design features for a specific renovation of an existing facility or the construction of a new facility which is based on mission requirements, existing UFCs, draft new facility criteria, and facility owner specific requirements.