BWI_HVAC_Upgrade_TORFP_final.pdf

CONSULTING AND TECHNICAL SERVICES+ (CATS+)

TASK ORDER REQUEST FOR PROPOSALS (TORFP)

DEPARTMENT OF INFORMATION TECHNOLOGY

(DOIT)

SOLICITATION NUMBER: BPM057440

BWI HVAC UPGRADE

ANNE ARUNDEL COUNTY

ISSUE DATE: JUNE 8, 2026

Maryland FiRST Project – BWI HVAC UPGRADE

Solicitation # BPM057440

CATS+ TORFP

RFP for the Department of Information Technology Page 2 of 72

DEPARTMENT OF INFORMATION TECHNOLOGY (DOIT)

KEY INFORMATION SUMMARY SHEET

Solicitation Title: BWI HVAC UPGRADE

Solicitation Number (TORFP#): FC-362-26

Functional Area: FA14 – Tower Equipment Installation and Services

TORFP Issue Date: June 8, 2026

TORFP Issuing Office: Department of Information Technology (DoIT)

DoIT Location: 100 Community Place, Crownsville, MD 21032

TO Procurement Officer:

e-mail:

Cherise Edmonds 100 Community Place Crownsville, MD 21032 cherise.edmonds@maryland.gov

TO Manager: Jennifer Zambito e-mail: Jennifer.Zambito@maryland.gov

TO Proposals are to be sent to: Submit on emma.maryland.gov under Solicitation Number

BPM057440

TO Pre-proposal Conference: June 22,2026 10:00 am Local Time at 7000 Elm Rd, Baltimore, MD 21240 See Attachment A for directions and instructions.

TO Proposals Due (Closing) Date and Time:

July 30,2026 at 2:00 PM Local Time Offerors are reminded that a completed Feedback Form is requested if a no-bid decision is made (see Section 5).

MBE Subcontracting Goal: 20%

VSBE Subcontracting Goal: 0%

Task Order Type: Firm Fixed Price

Task Order Duration: Final acceptance of the work and final documentation, not to exceed 180 working days from NTP

Primary Place of Performance: Baltimore/Washington International Thurgood Marshall Airport (BWI) Anne Arundel County, Maryland

SBR Designation: No mailto:Jennifer.Zambito@maryland.gov

RFP for the Department of Information Technology Page 3 of 72

SBP Designation: Yes

Federal Funding: No

Questions Due Date and Time June 29, 2026 by 2pm Local Time

TABLE OF CONTENTS

1 Minimum Qualifications

1.1 Master Contractor Minimum Qualifications

2 TO Contractor Requirements: Scope of Work

2.1 Summary Statement

2.2 Background and Purpose

2.3 Responsibilities and Tasks

2.4 Deliverables

2.5 Service Level Agreement (SLA)

3 TO Contractor Requirements: General

3.1 Task Order Initiation Requirements

3.2 End of Task Order Transition

3.3 Invoicing

3.4 Liquidated Damages

3.5 Insurance Requirements

3.6 Security Requirements

3.7 RESERVED

3.8 SOC 2 Type 2 Audit Report

3.9 Performance and Personnel

3.10 Substitution of Personnel

3.11 Minority Business Enterprise (MBE) Reports

3.12 Veteran Small Business Enterprise (VSBE) Reports

3.13 Work Orders

RFP for the Department of Information Technology Page 4 of 72

4 TORFP Instructions

4.1 TO Pre-Proposal Conference

4.2 Questions

4.3 TO Proposal Due (Closing) Date and Time

4.4 Award Basis

4.5 Oral Presentation

4.6 Limitation of Liability

4.7 MBE Participation Goal

4.8 VSBE Goal

4.9 Living Wage Requirements

4.10 Federal Funding Acknowledgement

4.11 Conflict of Interest Affidavit and Disclosure

4.12 Non-Disclosure Agreement

4.13 HIPAA - Business Associate Agreement

4.14 Iranian Non-Investment

4.15 Mercury and Products That Contain Mercury

4.16 Location of the Performance of Services Disclosure

4.17 Department of Human Services (DHS) Hiring Agreement

4.18 Small Business Reserve (SBR) Set-Aside

4.19 Bonds

5 TO Proposal Format

5.1 Required Response

5.2 Two Part Submission

5.3 TO Proposal Delivery

5.4 Volume I - TO Technical Proposal

5.5 Volume II – TO Financial Proposal

6 Evaluation and Selection Process

6.1 Evaluation Committee

6.2 TO Technical Proposal Evaluation Criteria

6.3 TO Financial Proposal Evaluation Criteria

RFP for the Department of Information Technology Page 5 of 72

6.4 Selection Procedures

6.5 Documents Required upon Notice of Recommendation for Task Order Award

7 TORFP ATTACHMENTS AND APPENDICES

RFP for the Department of Information Technology Page 6 of 72

1 Minimum Qualifications

1.1 Master Contractor Minimum Qualifications

There are no Minimum Qualifications for this procurement.

RFP for the Department of Information Technology Page 7 of 72

2 TO Contractor Requirements: Scope of Work

2.1 Summary Statement

2.1.1 The Department of Information Technology (“DoIT” or the "Department") is issuing this CATS+ TORFP to procure a contactor to design, and install an upgraded HVAC system in the MD First equipment room of The Baltimore/Washington International Thurgood Marshall Airport (BWI) in Anne Arundel County, Maryland. This system conditions equipment spaces on the 8th and 9th floor of the Daily Parking Garage

(DPG).

The new system would maintain stable environmental conditions required for proper operation and longevity of installed telecommunications and electrical equipment.

2.1.2 A Task Order award does not assure a TO Contractor that it will receive all State business under the Task Order.

2.1.3 DoIT intends to award a Task Order to one (1) Master Contractor that proposes a team of resources that can best satisfy the Task Order requirements.

2.1.4 Master Contractors are advised that should a solicitation or other competitive award be initiated as a result of activity or recommendations arising from this Task Order, the Master Contractors awarded this Task Order may not be eligible to compete if such activity constitutes assisting in the drafting of specifications, requirement, or design thereof.

2.2 Background and Purpose

2.2.1 Overview

The Maryland First Responder Radio System Team (MD FiRST) is a statewide, P25 Phase 2, Motorola trunked radio system that supports all public safety radio communications at the State level, as well as serving as the primary public safety communications system for eight (8) counties. MD FiRST uses various 700 MHz radio frequencies to provide outdoor, portable radio coverage across the State. The system consists of 170 transmitter sites across the State. The last phase of the system became operational in April 2023.

2.2.2 Current Situation

The MD First equipment room within the BWI Daily Parking Garage (DPG) routinely experiences excessive heat during the summer months which creates a risk to the reliability and service life of critical telecommunications and electrical equipment. To address these conditions, the Maryland Department of Information Technology (DoIT) seeks a TO Contractor to design, furnish, and install an

RFP for the Department of Information Technology Page 8 of 72 upgraded HVAC solution capable of maintaining stable environmental conditions to support future growth.

It is expected that the TO Contractor will assess existing infrastructure, recommend improvements, design and install a complete system that provides continuous temperature control, supports future expansion, provides redundancy, and meet BWI permitting requirements.

2.2.3 State Staff and Roles

In addition to the TO Procurement Officer and TO Manager, the State will provide a State Project Manager who will coordinate with the TO Contractor and BWI representatives to ensure all work is completed per the scope of work.

2.2.4 Other State Responsibilities

The State is responsible for providing the required information, data, documentation, and test data to facilitate the TO Contractor’s work performance and will provide such additional assistance and services.

2.3 TO Contractor Responsibilities and Tasks

2.3.1 Site Survey

The Contractor shall conduct a comprehensive assessment of existing site conditions, including equipment, available space, structural considerations, and other factors affecting design and installation, to identify any deficiencies, constraints, or capacity limitations that could impact the new HVAC installation. Any required upgrades or modifications necessary to support the proposed HVAC system shall be incorporated into the design.

The site survey shall include the following:

a) Existing equipment, electrical layout, and available space for potential additional units,

