FC-192-26 PORFP The Cruise Maryland Terminal Building.pdf

RADIO COMMUNICATIONS 2018 MASTER CONTRACT

PRICE REQUEST FOR PROPOSALS (PORFP)

MARYLAND

DEPARTMENT OF INFORMATION TECHNOLOGY

SOLICITATION NUMBER:

BPM058271

MARYLAND FIRST COVERAGE IMPROVEMENT PROGRAM

IN-BUILDING SYSTEMS

CRUISE MARYLAND TERMINAL BUILDING

BALTIMORE, MARYLAND

ISSUE DATE:

August 11, 2026

Maryland FiRST Coverage Improvement Program – In Building Systems Solicitation #: BPM058271 Radio Communications Master

MARYLAND DEPARTMENT OF INFORMATION TECHNOLOGY (DOIT )

KEY INFORMATION SUMMARY SHEET

Solicitation Title: Maryland FiRST Coverage Improvement Program – In-Building Systems

Solicitation Number

(PORFP#):

BPM058271

Functional Area: FA 1 & FA IV: Two-Way Radio Equipment

PORFP Issue Date: August 11, 2026

PORFP Issuing Office: Maryland Department of Information Technology (“DoIT or "the Agency")

DoIT Location: 100 Community Place Crownsville, MD 21032

TO Procurement Officer: Cherise Edmonds 100 Community Place e-mail:

cherise.edmonds@maryland.gov

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

PORFP Proposals are to be sent to:

https://emma.maryland.gov/page.aspx/en/usr/login (eMMA)

Site Visit: August 17, 2026, at 10:00 am est 2001 E. McComas Street, Baltimore, MD 21230.

See Attachment A for directions and instructions.

PORFP Proposals Due (Closing) Date and Time: September 22, 2026 @ 10:00 am 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: 0%

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 mailto:cherise.edmonds@maryland.gov mailto:Jennifer.Zambito@maryland.gov https://emma.maryland.gov/page.aspx/en/usr/login https://emma.maryland.gov/page.aspx/en/usr/login

Primary Place of Performance:

The Cruise Maryland Terminal 2001 E. McComas St.

Baltimore, MD 21230

SBR Designation: No

SBP Designation: Yes

Federal Funding: No

Questions Due Date and Time August 24, 2026, at 2:00 pm est

TABLE OF CONTENTS – PORFP

1 Minimum Qualifications 6

1.1 Offeror Minimum Qualifications 6

2 TO Contractor Requirements: Scope of Work 7

2.1 Summary Statement 7

2.2 Background and Purpose 7

2.3 Responsibilities and Tasks 7

2.4 Deliverables 12

2.5 Service Level Agreement (SLA) 14

3 TO Contractor Requirements: General 15

3.1 Task Order Initiation Requirements 15

3.2 End of Task Order Transition 15

3.3 Invoicing 17

3.4 Liquidated Damages 19

3.5 Insurance Requirements 19

3.6 Security Requirements 19

3.7 RESERVED 21

3.8 SOC 2 Type 2 Audit Report 21

3.9 PERFORMANCE AND PERSONNEL 21

3.10 Substitution of Personnel 22

3.11 Minority Business Enterprise (MBE) Reports 23

3.12 Veteran Small Business Enterprise (VSBE) Reports 23

3.13 Work Orders 23

3.14 Additional Clauses 23

3.15 TO Pre-Proposal Conference 25

3.16 Questions 25

3.17 PORFP Proposal Due (Closing) Date and Time 25

3.18 Award Basis 26

3.19 Oral Presentation 26

3.20 MBE Participation Goal 26

3.21 VSBE Goal 26

3.22 Living Wage Requirements 26

3.23 Federal Funding Acknowledgement 26

3.24 Conflict of Interest Affidavit and Disclosure 26

3.25 Non-Disclosure Agreement 26

3.26 HIPAA - Business Associate Agreement 26

3.27 Iranian Non-Investment 26

3.28 Mercury and Products That Contain Mercury 26

3.29 Location of the Performance of Services Disclosure 26

3.30 Department of Human Services (DHS) Hiring Agreement 26

3.31 Small Business Reserve (SBR) Set-Aside 26

3.32 Bonds 27

PORFP Proposal Format 28

4.1 Required Response 28

4.2 Two Part Submission 28

4.3 TO Proposal Packaging and Delivery 28

4.4 Volume I - TO Technical Proposal 29

4.5 Volume II – TO Financial Proposal 31

5 Evaluation and Selection Process 33

5.1 Evaluation Committee 33

5.2 TO Technical Proposal Evaluation Criteria 33

5.3 TO Financial Proposal Evaluation Criteria 33

5.4 Selection Procedures 33

5.5 Documents Required upon Notice of Recommendation for Task Order Award 34

6 PORFP ATTACHMENTS AND APPENDICES 35

1 Minimum Qualifications

1.1 Offeror Minimum Qualifications

There are no minimum qualifications.

THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.

2 TO Contractor Requirements: Scope of Work

2.1 Summary Statement

2.1.1 The Maryland Department of Information Technology (“DoIT” or "the Agency") is issuing this

Radio Communications 2018 Master Contract PORFP to procure a contractor to install an In- Building Antenna/Amplifier system at The Cruise Maryland Terminal building, 2001 E.

McComas St. Baltimore, MD 21230.

2.1.2 A Task Order (TO) award is not a guarantee that the TO Contractor will receive any or all State business under the Task Order.

2.2 Background and Purpose

2.2.1 Overview

Maryland First Responder Radio System Team (MD FiRST) is a State-Wide, P25 Phase 2, Motorola trunked radio system that supports Maryland's State, local, and federal first responders. MD FiRST uses multiple 700 MHz radio frequencies and was constructed state-wide to provide outdoor, portable radio coverage. The Cruise Maryland Terminal is a primary user of the MD FiRST system.

Locations within the Cruise Maryland Terminal have been identified that require higher levels of coverage (e.g., critical facilities requiring in-building service). The in-building solution proposed in response to this PORFP will correct radio coverage inefficiencies.

2.2.2 Current Situation

During preliminary signal testing inside The Cruise Maryland Terminal, significant attenuation was observed, with levels of -110 dBm or lower recorded at multiple interior locations. Further investigations identified a nearby multi-carrier site operating on Bands 13 and 14 as the source of interference. Band 14, which lies adjacent to the MD FiRST 769 MHz spectrum, caused detectable interference in the lower 769 MHz range. Field tests using a tactical/deployable BDA successfully improved in-building coverage and reduced interference and dropped calls. The Cruise Maryland Terminal, owned and operated by the Maryland Port Administration (MPA), spans approximately 65,880 square feet and includes a large open operations area, warehouse space for cargo and luggage handling, and partitioned offices for management and security.

This Price Request for Proposals (PORFP) seeks a TO Contractor to design, furnish, and install a Bi- Directional Amplifier (BDA) system to mitigate interference and enhance radio coverage throughout the facility.

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 Cruise Maryland Terminal to ensure all work is completed in accordance with 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 Responsibilities and Tasks

2.3.1 Design

1. The State requires a public safety Land Mobile Radio (LMR) grade In-Building system. The TO Contractor shall design an In-Building Antenna/Amplifier system that covers the existing interior spaces and includes a channelized Bi-Directional Amplifier (BDA), donor antennas, and a Distributed Antenna System designed to capture and rebroadcast MD FiRST 700 MHz public safety channels.

2. The In-Building system shall comply with National Fire Protection Association (NFPA) 1, Fire Code, 2018 Edition (NFPA1-2018) as its Fire Code, NFPA 101, Life Safety Code, 2018 Edition (NFPA1012018) as its Life Safety Code, and NFPA 1221, Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems, 2016 Edition (NFPA1221-2016) as its standard for Communications Enhancement Systems. NFPA1-2018 and NFPA101-2018 provide reliable public safety radio system coverage in occupancies, and NFPA1221-2016 provides requirements for the design, installation, and maintenance of communications enhancements systems.

3. Specific Planning Information for LMR design/equipment:

a) Inbound signal strength - A minimum inbound signal strength of -90 dBm shall be provided outside the BDA location building for the MD FiRST system.

