Attachment_J-C1-Sample_Task_Order_0001_PWS.pdf

Attachment J-C1: Sample Task Order 0001 Performance Work Statement (PWS)

HQ0034-15-R-0136

Revised Dated: 21 April 2016

Pages: 12

Performance Work Statement

Commissioning and Code Enforcement Services for the National Capital Region

Sample Task Order Number 0001

1.0 General

1.1 Background. The Department of Defense (DOD), Washington Headquarters Service (WHS) is implementing construction and renovation projects at DOD facilities in the National Capital Region (NCR). These projects require design, construction, and warranty phase commissioning (Cx) and code enforcement to verify that mechanical, electrical, and plumbing systems meet applicable codes and standards and the owner’s operational intent. In addition, WHS operated facilities require on-going, retro or re-Cx services to ensure operating system continue to operate efficiently. WHS’s goal is to ensure that completed facilities operate efficiently, are maintainable, and provide a quality work environment for DOD personnel.

1.2 Objective. The objective of this requirement is to provide design, construction, and post-occupancy Cx and code enforcement services for WHS facilities in the NCR.

2.0 Scope of Work. This task order provides Cx and code enforcement services supporting Standards and

Compliance Division (SCD) for construction projects and facilities operations in the NCR with particular emphasis on the Pentagon Reservation. The contractor shall provide all labor, equipment, materials, and supervision necessary to administer and conduct Cx services for mechanical, electrical, and plumbing systems (MEP), and code enforcement services for mechanical, plumbing, electrical, structural, civil, architectural, and specialty systems.

Cx services shall include Cx project management and administration, quality control, review of design and construction drawings, systems operations and maintenance manuals (SOMMs), and submittals, verification of as-built and redline drawings, developing pre-functional checklists (PFC) and witnessing some PFCs, developing and executing functional performances tests (FPT), developing final Cx reports and warranty phase Cx review report, equipment upload to MAXIMO, design and construction document management, and conducting Cx training. Code enforcement services include conducting plan reviews and documenting code compliance issues, conducting and documenting construction inspections, witnessing and documentation of code required testing, and supporting the development of the WHS Building Code. The contractor shall use Quicx and/or other similar software to review drawings and submittals, document design review comments and inspections, and document the project to completion. Design reviews shall evaluate whether the designer of record has met owner’s intent and applicable codes and standards. The contractor shall coordinate fire protection, fire alarm and life safety Cx with Other

Government Contractors (OGCs) and incorporate fire protection Cx results provided by OGC in monthly report.

The contractor shall assist FSD Federal Facilities Division (FFD) maintaining and updating the FFD design and construction document management database system using QuiCx software.

The contractor shall keep apprised of and adhere with required Government security and safety directives and initiatives, e.g., security clearances for appropriate personnel, document handling, construction site safety training, anti-terrorism training, other miscellaneous required Pentagon Force Protection training.

2.1 Task Order Quality Control Requirements. The contractor shall provide oversight of each subtask and perform periodic quality control review of project specific reports and other documents developed by the Cx specialist (CS) and code enforcement teams. The CS project manager (PM) shall maintain regular contact with the

Contracting Officer, Contracting Officer’s Representative (COR) and other client points of contact. It is anticipated that the CS PM will be full time supporting the SCD Cx and code enforcement programs. Specific tasks are:

Prepare monthly Cx status reports identifying activities, benefits, and lessons learned

Provide personnel planning and resource management.

Develop input for and attend monthly Cx briefing

Provide quality control review of CS and code enforcement deliverables to ensure adherence to Pentagon and contractor standards for Cx and code enforcement.

Provide functional performance test (FPT) quantity projections and monthly plan review and inspection quantity projections at monthly contract status meeting.

Develop and implement Cx Process training for FSD and contractor personnel

Provide recommendations for implementation of Cx industry best practices, as may be applicable, to

Pentagon Reservation projects

Provide recommendations for implementation of potential WHS building Code changes.

Coordinate all activities associated with this task order

Recommend Cx level of effort for each project to FSD.

2.2 Design and Construction Projects Cx. The contractor shall provide all labor, equipment, materials, and supervision necessary to conduct design, construction, and warranty phase Cx services for FSD construction projects. Provide the following services:

Lead SCD’s Cx efforts for each project. Maintain Cx action list, prepare for and lead Cx meetings, prepare Cx meeting minutes for the Cx Authority (CA). Facilitate contractor development of systems operations and maintenance manuals (SOMMs). Develop pre-functional checklists (PCs) and FPTs including integrated systems testing and incorporate FPT lessons learned. Review design drawings; analysis, e.g., hydraulic calculations, mechanical loads, voltage drop; specifications; equipment submittals (including specification compliance);