b) Parking space and traffic impacts, and

c) Locations of cores for future refrigerant lines.

2.3.2 Design

The Contractor shall design a system that maintains stable environmental conditions to ensure proper operation and longevity of all installed telecommunications and electrical equipment. The system will be designed to meet operational requirements, accommodate future growth, and comply with all applicable BWI permitting and structural requirements.

RFP for the Department of Information Technology Page 9 of 72

All designs, drawings, calculations, and supporting documentation shall be reviewed, and certified by a Professional Engineer (PE) licensed in the State of Maryland, with a current and active license in good standing, and shall bear the PE’s seal, signature, and date in accordance with applicable regulations.

The TO Contractor shall provide a design to address the following areas:

1. Environmental and Temperature Requirements

The system shall be designed to achieve and maintain the following environmental standards within the equipment room:

a) Normal Range: Maintain at all times a consistent temperature between 65°F (18°C) and 80°F (26.5°C) (32°C) under all normal load and ambient conditions.

b) Allowable Range: Ensure the room temperature never falls below 60°F (15.5°C) or exceeds 90°F at any time, including during peak load or extreme weather.

c) Thermal Integrity: Provide and install insulation as required to minimize exterior heat transfer and maximize the efficiency of the conditioned space.

d) Airflow Management: Design air exchange and distribution systems to provide uniform cooling and eliminate "hot spots" within equipment racks.

e) Emergency Mitigation: Provide an emergency ventilation system capable of exhausting heat in the event of a primary system failure or high-temperature threshold breach.

2. Room Heat Load Requirements

TO Contractor shall determine the British Thermal Unit (BTU) load of the current equipment room based on the existing equipment and the design requirements below:

a) For the purpose of the load calculation, existing G-series Transmitter and

Receiver (GTR) base stations shall be calculated as "D" series units.

b) Two (2) additional “D” series base stations should be included before establishing the baseline BTU load. The baseline shall include the heat load of two (2) additional "D" series base stations not yet installed.

c) Proposed systems should account for the baseline BTU as well as 10% and 20% expansion scenarios, with pricing provided for each.

d) The State will provide the BTU load for all Motorola propriety equipment.

RFP for the Department of Information Technology Page 10 of 72

3. HVAC System Features and Functionality The system shall include:

a) Redundant HVAC units with load-sharing and orphan mode capabilities.

b) Lead / lag operation to optimize efficiency and reliability.

c) Alarms for high temperature, low temperature, and summary events to support proactive monitoring.

d) Review of existing heat pump capabilities to ensure continuous conditioning for the 9th floor space, even during and after upgrades. If sufficient, the existing system may remain dedicated to this area to maintain uninterrupted operation.

4. Electrical and Grounding Requirements