b) Outbound signal strength - A minimum outbound signal strength of -90 dBm shall be provided outside the BDA location building for the MD FiRST system.

c) Balanced uplink/downlink path operation - All passive and active components used in the Bi-Directional Amplifier / Distributed Antenna System (BDA/DAS) shall provide equal uplink/downlink levels of insertion loss, passive gain, or active gain.

d) Voice audio quality - A minimum voice audio quality of Delivered Audio Quality (DAQ) 3.4 shall be provided throughout the building for the MD FiRST system.

DAQ 3.4 is “Speech understandable without repetition, some noise/distortion present.”

e) Coverage reliability in critical areas - Fire command centers, fire alarm control panel locations, fire pump rooms, exit stairs, exit passageways, elevators, elevator lobbies, standpipe cabinets, sprinkler valve locations, areas of refuge, and other areas deemed critical by the State shall be provided with 99% floor area reliability coverage for the MD FiRST system.

f) Coverage reliability in general building areas—All other interior levels and areas of the building not defined as critical shall have 90% floor area reliability coverage for the MD FiRST system. Due to their type, several rooms in the building (courtrooms, library) will potentially require non-conventional antenna installations.

g) Degradation of Donor Site Sensitivity Not Permissible – System design/operation must not cause any degradation to the MD FiRST donor Radio Frequency (RF) Sites.

