20220720 UMCS PWS.pdf
PDF 161 KB Posted
- Attached to
- Integrating Utility Management and Control System Software with existing building controllers
- Solicitation number
- FA6633-22-Q-A004
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 20220801 Clause Selection.pdf | ||
| 20220801 Notice of Intent.pdf | ||
| JACE and AX Versions.xlsx | XLSX spreadsheet | |
| UFC 3-470-01 UMCS Front End And Integration (12JAN18).pdf | ||
| 20220805 SSJ_signed.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT
Integrate Utility Management & Control System Software with Existing Building Controllers.
Minneapolis Air Reserve Station Project Number: QJKL 22-0012
20 July 2022
1.0 INTRODUCTION
Contractor shall provide all professional services necessary to fully meet all requirements of this Statement of Work, and all Contract Documents related to and/or titled: “Integrate Utility Management & Control System Software with Existing Building Controllers” at the Minneapolis Air Reserve Station, Minneapolis Minnesota.
2.0 SCOPE OF WORK
The performed tasks shall be based on the project description, other data furnished in this Statement of Work (SOW), and information covered during the project meeting. THE SCOPE
OF THIS PROJECT INTEGRATE UTILITY MANAGEMENT & CONTROL SYSTEM
SOFTWARE WITH EXISTING BUILDING CONTROLLERS. This shall include, but is not limited to:
a. See Existing Building Controller Software Version and Priority
Listing (attachment 1).
b. UFC 3-470-01 (12JAN18) Unified Facilities Criteria (UFC) Utility
Monitoring and Control system Front End and Integration (attachment 2).
2.1 Applicable Documents: If there is a conflict between codes, regulations and specifications, the most stringent requirements shall apply at all times. Documents listed by and/or provided by the Government are for reference only and do not relieve the Contractor from adherence with applicable codes not specifically addressed. Where conflicts between the drawings and specifications occur, specifications shall govern in accordance with FAR 52.236-21.
2.2 Background: The existing Base UMCS Tridium Niagara AX front-end is no longer supported by Tridium. The Base has decided to migrate the front-end to J2 Innovations FIN Stack.
2.3 General Expectations of Work: As part of the proposed effort, the Contractor shall implement means and methods that will limit disturbance to the base activities to the greatest extent practicable throughout the project performance. The government provided documents and existing field conditions shall be reviewed by the contractor to identify any potential discrepancies and develop necessary requests for information (RFI) prior to construction mobilization. The repair efforts shall be in strict accordance with the Scope of Work. Substitutions and/or deviations will not be accepted unless approved by the Contracting Officer (CO) in writing. Ancillary efforts required to access and complete the work not specifically listed in the task description shall be anticipated and accounted for in the contractor’s proposal documents. The task descriptions below are summaries of work to be completed to integrate the existing building controllers into the UMCS front end.
The Period of Performance shall be no longer than 90 calendar days from issuing the notice to proceed (NTP). Contractor shall provide a construction schedule with proposal breaking out all key work features along with a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.
2.3.1 WORK TASKS
1. The buildings that are targeted for migration and integration are listed by priority in
Attachment 1. The list includes the version of Niagara the building controller (JACE) is operating and the number of points in each building that need to be integrated into FIN Stack.
2. The integration will include, but not be limited to the following: alarms, notification messages, trend data, adjustable set points, equipment status, and sensor output.
3. The Contractor may discover equipment that has failed, may fail, or is inadequate for integration. At the CO’s request, a request for proposal (RFP) to replace and configuration the new equipment will be provided by the Contractor to the CO. If accepted and approved, the CO will direct the Contractor to complete the tasks identified on the RFP.
4. Work shall be conducted in accordance with Attachment 2: UFC 3-470-01.
2.3.2 Permits – NOT APPLICABLE
2.3.3 Integration: Upon approval by the CO; the Contractor may commence on-site activities. The Contractor shall conform to all specific references and other applicable requirements during performance of the work as described in the Scope of Work:
2.3.4 Government Furnished Equipment:
1. Utilize Base provided workstation and network connections
3.0 GENERAL REQUIREMENTS
Applicable provisions of the Contract Clauses in the contract will govern work under each section of the specifications
3.1 Qualifications: Contractor shall provide documented experience with the following work items:
1. 10 years’ experience with programing building automation systems.
a. BACNET.
b. LONWORKS.
c. Niagara AX Workbench and Supervisor.
2. 5 years’ experience with integrating building controllers with UMCS front-end.
3. 3 years’ experience with J2 Innovations FIN Stack.
3.2 Project Meeting: Project meeting will be accomplished with the Contractor, Contracting
Officer, Civil Engineering Squadron (CES), and user. The meeting objective is to review project details, start date, security procedures for site, dumpster locations, and any applicable requirements during the project.
3.3 Notification Requirements: The Contractor shall notify the Government a minimum of 21 days business days in advance of start of work. The Contractor is required to notify the CO and Government Project Manager of critical issues that may affect the contract performance and/or human health and the environment. For critical issues pertaining to human health and the environment, the Contractor shall immediately notify the CO and stop work.
Work shall only resume at the direction of the CO following resolution of the issue.
3.4 Federal Holidays: The Minneapolis Air Reserve Station observes the following Federal
Legal Holidays;
New Year’s Day 1 Jan Martin Luther King Birthday Third Monday in Jan Presidents Day Third Monday in Feb Memorial Day Last Monday in May Juneteenth 19 June Independence Day 4 July Labor Day First Monday in Sep Columbus Day Second Monday in Oct Veterans Day Second Monday in Nov Thanksgiving Day Fourth Thursday in Nov Christmas Day 25 Dec
3.5 Working Hours: The normal working hours for the base are from 7:00 AM to 3:30 PM, Monday thru Friday excluding Federal Holidays. All work shall be performed during normal duty hours. All other hours to include weekend and holidays shall be requested through the CO for approval. This request shall be submitted no less than five (5) business days prior to the time requested.
3.6 Availability and Use of Utility Services: The Government will make all reasonably required utilities available to the Contractor from existing outlets and supplies, as specified in the contract.
4.0 GENERAL SAFETY REQUIREMENTS
4.1 Workplace: Provide a safe and healthful workplace for employees and the general public while performing the contract work
4.2 Personal Protective Equipment: Supply each employee with personal protective equipment. This equipment includes but is not limited to protection for the eyes, face, head, ears and extremities. Use the proper protective equipment for the work performed.
4.3 Roads: Obey the posted base speed limits. Wear Seat belts on base in accordance with
AFI 91-207.
4.4 Accidents: Report Contractor accidents involving injury to Air Force personnel or damage to Government property to the Base Law Enforcement Desk and the CO.
4.5 Safety Regulations: Familiarize yourself and comply with the general safety requirements in accordance with DOL regulations, OSHA 29 CFR Part 1926, as well as applicable Air Force Office of Safety and Health (AFOSH) standards and Air Force Instructions (AFI).
5.0 GENERATED REFUSE – NOT APPLICABLE
6.0 UTILITY OUTAGES – NOT APPLICABLE
7.0 EXISTING UTILITIES – NOT APPLICABLE
8.0 DELIVERABLES / SUBMITTALS – NOT APPLICABLE
9.0 CONTRACTOR’S QUALITY CONTROL – NOT APPLICABLE
10.0 CONTRACTOR STORAGE /STAGING AREA – NOT APPLICABLE
11.0 CONTRACT ADMINISTRATION
11.1 Contracting Officer Authority: CO, the term used herein, does not include any representative not acting within the scope of his/her authority. Notwithstanding any of the provisions of this contract, the CO shall be the only individual authorized to in any way amend or modify the terms of this contract.
LIST OF ATTACHMENTS:
Attachment 1: Existing Building Controller Software Version and Priority Listing Attachment 2: UFC 3-470-01 (12JAN18) Unified Facilities Criteria (UFC) Utility Monitoring and Control system Front End and Integration
| PERFORMANCE WORK STATEMENT |
| 1.0 INTRODUCTION |
| 2.0 SCOPE OF WORK |
| 2.3.1 WORK TASKS |
| 2.3.4 Government Furnished Equipment: |
| 3.0 GENERAL REQUIREMENTS |
| 4.0 GENERAL SAFETY REQUIREMENTS |
| 11.0 CONTRACT ADMINISTRATION |
File details come from the government source that posted it. Updated .