The Contractor is responsible for all infrastructure modifications required to support the new mechanical system, including:

a) Electrical Upgrades: All necessary electrical service upgrades, circuiting, and disconnects required for the upgraded HVAC system.

b) Grounding and Bonding: All installations must comply with Motorola R56 standards and applicable local electrical codes to protect sensitive radio equipment from surges and interference.

5. Space and Structural Requirements

The design and installation shall accommodate the building’s structural constraints, including:

a) Structural Integrity (Post-Tensioned Concrete): The Contractor shall assume the presence of post-tensioned cables within the parking garage/building structure. Prior to any saw cutting or core drilling, the Contractor shall perform non-destructive concrete scans (GPR) to map rebar and tensioning cables.

b) Logistics: Installation shall not encroach upon active parking stalls or traffic lanes without prior written approval from BWI. TO Contractor shall complete

2.3.3 Installation

The Contractor shall install all equipment and materials for the proposed system consistent with the approved design and NFPA standards.

a) The work shall be completed within 180 calendar days from Notice to Proceed.

b) All work must be coordinated daily and confirmed with the State Project

Manager, BWI Technical Personnel and the MD FiRST team.

RFP for the Department of Information Technology Page 11 of 72

2.3.4 Warranty & Maintenance

The TO Contractor shall provide a comprehensive two-year (24-month) Maintenance and Warranty package for the complete HVAC system. This period shall commence immediately upon formal Final Acceptance by the State of the installed system.

1. Warranty Coverage

Full Parts and Labor: The warranty shall cover the repair or replacement of all system components, including compressors, fans, motors, control boards, and refrigerant, at no additional cost to the State.

Manufacturer Warranties: The Contractor shall facilitate and transfer all extended manufacturer warranties (e.g., 5-year compressor warranties) to the State upon project completion.

2.3.5 Permits

The Contractor shall obtain and comply with all permits necessary to perform the work outlined in this solicitation, including but not limited to any BWI permitting requirements.

2.3.6 TO Contractor-Supplied Hardware, Software, and Materials

A. By responding to this TORFP and accepting a Task Order award, an Offeror agrees explicitly that for any software and hardware that it proposes to install in response to this TORFP, the State will have the right to purchase the same from another source, instead of from the selected Offeror. Material costs shall be passed through with no mark-up by the TO Contractor.

2.3.7 Required Project Policies, Guidelines and Methodologies TO Contractor shall be required to comply with all applicable laws, regulations, policies, standards, and guidelines affecting Information Technology projects, which may be created or changed periodically. The offeror must review all applicable links provided below and state compliance in its response.

The TO Contractor is responsible for ensuring adherence and remaining abreast of new or revised laws, regulations, policies, standards, and guidelines affecting project execution. These include, but are not limited to:

A. The TO Contractor shall follow project management methodologies consistent with the most recent edition of the Project Management Institute’s Project Management Body of Knowledge Guide and

B. TO Contractor Personnel shall follow a consistent methodology for all Task Order

RFP for the Department of Information Technology Page 12 of 72 activities.

2.3.8 Product Requirements

A. Offeror must be authorized to furnish the proposed goods and services.

Offerors proposing to resell services of another entity must be approved by such other entity.

B. Any TO Agreement award is contingent on the State’s agreement, during the TORFP Proposal evaluation process, to any applicable terms of use and any other agreement. Such agreed upon terms of use shall apply consistently across services ordered under the TO Agreement.

C. In addition to any notices of renewal sent to the Agency, TO Contractors shall email notices of renewal to the e-mail address designated by the TO Manager.

2.4 Deliverables

2.4.1 Deliverable Submission

A. For every deliverable, the TO Contractor shall request the TO Manager confirm receipt by sending an email identifying the deliverable name and date of receipt.

B. For every deliverable, the TO Contractor shall submit an e-mail stating that the deliverable was completed and the completion date to the TO Manager.

C. Unless specified otherwise, written deliverables shall be compatible with Microsoft Office, Microsoft Project and/or Microsoft Visio within two (2) versions of the current version. At the TO Manager’s discretion, the TO Manager may request one hard copy of a written deliverable.

D. The State and the TO Contractor will elaborate on and agree on a standard deliverable review cycle. This review process begins when the TO Contractor completes a deliverable.

E. For any written deliverable, the TO Manager may request a draft version of the deliverable to comply with the minimum deliverable quality criteria listed in Section 2.4.3 Minimum Deliverable Quality. Drafts of each final deliverable, except status reports, are required at least two weeks before the final deliverables are due (except deliverables due at the beginning of the project where this lead time is not possible or where the draft delivery date is explicitly specified). Draft versions of a deliverable shall comply with the minimum deliverable quality criteria listed in Section 2.4.3 Minimum Deliverable Quality.

RFP for the Department of Information Technology Page 13 of 72

2.4.2 Deliverable Acceptance

A. A final deliverable shall satisfy the scope and requirements of this TORFP for that deliverable, including the quality and acceptance criteria for a final deliverable as defined in Section J. Deliverable Descriptions Acceptance Criteria.

B. The TO Manager shall review a final deliverable to determine compliance with the acceptance criteria as defined for that deliverable. The TO Manager is responsible for coordinating comments and input from various team members and stakeholders. The TO Manager is responsible for providing clear guidance and direction to the TO Contractor in the event of divergent feedback from various team members.

