B08_Attachment_A_-_EBCS_Performance_Work_Statement_06_12_2025.pdf

PERFORMANCE WORK STATEMENT

U.S. Army Reserve (USAR), Army Reserve Installation Management Directorate (ARIMD)

Enterprise Building Control System (EBCS)

08 July 2024

BACKGROUND

The Army Reserve Installation Management Directorate (ARIMD) considers an Enterprise Building Control System (EBCS) an important tool to save energy and provide improved remote monitoring and control of Army Reserve facilities. Army Reserve (AR) facilities are ideal candidates for an EBCS because they are dispersed across a wide geographic area, often lack on-site personnel capable of managing control systems, have highly variable occupancy, and often have long periods of low/partial occupancy.

The EBCS provides a platform to better implement scheduling (e.g., unoccupied period temperature set-back), monitoring of building equipment, and remote diagnostics and troubleshooting capabilities.

ARIMD has adopted a standardized architecture for EBCS that provides a uniform integration standard for communication at the “Enterprise” level (i.e., connection of building level controls to an Enterprise Server via the Army Reserve Network (ARNet)). Developing tools at the “enterprise” level ensures uniformity of equipment and interfaces, while providing the ability to develop region- or site-specific tools. The EBCS process has led to Army Reserve-wide controls specifications.

The EBCS is standardized on an available model of Tridium Niagara Framework that provides seamless integration and common hardware at the “enterprise” level. The Tridium Niagara Framework, running on a Java Application Control Engine (JACE), has the appropriate credentials to operate on the ARNet which include a Certificate of Noteworthiness (CON) and Authority to Operate (ATO). This standardized architecture will enable more efficient use of funding for equipment purchases, upgrades, and optimized implementation across Army Reserve regions. ARIMD has engaged Pacific Northwest National Laboratory (PNNL) as a long-term partner and technical advisor for EBCS.

DESIRED END STATE

All Reserve building-level assets (e.g., local building controls, heating, and cooling systems, etc.) are EBCS-connected, and individual buildings or systems can be viewed and controlled remotely. EBCS is used for more than basic scheduling, providing intelligent monitoring of systems and alerting operators of problems. Building operation is optimized based on actual needs and systems are retuned on an on-going basis.

PERIOD OF PERFORMANCE

Base Period: 06/01/2025 – 05/30/2026

Option Period 1: 06/01/2026 – 05/30/2027

Option Period 2: 06/01/2027 – 05/30/2028

Option Period 3: 06/01/2028 – 05/30/2029

Option Period 4: 06/01/2029 – 05/30/2030

ROLES AND RESPONSIBILITIES

While most of the project coordination will be between the Field Contractor and ARIMD through the Department of Interior (DOI), other key stakeholders are vested in the EBCS program and will have input into how the EBCS program is executed.

Specific roles and responsibilities for this project are as follows:

A. ARIMD, as the funding organization and official government affiliate, will have overall oversight and decision-making authority on this project. ARIMD will assign a primary point-of-contact who will track and manage this project. ARMID owns and maintains the EBCS server(s). ARIMD will collaborate with others (e.g., Army Reserve G6, EBCS Working Group, PNNL) for technical input throughout the project.

B. DOI will perform general contract oversight and contract with the Field Contractor who will complete Site Readiness Assessments (SRA), installation of integration controllers (JACEs), other associated equipment, graphics development, building integration into EBCS, and ensure all quality control checks have been accomplished. DOI will manage and track progress of DOI’s sub-contractors. DOI will select qualified subcontractor(s) only with ARIMD’s approval. The subcontractors under DOI may hire local crafts and trades people as required. All DOI sub-contractors and/or partnerships must be identified and approved by DOI and ARIMD.

C. PNNL shall act as a general consultant to ARIMD and the Working Group by providing technical expertise and quality control as required. PNNL has no direct authority under this SOW but serves at the behest of ARIMD.

D. The EBCS Working Group (WG) consists of designated technical representatives and primary POCs from ARIMD, G6, PNNL, and each Readiness Division (RD) (63rd, 81st, 88th, and 99th), the 9th

Mission Support Command (MSC), and certain AR-funded installations. The Working Group will provide feedback to ARIMD and act as a project steering committee.

E. Regional POCs may serve on the Working Group and may also be regional facilities personnel such as Regional Facilities Operations Specialists (RFOS) or Area Facilities Operations Specialists (AFOS). Regional POCS are those with whom the Field Contractor will coordinate site visits and provide coordination support for scheduling visits and executing this task. Also, the WG POCs shall provide building design packages of building design drawings and other applicable facilities documentation for their respective regions. Regional POCs will also be involved in QA/QC to validate successful integration.