h) The In-Building system must provide a means of remote monitoring and the ability to send alarm messages but making that connection is outside the Scope of Work.

TO Contractor shall provide a list of alarms that can be connected.

2.3.2 Installation

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

Please Note:

1. Due to the nature of business in this building, work may be required after regular business hours.

2. The work, design and installation, shall be completed within 180 working days from Notice to Proceed.

3. All work must be coordinated daily and confirmed with the State Project Manager, The Cruise Maryland Terminal, and the MD FiRST team.

2.3.3 Optimization and Testing

The TO Contractor shall:

A. Optimize the installed In-Building LMR antenna/amplifier system to show no degradation of the MD FiRST radio system.

B. Conduct 700 MHz grid testing per NFPA 1221 2016 A.11.3. Each floor of the building shall be gridded according to the requirements of A.11.3.9 (20’-80’ grids depending on floor area to be tested, at least 20 grid cells) and the downlink signal strength and roundtrip DAQ from the center of each grid must be measured and recorded. The TO Manager/Team will participate in a final round of coverage testing to validate the TO Contractor results.

C. Critical areas (fire command centers, fire alarm control panel locations, fire pump rooms, exit stairs, exit passageways, elevators, elevator lobbies, standpipe cabinets, sprinkler valve locations, areas of refuge, and other areas deemed critical by the State) must pass with 99% area reliability.

D. Other general areas of occupancy must pass with 90% area reliability. To pass, a grid must exhibit 3.4 or greater DAQ and -90 dBm or greater downlink Received Signal Strength Indicator (RSSI). DAQ ratings shall be according to the following:

a) DAQ 1: Unusable; speech present but unreadable,

b) DAQ 2: Understandable with considerable effort; frequent repetition due to noise/distortion,

c) DAQ 3: Speech understandable with slight effort; occasional repetition required due to noise/distortion,

d) DAQ 3.4: Speech understandable with repetition only rarely required; some noise/distortion,

e) DAQ 4: Speech easily understood; occasional noise/distortion,

f) DAQ 4.5: Speech easily understood; infrequent noise/distortion, and

g) DAQ 5: Speech easily understood.

E. System Reliability Testing – The TO Contractor shall measure and record the RF noise floor at the location of the external antenna before the system is activated. Degradation/Interference is defined as an increase in the noise floor due to the system's activation. The TO Contractor will coordinate with the appointed state of MD representative prior to activating the BDA to ensure the noise floor is not raised.

F. After the successful completion of coverage testing in the building, a 30-day acceptance period will begin to ensure that the system is performing as designed and that there is no degradation or interference to the MD FiRST system due to the activation of the BDA/DAS system. Final acceptance of the system is conditioned upon the successful completion of these 30 days with no reported degradation of the MD FiRST system.

2.3.4 Training

The TO Contractor shall:

Provide training to MD FiRST and MPA personnel to perform first-level equipment and software troubleshooting and understand the operation of the equipment and system. Provide complete documentation of all equipment installed, including as-built drawings.

2.3.5 Warranty & Maintenance

