MDOD TRS Relay Services RFP_ FINAL.docx
DOCX document 6 MB Posted
- Attached to
- Telecommunications Relay Services
- Solicitation number
- BPM054823
- Issued by
- Maryland
About this file
Summary
This is a Request for Proposals (RFP) issued by the Maryland Department of Disabilities (MDOD), Telecommunications Access of Maryland (TAM), for Telecommunications Relay Services (TRS) and Real Time Text (RTT) solicitation number DEXR6600001. The solicitation seeks cost-effective, unrestricted 24-hour-per-day, 365-day-per-year telecommunications relay services for hearing and speech-disabled citizens in Maryland. Required services include traditional TRS call types (TTY-based relay, Voice Carry Over, Hearing Carry Over, Speech-to-Speech, and Spanish relay services), Real Time Text services, and comprehensive operator support. A pre-proposal conference is scheduled for February 19, 2026, from 10:00 a.m. to 11:30 a.m. via Zoom, with RSVP required by February 12, 2026. Questions must be submitted by February 26, 2026, at 5:00 p.m., and proposals are due by March 6, 2026, at 5:00 p.m. The contract is structured as an indefinite quantity with firm fixed unit prices for a five-year base period, with award determined through competitive sealed proposals. No scheduled site visits are noted. This is a single-award contract with no minimum qualifications specified for offerors.
Pricing will be based on conversation-minute billing with six-second increments for call length measurement. The RFP contains no identified set-asides for Minority Business Enterprises or Veteran Small Business Enterprises, though minority business enterprises are encouraged to respond. No incumbent contractor is identified. The service is funded through surcharges applied by telephone companies to Maryland customers' bills for telephone and VoIP services. Current Maryland Relay processes an average of 16,202.37 minutes of service per month. The contract requires extensive compliance with FCC regulations, operator staffing within Maryland with designated management positions, comprehensive quality assurance standards (including 90% minimum spelling accuracy and 95% verbatim relay standards), 24/7 customer service operations, and detailed monthly reporting on traffic, complaints, quality metrics, and operational performance. The contractor must maintain disaster recovery procedures, allow state site visits, and provide ASL-trained operators and cultural competency training.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| TAM Amendment #2.doc | DOC document | |
| TAM Amendment #3.doc | DOC document | |
| 2.19.26 - Pre-Proposal Attendance Sheet.doc | DOC document | |
| Attachment B - MDOD TRS Service Pricing Sheet.xlsx | XLSX spreadsheet | |
| Attachment-1.-No-Bid_Proposal-Notice_Vendor-Feedback-Form-1-1.docx | DOCX document | |
| Attachment-2.-Pre-Bid_-Pre-Proposal-Conference-Response-Form-v2.pdf.docx | DOCX document | |
| 2.19.26 - Preproposal Summary.doc | DOC document | |
| TAM Amendment #1.doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Telecommunications Relay Services (TRS) Solicitation #: DEXR6600001 RFP Document
State of Maryland maryland department of disabilities (mdod) Request for Proposals (RFP) telecommunications relay services (trs) RFP Number: DEXR6600001 Issue date: January 9, 2026
A Prospective Offeror that has received this document from a source other than eMarylandMarketplace Advantage (eMMA) https://procurement.maryland.gov should register on eMMA https://emma.maryland.gov/
NOTICE TO OFFERORS
Minority Business Enterprises Are Encouraged to Respond to this Solicitation.
State of Maryland Maryland Department of Disabilities (MDOD) Key Information Summary Sheet
| Request for Proposals |
| Telecommunication Relay Services (TRS) |
| Solicitation Number: |
| DEXR6600001 |
| RFP Issue Date: |
| 1/9/26 |
| RFP Issuing Office: |
| Maryland Department of Disabilities (MDOD) |
| Procurement Officer: |
| Elizabeth Hall |
| Email: |
| Elizabeth.Hall2@maryland.gov |
| Proposals are to be sent to: |
| Elizabeth.Hall2@maryland.gov |
| No Bid/Proposal Notice Feedback Form |
| *If you are not submitting a proposal for this solicitation, submit Attachment 1 with your reasons why. |
| Pre-Proposal Conference: |
| February 19, 2026 – 10:00 am – 11:30 am Local Time, at |
https://us02web.zoom.us/j/88464533180?pwd=0kRv11Di2HZEobWBfeZBlmqAEQvA3g.1 See Section 4.3 for additional details.
See Attachment 2 to RSVP by February 12, 2026, at 5:00pm to Attend
| Scheduled Site Visit |
| N/A |
| Questions Due Date and Time: |
| February 26, 2026 - 5:00 pm Local Time |
| Proposal Due (Closing) Date and Time: |
| March 6, 2026 - 5:00 pm Local Time |
Offerors are reminded that a completed Feedback Form is requested if a no-bid/proposal decision is made (see Attachment 1 - No Bid Notice/Vendor Feedback Form).
| MBE Subcontracting Goal: |
| N/A |
| VSBE Subcontracting Goal: |
| N/A |
| Procurement Method: |
| A Contract will be awarded in accordance with the Competitive Sealed Proposals method under COMAR 21.05.03. |
| Multiple or Alternate Bids: |
| Multiple or alternate Proposals will not be accepted. |
| Contract Type: |
| Indefinite Quantity with Firm Fixed Unit Prices |
| Contract Duration: |
| Five (5) Year Base Period |
| Primary Place of Performance: |
| The Contractor’s Location |
| SBR Designation: |
| No |
| Federal Funding: |
| No |
TABLE OF CONTENTS – RFP
| Minimum Qualifications | 7 | |
| 1.1 | Offeror Minimum Qualifications | 7 |
| 2 | Contractor Requirements: Scope of Work | 8 |
| 2.1 | Summary Statement | 8 |
| 2.2 | Background and Purpose | 8 |
| 2.3 | Contractor Responsibilities and Tasks | 9 |
| 2.4 | Experience and Personnel | 40 |
| 2.5 | Substitution of Personnel | 41 |
| 3 | Standard Terms and Conditions | 45 |
| 3.1 | Contract Initiation Requirements | 45 |
| 3.2 | End of Contract Transition | 45 |
| 3.3 | Invoicing | 45 |
| 3.4 | Liquidated Damages | 46 |
| 3.5 | Problem Escalation Procedure | 46 |
| 3.6 | Work Orders | 47 |
| 3.7 | Payments by Electronic Funds Transfer | 47 |
| 3.8 | Prompt Payment Policy | 47 |
| 3.9 | Federal Funding Acknowledgement | 48 |
| 3.10 | Conflict of Interest Affidavit and Disclosure | 48 |
| 3.11 | Non-Disclosure Agreement | 48 |
| 3.12 | Maryland Healthy Working Families Act Requirements | 49 |
| 3.13 | The State of Maryland’s Commitment to Purchasing Environmentally Preferred Products and Services (EPPs) | 49 |
| 3.14 | Insurance Requirements | 49 |
| 3.15 | Non-Compete Clause Prohibition | 50 |
| 4 | Proposal Submission Information and Instructions | 51 |
| 4.1 | eMaryland Marketplace Advantage (eMMA) | 51 |
| 4.2 | Electronic Means | 51 |
| 4.3 | Pre-Proposal Conference | 51 |
| 4.4 | Questions | 52 |
| 4.5 | Proposal Due (Closing) Date and Time | 52 |
| 4.6 | Economy of Preparation | 52 |
| 4.7 | Public Information Act Notice | 52 |
| 4.8 | Oral Presentation | 53 |
| 4.9 | Duration of Proposals | 53 |
| 4.10 | Revisions to the RFP | 53 |
| 4.11 | Cancellations | 53 |
| 4.12 | Incurred Expenses | 54 |
| 4.13 | Protest/Disputes | 54 |
| 4.14 | Offeror Responsibilities | 54 |
| 4.15 | Acceptance of Terms and Conditions | 55 |
| 4.16 | Compliance with Laws/Arrearages | 55 |
| 4.17 | Verification of Registration and Tax Payment | 55 |
| 4.18 | False Statements | 55 |
| 5 | Proposal Submission Information and Instructions | 57 |
| 5.1 | Two Part Submission | 57 |
| 5.2 | Proposal Delivery and Packaging | 57 |
| 5.3 | Volume I - Technical Proposal | 58 |
| 5.4 | Volume II – Financial Proposal | 67 |
| 6 | Evaluation and Selection Process | 68 |
| 6.1 | Evaluation Committee | 68 |
| 6.2 | Technical Proposal Evaluation Criteria | 68 |
| 6.3 | Financial Proposal Evaluation Criteria | 68 |
| 6.4 | Reciprocal Preference | 68 |
| 6.5 | Selection Procedures | 69 |
| 6.6 | Documents Required upon Notice of Recommendation for Contract Award RFP Attachments (Table B) | 70 |
| 7 | RFP Appendices and Exhibits | 72 |
| 7.1 | Appendices (Table C) | 72 |
| 7.2 | Exhibits (Table D) | 74 |
Minimum Qualifications Offeror Minimum Qualifications There are no Offeror Minimum Qualifications for this procurement.
THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK.
Contractor Requirements: Scope of Work Summary Statement This Request for Proposals (RFP) is issued to procure the goods or services, as specified in this Section 2, from a contract between the selected offeror(s) and the State of Maryland (“State”).
The Maryland Department of Disabilities (MDOD or Department), Telecommunications Access of Maryland (TAM), in consultation with the Governor’s Advisory Board for Telecommunications Relay, is seeking to obtain cost-effective, unrestricted, 24 hours a day, 365 days a year, for the citizens that are hearing and speech disabled in Maryland, also referred to as the Maryland user community, the following services types:
| A. | Telecommunications Relay Service (TRS) |
| B. | Real Time Text (RTT). |
It is the State’s intention to obtain goods and services, as specified in this RFP, from a contract between the selected Offeror and the State.
This is a single award. See RFP Section 6.5 Selection Procedures for more Contract award information.
Please note that a Contract award does not guarantee a Contractor will receive all or any State business under the Contract.
Background and Purpose
TRS
TAM, a State unit within MDOD, oversees all Maryland Relay services and programs. Maryland Relay is a telecommunications relay service established in 1991 to serve Marylanders who have difficulty using a standard telephone.
The cost of the Maryland Relay service is funded by a surcharge applied by telephone companies to its Maryland customers’ bills for telephone and VoIP service.
This service provides a vast array of solutions to meet the diverse needs of our State.
For more information, visit the website at Telecommunication Access of Maryland
TRS
Maryland Relay processes an average of 16,202.37 minutes of service per month (this average was calculated based on data from May 2021 through April 2024, from the current Maryland Relay service).
Maryland Relay offers TRS in the form of various services to accommodate different communication needs. These include Real-Time Text (RTT), Teletypewriter (TTY) Relay, Visually Assisted Speech To Speech Services (VA-STS), Speech To Speech (STS), Voice Carryover (VCO), Hearing Carryover (HCO), and Spanish Relay Services.
The Governor’s Advisory Board for Telecommunications Relay convenes on a regular basis to review the level of access and quality of service provided by the Telecommunications Relay Service, in addition to other items. The Board consists of 12 Maryland residents appointed by the Governor from the Deaf, hard-of-hearing, mobility-impaired, speech-disabled, senior citizen, and deaf-blind communities, and government.
RTT
On December 15, 2016, the FCC adopted rules to facilitate a transition of TRS from TeleTypewritter (TTY) technology to Real-Time Text (RTT) technology. RTT is an IP-based communication method that allows text to be sent and received instantly as it is typed, over Internet Protocol networks.
Unlike TTY, which relies on analog telephone lines and requires specific hardware to encode and decode text, RTT utilizes digital networks, enabling more seamless and faster communication.
In its 2016 RTT order, the FCC permitted wireless service providers and device manufacturers to support RTT instead of TTY technology, to the extent that where they support RTT in lieu of TTY technology, such services and devices are backward compatible with TTYs connected to other networks.
State Staff and Roles In addition to the Procurement Officer and Contract Monitor, the State will provide a Project Manager.
A. State Project Manager
1. The State Project Manager is responsible for providing oversight of the project.
Contractor Responsibilities and Tasks
2.3.1 Compliance
The Contractor shall comply with all laws, regulations, policies, standards and guidelines affecting telecommunication services for Deaf, hard-of-hearing, and speech-disabled individuals. It is the responsibility of the Contractor to adhere to this requirement and comply with all changes affecting project execution. These may include, but are not limited to, the strictest amongst the laws, standards, and regulations of Title IV of the ADA - Telecommunications services for Deaf, hard-of-hearing, and speech-disabled individuals codified at 47 U.S.C. § 225 (“telecommunications services for hearing-impaired and speech-impaired individuals”). All current standards and regulations and any future standards implemented by the FCC relating to TRS, adopted by the FCC or regulations codified by FCC are hereby incorporated by reference, as minimum standards required in the context of this RFP, whether or not said standards are specifically mentioned, named, or referred to in this RFP. If there is a conflict between the FCC rules and the minimum standards required by this RFP regarding the stringency of a regulation, the more stringent standard shall be followed. In the event of FCC-mandated changes in the provision of Relay services, the terms of the Contract pertaining to change orders will apply. (See Section 2.2 of the sample Contract at Exhibit 2.)
2.3.2 Approvals
The Contractor shall be required to get all approvals for messaging, changes and outgoing announcements in writing.
| 2.3.3 | TRS |
| 2.3.3.1 | Functional/Business |
The Contractor shall provide functionally equivalent TRS, including, by way of example but not limited to, the following features:
| 1) | Cost to consumers, |
| 2) | Call blockages no different than experienced by voice-to-voice non-TRS callers, |
| 3) | Real-time communications in the transmission and reception of text and speech, and |
| 4) | Use of advanced and efficient technology, as it becomes technically feasible. |
| 2.3.3.1.2 | The Contractor may provide Traditional TRS features in excess of the above-cited FCC requirements, and this RFP, with the express, written approval of the State Project Manager. |
| 2.3.3.1.3 | The Contract Monitor and Project Manager shall have the option to conduct site visits of locations used in Maryland to process TRS calls. |
| 2.3.3.1.4 | Toll Free Number - The existing State owned, nationwide toll-free numbers, listed in Exhibit 5 shall be used. All current toll-free numbers, and any additional toll-free numbers provided under this solicitation, shall become the property of the State of Maryland. |
| 2.3.3.1.5 | The percentage of Maryland Relay calls not processed by operators who are processing calls within the state of Maryland shall be reported on a monthly basis to the State Project Manager. |
2.3.3.2 Technical
The Contractor shall provide and ensure the following:
2.3.3.2.2 Provision of Relay
The Contractor shall provide an unrestricted, 24 hours/7 days/week TRS. Approximately 15% of American adults ages 18 and older reports some trouble with hearing (as cited by the National Institute on Deafness and other Communication Disorders) Therefore, individuals who have a communication disabilities need to have access the telephone system for the purpose of communication to and from all other persons in the State, the nation, and the world.
2.3.3.2.3 Compliance with RFP Specifications
The Contractor shall establish and operate the TRS in compliance with specifications outlined in this RFP. The establishment of this service shall include the provision of all necessary facilities, equipment, software, circuits, telephone service, staff, training, setup, testing, reporting, and other program elements as may be needed for implementation and operation of the Maryland Relay program.
2.3.3.2.4 Upgrades and refresh of standards, services, quality of services, systems, and applications If the FCC requires new standards, services, and Quality of Service (QoS) or the Contractor plans to upgrade or refresh its system/technology at any level that may affect the outcome of services or price for services to the State and its end-user community, the Contractor shall provide to the State Project Manager a plan to upgrade and show any and all impacts of upgrade or refresh.
| 2.3.3.2.5 | The Contractor shall obtain the State Project Manager’s express, prior, written approval before implementing the upgrade or refresh. |
| 2.3.3.2.6 | For implementation of upgrades or refresh, the Contractor shall ensure that: |
A. The compatibility of the State’s systems, components, and applications are not diminished in functionality, quality of the information technology, quality of service, security, privacy, and reliability;
B. The upgrade or refresh is backwards compatible to all systems, components and software version levels as well as those already being utilized by the State and end users that are the subject of this RFP; and C. It has provided all information and pricing for contract administration to the State Contract Manager and State Procurement Officer to allow for timely modification of the Contract prior to implementation, if the State believes that such modification is necessary and appropriate.
2.3.3.2.7 Toll Call Access and Rate
The Contractor shall provide (in accordance with 47 CFR 64.603) for inter-Local Access Transport Area (LATA) and intra-LATA toll call access for calls that originate or terminate in Maryland at no greater than the rate for those same types of calls that can be made without Relay.
Contractors shall implement announcements for all of the various explanations of service for each call type provided to relay users. The State Project Manager must approve all call announcements and explanations of service prior to implementation.
2.3.3.2.8 Traditional TRS Call Types Required
The Contractor has the capability to process the TRS Call Types in a manner that allows users of each TRS Call Type to initiate or receive a call using their preferred TRS Call Type mode.
All dedicated lines for specific TRS Call Types shall be answered first in that TRS Call Type, while having the ability to switch to any other call type when needed by the inbound caller.
All of the Traditional Relay call types shall be reimbursed on a conversation-minute basis as contracted. Traditional TRS Call Types currently include all of the following services, which are described as:
A. Text-To-Voice TTY - based TRS – A person with a hearing or speech disability uses a text telephone, called a TTY, to call the Operator (OPR). TTYs have a keyboard and allow people to type their telephone conversations. The text is read on a display screen and/or a paper printout. The OPR Relays the call back and forth between the parties by speaking what a text user types, and typing what a voice telephone user speaks.
B. Voice Carry Over (VCO) – A type of TTY-based TRS that allows a person with a hearing disability, but who wants to use his or her own voice, to speak directly to the called party and receive responses in text from the OPR. No typing is required by either party.
C. Hearing Carry Over (HCO) – A type of TTY-based TRS that allows a person with a speech disability, but who wants to use his/her own hearing, to listen to the other party and type his/her part of the conversation on a TTY. The OPR reads these words to the other party, and the caller hears responses directly from the other party.
D. Speech-To-Speech (STS) Relay – This form of TRS is used by a person with a speech disability, enabling persons with a speech disability to make telephone calls using their own voice (or an assistive communication device). An OPR, who is specially trained in understanding a variety of speech disorders, repeats what the caller says in a manner that makes the caller’s words clear and understandable to the called party. No special telephone is needed.
a) The Contractor shall provide Operators on the contract for STS that meet the following criteria.
i. As part of this provisioning, the Contractor shall test the hearing of Operators and their ability to understand people with a variety of speech disabilities.
ii. For hearing: Each STS Operator shall score 92% or higher in each ear using, at a minimum, a 50-word, W-22, or NU6 speech recognition test. Each STS Operator shall measure hearing acuity of 20dB or less in each ear using a pure tone test. The test shall be given before STS Operator may begin relaying calls.
iii. The Contractor shall obtain a written test result for every STS Operator from an audiologist that is a State licensed professional audiologist or certified by the American Speech-Language-Hearing Association with a Certificate of Clinical Competence in Audiology (CCC-A).
iv. All new Speech-to-Speech Operators will be tested prior to beginning processing Speech-to-Speech calls for the life of the contract.
v. The Contractor shall ensure that STS users are able to choose, on a call-by-call basis, or in their customer database record, whether or not the other party will be allowed to hear the speech disabled person’s voice.
b) Visually Assisted Speech-to-Speech (VA STS) Relay- This form of TRS is used by a person with a speech disability enables persons with a speech disability to make telephone calls using their own voice (or an assistive voice device). An OPR, who is specially trained in understanding a variety of speech disorders, repeats what the caller says in a manner that makes the caller’s words clear and understandable to the called party. In addition to the mechanisms used with STS, in VA STS, the OPR uses visual cues/methods to understand better the relay user. The VA STS user connects to the OPR via phone line (as per STS) as well as through a video mechanism (e.g. Skype, Google Hangout, etc.). The OPR must be able to see the relay user, but the relay user does not need to be able to see the OPR.
2.3.3.2.10 Shared Non-English Language Relay Service
The FCC requires interstate TRS providers to offer Spanish-to-Spanish traditional TRS. The Contractor shall provide Spanish-to-Spanish Relay as well as Spanish/English translation Relay.
2.3.3.2.11 2-Line HCO The capability to allow a speech-disabled customer to type to the Relay Operator while having a direct connection to the standard phone user to listen to the conversation, thus allowing for interruption from either party.
2.3.3.2.12 2-Line VCO The capability to allow a deaf or hard-of-hearing customer to speak directly to the standard phone user via the Relay and to be able to receive responses typed in text by the Relay Operator.
2.3.3.2.13 Voice-to-Text
A person using voice on a standard phone will call a Maryland Relay OPR. The OPR relays the call to a person with a hearing or speech disability using TTY. The OPR types the conversation to the TTY user and voices to the standard phone user. The OPR relays the call back and forth between the parties by speaking what a text user types, and typing what a voice telephone user speaks.
2.3.3.2.14 Non-Traditional TRS Call Types
Are not covered by this RFP unless by prior modification of the Contract. Non-Traditional TRS Call Types would only be considered to ensure that the State receives a cost effective and efficient means to carry out its business model(s) while maintaining the quality of service and types of products that are the subject of the RFP.
All requirements for processing calls and training Operators also apply to Spanish Translation support.
2.3.3.2.15 Operator Services
The Contractor shall provide access on a functionally equivalent level of Operator services to those provided to Standard Phone users.
All requirements for processing calls and training apply to Operator Services support regardless of where Operator Services is physically located.
The Contractor shall ensure that all Traditional TRS Call Types have the ability to communicate with each other via Relay.
2.3.3.3 Contractor User Preference Database
2.3.3.3.1 The Contractor shall have the ability to accept all User Preference Database information from the previous provider as required in 47 C.F.R. § 64.604 - Mandatory minimum standards. Further, the information shall be transferred in an ASCII delimited format or other format as approved by the State Project Manager.
A. The Contractor shall include all information from the previous provider’s database.
B. The Contractor shall agree that the data and record format of the User Preference Database is the property of the State.
C. The Contractor shall provide a mechanism to enable any Relay user, at the user’s discretion, to enter a Personal Identification Number (PIN) that will access their personal preference information from any phone.
D. The Contractor shall provide the capability to allow the Relay user to change the PIN by phone. Additionally, Contractor may also provide other methods for changing PIN.
| 2.3.3.4 | System and Process |
| 2.3.3.4.1 | Call Type Registration |
The Contractor shall have a call recognition method to accurately determine and record the call type of all inbound calls for proper call set-up and for accurate call type reporting.
2.3.3.4.2 Call Connection Mode
The Contractor shall have a call connection mode-recognition method to accurately determine and record the call connection mode of all inbound calls for proper call set-up and for accurate call connection mode reporting.
2.3.3.4.3 Performance Standards
The Contractor’s transmission circuits for Standard Telecommunication Relay shall meet or exceed FCC and Inter-exchange Carrier performance standards as stated in 47 CFR §64, subpart F, all other FCC requirements for common carriers, the American National Standards Institute (ANSI) Standards, and all applicable industry standards.
Relay users shall not be required to perform any additional steps or interaction to invoke optional services already paid for on the phone line being used to dial into Maryland Relay.
Any LEC Service(s) offered shall be functionally equivalent and may not be simulated to mimic the local phone company’s optional service.
2.3.3.4.4 Startup Equipment and Software
The Contractor’s transmission circuits shall meet or exceed FCC Inter-exchange performance standards. Telecommunications equipment, including station terminals, shall be capable of receiving and transmitting in both Baudot and ASCII codes, and be backwards compatible to TTY devices in service and shall also receive, access, and communicate with computers at any speed available.
2.3.3.4.5 Outbound Volume Control
The Contractor’s system shall have the ability to increase the volume on the outbound leg of the call for both the Operator’s microphone when the Operator is voicing, and the outbound line when the Relay user is voicing, as in an HCO call.
This control shall be independent of the Operator’s headset receiver control.
2.3.3.4.6 Auto-switchable Modems
The Contractor shall have modems that are auto-answer and auto-switchable at all available speeds.
2.3.3.4.7 Technology
The Contractor shall provide functionally equivalent technology and support equivalency to all Standard Phone services. These services include Automatic Number Identification (ANI), and other service enhancements, which increase the functional equivalency of the Relay Service for all calls, both carried on the provider’s network and sent out to inter-exchange carrier (IXC) networks.
2.3.3.4.8 Recorded Announcements for System Failures
Recorded messages are not permissible unless there is system failure. The Contractor shall provide approved recorded announcements as appropriate if a system failure/service interruption occurs within the Relay switch or on outbound circuits Recorded.
2.3.3.4.9 Announcements for System Failures
The Contractor shall add, at the direction of the State Project Manager, approved temporary messages to inform users of delays in obtaining service due to events such as, inclement weather, switch malfunction, natural disaster, civil disturbances, or other events sufficient to impede the delivery of service to Maryland Relay users.
2.3.3.4.10 Recorded Announcements for System Failures
All messages shall be provided in both voice and text and must be approved.
2.3.3.4.11 Regionally Directed Toll Free Numbers
The Contractor shall ensure that Relay users will be able to access regionally directed toll free numbers. These numbers would typically be accessible to the Relay user in his or her calling area. Example: the AAA has a national toll-free number. When a call arrives at the AAA call center, it is automatically rerouted to the correct state based on information in the Relay User’s ANI.
2.3.3.4.12 Regionally Restricted Toll-Free Numbers
The Contractor shall ensure that regionally restricted toll-free numbers will be accessible through its system. Example: If a Maryland Relay user is within Maryland and calls an 800 number that is restricted to intra-state calls, and the call is routed to a remote center, the Contractor shall have the capability of accessing the restricted toll-free call regardless of the location where the outbound call is initiated.
2.3.3.4.13 Service Reliability
The Contractor shall comply with requirements from Maryland to ensure reliability. These requirements include:
A. Switching System – Contractor shall have redundancy of equipment and the ability to upgrade system and perform preventative maintenance without taking the system offline.
B. Redundant Relay Capabilities – In the event of a complete system shutdown at one or more of its centers, the Contractor shall have the capability of re-routing calls to other functional centers.
C. Site Visits - For quality assurance and contract oversight, the Contractor shall allow the State to conduct unannounced site visits to any of the centers that process the State’s Relay calls.
D. Disaster Recovery Plan (DRP) and Escalation – Within ten (10) business days of the contract’s Kick-off Meeting, the Contractor shall provide the State with a copy of its Disaster Recovery Plan. The DRP shall include at a minimum at least three levels of escalation for 24/7/365(6) emergency personnel and their contact information. Contact information shall be kept current during the life of the contract.
E. In addition, no later than on an annual basis, the DRP shall be periodically reviewed and updated to remain consistent with the MDOD current DRP.
F. Notification of Disasters to the State – The State Project Manager and CM shall be notified of any event that disrupts the ability to process calls.
G. Written report of incident or event relating to a disaster- A written report shall explain how and when each event occurred, what was required to correct it and the time and date when the Maryland Relay resumed full operation. The report shall be given to the State Project Manager within two (2) calendar days of resumption of operation.
2.3.3.4.14 Automatic Spell Check and Auto-Correction
The spell check system used shall include, but not be limited to, the ability to adapt to new vocabulary (i.e. adding new words to vocabulary list, adding TTY abbreviations, etc.).
A. The Contractor’s system shall have automatic spell check. A list of words in the system’s spell check dictionary shall be provided to the State Project Manager at the time of award and quarterly thereafter for the life of the contract.
B. Automatic Change of TTY Abbreviations Upon Request - The Contractor’s system shall have the ability to change any TTY abbreviations used by Operators or the Contractor’s system to full words upon request of the customer. Example: Late Deafened VCO user is not comfortable with TTY abbreviations and prefers full words.
2.3.3.4.15 Macros
The Contractor shall submit to the State Project Manager a complete, detailed list of all macros used or planned by the Contractor’s operations platform. This list is to be submitted to the State Project Manager every three months beginning on the award date of the contract.
If any macros are developed during a quarter, all modifications shall be given to the State Project Manager at least one week before implementation.
2.3.3.4.16 Access to Directory Assistance
The Contractor shall provide callers with access to local and long-distance directory assistance at a cost rate no greater than the cost rate charged to standard telephone users.
2.3.3.4.17 Use of ANI
Automatic Number Identification (ANI) technology shall be utilized so that no caller is required to provide the originating calling number, except in instances where ANI information is not available from the local phone companies. If the Operator does not receive the ANI, the Operator will explain to the inbound party the reason for asking for the phone number.
2.3.3.4.18 1-900 or Any Pay per Calls The Contractor shall provide access to 900 numbers, and any other pay per call numbers.
Any additional inbound lines needed to access pay per call numbers are the responsibility of the Contractor and are not a recoverable expense.
Any such lines shall be toll free to ensure that TRS customers are not assessed an additional fee over and above the regular pay-for-call fee for accessing this service.
2.3.3.4.19 Handling of 7-1-1 Calls
Calls to 7-1-1 are to be answered first in voice mode with additional access for all TRS access modes.
2.3.3.4.20 No Branding of Inbound Phone Lines
There is to be no pre-determined answer sequence based on ANI, whether permanent or temporary, placed on the inbound line unless specifically requested by the user via a User Preference Data Base.
User Preference Database information shall be available to the Operator at the time of connection with the inbound caller. The user’s profiled connect mode will be automatically initiated regardless of the inbound DNIS dialed.
| 2.3.3.5 | Maryland Relay Operator Access |
| 2.3.3.5.1 | Access to Maryland Operator’s location |
The Contractor shall provide that the State Project Manager and/or Department designee(s) on a 24/7/365 basis will be given unlimited, unimpeded, physical access to home-based offices to conduct compliance checks. This will include providing for all badging, security/access codes, etc.
The Contractor’s name or logo may appear, in a smaller font, as the provider of Maryland Relay, subject to prior written approval of the State Project Manager, to indicate clearly correspondence from Maryland Relay.
| 2.3.3.6 | Staffing |
| 2.3.3.6.1 | Minimum Staff Positions in the State of Maryland and Management Corporate. |
A. If the Contractor requires staff or management to be temporarily dedicated to other tasks (such as conducting training for other centers, or engaged in corporate business), all time not devoted directly to Maryland Relay shall be approved in advance by the State Project Manager, documented and reported to the State Project Manager, and submitted with the Contractor’s monthly reports. Maryland specific trainers are required regardless of the location of the primary center to ensure that the requirements of the state are met.
B. All meetings noted as ‘monthly meetings’ or ‘every two-week meetings’ for staff positions in the following descriptions may be by video/phone at discretion of the State Project Manager.
C. Escalation of issues - Any issues that shall be escalated to, or information provided by, shall be reported to the State Project Manager along with the names and contact information for persons in the escalation path as documented in accordance with the deliverables in the Transition Milestone provided by the Contractor.
D. Recruitment of Persons with Disabilities - The Contractor shall actively recruit persons with disabilities, including individuals who are deaf, hard-of-hearing, speech disabled, Deafblind, or blind. Preference will be given to employing individuals with ASL fluency, Relay Service experience, and experience working within the deaf, hard of hearing and/or speech disabled community.
2.3.3.6.2 Additional Personnel/Contacts–
2.3.3.6.2.1 The Contractor shall also provide the following staff:
A. Account Liaison/Manager A. At least one liaison to represent the Contractor’s company who has full power and authority to ensure compliance with all the terms and conditions of this Contract.
B. This person shall be senior management level.
C. Shall be available to the State at any time by phone or in person.
D. Shall have the authority to resolve issues based on the service level agreement.
B. Senior Management Representative for each of the Contractor’s departments (examples: Sales, Account Management, Technical, Operations, etc.) that contribute to the provision of Maryland Relay:
A. Representatives from each department shall attend quarterly meetings at a minimum at the TAM office or other site as designated by the State Project Manager. The majority of the meetings will take place in the Baltimore/Washington area, although this representative shall be prepared to support the contract at any location in Maryland, or virtually.
B. This staff’s work time need not be fully dedicated to this contract; however, must be attentive to this contract and be able to respond in a timely and efficient manner as the position title and responsibilities dictate.
| 2.3.3.7 | Billing Standards and Access |
| 2.3.3.7.1 | Toll- and Toll-Free Calls: If a call is free on a direct call, it must be free on a Relay call; conversely, if a call is a toll call on a direct call, the same toll charges must be applied to a Relay call. |
| 2.3.3.7.2 | Inbound International Calls - The Contractor shall provide international access to calls into Maryland Relay when the inbound caller is outside the United States. |
| 2.3.3.7.3 | Landline Flat Rate Calling Plans - The Contractor shall ensure that a customer having an expanded flat rate calling plan is able to place calls through the Maryland Relay to points within the expanded local calling area without incurring any charge for the call. |
| 2.3.3.7.4 | Cellular Flat Rate Calling Plans - The Contractor shall ensure that flat rate plans purchased by cellular users accessing Maryland Relay, should be a local call, and do not incur any additional charges. These types of calls are identified by call codes 60, 61, 62, or by users stating that they are on a cell phone. |
| 2.3.3.7.5 | Wireless Text Messaging Flat Rate Plans - The Contractor shall ensure that flat rate plans purchased by wireless users enable them to access Maryland Relay without incurring any additional charge. This will include, but not be limited to, access to Maryland Relay via wireless devices able to initiate and receive text messaging. |
| 2.3.3.7.6 | System Billing Process – The Contractor shall provide call detail record generation. The call detail records will be automated and available for audit and monitoring by the Department or its designee. |
| 2.3.3.7.7 | General Assist Minutes – The Contractor shall define in detail what is included in the definition of General Assist Minutes. |
| 2.3.3.7.8 | Caller-provided Information - The Contractor may require that a caller provide NPA/NXX type information to identify the caller’s local calling area, if that information is not delivered to the Contractor’s network to distinguish local calls from toll calls and allow for faster call set-up. |
| 2.3.3.8 | Access to RTT via 7-1-1 |
| 2.3.3.8.1 | Persons using standard telephones shall be able to contact Maryland RTT customers by dialing 7-1-1. Upon being told (directly or via a user profile) that the customer is calling a RTT user, the call is immediately transferred to the Maryland RTT and the call will be released from the TRS platform. |
| 2.3.3.8.2 | Calls to the Maryland RTT shall be documented on separate line items on the TRS YTD Summary reports as well as a daily detail report. |
| 2.3.3.8.3 | Three-digit dialing – All Maryland three-digit numbers must be accessible via Maryland Relay (Examples are 211, 311, 411, 511, 611, 711, 811, and 911). |
| 2.3.3.8.4 | Billing Record -The billing account record shall contain, but not be limited to, the following information: |
A. Telephone number or credit/calling card number to be billed (NPA-prefix-line number).
B. Originating telephone number (NPA-prefix-line number).
C. Terminating telephone number (NPA-prefix-line number).
D. Date of call.
E. Start time: Defined here as the actual time the calling party is initially connected to the called party or to an answering machine at the called party’s number, or intercept message for the called number, including:
1. Session Start
2. Conversation Start
F. End time: Defined here as the time when either the called party or the calling party hangs up; whichever occurs first, including:
A. Conversation End B. Session End
G. The Contractor shall bill in six (6) second increments when measuring call length. If the call goes past a six-second interval, the Contractor shall round up and invoice on the nearest six-second interval. Example: 7 seconds shall be billed as two six-second intervals and 67 seconds shall be billed as twelve (12) six-second intervals.
| 2.3.3.9 | Complaint Resolution and Customer Satisfaction |
| 2.3.3.9.1 | The Contractor shall maintain a 24-hour toll-free Customer Service number for the convenience of all callers. |
| 2.3.3.9.2 | This Customer service number shall be operated by staff within the state of Maryland 24/7/365(6) to provide the highest quality customer service to Maryland Relay Users. |
| 2.3.3.9.3 | At least one (1) person shall function at all times (24/7/365as a Customer Service representative. While performing this Customer Service function, this individual must perform Customer Service functions (and/or related to) only. |
| 2.3.3.9.4 | In addition, the Customer Service representative must have completed training specific to Maryland Relay. |
| 2.3.3.9.5 | Non-Maryland Complaints will be directed to the appropriate Customer Service Team.. |
| 2.3.3.9.6 | The Contractor’s Customer Service Team shall meet with the State Project Manager on a monthly basis to discuss Maryland specific customer complaint issues. Training/retraining issues will be determined during these meetings. |
| 2.3.3.9.7 | Complaint Resolution Process for Call Processing and/or Call Processing Personnel: Within thirty (30) calendar days of the Kick-off Meeting, the Contractor shall document in a Complaint Resolution Plan, procedures for collecting and handling complaints, inquiries, and comments regarding the Contractor’s service or personnel as they relate to call processing. |
| 2.3.3.9.8 | The Complaint Resolution Plan is a deliverable and shall be approved for the project by the State Project Manager. Any changes made after the State’s initial acceptance must have prior express, written approval from the State Project Manager before initiation. |
| 2.3.3.9.9 | The following processes are also to be included in the Complaint Resolution Plan: |
A. If a call is processed outside the state of Maryland and either party on the call requests Customer Service or a Supervisor, the call is to be transferred and processed by the Maryland Customer Service.
| B. | Inbound Party Complaint: The Contractor shall ensure that any Relay customer will be able to reach a Supervisor or the Customer Service within a maximum time limit of one (1) minute while still online during a Relay call. |
| C. | Outbound Party Complaint: If the outbound caller states that they wish to speak to a Supervisor, or, in any way indicates that they wish to register a comment or complaint, the Contractor’s system and Customer Service procedures shall provide that the outbound caller is connected with the Supervisor without delay and without time limit. The Relay Supervisor must log this comment or complaint. |
| D. | Complaint Reporting - Complaints are to include customer contact information if given, Operator number, date, time, nature of complaint(s), and resolution or immediate steps taken toward a resolution. The State Project Manager is to receive all information regarding each complaint, not a summary. All complaints and relevant information concerning each complaint are to be forwarded to the State Account Manager, and a copy forwarded to the State Project Manager within 24 hours of the complaint. |
| E. | Multiple Complaints During One Contact – If a Relay customer contact contains multiple issues, each issue shall be documented, answered, and tallied individually within the customer complaint report. |
| F. | Complaints Not Immediately Resolved - Complaints not resolved within 24 hours will have the original complaint and all follow-up information included and forwarded to the State Project Manager as the Contractor’s follow-up steps occur. |
| G. | Customer Contact Information - Customers shall be asked if they would like to leave contact information in order that a complaint may be made in writing. If the customer requests written follow-up, the complaints shall be followed up with a letter to the customer that will clearly indicate the issues reported and steps taken toward resolution, with a copy to the State Project Manager. |
| 2.3.3.10 | Quality Assurance |
| 2.3.3.10.1 | Relay Service Quality Assurance Testing and Evaluation - The Contractor and the State Project Manager will continuously evaluate the quality of Relay service with the objective of maintaining the service standards established in the RFP and/or by Federal and other State mandate. |
| 2.3.3.10.2 | The State or the State’s independent evaluator may perform quarterly formal evaluations, which at a minimum will evaluate five hundred (500) actual Relay scripted test calls. The results of these surveys will be used to evaluate the Contractor’s performance. Results that do not meet the requirements of each area given below, at the minimum value for that area, may be the basis for the State assessing liquidated damages. |
| 2.3.3.10.3 | The Contractor shall cooperate with either a State or an independent evaluator selected by the State Project Manager to identify quality issues. |
| 2.3.3.10.4 | The Contractor’s performance will be assessed in the following areas. The values noted in each area are the minimum values that are acceptable. The State reserves the right to assess liquidated damages if the State, in its sole and exclusive judgment, determines that the Contractor fails to meet the minimum values because of testing for any given period, and for any given area. |
| A. | Spelling Accuracy – An average of 90% of all QA tested calls shall have a spelling accuracy of 95% or better. |
| B. | Verbatim – An average of 95% of QA tested calls shall be relayed verbatim. A sample testing will occur measuring the percentage of calls relayed verbatim. |
| C. | Typing Speed - All QA tested calls shall be relayed at a minimum speed of 60 WPM, which will include spelling accuracy as measured. |
| D. | Keeping user informed of call progress - Measure is at least 85% of the total number of users are kept informed of a call’s progress (example – you have reached an answering machine, put on hold, person talking to others not on call, etc... Things a hearing person would know by listening on the call) |
| 2.3.3.10.5 | Quality Assurance Plan - The Contractor shall have a Quality Assurance Plan for conducting, quantifying, recording, and scoring on a monthly basis their own separate quality assurance test call results. The State Project Manager will share the standards used in the independent quality assurance testing with the Contractor to ensure consistency of testing. The Contractor shall have a mechanism in place to ensure remedies for any issues found during testing. |
| 2.3.3.10.6 | State Access to Evaluation - The State shall have unlimited access to all phases, documentation and results of the Contractor’s evaluation tests calls. The State may share this information and data with State management, auditors, and legislative bodies as necessary for reporting. |
| 2.3.3.10.7 | Annual Customer Survey - The Contractor shall conduct an annual customer survey by mail to obtain feedback from users. The State will work with the Contractor to develop a survey to access areas of concern. The survey will be approximately 10 – 15 questions with agree/disagree type answers to obtain quantifiable answers. The State Project Manager must provide prior, express written approval for the surveys before their release and have complete access to all results in both summary and detailed formats. |
| 2.3.3.11 | Customer Confidentiality |
| 2.3.3.11.1 | Written Confidentiality Policy – The Contractor shall have a Confidentiality Policy regarding call content privacy. A copy of the confidentiality policy shall be provided to users upon request. |
| 2.3.3.11.2 | Violation of Confidentiality – |
A. The Contractor shall have a policy for reviewing alleged violations of confidentiality. The State PM must give prior written approval of this policy.
B. An Operator or Supervisor who, after investigation, is found to have violated the confidentiality policy, shall be disciplined in accordance with the Contractor’s approved confidentiality policy. If a second violation occurs with an individual, the State reserves the right to have that individual removed from providing services under this Contract. All violations shall be reported to the State PM monthly.
| 2.3.3.11.3 | All violations shall be reported to the State Project Manager monthly. |
| 2.3.3.11.4 | Collection of Confidential Information - The Contractor shall be restricted to collecting only the personal information necessary to provide the Relay service being rendered, i.e. customer database information given on a voluntary basis. This information shall not be used or shared outside those associated with the State contract for any other purpose. |
| 2.3.3.11.5 | Confidential Emergency Information - If a user is in an emergency or life-threatening situation, or causes an emergency to exist by threatening the Operator or other staff, names and specific information may be disclosed by the Operator to a Supervisor to address the situation expeditiously. |
| 2.3.3.12 | Operator Standards |
The Contractor shall provide support and services that meet the following standards. The Contractor shall document each of the following requirements and/or standards within thirty (30) calendar days of the Kick-off meeting unless another timeframe is noted.
| 2.3.3.12.1 | Operator Recruitment - The Contractor shall have employee recruitment and selection procedures, demonstrating that persons already on staff, or to be selected and employed as Operators, meet all proficiency requirements as specified in this RFP. Operators shall be able to type expeditiously and accurately a TTY Relay message. This will include, but not be limited to the following: |
| A. | English Grammar - Basic skills in English grammar are required to be assessed quarterly by a written test(s) measuring grammar at a first-year college level. Results are to be submitted to the State Project Manager as Operators are hired. The Contractor shall document its proposed Testing Plan for English Grammar to the State Project Manager for prior express, written approval. |
| B. | ASL Grammer – Operators shall be able to read and understand ASL grammar to facilitate Operator understanding of Relay callers that use ASL |
| C. | Understandable Voice - Operators shall be able to speak in a clear, concise, and understandable manner. Traditional TRS Operators shall be fluent English speakers to facilitate Operator understanding of STS users and understanding of hard-of-hearing users. |
| D. | Typing Speed and Accuracy - The Contractor shall require all Operators, including trainees during any probation period, to possess a minimum typing speed of sixty words per minute, with a maximum error rate of no greater than five percent (5%) before being allowed to process a Maryland Relay call. The formula to calculate words per minute is: |
| 1) | Five (5) keystrokes (four alphanumeric characters plus one space) per “word,” requiring three hundred (300) keystrokes per minute, to achieve sixty words per minute with a maximum error rate of no greater than five percent (5%). |
| 2) | (Macros that are executed by one function key shall count as one keystroke regardless of the number of alphanumeric characters “attached” to that macro. Similarly, a macro executed with two key strokes shall count for two keystrokes regardless of the number of alphanumeric characters “attached” to that macro.) |
| E. | Spelling Skill Level - The Contractor shall require that all Operators possess spelling skills at a level equivalent to those used in the first year of college. |
| F. | The Contractor shall document its proposed Testing Plan for Spelling Skill Level to the State Project Manager for prior express, written approval. |
| 2.3.3.12.2 | Identification of Operator Trainees - Trainees shall be identified to both the voice and TTY customers of a Telecommunications Relay call at the onset of each conversation, mitigating potential for criticism of Operator quality or speed. |
| 2.3.3.12.3 | Operator Monitoring - The Contractor shall ensure that the Supervisor has the capability for remote, silent monitoring of both the Standard Phone and TTY leg of a call being processed by any Operator. Observing or listening to actual calls is prohibited except for training or monitoring purposes or other purposes specifically authorized by the FCC, the PSC, the Department, or by this RFP. |
| 2.3.3.12.4 | The State Project Manager is to receive monthly reports by the 15th of the month following the month of activity, identifying the issues found during monitoring and the necessary, appropriate, corrective action taken. |
| 2.3.3.12.5 | Appropriate Voice Tone and Tempo by Operator - The Operator shall use a conversational voice tone and tempo of voice appropriate to the type of call being made when speaking for the TTY user. |
| 2.3.3.12.6 | Voice ‘Inflection’ by Operator - The Operator shall utilize the voice inflexion cue typed by the TTY user instead of voicing the actual cue word. Example: The word “smile” should not be voiced; the voice tone should indicate a “smile in the voice.” |
| 2.3.3.12.7 | Change of Voice User During a Call - Operators shall indicate to the Relay user(s) if another speaking person comes on the line. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .