Attachment B- Technical Matrix.pdf
PDF 317 KB Posted
- Attached to
- Enterprise Telecommunication Services
- Solicitation number
- BPM058210
- Issued by
- Maryland
About this file
This is a Technical Matrix document for an Enterprise Telecommunications Services Request for Proposal issued by the University of Maryland, College Park (UMD). The RFP solicits qualified vendors to provide comprehensive voice services, Session Initiation Protocol (SIP) trunking, unified communications, and traditional Plain Old Telephone Services (POTS) lines across multiple campus locations, including the main UMCP campus and satellite facilities at the Institute for Bioscience and Biotechnology Research (IBBR) and USMSM sites. Required services include a minimum of 300,000 minutes per month of local and long distance calling, SIP trunking with 400 concurrent call paths at two geographically distinct sites (minimum 200 concurrent each at the main campus), E911 support with accurate location routing, 99.99% uptime SLA with documented remediation procedures, and 92+ analog POTS lines for elevators, alarms, and faxes. The contract term is structured as a three-year base period with two optional twelve-month renewal periods.
The technical matrix establishes mandatory requirements across multiple service categories, including voice services features (caller ID, call forwarding, voicemail, call transfer), SIP trunking specifications (minimum 32,000 DID station numbers, failover and redundancy options, codec support for G.711 and G.729, T.38 fax-over-IP protocol, static IP block allocation, Quality of Service support, and 24x7 network monitoring), toll-free services with number portability, and comprehensive reporting with detailed monthly call records. Service level requirements mandate 24x7 technical support availability via email and telephone, while implementation deliverables include a detailed project timeline with milestones, migration strategy to minimize service disruption, staff training plan, and overall project management plan. Desirable features include routing flexibility with time-of-day and geographic options, integration with cloud service providers such as Microsoft Teams Phone, Zoom Phone, or WebEx Calling, self-service portal capabilities for call forwarding and redirection, and invoicing through the portal within five days of billing cycle end.
View the file
Other files
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
Enterprise Telecommunications Services (Technical Matrix)
General Requirements Technical Approach Technical Requirements Reporting Services Levels Implementation Plan Desirables Billing and Administrative
General Requirements
G-1 Certification and Expertise – Offeror shall provide certification, expertise and evidence of providing voices services including local and long distance calling, SIP trunking with 400 concurrent call paths at two (2) geographically sites (minimum of 200 each), Unified Communications , Toll –Free inbound services and Traditional analog POTS lines for elevators, alarms and faxes.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
Technical Requirements Voice Services
V-001 Provide minimum 300,000 minutes per month of local and long distance calling.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
V-002 Support E911 services with accurate location routing for all service locations.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
V-003 Provide 99.99% uptime SLA with documented remediation procedures. Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
V-004 Support caller ID, call forwarding, voicemail and call transfer features.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
SIP Trunking
S-001 Provide a minimum of 4 geographically distinct SIP circuits/call paths, with 2 supporting a minimum of 200 concurrent each at the main UMCP campus, and 2 supporting a minimum of 50 concurrent calls at the Institute for Bioscience and Biotechnology Research (IBBR) satellite campus, plus options to expand service to additional sites.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-002 Support Direct Inward Dialing or (DID) number blocks with minimum 32,000 station numbers.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-003 Provide failover and redundancy options for SIP call paths, including inbound DID failover.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-004 Support codec negotiation including G.711 and G.729, with G.711 the preferred codec.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-005 Provide interoperability with existing Private eXchange (PBX) infrastructure.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-006 Support for T.38 based Fax-over-IP protocol
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-007 Support Ethernet access with minimum bandwidth required for specified SIP concurrent calls
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-008 Provide Static IP block allocation (/30 minimum) for each SIP circuit
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-009 Provide Quality of Service (QoS) support for voice traffic prioritization
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-010 Support 24x7 network monitoring with proactive alerting
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-011 Provide 2 geographically distinct SIP circuits for remote IBBR site, supporting 50 concurrent calls each.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
S-012 Provide 1 SIP circuit for remote USMSM site, supporting 20 current calls.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Toll-Free Services
TF-001 Provide domestic toll-free access with competitive per-minute rates.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
TF-002 Provide number portability for existing toll-free numbers
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
POTS Lines
P001 Support 92+ analog lines for elevators, alarms and fax machines.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
P-002 Provide long distance only service option(s) for specific lines.
Requirement Level:
MANDATORY
Self-Assessment:
Fully Meet☐ Don’t Meet☐
P-003 Provide National Access Charge compliance for multi-line business.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Reporting
RPT-001 (V-005) Provide detailed call records with monthly usage reports.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Service Levels
SL-001 Provide uptime system guarantee (target 99.99%)
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
SL-002 Provide 24 x 7 technical support availability to include email and call communication.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Implementation Plan
IP-001 Provide a detailed project timeline with milestones.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
IP-002 Provide a migration strategy that minimize service disruption.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Self-Assessment:
Fully Meet☐ Don’t Meet☐
IP-003 Provide a training plan for the University Telecommunication Staff
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
IP-004 Provide an overall project management plan that outlines approach and resources.
Requirement Level:
MANDATORY
Explanation of how the requirement is met (delete this text when responding)
Billing and Administration
BA-001 Administrative portal for self-service Management
Requirement Level:
MANDORTORY
Explanation of how the requirement is met (delete this text when responding)
Desirables
D-001 (TF-003) Provide routing flexibility with time-of-day and geographic options
Requirement Level:
Desirable
D-002 (UC-001) Integration with cloud service providers, such as Microsoft Teams Phone, Zoom Phone, WebEx Calling or similar platforms.
Requirement Level:
Desirable
D-003 (BA-003) Ability to forward/redirect calls from self-service portal.
Requirement Level:
Desirable
D-004 Provide invoices in portal no later than the 5th day or after the billing cycle end.
Requirement Level:
Desirable
File details come from the government source that posted it. Updated .