The TO Contractor shall provide 2 years of maintenance/warranty services for the installed In- Building antenna/amplifier system, commencing at the final acceptance of the system. (See Maintenance and Support 2.3.10).

2.3.6 Permits

The TO Contractor is responsible for determining and obtaining all permits necessary to perform the work outlined in this solicitation. The TO Contractor shall coordinate all In-Building System approvals with the MPA Office of Information Technology.

2.3.7 TO Contractor-Supplied Hardware, Software, and Materials

A. The TO Contractor is responsible for acquiring and operating all new hardware, software, and network support related to the services being provided and shall keep all software current.

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

C. Material costs shall be passed through with no mark-up by the TO Contractor.

D. The Offeror shall provide a manufacturer or provider’s standard warranty for each item it supplies. Any warranty period for goods and services will not commence until the Agency accepts the products or services. Notwithstanding anything to the contrary, all defective items must be replaced at no additional cost to the State.

2.3.8 Required Project Policies, Guidelines and Methodologies

The 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 State of Maryland System Development Life Cycle (SDLC) methodology at:

www.DoIT .maryland.gov - keyword: SDLC;

B. The State of Maryland Information Technology Security Policy and Standards at www.DoIT .maryland.gov - keyword: Security Policy;

C. The State of Maryland Information Technology Non-Visual Standards at http://DoIT .maryland.gov/policies/Pages/ContractPolicies.aspx.

2.3.9 Product Requirements

A. The Offeror must provide operational support for any software proposed as part of its PORFP Proposal.

B. 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 (See PORFP Section 5.4.2.J.2.)

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

2.3.10 Maintenance and Support

Maintenance and support, and TO Contractor’s ongoing maintenance and support obligations, are defined as follows:

A. Maintenance commences at the final acceptance of the system.

B. Software maintenance includes all future software updates and system enhancements within two (2) years.

C. For the two (2) year period commencing upon the final acceptance date, the following services shall be provided for the current version and one previous version of any Software provided hereunder,.

1) Error Correction. Upon the State's notice of a problem with the Software (which can be verified), reasonable efforts must be made to correct it or provide a working solution.

2) Material Defects. TO Contractor shall notify the State of any material errors or defects in the Deliverables known or made known to the TO Contractor from any source during the life of the Task Order that could cause the production of inaccurate or otherwise materially incorrect results. The TO Contractor shall initiate actions as may be commercially necessary or proper to effect corrections of any such errors or defects.

3) Updates. TO Contractor will provide to the State at no additional charge all new releases and bug fixes (collectively referred to as “Updates”) for any software Deliverable developed or published by the TO Contractor and made available to its other customers.

http://doit.maryland.gov/policies/Pages/ContractPolicies.aspx

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.

2.4.2 Deliverable Acceptance

A. A final deliverable shall satisfy the scope and requirements of this PORFP 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.

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.

The table below details deliverables due hereunder and their due date(s).

Deliverable Due Date Acceptance Criteria

1. Final Design Document 45 working days from

NTP

Acceptance at Customer Design Review

(CDR)

2. Draft Coverage Test Plan 60 working days from

CDR

Acceptance after review of State

3. Draft Final Acceptance Test Plan (FATP)

10 working days from anticipated date of

FATP

The State will review the draft plan for completeness and either accept it as final or return to TO Contractor for revision. It will be considered accepted when the State approves it as Final.

4. Final Acceptance Walk and Documentation

20 working days from the close of the 30-day burn-in test.

Acceptance after:

• All As-Built documentation, System Equipment Documentation Coverage testing results, and 30-day test results have been completed, submitted and given final approval

• The State team tours the facility with the TO Contractor to verify general installation workmanship, spot check coverage testing results and finalize a punch list.

2.5 Service Level Agreement (SLA)

THIS SECTION IS NOT APPLICABLE TO THIS PORFP.

3 TO Contractor Requirements: General

3.1 Task Order Initiation Requirements

The 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:

1. Introductions of TO Contractor project team, and

2. Baseline project schedule

3.2 End of Task Order Transition

3.2.1 The TO Contractor shall work toward a prompt and timely transition, proceeding in accordance with the directions of the TO Manager. The TO Manager may provide the TO Contractor with additional instructions to meet specific transition requirements before the end of the Task Order.