F. Army Reserve G6 is responsible for all computers, server, and network resources. G6 serves to advise the Working Group on EBCS server issues, and general oversight to facilitate the server meets information architecture best practices and all Army policies/guidelines.

TASK REQUIREMENTS

The following provides a description of major project tasks. Global tasks are those required for the work, but not associated with a particular building; these include the PM function, coordination, reporting, etc.

Building integration tasks make a set that are necessary to integrate a building to the EBCS with the set repeated for every building.

1. Global: Project Management and Communication

A project manager from both DOI and Field Contractor primary POCs for ARIMD and associated affiliates throughout the project. The project managers shall participate in project management and execution activities including:

• Attend project meetings in person or via teleconference to include design charrettes, kick-off meetings, design reviews, scheduling meetings, budget reviews, and bi-weekly status meetings with all project stakeholders. A schedule of in-person and/or telephonic meetings will be determined at a later date.

• The project managers or representatives shall communicate to WG members, DOI, ARIMD, and Regional POCs at least two weeks in advance of travel to confirm the trip and coordinate all work activities to include working schedules and buildings where work will be performed. Effective communication is imperative and must be adhered to under all circumstances. The Field Contractor or representative shall NOT access or leave a site/installation/building without first coordinating with site/installation personnel; this includes daily reporting and departures. Before each trip provide at a minimum:

o Name of person(s) coming to the site and contact info o Supervisor and company –for person(s) coming to the site and contact info o General SOW to be accomplished at the site o Estimated duration of work o Access/personnel (with keys/passwords) and equip/tools (e.g. ladders, lighting) needed at the site o Anything “required” to perform the work (e.g. power/IT-BAS/Network outages)

• All background information and affiliations of personnel performing work under this SOW shall be provided upon request.

a. DOI and Field Contractor(s) shall ensure and facilitate the acquisition of any required credentials (e.g., Common Access Cards (CACs), Licenses, etc.) for performing this work scope

2. Global: Reporting

• Weekly Status Updates - Provide a weekly, written status update on schedule, progress, issues, etc. to ARIMD. For ease of viewing, all schedules should be submitted in a project management format such as Microsoft Project or other suitable PM software package.

NOTE: ARIMD will review Contractor’s current reporting methods and templates and will issue reporting templates as needed.

• Monthly Teleconference Updates – Primary POCS from the Working Group have been identified and will participate with ARIMD, DOI, Field Contractor, and other parties monthly for general coordination. Contractors shall prepare and disperse necessary meeting materials in advance.

• SRA Intermediate Report – Contractor will deliver a cursory SRA Report within one week of on-site or remote SRAs that will specify whether a building is integration ready, the reasons why a building is not integration ready if applicable, the general HVAC configuration, control points listing, and inspection log (as assessed from point-to-point test, and field inspections/checks). The inspection log should contain any observed malfunctioning equipment as observed through BCS or during facility checks.

• SRA Final Report and Integration Proposal – A final SRA report will contain all information previously submitted in the SRA Intermediate Report plus a more detailed HVAC configuration, points list following Attachment M, and estimates for field work, integration, and graphics package. The control points should have been verified during the SRA and any discrepancies should be noted in the report. A detailed log of malfunctioning equipment shall be included in the Final SRA Report and Proposal. Also, if requested in the SRA Work Package, Field Contractor shall include estimates to repair malfunctioning equipment observed during the SRA.

Each building should have its own report, cost estimate, materials listing, inspection log, repair estimates, and labor breakouts. Cost categories and line items in the estimates should be presented consistently across all buildings. If a cost category is not applicable for a building, the Field Contractor may simply note as such with “N/A.” As a rule, the Field Contractor shall reference the associated Work Package for any additional details to be collected during the SRA.

• Final Status Report - Deliver a final status report that includes the following information:

o SRA results for each building. Refer to the associated Work Package for specific reporting requirements.

o The Work completed, e.g. final points listing, user interface designs, tests completed, and challenges.

o Transmittal of building plans, equipment schedules, and all other drawings.

o Budget status such as any expected and unforeseen additional expenses for approvals, or savings realized.

3. Global: Project Tracking and Work Packages