C. The TO Manager will issue the TO Contractor a notice of acceptance or rejection of the deliverable. Following the TO Manager’s approval, the TO Contractor shall submit a proper invoice in accordance with the procedures in Section 3.3. The invoice must accompany a copy of the TO Manager’s email acceptance, or payment may be withheld.

D. In the event of rejection, the TO Manager will formally communicate in writing any deliverable deficiencies or non-conformities to the TO Contractor, describing in those deficiencies what shall be corrected before acceptance of the deliverable in sufficient detail for the TO Contractor to address the deficiencies. The TO Contractor shall correct deficiencies and resubmit the corrected deliverable for acceptance within the agreed-upon period for correction.

2.4.3 Minimum Deliverable Quality

The TO Contractor shall subject each deliverable to its internal quality-control process before submitting it to the State.

Each deliverable shall meet the following minimum acceptance criteria:

A. Be presented in a format appropriate for the subject matter and depth of discussion.

B. Be organized to present a logical flow of the deliverable’s content.

C. Represent factual information reasonably expected to have been known at the time of submission.

D. In each section of the deliverable, include only information relevant to that section.

E. The content and presentation must be consistent with industry best practices regarding deliverable completeness, clarity, and quality.

F. Meets the acceptance criteria applicable to that deliverable, including

State policies, functional or non-functional requirements, or industry standards.

RFP for the Department of Information Technology Page 14 of 72

G. Contains no structural errors such as poor grammar, misspellings, or incorrect punctuation.

H. Must contain the date, author, and page numbers. When applicable for a deliverable, a revision table must be included.

I. A draft written deliverable may contain limited structural errors such as incorrect punctuation and shall represent significant completeness toward the final written deliverable. The draft written deliverable shall otherwise comply with the minimum deliverable quality criteria above.

2.4.4 Deliverable Description / Acceptance Criteria

Deliverable Due Date Acceptance Criteria

1. Initial Site Survey Report

NTP +30 days Complete documentation of existing equipment, electrical layout, structural conditions, and design considerations.

2. Room Heat Load Calculation Report

NTP + 30 days BTU analysis including baseline, 10%, and 20% expansion scenarios, incorporating existing and proposed equipment.

3. Design Documentation and Permits

NTP + 90 days Full engineering design package including drawings, specifications, equipment selection, and calculations, signed and sealed by a licensed PE in the State of Maryland.

For construction permits: Develop an Acceptance test for State review.

4. Installation

Permits + 60 days Final acceptance walk to verify installation and operation of designed system.

Acceptance Test on system, temperature controls and alarms.

RFP for the Department of Information Technology Page 15 of 72

5. Final Documentation

• As-Built Drawings

• System Equipment Documentation

• Testing results

• 30-day test results

Completion of Installation + 15 days

Submission, review and approval by TO Project Manager of all submitted documents. -Close out and passing of all MAA permits.

2.5 Service Level Agreement (SLA)

THIS SECTION IS NOT APPLICABLE TO THIS TORFP.

THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.

RFP for the Department of Information Technology Page 16 of 72

3 TO Contractor Requirements: General

3.1 Task Order Initiation Requirements

TO Contractor shall schedule and hold a kickoff meeting within 10 Business Days of the NTP Date. At the kickoff meeting, the TO Contractor shall provide the following:

A. Introductions of TO Contractor project team B. Baseline project schedule

3.2 End of Task Order Transition

TO Contractor shall support end-of-task order transition efforts with technical and project support to include but not be limited tol ensuring that all documentation and data, including, but not limited to, System Documentation and current operating procedures, is current and complete in a format prescribed by the TO Manager.

3.3 Invoicing

3.3.1 Definitions

A. “Proper Invoice” means a bill, written document, or electronic transmission, readable by the agency, provided by a vendor requesting an amount that is due and payable by law under a written procurement contract for property received or services rendered that meets the requirements of COMAR 21.06.09.02 and Section 3.3.2.C below.

B. “Late Payment” means any amount that is due and payable by law under a written procurement contract, without deferral, delay, or set-off under COMAR 21.02.07.03, and remains unpaid more than 45 days after an agency receives a Proper Invoice.

C. “Payment” includes all required processing and authorization by the Comptroller of the Treasury, as provided under COMAR 21.02.07, and may be deferred, delayed, or set-off as applicable under COMAR 21.02.07.03.

3.3.2 General

A. Invoice payments to the TO Contractor shall be governed by the terms and conditions defined in the CATS+ Master Contract.

B. The TO Contractor shall e-mail each invoice to doitfiscal.invoiceservice@maryland.gov.

Submission of an invoice serves as the TO Contractor’s verification of accuracy.

C. Invoices submitted without the required information cannot be processed for payment. A

Proper Invoice, required as Payment documentation, must include the following information, without error:

1) TO Contractor’s name and address;

2) Remittance address;

3) Federal taxpayer identification (FEIN) number, social security number, as appropriate;

mailto:doitfiscal.invoiceservice@maryland.gov

RFP for the Department of Information Technology Page 17 of 72

4) Invoice period (i.e., time period during which services covered by invoice were performed);

5) Invoice date;

6) Invoice number;

7) State assigned TO Agreement number;

8) State assigned (Blanket) Purchase Order number(s);

9) Goods or services provided;

10) Amount due; and

11) Any additional documentation required by regulation or the Task Order.

D. Invoices that contain both fixed price and labor items shall clearly identify the items as either fixed price or labor billing.