equipment shop drawings; project specific reports; and other documents, e.g., OGC developed project specific designs, PCs, and SOMMs. Perform as-built field observations for verification that red-line drawings capture field changes and that as-built updates capture red-line changes (spot checks). Coordinate FPT execution and CS labor requirements. Witness testing, adjusting, and balancing (TAB) verification FPTs and review TAB reports.

From a quality assurance level of effort, monitor and review building systems construction activities for significant deviations from design documents, code, or industry installation standards, e.g., operability, maintainability, fire barriers, handrails, step/riser/headroom, and door ratings. Review contractor training plans and training material and facilitate training activities. Update the Cx Plan. Provide Cx input for monthly status briefing. Provide qualified technicians and engineers to direct and document FPTs performed by contractors. Track completion of Cx Plan deliverables, including, but not limited to, PCs, FPTs, SOMMs updates, and training plans. Design reviews

(estimated at a total of 100 drawing sheets) shall evaluate whether the designer has met owner’s intent during TFO design based on contract serviceability, maintainability, and operability requirements, that the designer has met owner’s intent by adhering to applicable building, fire and life safety codes, and assess whether MEP utility systems and components are adequately sized for owner/tenant identified requirements. Facilitate the adherence by all CS project labor with required Pentagon Reservation safety and security directives and initiatives.

Based on the PSOC concept design drawings and construction schedule, and the proposed testing rates identified in the draft Cx Plan, it is estimated that FPTs will be developed and executed as identified in paragraph 2.9

2.3 Upgrades at Other DOD Sites in the NCR. The contractor shall provide all labor, equipment, materials, and supervision necessary to administer and conduct design and construction phases Cx services for the upgrade projects at other DOD sites in the NCR, e.g., Fuel Oil Storage Facility, Uninterruptible Power Supply, Power Distribution

Project, Chillers and Computer Room HVAC, Fire Alarm/Fire Pump Upgrade and Power Plant Replacement,. No additional travel costs will be provided for Cx services provided at other DOD sites in the NCR, however, FPT estimates in paragraph 2.9 include a 20% increase in FPT execution quantities for site access and travel allowance.

Provide the following services:

Lead SCD’s Cx efforts for the upgrade projects at other DOD sites in the NCR. Maintain Cx action list, prepare for and lead Cx meetings, and prepare Cx meeting minutes for CA. Develop Power Plant Cx Criteria. Review design drawings; analysis, e.g., hydraulic calculations, mechanical loads, voltage drop; specifications; equipment submittals; equipment shop drawings; project specific reports; and other documents, e.g., OGC developed project specific designs. Review D-B developed SOMMs and equipment and systems training. Finalize Cx Plans prepared under separate contract. Provide Cx input for monthly status briefings. Perform site observations, inspections, and as-built and redline verification. Develop PCs and FPTs and perform FPTs per paragraph 2.9.

2.4 Miscellaneous Construction Projects Closeout. The contractor shall provide all labor, equipment, materials, and supervision necessary to conduct Construction Phase Cx services for the Pentagon miscellaneous construction projects closeout. Provide the following services:

Lead SCD’s Cx project closeout efforts for miscellaneous construction projects. Maintain Cx action lists identifying

Cx items remaining to be closed out and provide input to the Cx IPT leader (one for each project), prepare for and lead Cx meetings, prepare Cx meeting minutes for the CA. Coordinate remaining FPT execution and CS labor requirements. Provide Cx input for monthly status briefings. Provide qualified technicians and engineers to direct and document remaining FPTs performed by contractors. Track completion of Cx Plan deliverables, including, but not limited to, SOMMs. Conduct warranty phase Cx review. Provide final Cx reports for large and small projects.

2.5 Construction Management Division (CMD) and Alterations Work Group (AWG) Projects. Provide all labor, equipment, materials, and supervision necessary to administer and conduct design and construction phase Cx services for CMD Projects. Provide the following services:

Lead SCD’s Cx efforts for the CMD design-build and construction Projects. Maintain Cx action list, prepare for and lead Cx meetings, and prepare Cx meeting minutes for CA. Facilitate contractor development of SOMMs. Develop

PCs and FPTs. Review design drawings, analysis, e.g., hydraulic calculations, mechanical loads, voltage drops;

specifications, equipment submittals, equipment shop drawings, project specific reports and other documents, e.g., OGC developed project specific designs, PCs, and SOMMs. Perform as-built field observations for verification that red-line drawings capture field changes and that as-built updates capture red-line changes (spot checks). Coordinate