3.2.2 The TO Contractor shall ensure that all necessary knowledge and materials for the tasks completed are transferred to the custody of State personnel or a third party, as directed by the TO Manager.

3.2.3 TO Contractor shall support end-of-task order transition efforts with technical and project support to include but not be limited to:

A. For 30 days following final system acceptance, the TO contractor shall assist the TO manager with the following:

1) Any staffing concerns/issues related to the closeout of the Task Order;

2) Communications and reporting process between the TO Contractor, the Agency, and the TO Manager;

3) Security and system access review and closeout;

4) Any hardware/software inventory or licensing, including transfer of any point of contact for required software licenses to the Agency or a designee;

5) Any final training/orientation of the Agency staff;

6) Connectivity services provided, activities, and approximate timelines required for Transition-Out;

7) Knowledge transfer, to include:

a) A working knowledge of the current system environments as well as the general business practices of the Agency;

b) Review with the Agency the procedures and practices that support the business process and current system environments;

c) Working knowledge of all technical and functional matters associated with the Solution, its architecture, data file structure, interfaces, any batch programs, and any hardware or software tools utilized in the performance of this Task Order;

d) Documentation that lists and describes all hardware and software tools utilized in the performance of this Task Order;

e) A working knowledge of various utilities and corollary software products used in support and operation of the Solution;

8) Plans to complete tasks and any unfinished work items (including open change requests and known bugs/issues) and

9) Any risk factors with the timing, transition-out schedule, and transition process. The TO Contractor shall document any risk factors and suggested solutions.

B. The TO Contractor shall ensure all documentation and data, including, but not limited to, System Documentation and current operating procedures, is current and complete with a hard and soft copy in a format prescribed by the TO Manager.

C. Access to any data or configurations of the furnished product and/or services shall be available after the expiration of the Task Order as described in Section 3.2.5.

3.2.4 Return and Maintenance of State Data

A. Upon termination or the expiration of the TO Agreement term, the TO Contractor shall: (a) return to the State all State data in either the form it was provided to the TO Contractor or in a mutually agreed format along with the schema necessary to read such data; (b) preserve, maintain, and protect all State data until the earlier of a direction by the State to delete such data or the expiration of 90 days (“the retention period”) from the date of termination or expiration of the TO Agreement term; (c) after the retention period, the TO Contractor shall securely dispose of and permanently delete all State data in all of its forms, such as disk, CD/DVD, backup tape and paper such that it is not recoverable, according to National Institute of Standards and Technology (NIST)-approved methods with certificates of destruction to be provided to the State; and (d) prepare an accurate accounting from which the State may reconcile all outstanding accounts. The final monthly invoice for the services provided hereunder shall include all charges for the 90-day data retention period.

B. During any period of service suspension, the TO Contractor shall maintain all State data in their then-existing form unless otherwise directed in writing by the TO Manager.

C. In addition to the preceding, the State shall be entitled to any post-termination/expiration assistance generally made available by the TO Contractor concerning the services.

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.

B. “Late Payment” means any amount 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 established in the Radio Communications 2018 Master Contract.

B. The TO Contractor shall e-mail each invoice to the TO Manager with a cc to the DoIT Fiscal

Service Invoice email address at doitfiscal.invoiceservice@maryland.gov.

C. The TO Contractor shall verify all service invoices are accurate at the time of submission.

D. 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 name and address;

2) Remittance address;

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

4) Invoice period (i.e., 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.

E. Invoices containing fixed-price and time-and-material items shall identify the items as either fixed-price or time-and-material billing.

F. The Agency reserves the right to reduce or withhold Task Order payment in the event the TO Contractor does not provide the Agency 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 the TO Contractor brings itself into full compliance with the Task Order.

G. Any action on the part of the Agency, or dispute of action by the TO Contractor, shall be in accordance with the provisions of Md. Code Ann., State Finance and Procurement Article §§ 15-215 through 15-223 and with COMAR 21.10.04.

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

I. Invoices for final payment shall be marked as “FINAL” and submitted when all work requirements have been completed, and no further charges are to be incurred under the TO Agreement. No invoice shall 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:

1) Agency Acceptance of Design: 15%