E. DoIT reserves the right to reduce or withhold payment in the event the TO Contractor does not provide it with all required deliverables within the time frame specified in the Task Order or otherwise breaches the terms and conditions of the Task Order until such time as the TO Contractor brings itself into full compliance.

F. The State is generally exempt from federal excise taxes, Maryland sales and use taxes, District of Columbia sales taxes and transportation taxes. The TO Contractor; however, are not exempt from such sales and use taxes and may be liable for the same.

G. Invoices for final payment shall be clearly marked as “FINAL” and submitted when all work requirements have been completed and no further charges are to be incurred under the TO Agreement. In no event shall any invoice be submitted later than 60 calendar days from the TO Agreement termination date.

3.3.3 Invoice Submission Schedule

The TO Contractor shall submit invoices within 30 days of the State certifying a milestone below as having been satisfactorily completed:

A. Agency Acceptance of Design: 15% B. Confirmed Delivery of Equipment to designated staging facility: 30% C. Installation of Equipment in the Field: 30% D. Acceptance of Testing of the system: 15% E. Final Acceptance of system and final documentation: 10%

3.3.4 For the purposes of this Task Order an amount will not be deemed due and payable if:

A. The amount invoiced is inconsistent with the Task Order.

B. The proper invoice has not been received by the party or office specified in the Task Order.

C. The invoice or performance is in dispute or the TO Contractor has failed to otherwise comply with the provisions of the Task Order.

RFP for the Department of Information Technology Page 18 of 72

D. The item or services have not been accepted.

E. The quantity of items delivered is less than the quantity ordered.

F. The items or services do not meet the quality requirements of the Task Order G. If the Work Order provides for progress payments, the proper invoice for the progress payment has not been submitted pursuant to the schedule.

H. If the Work Order provides for withholding a retainage and the invoice is for the retainage, all stipulated conditions for release of the retainage have not been met.

I. The TO Contractor has not submitted satisfactory documentation or other evidence reasonably required by the TO Procurement Officer concerning performance under the Contract and compliance with its provisions.

3.3.5 Travel Reimbursement

Travel will not be reimbursed under this TORFP.

3.3.6 Retainage

This solicitation does not require retainage.

3.4 Liquidated Damages

This solicitation does not require additional liquidated damages.

3.5 Insurance Requirements

3.5.1 Offeror shall confirm that, as of the date of its proposal, the insurance policies incorporated into its Master Contract are still current and effective at the required levels (See Master Contract Section 2.7).

3.6 Security Requirements

3.6.1 Employee Identification

A. TO Contractor Personnel shall display his or her company ID badge in a visible location at all times while on State premises. Upon request of authorized State personnel, each such TO Contractor Personnel shall provide additional photo identification.

B. TO Contractor Personnel shall cooperate with State site requirements, including but not limited to, being prepared to be escorted at all times, and providing information for State badge issuance.

C. TO Contractor shall remove any TO Contractor Personnel where the State determines, in its sole discretion, that said TO Contractor Personnel has not adhered to the Security requirements specified herein.

RFP for the Department of Information Technology Page 19 of 72

D. The State reserves the right to request that the TO Contractor submit proof of employment authorization of non-United States Citizens, prior to commencement of work under the Task Order or any Work Order.

E. Unless otherwise specified, the cost of complying with all security requirements specified herein are the sole responsibility and obligation of the TO Contractor and its subcontractors and no such costs shall be passed through to or reimbursed by the State or any of its agencies or units.

3.6.2 Security Clearance / Criminal Background Checks

A. The Contractor shall have a State and federal criminal background investigation performed for all Contractor employees, agents, and subcontractors performing services under the State contract prior to the commencement of any work under the State contract. This check may be performed by a public or private entity. The criminal background investigations will be conducted at the Contractor’s expense. Even if a criminal background investigation has been obtained pursuant to a prior agreement with the State, a new one shall be performed for each individual providing service under the State contract.

B. The Contractor has the responsibility of reporting to the State any positive criminal history of any Contractor employee, agent, or subcontractor as soon as this information becomes available. The Contractor shall perform annual updates on their criminal background investigation for all Contractor employees, agents, and subcontractors performing services under the State contract.

C. Persons with a criminal record may not perform services under this Contract unless prior written approval is obtained from the Contract Monitor. The Contract Monitor reserves the right to reject any individual based upon the results of the background check. Decisions of the Contract Monitor as to acceptability of a candidate are final. The State reserves the right to refuse any individual Contractor Personnel to work on State premises, based upon certain specified criminal convictions, as specified by the State.

D. The CJIS criminal record check of each Contractor Personnel who will work on State premises shall be reviewed by the Contractor for convictions of any of the following crimes described in the Annotated Code of Maryland, Criminal Law Article:

1) §§ 6-101 through 6-104, 6-201 through 6-205, 6-409 (various crimes against property);

2) any crime within Title 7, Subtitle 1 (various crimes involving theft);

3) §§ 7-301 through 7-303, 7-313 through 7-317 (various crimes involving telecommunications and electronics);

4) §§ 8-201 through 8-302, 8-501 through 8-523 (various crimes involving fraud);

5) §§9-101 through 9-417, 9-601 through 9-604, 9-701 through 9-706.1 (various crimes against public administration); or

6) a crime of violence as defined in CL § 14-101(a).

E. Contractor Personnel with access to systems supporting the State or to State data who have been convicted of a felony or of a crime involving telecommunications and electronics from the above list of crimes shall not be permitted to work on State premises under this Contract;