FPT execution and CS labor requirements. Witness TAB verification and review TAB reports.

From a quality assurance level of effort for code applications, monitor and review building systems construction activities for significant deviations from design documents, code, or industry installation standards, e.g., operability, maintainability, fire barriers, handrails, step/riser/headroom, door ratings. Review contractor training plans and training material and facilitate training activities. Finalize Cx Plans prepared under separate contract. Provide Cx input for the FSD Facilities Project Progress Review (FPPR). Provide qualified technicians and engineers to direct and document FPTs performed by contractors. Track completion of Cx Plan deliverables, e.g., PCs, FPTs, SOMMs, training plans. Design reviews (estimated total of 350 drawing sheets) shall evaluate whether the designer has met owner’s intent based on contract serviceability, maintainability, and operability requirements, that the designer has met owner’s intent by adhered to applicable building, fire and life safety codes, and assess whether MEP and fire protections systems and components are adequately sized for owner/tenant identified requirements. Facilitate the adherence by all CS project labor with required Pentagon Reservation safety and security directives and initiatives.

Small AWG projects may require limited MEP Cx services; large AWG projects will require MEP design review and FPT development/execution. Based on historical data for CMD projects (excluding AWG projects), assuming the same level of project volume during the performance period as occurred in the past year, the proposed testing rates identified in the WHS Master Cx Plan, and prior AWG projects testing requirements, FPT development and execution is estimated in paragraph 2.9. AWG projects will not require a Cx Plan or a final Cx Report. Data on

AWG FPTs will be incorporated in the monthly Cx status reports. AWG projects do not normally have a TAB contractor. The Cx contractor shall provide TAB on one large and 5 small AWG projects.

CMD Projects – four (4) projects

Large (>5,000 SF) AWG Projects - one (1) project

Small AWG Projects – twenty-four (24) projects.

2.6 Integrated Systems Test. Provide Cx services to support Federal Facilities Division’s (FFD) development of an integrated systems test (IST) for the verification and integration of electrical and mechanical systems throughout the

Pentagon renovated spaces and systems. Cx services to include attendance at meetings for coordination and scheduling prior to test execution, test support during execution, and after action report documentation. In addition, the contractor shall gather data on mission and life safety loads from the building energy monitoring and control system (EMCS) and Government data loggers (30); analyze data to identify average and peak hourly readings for vaults and feeders. Update the existing IST to incorporate recent Pentagon power upgrade information and systems.

2.7 Re-Commissioning (ReCx). Provide implementation support for the Re-Cx Plan developed under the prior Cx contract for re-commissioning of Pentagon Reservation Facilities. Coordinate and oversee execution of ReCx FPTs with PBMO and/or OGC personnel. It is assumed that limited PC and FPT development will be required since FPTs for equipment and systems were developed under prior contracts. PC and FPT development and FPT execution is estimated in paragraph 2.9. Where tagging and labeling are deficient provide data to the Government for labeling correction. Provide TAB for 10% of mechanical FPTs.

2.8 MAXIMO Support. FFD uses MAXIMO, a computerized maintenance management system, to manage maintenance and repair programs at FFD operated facilities in the NCR. As areas of the Pentagon are renovated equipment must be added to the database and the new equipment must be linked to preventative maintenance (PM) job plans and safety plans which include lock-out/tag-out (LOTO) procedures. New equipment characteristics are included in the SOMMs design master equipment lists (DMELs). The DMEL information along with additional information, e.g., O&M fund cite, provided by FFD must be reconfigured and formatted for MAXIMO. These uploads are best handled in a batch format for efficient implementation. The contractor is responsible for preparation of these batch updates suitable for the Government to upload.

Receive a design master equipment list (DMEL) for PSOC Facility from the Government. Format the DMEL data into a MAXIMO uploadable batch format excluding parent associations. Provide the formatted data in MS Excel file batch format (Government will provide latest data load template) for Government review, comment, and any data correction. The Government will review data functionality for a period of 2 weeks from date of receipt and after loading into MAXIMO Test Environment. The Contractor shall fix any data issues reported in the first review period before upload into the MAXIMO Test Environment. Contractor shall provide a parallel quality control (QC) data check on equipment records uploaded into the MAXIMO Test Environment.