2) Confirmed Delivery of Equipment to designated staging facility: 30%

3) Installation of Equipment in the Field: 30% mailto:doitfiscal.invoiceservice@maryland.gov

4) Acceptance of Coverage Testing of building: 15%

5) Final Acceptance of system and final documentation: 10%

3.3.4 Deliverable Invoicing

This section does not apply.

3.3.5 For 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.

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 Task Order provides for progress payments, the proper invoice for the progress payment has not been submitted pursuant to the schedule.

H. If the Task Order provides for withholding a retainage and the invoice is for the retainage, all stipulated conditions for releasing 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 or the contract concerning performance under the contract and compliance with its provisions.

3.3.6 Travel Reimbursement

Travel will not be reimbursed under this PORFP.

3.3.7 Retainage

This solicitation does not require retainage.

3.4 Liquidated Damages

This solicitation does not include liquidated damages.

3.5 Insurance Requirements

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).

The Offeror shall also confirm that any insurance policies intended to satisfy the requirements of this PORFP are issued by a company licensed to do business in the State of Maryland.

The recommended awardee must provide a certificate(s) of insurance with the prescribed coverages, limits, and requirements outlined in this Section 3.5 “Insurance Requirements” within five (5) Business Days from notice of recommended award. During the performance period for multi-year contracts, the TO Contractor shall update certificates of insurance annually or otherwise directed by the TO Manager.

In addition to the insurance requirement specified above, the TO Contractor is required to adhere to the MPA-specific insurance requirements contained in Attachment AA.

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 the job site. 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 from working on the Task Order where the State determines, in its sole discretion, that said TO Contractor Personnel has not adhered to the Security requirements specified herein.

D. The State reserves the right to request that the TO Contractor submit proof of employment authorization for non-United States Citizens before the commencement of work under the Task Order.

E. Unless otherwise specified, the cost of complying with all security requirements specified herein is the sole responsibility and obligation of the TO Contractor and its subcontractors. No such costs/fees 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 TO Contractor shall obtain from all Contractor Personnel assigned to work on the Task Order a signed statement permitting a criminal background check. Before commencement of work, the TO Contractor shall secure at its own expense the following type of national criminal history record check and provide the TO Contract Manager with completed checks on such Contractor Personnel before assignment:

B. A national criminal history record check. A public or private entity may perform this check.

C. These background checks must include all convictions and probation before judgment (PBJ) dispositions. The TO Contractor may not assign an individual whose background check reflects any criminal activity to work under this Task Order unless prior written approval is obtained from the TO Contract Manager.

D. TO Contractor shall ensure that TO Contractor Personnel background check certifications are renewed annually and at the sole expense of the TO Contractor.

E. Further, TO Contractor Personnel may be subject to random security checks during entry and exit of state-secured areas. The State reserves the right to require TO Contractor Personnel to be accompanied while on secured premises.

F. TO Contractor shall complete a criminal background check before any individual TO Contractor Personnel is assigned work on the project. TO Contractor shall provide a Criminal Background Check Affidavit (Appendix 3) before any work commencing on the Task Order.

G. Resources proposed to perform services for Maryland Port Administration (MPA) must comply with all MPA security requirements. MPA security requirements can be found at https://mpa.maryland.gov/pages/access-control-requirements.aspx.

https://mpa.maryland.gov/pages/access-control-requirements.aspx

3.6.3 On-Site Security Requirement(s)

A. For the conditions noted below, TO Contractor Personnel may be barred from entering or leaving any site until 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 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 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 entering and exiting 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. Any TO Contractor Personnel who enters the premises of a facility under the jurisdiction of DoIT may be searched, fingerprinted (for a criminal history background check), photographed, and required to wear an identification card issued by the Department of General Services

(DGS).

C. Any TO Contractor personnel entering the premises of a facility under the Jurisdiction of MPA is required to obtain and wear a Transportation Worker Identification Card (TWIC), issued by the Department of Homeland Security, in order to gain unescorted access within the facility.

The TO Contractor shall be responsible for all costs associated with obtaining the TWIC.