RFP for the Department of Information Technology Page 20 of 72

Contractor Personnel who have been convicted within the past five (5) years of a misdemeanor from the above list of crimes shall not be permitted to work on State premises.

F. A particular on-site location covered by this Contract may require more restrictive conditions regarding the nature of prior criminal convictions that would result in Contractor Personnel not being permitted to work on those premises. Upon receipt of a location’s more restrictive conditions regarding criminal convictions, the Contractor shall provide an updated certification regarding the Contractor Personnel working at or assigned to those premises.

3.6.3 On-Site Security Requirement(s)

A. For the conditions noted below, TO Contractor Personnel may be barred from entrance or leaving any site until such time that the State’s conditions and queries are satisfied.

1) TO Contractor Personnel may be subject to random security checks when entering and leaving State secured areas. The State reserves the right to require TO Contractor Personnel to be accompanied while in secured premises.

2) Some State sites, especially those premises of the Department of Public Safety and Correctional Services, require each person entering the premises to document and inventory items (such as tools and equipment) being brought onto the site, and to submit to a physical search of his or her person. Therefore, TO Contractor Personnel shall always have available an inventory list of tools being brought onto a site and be prepared to present the inventory list to the State staff or an officer upon arrival for review, as well as present the tools or equipment for inspection. Before leaving the site, the TO Contractor Personnel will again present the inventory list and the tools or equipment for inspection. Upon both entering the site and leaving the site, State staff or a correctional or police officer may search TO Contractor Personnel. Depending upon facility rules, specific tools or personal items may be prohibited from being brought into the facility.

B. Contractor Personnel shall display his or her company ID badge in a visible location at all times while on State premises. Upon request of authorized State personnel, each such Contractor Personnel shall provide additional photo identification.

C. Contractor Personnel shall cooperate with State site requirements, including but not limited to, being prepared to be escorted at all times, and providing information for State badge issuance.

D. Contractor shall remove any Contractor Personnel from working on the Contract where the State determines, in its sole discretion, said Contractor Personnel has not adhered to the Security requirements specified herein.

E. The State reserves the right to request that the Contractor submit proof of employment authorization of non-United States Citizens, prior to commencement of work under the Contract. Any TO Contractor Personnel who enters the premises of a facility under the jurisdiction of DoIT may be searched, fingerprinted (for the purpose of a criminal history background check), photographed and required to wear an identification card issued by DoIT.

RFP for the Department of Information Technology Page 21 of 72

F. Further, TO Contractor Personnel shall not violate Md. Code Ann., Criminal Law Art.

Section 9-410 through 9-417 and such other security policies of the agency that controls the facility to which the TO Contractor Personnel seeks access. The failure of any of the TO Contractor Personnel to comply with any provision of the TO Agreement is sufficient grounds for the State to immediately terminate the TO Agreement for default.

3.7 RESERVED

3.8 SOC 2 Type 2 Audit Report

A SOC 2 Type 2 Report is not a TO Contractor requirement for this TO Agreement.

3.9 Performance and Personnel

3.9.1 ROLES AND RESPONSIBILITIES

Personnel roles and responsibilities under the Task Order:

A. TO Procurement Officer – The TO Procurement Officer has the primary responsibility for the management of the TORFP process, for the resolution of TO Agreement scope issues, and for authorizing any changes to the TO Agreement.

B. TO Manager - The TO Manager has the primary responsibility for the management of the work performed under the TO Agreement, administrative functions, including issuing written directions, and for ensuring compliance with the terms and conditions of the CATS+ Master Contract.

The TO Manager will be responsible for providing the scope of work in each Work Order, assign tasks to the personnel provided under this TORFP and will track and monitor the work being performed through the monthly accounting of hours’ deliverable for work types; actual work produced will be reconciled with the hours reported.

C. TO Contractor – The TO Contractor is the CATS+ Master Contractor awarded this Order.

The TO Contractor shall provide human resources as necessary to perform the services described in this TORFP Scope of Work.

D. TO Contractor Manager – The TO Contractor Manager will serve as primary point of contact with the TO Manager to regularly discuss progress of tasks, upcoming tasking, historical performance, and resolution of any issues that may arise pertaining to the TO Contractor Personnel. The TO Contractor Manager will serve as liaison between the TO Manager and the senior TO Contractor management.

E. TO Contractor Personnel – Any official, employee, agent, Subcontractor, or Subcontractor agents of the TO Contractor who is involved with the Task Order over the course of the Task Order period of performance.

F. Key Personnel – A subset of TO Contractor Personnel whose departure during the performance period, will, in the State’s opinion, have a substantial negative impact on Task Order performance. Key Personnel proposed as part of the TO Proposal shall start as of Work Order issuance.

RFP for the Department of Information Technology Page 22 of 72

3.9.2 Offeror Experience

The following experience is expected and will be evaluated as part of the TO Technical Proposal (see the Offeror experience, capability and references evaluation factor from Section 6.2):

A. Demonstrated knowledge of design and installation of in-building radio antenna systems through supplied references from at least two (2) projects of similar scope. References shall include:

1) Name and location of the project

2) Scope of project

3) The project point of contact should include the name, title, email address, and phone number.

3.10 Substitution of Personnel

3.10.1 Directed Personnel Replacement