The work will be released from ARIMD in a series of sequential Work Packages, which will contain a Performance Work Statement (PWS), Period of Performance, and not-to-exceed cost for physical work, integration labor, and graphics related work. Depending on the complexity of a specific building’s equipment and BCS, the work may be split over several task orders, e.g. Site Readiness Assessment (SRA), Physical Work, and Integration. More than one building may be assigned to a single Work Package. The intent behind the Work Package procedure is to ensure ARIMD can accurately track costs, monitor performance, and maintain schedules.

The first Work Package in a building’s EBCS integration sequence will authorize DOI to release the Field Contractor to complete Site Readiness Assessments (SRA) for the facilities specified in the Work Package. The SRA will be conducted according to the plan provided in this SOW and

Work Package. Note that the Work Package takes precedence over this SOW, thus Contractor and Field Contractor will follow the Work Package protocol if contradictions between this SOW and the Work Package exists. SRA findings shall be captured according to Attachment L to this SOW. An SRA Report will be delivered to ARIMD in addition to a proposal for each building that specifies budget, schedule, and scope to integrate the buildings specified in the Work Package.

Subsequent Work Package(s) will authorize DOI to release Field Contractor to complete any required physical work, graphics design, and integration into the EBCS.

4. Site Readiness Assessments

The contractor(s) will perform an SRA according to the scope in the relevant Work Package, this SOW, and pertinent Attachments to this SOW. Generally, the goals of the SRA are:

• Prepare for site integration by performing required data collection.

• Evaluate the current functionality of the building control system.

• Collect a record of all control points including a scan of all field devices.

• Assess and rectify point status to verify open points in the BCS.

• Assess the existing Network Area Controller (NAC) status (open or closed).

• Conduct functional check of controlled equipment from NAC terminal by performing point-by-point and functionality test.

• Check communication between existing NAC and field controllers.

• Log all malfunctioning equipment and broken control points along with fix costs in SRA reports.

• Assess building’s integration readiness and provide reasons if not integration ready.

• Ascertain which utility commodities (if any) are metered under the Army’s Metering

Program and the type of JACE which connects metering equipment to the ARNet.

• Record the location of the existing NAC and approximate length of conduit runs on floor plans.

• Record the distance to the nearest ARNet LAN closet and/or network drop.

The functional tests and communication checks should be performed from the existing NAC/terminal in conjunctions with field checks. Before the Field Contractor leaves a site, all pertinent data and information shall be collected so that an accurate assessment may be made of a building’s feasibility for integration. Malfunctioning equipment identified by the functional check should be logged and provided in the SRA Intermediate Report and SRA Final Report;

repair estimates shall be included in the final SRA report, and the costs shall be itemized under an O&M category. It is important that all O&M costs be itemized and separated from EBCS related costs. The contractor shall utilize the EBCS Design Guide Attachment 4: Site Readiness Assessment Workbook Template in the completion of all SRA reports.

Contractor should check for remote access through the ARNet and perform the SRA remotely if possible and if approved by the respective RD point-of-contact. If the existing NAC proves to be closed during remote assessment, Contractor shall notify ARIMD and associated Working Group POCs for instructions on how to proceed. Contractor should indicate if SRAs are conducted remotely in the associated SRA reports.

Field Contractor(s) may choose to obtain tools/software platforms (YABE, Cimetrics) that are utilized to verify if a system is open. Additionally, Field Contractor(s) will determine “closed” points. If necessary, ARIMD will assist the Field Contractor. Field Contractor will report closed status to ARIMD and Working Group POCs prior to travel if remote access is possible, or immediately after the on-site SRA according to the reporting schedule.

5. System Design and Development The Integration Contractor shall provide system design and strategic planning services as requested by ARIMD and may include tasks outside the physical boundaries of a specific building or installation location to include virtual and enterprise services.

All Information Communication Technology (ICT) systems used for energy and utilities management, including all hardware, software, and web and non-web electronic content, must conform to the applicable requirements in the current ICT Standards and Guidelines (36 C.F.R. § 1194). See Attachment F for all applicable Section 508 standards.

6. Procure and Install Hardware and Software The Integration Contractor shall procure all necessary hardware and software needed to integrate all buildings and systems as identified by ARIMD. Applicable hardware and software shall include but not be limited to:

• A VYKON JACE-8000 (or JACE-9000 pending ARIMD approval)

• Data gateways, protocol translators, and network switches

• Niagara framework software (Workbench)

• Niagara Modules Reflow modules

• Device and protocol drivers

7. System Integration

a. New Buildings/Systems: The integration contractor shall integrate all building control systems and equipment as identified by ARIMD. Integration shall be in accordance with the EBCS Design Guide and shall include development of building-level graphics, alarms, historical trends, analytics, point naming/renaming, data validation, as well as integration with the EBCS servers.