Per Government regulations, when FFD issues any work order to their workforce, FFD must inform their employees of any hazards they might encounter while performing work. To fulfill these regulatory requirements, all FFD work orders created against any asset or location must have detailed safety plans including hazards and their precautions, hazardous materials, and LOTO procedures. Some assets/locations will require specific safety plans while others may fit into one common default safety plan depending on Government requirements. Each unique equipment type in MAXIMO should have a unique PM job plan and safety plan attached. LOTO procedures within safety plan shall be specific to a unique asset number. The unique job plan and safety plans can be assigned to multiple pieces of like equipment. Contractor shall review equipment installed and where equipment tags or labels are missing but are needed for correct LOTO procedures; the contractor shall provide equipment tag and label data to the Government.

Review equipment installed in Switch House 2 and assign job plans previously developed for Wedges 2-5. Where new job plans are required, develop equipment specific job plans that meet original equipment manufacturers

(OEM) recommendations and industry standards (up to 5 plans). If there is a difference between OEM maintenance recommendations and industry standards the more stringent standard shall be met.

Develop complete safety plans for each type of asset listed in project DMEL. The scope of systems includes HVAC, Steam, Electrical, and Plumbing systems. This requirement includes identifying and writing safety plans which include but are not limited to, hazards and precautions, hazardous materials, LOTO procedures, and linking these to the correct assets in MAXIMO. The contractor shall provide the following data electronically in the Government provided templates and format in MS Excel (for MAXIMO Data upload) and in MS Word (printable book format with index for maintenance shops).

2.9 PC and FPT Development. Develop and execute FPTs for projects identified in paragraphs 2.2-2.7 per table 1.

Develop PC based on FPT development quantity from table 1.

2.10 FFD Construction Documentation Support. FFD’s Pentagon Renovation Liaison Office (PRLB) utilizes a robust document control software system, QuiCx tm by Chinook Systems, Inc., to support FSD construction document control. This system provides for tracking of when contract submission documents are due throughout the life of a design-build project from pre-design through project close-out and acceptance and provides the ability to link documents, comments, and submission status electronically. The QuiCx software operates on a MS SQL Server database and documents are maintained in a PDF format. The Cx contractor shall use the QuiCx system and provide yearly licensing and user accounts defined in individual task orders. Pricing is available at:

https://www.gsaadvantage.gov/ref_text/GS21F0019X/0ILFTF.288CNV_GS-21F-0019X_CHINOOK.PDF .

Table 1. PC AND FPT DEVELOPMENT, FPT EXECUTION, AND OTHER NCR SITES TRAVEL

Project Discipline

PC

Develop-ment

FPT

Develop-ment

FPT Execution

Non-

Mission

Critical

Mission

/Life

Safety

Retest* Total

PSOC

Facility

Electrical 10 10 5 15 3 23

Mechanical/Plumbing 15 15 10 30 6 46

Subtotal 25 25 15 45 9 69

Upgrades at Other

NCR

sites**

Electrical 6 6 0 24 4 28

Mechanical/Plumbing 6 6 0 24 4 28

Subtotal 12 12 0 48 8 56

Project

Closeout

PEU/Misc.

Electrical 5 5 0 17 3 20

Mechanical/Plumbing 2 2 0 8 2 10

Subtotal 7 7 0 25 5 30

CMD/

AWG

Electrical 6 6 15 0 2 17

Mechanical/Plumbing 10 10 30 0 5 35

Subtotal 16 16 45 0 7 52

ReCx

Electrical 2 2 20 1 3 24

Mechanical/Plumbing 2 2 100 5 16 121

Subtotal 4 4 120 6 19 145

Total

Projects

Electrical 29 29 40 40 32 112

Mechanical/Plumbing 35 35 140 59 40 240

Total 64 64 180 99 72 352

*15% Retest

**Other NCR sites FPT execution quantity increased by 20% for site access and travel allowance

2.10.1 Work Description: The contractor shall provide document management support for the PSOC and several smaller CMD and AWG projects. The smaller CMD projects include PAC HVAC Upgrades, Repairs and

Replacement at HRP, HRP Switch House 1.

2.10.2 Project Setup. Contractor shall setup new projects in the document management software system (~4 CMD projects). Assist the Government with defining project specific users, permissions, companies, contacts, and location data from Excel templates when available or by manual input if spreadsheets are not provided. Review the construction contract and specifications to extract deliverable information for project setup in the document management system, and for the purpose of drafting the master list of deliverables owed to the Government.

Develop close out logs to include warranty log, spare parts log, and training logs as required by construction documents. Submit master list of deliverables and close out logs to the PRLB.