A. The TO Manager may direct the TO Contractor to replace any TO Contractor Personnel who, in the sole discretion of the TO Manager, are perceived as being unqualified, non-productive, unable to fully perform the job duties, disruptive, or known, or reasonably believed, to have committed a major infraction(s) of law or DoIT Policy or any Contract or Task Order requirement.

B. If deemed appropriate in the discretion of the TO Manager, the TO Manager shall give written notice of any TO Contractor Personnel performance issues to the TO Contractor, describing the problem and delineating the remediation requirement(s). The TO Contractor shall provide a written Remediation Plan within three (3) days of the date of the notice. If the TO Manager rejects the Remediation Plan, the TO Contractor shall revise and resubmit the plan to the TO Manager within five (5) days of the rejection, or in the timeframe set forth by the TO Manager in writing. Once a Remediation Plan has been accepted in writing by the TO Manager, the TO Contractor shall immediately implement the Remediation Plan.

C. Should performance issues persist despite the approved Remediation Plan, the TO Manager will give written notice of the continuing performance issues and either request a new Remediation Plan within a specified time limit or direct the removal and replacement of the TO Contractor Personnel whose performance is at issue. A request for a new Remediation Plan will follow the procedure described in Section 3.11.1.B.

D. In circumstances of directed removal, the TO Contractor shall provide a suitable replacement for TO Manager approval within fifteen (15) days of the date of the notification of directed removal, or the actual removal, whichever occurs first, or such earlier time as directed by the TO Manager in the event of a removal on less than fifteen days’ notice

E. Normally, a directed personnel replacement will occur only after prior notification of problems with requested remediation, as described above. However, the TO Manager reserves the right to direct immediate personnel replacement without utilizing the remediation procedure described above.

F. Replacement or substitution of TO Contractor Personnel under this section shall be in addition to, and not in lieu of, the State’s remedies under the Task Order or which otherwise may be available at law or in equity.

RFP for the Department of Information Technology Page 23 of 72

3.10.2 Substitution Prior to and 30 Days After Task Order Execution A. Prior to TO Agreement Execution or within thirty (30) days after TO Agreement Execution, the Offeror may substitute proposed Key Personnel only under the following circumstances:

vacancy occurs due to the sudden termination, resignation, or approved leave of absence due to an Extraordinary Personnel Event, or death of such personnel. To qualify for such substitution, the Offeror must describe to the State's satisfaction the event necessitating substitution and must demonstrate that the originally proposed personnel are actual full-time direct employees with the Offeror (subcontractors, temporary staff or 1099 contractors do not qualify). Proposed substitutions shall be of equal caliber or higher, in the State's sole discretion. Proposed substitutes deemed by the State to be less qualified than the originally proposed individual may be grounds for pre-award disqualification or post-award termination.

B. An Extraordinary Personnel Event – means leave under the Family Medical Leave Act; an incapacitating injury or incapacitating illness; or other circumstances that in the sole discretion of the State warrant an extended leave of absence, such as extended jury duty or extended military service.

3.10.3 Substitution More Than 30 Days After TO Agreement Execution The procedure for substituting personnel after TO Agreement execution is as follows:

A. The TO Contractor may not substitute personnel without the prior approval of the TO Manager.

B. To replace any personnel, the TO Contractor shall submit resumes of the proposed individual specifying the intended approved labor category. Any proposed substitute personnel shall have qualifications equal to or better than those of the replaced personnel.

C. Proposed substitute individual shall be approved by the TO Manager. The TO Manager shall have the option to interview the proposed substitute personnel and may require that such interviews be in person. After the interview, the TO Manager shall notify the TO Contractor of acceptance or denial of the requested substitution. If no acceptable substitute personnel is proposed within the time frame established by the TO Manager, the TO Agreement may be cancelled.

3.11 Minority Business Enterprise (MBE) Reports

There is no MBE Participation Goal for this Task Order.

3.12 Veteran Small Business Enterprise (VSBE) Reports

There is no VSBE Goal for this Task Order.

3.13 Work Orders

This section is not applicable to this TORFP.

3.13.1 TORFP Subject to CATS+ Master Contract

In addition to the requirements of this TORFP, the Master Contractors are subject to all terms and conditions of the Master Contract.

RFP for the Department of Information Technology Page 24 of 72

By responding to this TORFP and accepting a Task Order award, an Offeror specifically agrees that for any software, hardware or hosting service that it proposes for use by the State in response to this TORFP, the State will have the right to purchase from another source, instead of from the selected Offeror.

3.13.2 All times specified in this document are local time, defined as Eastern Standard Time or Eastern Daylight Time, whichever is in effect.

3.13.3 Contract Management Oversight Activities

A. DoIT is responsible for contract management oversight on the CATS+ Master Contract. As part of that oversight, DoIT has implemented a process for self-reporting contract management activities of Task Orders under CATS+. This process typically applies to active TOs for operations and maintenance services valued at $1 million or greater, but all CATS+ Task Orders are subject to review.

3.13.4 Source Code Escrow

Source code Escrow does not apply to this Task Order.

3.13.5 Purchasing and Recycling Electronic Products

This section does not apply to this solicitation.

3.13.6 Change Control and Advance Notice

A. Unless otherwise specified in an applicable Service Level Agreement, the Contractor shall give seven (7) days advance notice to the State of any upgrades or modifications that may impact service availability and performance.

B. Contractor may not modify the functionality or features of any SaaS provided hereunder if such modification materially degrades the functionality of the SaaS.