b. Existing Systems Maintenance: The integration contractor shall update previously integrated building control systems and equipment as identified by ARIMD. The updates include point name changes and additions, graphics changes, addition or modification of histories, alarms, analytics, and data tagging at both the building (JACE) and server levels.

8. Functional Improvements

a. Cybersecurity: In tandem with Task 6, the Integration Contractor shall perform software and firmware updates as identified by ARIMD in order to maintain cybersecurity of the building control system. Cybersecurity tasks may also include update or replacement of physical equipment as required to meet current cybersecurity standards.

b. User Interface / UX: In tandem with Task 7B, the Integration Contractor shall perform user interface modifications at both the building control system level as well as the enterprise level, working to migrate existing graphical elements into the Reflow interface and maintain the Reflow interface as system changes occur.

c. Controller replacements and networking: In tandem with Tasks 7A and 7B, the Integration Contractor shall replace physical building control system devices including controllers, sensors, actuators, relays, power supplies, cables and networking components in order to create a fully functional control system that is integration ready.

d. Energy control devices: the contractor shall replace or install physical energy control devices including lighting controls, PV/renewable energy control and monitoring devices, or utility metering devices as directed by ARIMD for the creation or maintenance of intelligent building systems.

9. QA/QC and Project Closeout

a. The contractor shall perform quality assurance/quality control measures prior to closeout of each work package. The QAQC process shall be in accordance with the processes and procedures in the EBCS Design Guide, QAQC form, and QAQC Tool. A report of all findings shall be provided to the USG upon completion of work.

b. The subcontractor shall provide technical support and maintenance (i.e., troubleshooting and resolution of issues/problems with hardware and software) for a period of one year after acceptance of the EBCS by regions/ARMID.

The following task 9 deliverable shall be completed quarterly during the sustainment period: Update the status report indicating the technical problem and resolution thereof and any associated scope, cost and schedule changes per building.

10. Training

Closeout Training: Upon completion of integration for a single site or building, provide a one (1) hour training course, appropriately tailored to the expected audience, in person or virtually for each region and ARMID, for up to 10 personnel per session, and include at a minimum: The structure of the EBCS network, how to drill down to specific equipment and change set-points, as well as features available, such as trends and graphing, and alarming.

End-user Training: Provide up to 12 one (1) hour virtual training sessions.

Refresher Training: The subcontractor shall also provide up to 40 hours of refresher training session via webinar and complete all the training before the sustainment period begins.

Specialty Training: Advanced user training and product certifications as requested by ARIMD.

Assumptions

• All sub-contractors requiring access to the ARNet and/or EBCS Supervisor Servers subcontractor will apply for a Common Access Card (CAC) for key staff within 5 days of execution of contract.

Field personnel performing repairs, installations, or surveys of Army Reserve facilities who do not require network access in the performance of their duties are exempt from possession of a

CAC.

• Contractor employees shall obtain a CAC in accordance with DAF Federal Acquisition Regulation (FAR) Supplement (DAFFARS) 5252.242-9001, Common Access Cards (CAC) for Contractor Personnel.

• The subcontractor shall provide all required computers. Computers shall be in accordance with USAR specifications and shall be imaged by USAR G6.

• The subcontractor will follow all applicable national and local codes.

• PNNL will supply the subcontractor with a list of buildings.

• Any hardware and/or equipment discovered in the buildings to be malfunctioning shall be reported to the regional POC and ARIMD/PNNL.

• An average of 5% of the recommended points provided with the “integration-ready” building may not exist in the NAC and should be entered manually as part of the integration process.

• All equipment that is visible or discoverable is to be integrated to the EBCS integration JACE.

That is, all points and equipment that may have been omitted during the original NAC installation and programming stage should be added and integrated into EBCS. All data and equipment are to be considered for integration. The Regions will provide input as to what is not to be integrated in the EBCS JACE. This step will be reconciled during/after the SRA.

• All required Army G6 Guidelines will be detailed and provided to DOI and subcontractors.

• Access to the EBCS server will be provided to the Contractor; unless otherwise necessary, Contractor will access the EBCS server remotely.

• As the EBCS, associated network controllers, and equipment are the property of the Readiness

Divisions, they should be the authority to authorize building setpoints, schedules, and alarms.

Contractor shall consult ARIMD before changing these parameters.

• All property, hardware, software, usernames, passwords, and related programming created including graphics and user interface designs are to be transferred to ARIMD/PNNL and will become the property of the Army Reserve Installation Management Directorate (ARIMD).