D. Further, TO Contractor Personnel shall not violate Md. Code Ann., Criminal Law Art. Section 9-410 through 9-417 and other agency security policies that control 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 Task Order.

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 is primarily responsible for managing the PORFP process, resolving TO Agreement scope issues, and authorizing any changes to the TO Agreement.

B. TO Manager—The TO Manager is primarily responsible for managing the work performed under the TO Agreement and performing administrative functions, including issuing written directions and ensuring compliance with the terms and conditions of the Radio Communications Master Contract.

The TO Manager will assign tasks to the personnel provided under this PORFP and will track and monitor the work being performed through the monthly accounting of hours’ deliverables for work types; actual work produced will be reconciled with the hours reported.

C. TO Contractor – The TO Contractor is the Radio Communications Master Contract Master Contractor awarded this Task Order. The TO Contractor shall provide human resources as necessary to perform the services described in this PORFP Scope of Work.

D. TO Contractor Manager—The TO Contractor Manager will be the primary point of contact with the TO Manager to regularly discuss task progress, upcoming tasking, historical performance, and resolution of any issues that may arise regarding the TO Contractor Personnel. The TO Contractor Manager will also serve as a liaison between the TO Manager and 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 throughout 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, substantially negatively impact Task Order performance. Key Personnel proposed as part of the PORFP Proposal shall start as of TO Agreement issuance unless specified otherwise in this PORFP or the Offeror’s TO Technical Proposal. Key Personnel may be identified after the Task Order award. TO Contractor Key Personnel shall include:

1) Project Manager

2) Project Lead Engineer

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.9.3 Personnel Experience

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 the Agency, 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 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.

3.10.2 Substitution Before and 30 Days After Task Order Execution

A. Before Task Order Execution or within thirty (30) days after Task Order 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 demonstrate that the initially 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 at the State's sole discretion.

Proposed substitutes deemed by the State less qualified than the proposed initial 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 Task Order Execution

The procedure for substituting personnel after Task Order 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. The TO Manager shall approve the proposed substitute individual. 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 are proposed within the time frame established by the TO Manager, the TO Agreement may be canceled.

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

3.14 Additional Clauses

The TO Contractor is subject to the requirements in this section and shall flow down the provisions of Sections 3.14.1 – 3.14.5 (or the substance thereof) in all subcontracts.

3.14.1 PORFP Subject to Radio Communications Master Contract

In addition to the requirements of this PORFP, the Master Contractors are subject to all terms and conditions contained in the Radio Communications Master Contract 060B7400088 RFP issued by the Maryland Department of Information Technology (DoIT ) and subsequent Master Contract Number 060B2490023. All times specified in this document are local, defined as Eastern Standard Time or Eastern Daylight Time, whichever is in effect.

3.14.2 Contract Management Oversight Activities

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

3.14.3 Source Code Escrow

Source code Escrow does not apply to this Task Order.

3.14.4 Purchasing and Recycling Electronic Products

A. State Finance and Procurement Article, Md. Code Ann. § 14-414 requires State agencies purchasing computers and other electronic products in categories covered by EPEAT to purchase models rated EPEAT Silver or Gold unless the DoIT waives the requirement. This information is located on the DGS website:

http://www.dgs.maryland.gov/GreenOperations/GreenPurchasing/Guidelines/specs/Electroni candITProductsSpecification.pdf.

B. DGS guidelines require planning and coordinating the proper disposition of Information Technology equipment. State Finance and Procurement Article, Md. Code Ann. § 14-415 requires State agencies awarding contracts for services to recycle electronic products to award the contract to a recycler that is R2, or e-Stewards certified. This information is located on the DGS website:

http://www.dgs.maryland.gov/GreenOperations/GreenPurchasing/Guidelines/specs/Electroni cProductDisposalSpecification.pdf.

C. DoIT guidelines provide information and guidance on the proper disposition of IT equipment, media sanitization, and protecting confidential information stored on media. This information is located in the State's Information Technology (IT) Security Policy, which can be accessed at http://DoIT .maryland.gov/support/pages/security policies.aspx. Section 6.5 Media Protection provides guidance on proper precautions to protect confidential information stored on media.

3.14.5 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. The Contractor may not modify the functionality or features of any SaaS provided hereunder if such modification materially degrades its functionality.

3.15 TO Pre-Proposal Conference

A. TO pre-proposal…