2.10.3 Document Management and Data Entry. Contractor shall provide document management and technical support throughout the performance period or until all turnover documents have been received, entered into the document management database, and the projects accepted. Log the receipt of contract deliverables for the projects setup in the document management system. Contract deliverables are typically engineering drawings, EMCS control drawings, specifications, RFIs, contract change documents, formally transmitted correspondence, design and submittal review comments, design master equipment lists (DMEL), and product submittals as identified in contract construction documents. Upload electronic submissions of contract deliverables to the Government provided and designated document management system server. Ensure electronic files are stored in the proper location, rename files to meet document s file naming convention requirements, and manage file revisions. For files that are not provided in electronic format, scan hardcopy files. Contractor shall provide monitoring of data entry and file management, procedure compliance, and data integrity checks and track deliverable submissions received by the

PRLB and completed. The document management system shall enable PRLB personnel to access performance statistics on a periodic basis, e.g., daily, weekly, monthly, quarterly, to allow metrics reporting to FFD management.

Contractor shall provide a monthly report of performance statistics.

2.10.4 AWG Projects. FFD has identified a need to centrally manage AWG renovation and alteration construction project documentation. FFD will identify eight (8) current AWG projects to implement standardized workflows on.

Contractor shall review the AWG project work orders (WO). Contractor shall provide document management services to include entering the WO in the document management database as design change notices to appropriate as-builts, associate room numbers and as-built drawings to sketches, review appropriate as-built drawings, develop a list of drawings related to the WOs, and record room locations associated with sheets. Contractor shall review WO scope to identify products being used, develop a submittal register to match specification deliverables, record submittal data in the document management system, and, if new equipment is being added, update the DMEL.

Contractor shall populate warranty, spare parts, and training logs as required by specification deliverables.

Contractor shall provide a summary report on implementation and recommendations for path forward.

2.10.5 Commissioning Process Implementation: Contractor shall review the WHS Master Cx Plan, map the commissioning process to the document management Cx module, establish a process to implement FPT development, track field tests, manage the DMEL and Cx issues, and relate Cx documents to actual DMEL equipment records. Contractor shall update the existing FFD workflow analysis with recommended Cx process

(flowchart and narrative form).

2.10.6 Training and Support to MS SQL Server Platform. Contractor shall provide support for the MS SQL Server platform, to include administrative/data entry training platform to PRLB core staff (7 users). Contractor shall provide training (fifteen (15) users per session for 3 (~2 hour sessions)) to designated AWG and PRLB personnel on developing transmittals, RFI’s, completing field reports, and using the document management system Issues