3.13.7 No-Cost Extensions

This section does not apply to this solicitation.

RFP for the Department of Information Technology Page 25 of 72

4 TORFP Instructions

4.1 TO Pre-Proposal Site Visit

A pre-proposal site visit will be held at the time, date and location indicated on the Key Information Summary Sheet. Attendance at the pre-proposal site visit is not mandatory, but all Master Contractors are encouraged to attend in order to facilitate better preparation of their proposals.

The pre-proposal site visit will be summarized in writing. As promptly, as is feasible, subsequent to the pre-proposal site visit, the attendance record and pre-proposal site visit summary will be distributed via e- mail to all Master Contractors known to have received a copy of this TORFP.

In order to assure adequate accommodations at the pre-proposal site visit, please e-mail the TO Procurement Officer no later than three (3) business days prior indicating planned attendance. In addition, if there is a need for sign language interpretation and/or other special accommodation due to a disability, please contact the TO Procurement Officer no later than five (5) business days prior to the pre-proposal site visit. The TO Requesting Agency will make reasonable efforts to provide such special accommodation.

4.2 Questions

4.2.1 All questions shall identify in the subject line the Solicitation Number and Title BPM057440 Maryland FiRST Project – BWI HVAC UPGRADE) and shall be submitted in writing via e-mail to the TO Procurement Officer no later than the date and time specified the Key Information Summary Sheet.

4.2.2 Answers to all questions that are not clearly specific only to the requestor will be provided to all Master Contractors who are known to have received a copy of the TORFP.

4.2.3 The statements and interpretations contained in responses to any questions, whether responded to verbally or in writing, are not binding on DoIT unless it issues an amendment in writing.

4.3 TO Proposal Due (Closing) Date and Time

4.3.1 TO Proposals, in the number and form set forth in Section 5 TO Proposal Format, must be received by the TO Procurement Officer no later than the TO Proposal due date and time indicated on the Key Information Summary Sheet in order to be considered.

4.3.2 Requests for extension of this date or time shall not be granted.

4.3.3 Offerors submitting TO Proposals should allow sufficient delivery time to ensure timely receipt by the TO Procurement Officer. Except as provided in COMAR 21.05.03.02.F and 21.05.02.10, TO Proposals received after the due date and time listed in the Key Information Summary Sheet will not be considered.

RFP for the Department of Information Technology Page 26 of 72

4.3.4 The date and time of an email submission is determined by the date and time of arrival in the Procurement Officer’s email address indicated on the Key Information Summary Sheet.

4.3.5 TO Proposals may be modified or withdrawn by written notice received by the TO Procurement Officer before the time and date set forth in the Key Information Summary Sheet for receipt of TO Proposals.

4.4 Award Basis

Based upon an evaluation of TO Proposal responses as provided in Section 6.2, below, one (1) Master Contractor will be selected for award. A specific TO Agreement, Attachment M, will then be entered into between the State and the selected Master Contractors, which will bind the selected Master Contractors (each a TO Contractor) to the contents of its TO Proposal, including the TO Financial Proposal.

4.5 Oral Presentation

4.5.1 Master Contractors and proposed TO Contractor Personnel may be required to make an oral presentation to and be interviewed by State representatives. Master Contractors must confirm in writing any substantive oral clarification of, or change in, their Proposals made in the course of discussions. Any such written clarifications or changes then become part of the Master Contractor’s TO Proposal.

4.5.2 The TO Procurement Officer will notify Master Contractors of the time and place of oral presentations and interviews, should interviews be scheduled.

4.6 Limitation of Liability

The TO Contractor’s liability is limited in accordance with the Limitations of Liability section of the CATS+ Master Contract. TO Contractor’s liability for this TORFP is limited to two (2) times the total TO Agreement amount.

4.7 MBE Participation Goal

There is no MBE Participation Goal for this Task Order.

4.8 VSBE Goal

There is no VSBE Goal for this Task Order.

4.9 Living Wage Requirements

The Master Contractor shall abide by the Living Wage requirements under Title 18, State Finance and Procurement Article, Annotated Code of Maryland and the regulations proposed by the Commissioner of Labor and Industry.

All TO Proposals shall be accompanied by a completed Living Wage Affidavit of Agreement, Attachment F of this TORFP.

4.10 Federal Funding Acknowledgement

This Task Order does not contain Federal funds.

RFP for the Department of Information Technology Page 27 of 72

4.11 Conflict of Interest Affidavit and Disclosure

4.11.1 Offerors shall complete and sign the Conflict of Interest Affidavit and Disclosure (Attachment H) and submit it with their Proposals. All Offerors are advised that if a TO Agreement is awarded as a result of this solicitation, the TO Contractor’s Personnel who perform or control work under this TO Agreement and each of the participating subcontractor personnel who perform or control work under this TO Agreement shall be required to complete agreements substantially similar to Attachment H, conflict of interest Affidavit and Disclosure.

4.11.2 If the TO Procurement Officer makes a determination that facts or circumstances exist that give rise to or could in the future give rise to a conflict of interest within the meaning of COMAR 21.05.08.08A, the TO Procurement Officer may reject an Offeror’s TO Proposal under COMAR 21.06.02.03B.

4.11.3 Master Contractors should be aware that the State Ethics Law, Md. Code Ann., General Provisions Article, Title 5, might limit the selected Master Contractor's ability to participate in future related procurements, depending upon specific circumstances.

4.11…