Management feature to track punch list items. Contractor shall provide system overview and navigation training to system users on the SQL platform (fifteen (15) users per session for 6 (~2 hour sessions)). In addition, the contractor shall provide system overview, navigation, and Cx process training to the Wedge 5 Cx team (fifteen (15) users per session for 3 (~4 hour sessions). Finally, the contractor shall provide document management system application technical support Monday through Friday, 8:00 AM to 4:00 PM. This technical support shall include assistance with application installation, project setup, user setup and permissions, user navigation support, and application troubleshooting. QuiCx Upgrades and Customizations: Contractor shall provide one QuiCx upgrade.

Contractor shall work closely with EITSD to deploy new release of QuiCx and test functionality in a CAC enabled test environment. Contractor shall assist EITSD with deployment to production environment and perform any required data migration (estimated 100 hours. Contractor shall develop new or update existing system administration and functional user manuals to capture unique customizations and configuration specific to the WHS/FCMP environment. Provide 100 hours of customizations to QuiCx in support of department specific data and document management initiative/requirements of WHS.

2.11 Code Enforcement. The contractor shall provide all labor, equipment, materials, and supervision necessary to conduct code enforcement support services for FSD construction projects. Provide the following services:

Contractor shall perform surveys of existing areas and facilities, conduct inspections for the Pentagon Reservation and WHS leased facilities, execute the WHS Building Permit Program, conduct plan reviews, witness code required testing, and assist in code development and implementation, All work shall be performed in coordination with the

Office of the Pentagon Fire Marshal (OPFM), Code Review and Inspection Group (CRIG) Sub-Building Code

Official and/or the Building Code Official.

The contractor shall provide code enforcement services support that continuously improves the effectiveness and efficiency of the FSD code enforcement program. The Contractor shall use the following codes, standards, and technical documents as a basis for their engineering and inspection services:

• Washington Headquarters Services Building Code (WHSBC)

• Unified Facilities Criteria (UFC) – General Building Requirements, UFC 1-200-01

• International Code Council (ICC) I-Codes

• National Fire Protection Association (NFPA) National Fire Codes

• Architectural Barriers Act (ABA)

• American Society of Mechanical Engineers (ASME) Safety Code for Elevators ASME 17.1

The contractor shall use the appropriate edition of the code based on the specific project requirements. Tasks include the following:

2.11.1 Conduct Code Compliance Inspections and Corrective Action Follow-up.

The Inspector shall provide basic inspections relative to their discipline of all projects for which a building permit has been issued to ensure conformance with the approved design and the WHS Building Code.

The Inspector shall use the WHS Building Code to document all violations identified during the inspection. Code references should be included for each violation; and photographic documentation shall be provided to clarify a condition or violation. The Inspector shall populate a log of all deficiencies noted throughout the course of a project.

The log shall include, among other things, date issue generated, the feature with issue, issue description, dated response to issue, issue status, dated updates, dated resolution, and responsible party. Deficiency photographs shall be indexed to the issue within the deficiency log. The deficiency log shall be owned by the Sub-code official.

The inspector shall document, through photographs, features of work behind walls and above ceilings relevant to their discipline, after the work has been completed, but before close in. These photographs shall be incorporated into a project master PDF file that catalogs each photo to its location on the final construction as-built.

The inspector shall provide a weekly briefing to the Sub-code official as to the status of projects’ deficiencies.

The inspector is responsible for providing all administrative services required to run the inspection program including populating the deficiency database, cataloging deficiency photographs, maintaining inspection files, maintaining/creating inspection and re-inspections schedules and notifications in accordance with the Building Code

Official’s instructions, updating issue status accordingly, and coordinating re-inspections.

Table 2. Compliance Inspections

Action Total per Year

Construction Inspection (each) 180

Maintain Deficiency Log (each) 180

Catalog Deficiency Pictures (each) 180

Catalog Close-in Pictures (each) 180

Weekly Brief (each) 52

Construction Re-inspection (each) 150

2.11.2 Monitor Code Compliance Testing.

The Inspector shall be present for all code compliance testing. The contractor shall document tests for required compliance, and identify non-compliance citing appropriate code.

The Inspector shall document the results of each test on the most up to date version of the relevant project drawing.

If the contractors work is not accurately reflected on the drawing the inspector will redline the drawing to match the field conditions. The Inspector shall differentiate the features that have passed and failed, provide a description of the failure, relevant test information, and notes on the drawing. Upon completion of testing the drawing shall be signed off on by the responsible Sub, the General Contractor, PM, and Inspector 1 business day after completion of the test. Any issues uncovered during compliance testing shall be noted in the deficiency log and presented during the weekly progress briefing with the sub code official.

Table 3. Compliance Testing

Action Total per Year

Monitor Code Required Tests (each) 96

Code Required Testing Documentation (each) 96

Maintain Deficiency Log (each) 96

Re-test (each) 72

2.11.3 Support the development and updating of the WHS Building Code.

The code enforcement team shall provide impact analysis on the updates to the referenced codes and standards contained within the WHS building Code referenced codes and additions, changes, and updates to building operations for WHS managed facilities.

Table 4. Code Updates

Document Total per Year

Change Proposals for WHS Building Code (each) 12

2.11.4 Plan Review.

The Plan Reviewer shall provide design reviews which evaluate whether the designer has met the requirements of the WHS Building Code. The Design Review shall incorporate among other things a review of the project drawings, specifications, submittals, and plans.

The Plan Reviewer shall utilize current Government project submittal/review systems (QuiCx, Design Review

Account, or similar based on project use) to review drawings and submittals, document design review comments and inspections, and document the project to completion. Comments shall be tracked in the appropriate comment review system for each project (QuiCx, Dr. Checks, spreadsheets, etc.).

Table 5. Plan Review

Project Size Total per Year

Small < 1,000 sf (~26 hr per project) (each) 68

Medium 1,000 - 5,000 sf (~40 hr per project) (each) 34

Large > 5,000 sf (~320 hr per project) (each) 10

3.0 Deliverables. All deliverables required by this Task Order shall be submitted to the Contracting Officer’s

Representative (COR) within the specified times. The number of submittals shall be in accordance with the type of submittal required, but in no case shall quantity exceed 1 hard copy and 2 electronic copies. Distribution shall be as directed by COR. All deliverables shall be provided per Table 2. All days shown are calendar days.

4.0 Other Performance Requirements

4.1 Orientation Briefing/Kickoff Meeting. Approximately 10-work days after award, the Contractor shall conduct an orientation briefing for the COR. This can be in conjunction with the monthly contract review meeting. (SCD does not want an elaborate orientation briefing nor does it expect the Contractor to expend significant resources in preparation for this briefing.) The intent of the briefing is to initiate the communication process between the COR and Contractor by introducing the Contractor’s on-site PM and key task participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of requirements and objectives of this Task Order. The Orientation

Briefing will be held at the Pentagon. The date and time will be mutually agreed upon by both parties. The completion of this briefing will result in the following:

Introduction of key Contractor and Government personnel performing work under this Task Order.

The Contractor shall demonstrate confirmation of their understanding of the work to be accomplished under this PWS.

Table 2. Deliverables

Deliverable

PWS

Para. Due Date

Task Order QC

Monthly Cx Status Report

Monthly Briefing input

Contract status meeting agenda and meeting minutes

Cx process training & attendee evaluation summary

2.1 th day of month th day of month

Agenda-15 th of each month

Meeting minutes within 2 business days

Conduct Quarterly Training with evaluation

Summary due within 2 days of session

Projects

Cx Meeting Minutes

Cx Action List and Updates

Cx Status Reports

Functional Performance Tests

Input to briefings

Updated Cx Plan

2.2-4

2.2-4

2.2-4

Frequency commensurate w/proj. activity level

Frequency commensurate w/proj. activity level th day of month

Final FPT due prior to execution date th of each month

30 days after Cx IPT Leader and CA approve comments & provide direction to CS

As-built verification comment reports

Construction inspection and observation reports

FPT Tracking List

Submittal comments

Design package review comments

Final Cx Report

Warranty phase Cx Review Report

2.2-4

2.2-4

2.2-4

2.2-4

14 days after submittal receipt from Govt.

3 days after inspection

Weekly

14 days after submittal receipt from Govt.

14 days after submittal receipt from Govt.

90 days after transition to the Government

330 days after transition to the Government

ReCx Status

ReCx FPT Execution

2.6

2.6

Update in monthly TO report

15 each-15 OCT, 15 DEC 2016

IST After Action Report

Metering Data Analysis Report

IST Appendix-Tenant Checklists

2.7

2.7

2.7

15 days after test execution

Weekly, JUN 1-JUL 31 2017

15 MAY 2017

MAXIMO Upload

LOTO/Safety Plans

2.8

2.8

30 AUG 2017

30 AUG 2017

Submit master list of deliverables and close out logs to PRLB

Performance Statistics Report

AWG Short Form Specifications

Updated FFD work flow analysis with CMD

Projects Cx process integration

Document Management System Training-PRLB, AWG, General System, and CMD team

2.10.2

2.10.3

2.10.4

2.10.5

2.10.6

14 calendars after 100% design th of each month

30 days after WO assignment

1 December 2016

Quarterly

Update deficiency log

Status update

Catalog inspection photos

2.11.1

2.11.1

2.11.1

1 business day after inspection

Every Tuesday

5 business days after inspection

Submit testing documentation

Update deficiency log

Status update

2.11.2

2.11.2

2.11.2

1 business day after test

Every Tuesday

5 business days after inspection

Submit WHS Building Code change proposal 2.11.3 1 June 2017

Submit plan review comments 2.11.4 10 business days after submittal receipt from Govt.

4.2 Contractor Interface. The Contractor and/or its subcontractors may be required, as part of the performance of this effort, to work with other contractors working for the Government. Such other contractors shall not direct this

Contractor and/or its subcontractors in any manner. This Contractor and/or its subcontractors shall not direct the work of other contractors in any manner. The Government will establish the initial contact between the Contractor and other contractors and will participate in an initial meeting at which the conventions for the scheduling and conduct of future meetings/contacts will be established. Any COR assigned to other contracts that may affect work under this Task Order shall be included in any establishment of conventions. (Also See Paragraph 4.9 “Cooperation with Other On-Site Contractors.”

4.3 Disclosure of Information. Information made available to the Contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer (CO). The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each Contractor or

Contractor employee to whom information may be made available or disclosed shall be notified in writing by the

Contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

4.4 Limited Use of Data. Performance of this effort may require the Contractor to access and use data and information proprietary to a Government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.

4.5 Confidentiality. All information regarding the procedures developed under this Task Order shall be regarded as sensitive information by the Contractor and shall not be disclosed to anyone outside the Contractor’s organization without the written permission of the CO. All Contractor employees supporting the Government on this project must sign a non-disclosure statement before the start of work on this Task Order.

4.6 Contractor Personnel. The Contractor shall be responsible for managing and overseeing the activities of all

Contractor personnel, as well as subcontractor efforts used in the performance of this effort. The Contractor's management responsibilities shall include all activities necessary to ensure the accomplishment of timely and effective support, performed in accordance with the requirements contained in this PWS. Resumes submitted for key employees assigned to perform under this PWS shall include documented experience directly applicable to the

Government’s requirements. Furthermore, prior work experience shall be specific and of sufficient variety and duration to ensure that the employee is competent and able to efficiently perform his/her assigned work.

4.7 Contractor Project Manager. The Contractor Project Manager (PM) shall be the primary technical and managerial interface between the Contractor, Contracting Officer (CO), and the COR. The PM will facilitate

Government-Contractor communications and be co-located with the COR. The Contractor shall provide written designation of the PM on this Task Order to the CO and COR. Alternates must also be designated and represent the

Contractor when the PM is absent. The PM or alternates shall have full authority to act for the Contractor on all contracting matters relating to daily operations. The PM and alternates shall be fluent in the English language.

The PM or alternates shall be available during established operating hours, as specified herein, to meet with

Government personnel within 24 hours of any request to discuss problems. The Contractor's PM shall meet with the CO/COR as necessary to maintain satisfactory performance and resolve any issues pertaining to this Task Order.

A mutual effort will be made to resolve any and all issues at these meetings. The Contractor shall prepare written minutes of these meetings and provide a copy to the Government within two (2) workdays after the meeting.

The Contractor’s PM or alternates shall be responsible for managing and overseeing the activities of all Contractor personnel, as well as subcontractor efforts used in performance under this Task Order. The Contractor's management responsibilities shall include all activities necessary to ensure the accomplishment of timely and effective support, performed in accordance with the requirements contained in this PWS.

4.8 Physical Security. The Contractor shall be responsible for safeguarding all government property and data provided for use under this Task Order. At the end of the workday, all Government facilities, equipment, and materials shall be secured.

4.9 Cooperation with Other On-Site Contractors (as applicable). When the Government undertakes or awards other task orders or contracts for other work at the facilities, the Contractor must: (1) fully cooperate with the other contractors and Government employees, and (2) carefully coordinate its own work to such other contracted work as may be directed by the COR. The Contractor shall not take or permit any action that may interfere with work under other contracts or with the performance of Government employees.

If the Contractor disturbs any work accomplished by another contractor, completed or in-progress, the Contractor shall restore the affected work. If the affected work was covered by warranty under another contract, then the

Contractor shall honor the original warranty at its own expense. Affecting the completed work of other contractors voids an active warranty; therefore, the party causing the warranty to terminate shall be responsible for restoring it.

5.0 Place of Performance. The primary worksite location is the Pentagon. Some work will occur at the other DoD and leased facilities in the National Capital Region. Some work may be accomplished at the contractor offices off-site, e.g., contractor corporate office. The Government will provide a minimum of two (2) workstations at the

Pentagon to support this task order.

6.0 Period of Performance. The performance period for this Task Order is July 1, 2016 through June 30, 2017.

7.0 Administrative Considerations

7.1 Correspondence. To promote timely and effective administration, correspondence shall comply with the following procedures:

a. Technical correspondence (where technical issues relating to compliance with the requirements herein) must be addressed to the COR.

b. All other contractual correspondence (including invoices) which represent or otherwise involve waivers, deviations or modifications to the requirements, terms or conditions of this PWS shall be addressed to the CO with an informational copy to the COR.

7.2 Points of Contact

7.2.1 Contracting Officer’s Representative (COR). The COR for this task order will be identified in writing by the CO after task order award. The COR is the individual within the Program Management function who has overall technical responsibility for this effort and serves as the Government’s day-to-day interface with the Contractor.

72.2 Contracting Officer. Lawrence Yates and his phone number is 703-545-1623.

8.0 Government Furnished Information. PWS Paragraphs 5.3 “Disclosure of Information”, 5.4 “Limited Use of

Data,” and 5.5 “Confidentiality” will be used with all information furnished to the Contractor.

8.1 References. The following references will be made available to the contractor in support of this task order:

a. WHS Building Code

b. WHS Master Cx Plan

c. PSOC Requirements Document and Cx Plan

d. MAXIMO 6.2 System Operations Manual(s) (current version for proposed system)

8.2 Provided by the Government. All documents, drawings, and equipment will be proprietary property of the

Federal Government. The following will be furnished by the Government:

a. Local on-site access to a networked computer workstation with MS Office Professional full suite.

b. Remote off-site access to the Government network via an appropriately configured Government laptop.

c. MAXIMO data upload templates with format requirements.

d. Access to the Pentagon BAS, MAXIMO, and other associated systems/databases, as required.

e. Access to Pentagon Systems Operations and Maintenance Manuals (SOMMs).

f. MAXIMO 6.2 System Operations Manual (current version).

g. File server for document management database

h. All applicable construction contract deliverables

i. Scanner

j. Project DMELs