2-20260624 - Enterprise Phone Replacement Pricing Form.xlsx
XLSX spreadsheet 56 KB Posted
- Attached to
- 20260624 - Enterprise Phone Replacement
- Solicitation number
- US.252010
- Issued by
- Adams County, Pennsylvania
About this file
This is an Enterprise Phone Replacement Pricing Form for the Susquehanna Regional Transportation Authority (SRTA), a Pennsylvania-based regional transportation agency. SRTA is soliciting proposals for a complete turnkey enterprise communications solution to replace its existing Cisco Unified Communications Manager platform and associated administrative desk phones across multiple locations in Adams, Columbia, Cumberland, Dauphin, Franklin, Harrisburg City, Montour, Northumberland, Perry, Snyder, Union, and York Counties. The scope includes all labor, hardware, software, licensing, implementation, configuration, testing, training, support, and related services, with the NICE CXone Customer Service call center platform remaining outside the scope and operational throughout implementation. The proposal encompasses 205 total phones distributed across Harrisburg/Dauphin (50 units), other regional locations (60 units), and York (95 units), including devices for various departments such as mobility, information specialists, customer service, driver areas, dispatch, and executive offices. Proposals are due by 2:00 PM on October 14, 2026, via the PennBid.net platform in both Excel and signed PDF formats.
Pricing must be all-inclusive for labor, supervision, resources, and materials, with costs separated into installation/deployment milestones, maintenance, and subscription components across a five-year base term. The pricing form requires quoting firms to complete detailed worksheets specifying implementation milestones (not to exceed 10 percent of total installation cost for initiation/kickoff and not less than 10 percent for the final milestone), additional integrations and training costs, annual maintenance and subscription fees, optional items, and estimated storage needs. Pricing must be guaranteed for 120 days after the proposal due date. Proposers must designate a single qualified project manager, provide references for similar past projects, and submit complete technical proposals identifying the solution architecture, implementation methodology, device schedule, and licensing schedule. All proposals must include company information, authorized signatures, and compliance with Commonwealth and Federal laws, as well as the financial assistance requirements of the Federal Transit Administration and Pennsylvania Department of Transportation.
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
Instructions
| Quoting Firm Name | ||
| Contact Person | Telephone | |
| Quoting Firm Address | Quoting Firm Town and Zip | |
| Quoting Firm Telephone |
1 Complete each of the five (5) work sheets within this file.
2 Those cells with a green background must be completed. Other cells are locked and cannot be edited or changed
3 Sign each sheet.
4 Please submit the signed copies within PennBid.
5 Please include signed copies as a .PDF on the PennBid Platform in addition to this Excel file. Please be sure to include the completed Excel file within PennBid.net.
6 Pricing should be all inclusive for the supply of all labor, supervision, resources, and materials necessary to perform Contracted service.
7 Reserved
8 Pricing must be guaranteed for one-hundred, twenty (120) days after proposal due date.
9 Complete company information above, the remaining sheets will fill automatically.
10 Return the Excel workbook with the required signed PDF version.
11 Other than entering required informration in the green shaded cells Proposers shall not alter this Excel file in any way. Evidence found of modification to this file will result in complete disqualification.
12 Return the Excel workbook within PennBid.
13 Reserved
14 Repeated items on this page are intentional for emphasis.
15 If the resulting Contract will be endorsed by an individual different than the Authorized Signature below, please provide the name and title here.
Name Title
Authorized Name Date
Authorized Signature Signer's Title
20260624 - Enterprise Phone Replacement Pricing Form Instructions
Project Pricing
| Quoting Firm Name | 0 | 0 | Quoting Firm Name | 0 | 0 | ||||
| Contact Person | 0 | Telephone | 0 | Contact Person | 0 | Telephone | 0 |
| Installation/Deployment Milestones | Phone System Support | ||||||||||||||
| Number | Description | Days* | Cost | NOTE: Initiation and Kickoff shall not be more than 10% of the total Installation/Deployment total cost. | Additional Integrations | Additional Training On Site | Additional Training Remote | ||||||||
| 1 | Initiation/Kickoff Meeting | ERROR:#DIV/0! | Position | Hourly Rate | Position | Hourly Rate | Position | Hourly Rate | |||||||
| 2 | ERROR:#DIV/0! | ||||||||||||||
| 3 | ERROR:#DIV/0! | ||||||||||||||
| 4 | ERROR:#DIV/0! | ||||||||||||||
| 5 | ERROR:#DIV/0! | ||||||||||||||
| 6 | ERROR:#DIV/0! | ||||||||||||||
| 7 | ERROR:#DIV/0! | Please note that invoicing should correlate with Milestone Achievements. Invoices shall be marked to indicate Milestone Achievements or Annual Maintenance/Subscription Fees. | Additional Technical Support On Site | Additional Technical Support Remote | |||||||||||
| 8 | ERROR:#DIV/0! | Position | Hourly Rate | Position | Hourly Rate | ||||||||||
| 9 | ERROR:#DIV/0! | ||||||||||||||
| 10 | ERROR:#DIV/0! | ||||||||||||||
| 11 | ERROR:#DIV/0! | ||||||||||||||
| 12 | ERROR:#DIV/0! | Optional Items | |||||||||||||
| 13 | ERROR:#DIV/0! | Description | Unit Cost | ||||||||||||
| 14 | ERROR:#DIV/0! | NOTE: The final Milestone shall not be less than 10% of the total Installation/Deployment total cost. | |||||||||||||
| Installation Total | $ - 0 | ||||||||||||||
| *Days- shall mean the number of days after the receipt of the Notice to Proceed. | SRTA Estimated Storage Needs (TB) | Base Annual Remote Technical Support Hours | |||||||||||||
| Annual fees shall not be included in Milestones above. | |||||||||||||||
| Maintenance and Subscriptions | Total 5 Year Contract Value | Storage Provided in Base Cost (TB) | Base Annual On SIte Technical Support Hours | ||||||||||||
| 1 Year Cost | 2nd Year | 3rd Year | 4th Year | 5th Year | $ - 0 | ||||||||||
| Annual Maintenance Fee | Minimum Contracted Availability | Additional Storage Costs (per TB) | |||||||||||||
| Annual Subscription Fee |
| Annual Total | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Year 1 with Installation Total | $ - 0 |
| Authorized Name | Date | |
| Authorized Name |
Authorized Signature
Authorized Signature Date
| Quoting Firm Name | 0 | 0 | |||||||
| Contact Person | 0 | Telephone | 0 | ||||||
| Enterprise Phone Replacement - Phone Counts | |||||||||
| Current distribution and RFP quantity summary | |||||||||
| Harrisburg/Dauphin | Other Locations | ||||||||
| Location / Department | Quantity | Unit Cost | Total Cost | Location / Department | Quantity | Unit Cost | Total Cost | ||
| Mobility | 4 | $ - 0 | Adams | 9 | $ - 0 | ||||
| Information Specialists | 3 | $ - 0 | Cumberland | 5 | $ - 0 | ||||
| IT & Planning Hall | 5 | $ - 0 | Franklin | 5 | $ - 0 | ||||
| Bill's Hall | 3 | $ - 0 | Northumberland | 8 | $ - 0 | ||||
| Customer Service | 5 | $ - 0 | Perry | 5 | $ - 0 | ||||
| Driver Area | 1 | $ - 0 | Union/Snyder (USTA) | 6 | $ - 0 | ||||
| Dispatch | 8 | $ - 0 | West Milton | 2 | $ - 0 | ||||
| Training + Fred | 3 | $ - 0 | Stock / Replacement / Future Growth | 20 | $ - 0 | ||||
| Server Room | 1 | $ - 0 | Other Locations Total | 60 | $ - 0 | ||||
| Second Floor Hall | 4 | $ - 0 | |||||||
| Bev's Office | 2 | $ - 0 | |||||||
| Executive Suite | 6 | $ - 0 | |||||||
| Maintenance | 5 | $ - 0 | |||||||
| Harrisburg/Dauphin Total | 50 | $ - 0 |
| York | |||||
| Location / Department | Quantity | Unit Cost | Total Cost | Authorized Name | |
| Maintenance | 8 | $ - 0 | |||
| Bus Barn | 4 | $ - 0 | |||
| Clean Room | 1 | $ - 0 | Authorized Signature | ||
| Customer Service | 30 | $ - 0 | |||
| Front Desk | 1 | $ - 0 | |||
| Operations | 21 | $ - 0 | |||
| Server Room | 1 | $ - 0 | |||
| IT Room | 3 | $ - 0 | |||
| York Transfer Center | 1 | $ - 0 | Date | ||
| Second Floor Administration | 25 | $ - 0 | |||
| York Total | 95 | $ - 0 |
NOTE: All costs shall be captured in the Milestones, Maintenance, and Subscriptions tables. The location costs are for SRTA planning and funding purposes only.
20260624 - Enterprise Phone Replacement Price Form
&P of &N
Sheet1
ERROR
References-Past Projects
| Quoting Firm Name | 0 | 0 | ||
| Contact Person | 0 | Telephone | 0 |
Please list references and past projects for like organizations. Please include projects for which like service was provided. References should coincide with Past Projects. Please include projects which presented difficult circumstances.
| References | |||||||
| Organization Name | Primary Business Purpose | Name | Telephone Number | Email Address | |||
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 | |||||||
| 6 | |||||||
| 7 | |||||||
| 8 | |||||||
| 9 | |||||||
| 10 | |||||||
| Past/Similar Projects and Description | |||||||
| Organization Name | Project Start Date | Project Description | Project Outcome |
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
| References listed in the first and second tables shall match. | ||
| Authorized Name | Date |
| Please note the white spaces in these two tables are unlocked and can be edited by Quoting firms. | |
| Authorized Signature |
20260624 - Enterprise Phone Replacement &"-,Bold" &"-,Regular" References
Notes
| Quoting Firm Name | 0 | 0 | ||
| Contact Person | 0 | Telephone | 0 |
Please add any notes related to pricing on this page.
Authorized Name Date
Authorized Signature
20260624 - Enterprise Phone Replacement Notes
Requirements Matrix
| Quoting Firm Name | 0 | |||||
| 20260624 - Enterprise Phone Replacement Requirements List | 20260624 - Enterprise Phone Replacement Requirements Response | |||||
| Item | Requirement | Category | Sub Category | Requirement Type | Compliance | Comments |
| 1 | (3.1) Provide a complete turnkey enterprise communications solution, including all labor, hardware, software, licensing, implementation, testing, documentation, training, warranty, and support. | Project | General Requirements | Required | 1 |
| 2 | (3.1) Designate a single qualified Project Manager and serve as the single point of responsibility for the complete Solution and all third parties. | Project | General Requirements | Required | 2 |
| 3 | (3.1) Propose commercially available, actively supported products; include all required licensing; preserve SRTA ownership and administrative control; and support future expansion. | System | Solution Requirements | Required | 3 |
| 4 | (3.2) Perform a comprehensive assessment and independently validate the existing CUCM environment, inventory, network, carrier services, integrations, and site conditions. | Implementation | Discovery & Validation | Required | 4 |
| 5 | (3.2) Provide an implementation methodology that coordinates all required parties, identifies assumptions and dependencies, and minimizes disruption to SRTA operations. | Implementation | Implementation Approach | Required | 5 |
| 6 | (3.3) Support all identified SRTA facilities and telecommunications assets and validate final device, user, number, carrier, network, and integration quantities before implementation. | System | Existing Environment | Required | 6 |
| 7 | (3.4) Provide project management, a kickoff meeting, a detailed implementation schedule, regular status meetings, written minutes, and prompt notice of schedule risks. | Implementation | Project Management | Required | 7 |
| 8 | (3.4) Complete discovery and develop an SRTA-approved detailed Solution design covering architecture, network, dial plan, call routing, security, integrations, devices, migration, and testing. | Implementation | Solution Design | Required | 8 |
| 9 | (3.4) Provide a detailed migration and cutover plan; coordinate all third parties; and obtain SRTA approval before material changes affecting scope, schedule, cost, or operation. | Implementation | Migration & Change Control | Required | 9 |
| 10 | (3.5) Provide an enterprise-grade architecture and identify deployment model, hosting locations, dependencies, maximum capacity, supported users, devices, sites, and concurrent calls. | System | Architecture & Capacity | Required | 10 |
| 11 | (3.5) Provide high availability, redundancy, failover, monitoring, alerting, and sufficient capacity for SRTA's current operational requirements. | System | Availability & Monitoring | Required | 11 |
| 12 | (3.5) Support scalable expansion of users, devices, locations, licenses, integrations, and carrier capacity without replacement of the core platform; disclose all limitations. | System | Scalability & Licensing | Required | 12 |
| 13 | (3.5) Provide SRTA full customer-level administrative access, recognized open standards, supported third-party integration methods, and continuing software and firmware updates. | System | Administration & Standards | Required | 13 |
| 14 | (3.6) Provide enterprise call processing, internal and external calling, Direct Inward Dial service, number retention and portability, extension management, and an enterprise dial plan. | Telephony | Core Call Processing | Required | 14 |
| 15 | (3.6) Provide SRTA-configurable call routing using schedules, holidays, caller information, time of day, overflow, failover, and other supported conditions. | Telephony | Call Routing | Required | 15 |
| 16 | (3.6) Support multiple auto attendants, hunt groups, call queues, shared line appearances, configurable distribution methods, announcements, hold treatment, overflow, and routing. | Telephony | Call Distribution | Required | 16 |
| 17 | (3.6) Provide call transfer, forwarding, hold, park, pickup, conference, do-not-disturb, caller ID, speed dial, call waiting, BLF/presence, and executive-assistant features. | Telephony | Calling Features | Required | 17 |
| 18 | (3.6) Support compatible SIP endpoints, point-to-point video communications, desktop and conference devices, and disclose device, codec, bandwidth, and licensing requirements. | Telephony | Endpoints & Video | Required | 18 |
| 19 | (3.6) Provide enterprise voicemail, paging and analog-device support, E911 capabilities, Call Detail Records, and recommended network Quality of Service requirements. | Telephony | Voicemail, E911 & Records | Required | 19 |
| 20 | (3.7) Provide synchronized presence and secure instant messaging with supported message history, file exchange, notifications, and cross-platform user access. | Collaboration | Presence & Messaging | Required | 20 |
| 21 | (3.7) Provide audio and video conferencing, screen sharing, secure file sharing, call escalation, mobile collaboration, and call continuity between supported devices. | Collaboration | Meetings & Mobility | Required | 21 |
| 22 | (3.7) Integrate with directories, Microsoft Teams, NICE inContact, and required recording interfaces, and provide a unified communications client across supported platforms. | Integration | Unified Communications | Required | 22 |
| 23 | (3.8) Furnish a complete Device Schedule and all required desktop, video, and conference telephones that are compatible, supported, configurable, and ready for operational use. | Hardware | End User Devices | Required | 23 |
| 24 | (3.8) Support required wireless devices, expansion modules, headsets, hot desking, device login, and restoration of the authenticated user's profile and assigned features. | Hardware | Device Features | Required | 24 |
| 25 | (3.8) Provide accessible devices, centralized firmware and device management, recommended spares, efficient replacement and reconfiguration, and required device warranties. | Hardware | Management & Accessibility | Required | 25 |
| 26 | (3.9) Provide supported desktop and mobile applications for placing, receiving, transferring, and managing enterprise calls and accessing applicable collaboration features. | Applications | Desktop & Mobile Clients | Required | 26 |
| 27 | (3.9) Support remote use, enterprise caller identity, single-number reach, Single Sign-On, Multi-Factor Authentication, and secure connectivity without avoidable user complexity. | Applications | Remote Access & Authentication | Required | 27 |
| 28 | (3.9) Provide centralized application administration, lost-device controls, session management, secure BYOD use where authorized, lifecycle updates, and all required client licensing. | Applications | Application Security & Management | Required | 28 |
| 29 | (3.10) Provide centralized multi-location administration for users, devices, telephone numbers, extensions, call routing, voicemail, and efficient device replacement. | Administration | Centralized Management | Required | 29 |
| 30 | (3.10) Support role-based and limited administrative access, administrative audit logging, bulk administration, configuration templates, and license usage and threshold visibility. | Administration | Access & Automation | Required | 30 |
| 31 | (3.10) Provide system-health monitoring, administrative alerts, configuration backup and recovery, reporting, data export, current documentation, and SRTA control of Contractor access. | Administration | Monitoring & Recovery | Required | 31 |
| 32 | (3.11) Integrate with Microsoft 365, Outlook, calendars, and Microsoft Entra ID for authentication, Single Sign-On, provisioning, group-based administration, and directory synchronization. | Integration | Microsoft 365 & Entra ID | Required | 32 |
| 33 | (3.11) Provide documented APIs and supported integration methods for third-party applications, CRM, contact center, call recording, paging, notification, and future integrations. | Integration | APIs & Third Parties | Required | 33 |
| 34 | (3.11) Use secure, standards-based integrations with least-privilege service accounts and complete integration testing, results, configuration, dependency, and support documentation. | Integration | Integration Security & Testing | Required | 34 |
| 35 | (3.12) Retain all existing SRTA telephone numbers and manage number inventory, porting documentation, scheduling, risk, carrier coordination, validation, and corrective action. | Carrier Services | Number Portability | Required | 35 |
| 36 | (3.12) Review carrier services and support required SIP trunking, toll-free services, carrier redundancy, emergency services, analog lines, elevator phones, alarms, and other critical services. | Carrier Services | Carrier Architecture | Required | 36 |
| 37 | (3.12) Perform carrier migration and number-porting cutovers outside normal business hours unless approved; provide on-site or remote support, testing, documentation, and written authorization before disconnects. | Carrier Services | Cutover & Testing | Required | 37 |
| 38 | (3.13) Provide stated system availability, component redundancy, automatic failover, site survivability, alternate routing, and identification of all single points of failure. | Continuity | Availability & Failover | Required | 38 |
| 39 | (3.13) Minimize effects of internet, WAN, carrier, and power failures and provide business continuity, disaster recovery, configuration protection, backups, RTO, RPO, and cloud resiliency. | Continuity | Disaster Recovery | Required | 39 |
| 40 | (3.13) Provide outage notifications, restoration priorities, major incident reports, root-cause and corrective-action information, and documented initial and periodic continuity testing. | Continuity | Incident Response & Testing | Required | 40 |
| 41 | (3.14) Encrypt communications signaling, media, and administrative access and provide secure authentication, Single Sign-On, Multi-Factor Authentication, role-based access, and least privilege. | Cybersecurity | Encryption & Access Control | Required | 41 |
| 42 | (3.14) Restrict and log Contractor remote access; provide security logging, monitoring, alerts, audit access, and SRTA's ability to revoke Contractor access. | Cybersecurity | Monitoring & Remote Access | Required | 42 |
| 43 | (3.14) Maintain vulnerability management, security patching, malware protection, network security, SBC protection, certificate management, and secure mobile, desktop, and cloud services. | Cybersecurity | Vulnerability & Platform Security | Required | 43 |
| 44 | (3.14) Preserve SRTA data ownership and export rights; disclose retention and cloud processing; promptly notify and cooperate on security incidents; preserve evidence; and exclude prohibited equipment. | Cybersecurity | Data Protection & Incident Response | Required | 44 |
| 45 | (3.15) Provide standard reporting and accessible Call Detail Records covering call activity, users, devices, trunks, routes, durations, outcomes, and other available call information. | Reporting | Standard Reports & CDR | Required | 45 |
| 46 | (3.15) Provide call-queue reports, real-time dashboards, custom and scheduled reports, multi-location filters, and export to commonly usable formats including CSV, XLSX, and PDF. | Reporting | Dashboards & Export | Required | 46 |
| 47 | (3.15) Provide defined historical retention plus user, device, license, system-performance, call-quality, audit, and security reporting; preserve SRTA ownership and API access to data. | Reporting | Analytics & Retention | Required | 47 |
| 48 | (3.16) Develop an SRTA-approved Training Plan and provide role-based administrator, technical-support, end-user, specialized-user, and train-the-trainer instruction before cutover. | Training | Training Program | Required | 48 |
| 49 | (3.16) Provide instructor-led and hands-on training at approved locations, post-cutover support, attendance records, and certificates for train-the-trainer participants. | Training | Delivery & Records | Required | 49 |
| 50 | (3.16) Furnish reproducible training materials, quick-reference guides, and a complete New-Hire Training Manual; identify optional refresher training and all associated costs. | Training | Materials & Refresher Training | Required | 50 |
| 51 | (3.17) Serve as the single support contact, coordinate manufacturers and third parties, and provide multiple support channels with 24x7 support for critical outages. | Support | Support Availability | Required | 51 |
| 52 | (3.17) Maintain defined severity levels, required response times, continuous critical-incident response, escalation contacts, status updates, resolution records, and root-cause analysis. | Support | Incident Management | Required | 52 |
| 53 | (3.17) Provide software maintenance, supported versions, maintenance notices, secure remote and on-site support, hardware replacement, manufacturer support, support records, and transparent pricing. | Support | Maintenance Services | Required | 53 |
| 54 | (3.18) Provide Contractor and manufacturer warranties beginning at Final Acceptance and covering labor, parts, shipping, configuration, software, integrations, and correction without additional charge. | Warranty | Warranty Coverage | Required | 54 |
| 55 | (3.18) Serve as the single warranty contact; manage repairs, replacements, claims, recalls, recurring defects, and documentation; and disclose all exclusions and optional extended-warranty pricing. | Warranty | Warranty Administration | Required | 55 |
| 56 | (3.19) Prepare an SRTA-approved written Test Plan in accordance with Section 3.19.2, including test procedures, responsibilities, schedule, expected results, acceptance criteria, and deficiency tracking. | Testing | Test Plan | Required | 56 |
| 57 | (3.19) Complete pre-cutover, functional, endpoint, desktop/mobile, carrier, porting, integration, E911, security, failover, reporting, performance, and call-quality testing. | Testing | System Testing | Required | 57 |
| 58 | (3.19) Track, correct, and retest deficiencies and obtain written Final Acceptance only after all required testing, documentation, training, and Deliverables are complete. | Testing | Acceptance | Required | 58 |
| 59 | (3.20) Provide accurate final architecture, network, telecommunications, call-flow, user, device, license, carrier, integration, security, warranty, support, backup, testing, training, and project documentation. | Documentation | Final Documentation | Required | 59 |
| 60 | (3.20) Furnish documentation electronically in organized, commonly usable formats, including editable native files for SRTA-specific materials, and update it through Final Acceptance and material changes. | Documentation | Format & Maintenance | Required | 60 |
| 61 | (3.20) Deliver all administrative credentials and SRTA-controlled accounts before Final Acceptance without unnecessary Contractor dependency; SRTA shall own and may use SRTA-specific Deliverables. | Documentation | Credentials & Ownership | Required | 61 |
| 62 | (3.21) Support future expansion of locations, users, devices, licenses, integrations, and services and disclose expansion pricing, limitations, technology roadmap, and discontinuation risks. | Transition | Future Expansion | Required | 62 |
| 63 | (3.21) Provide a Transition Plan at least ninety days before expiration or termination and cooperate with SRTA and any successor without disrupting service or restricting access. | Transition | Transition Planning | Required | 63 |
| 64 | (3.21) Preserve SRTA ownership and portability of telephone numbers, data, configurations, accounts, portals, and administrative access and provide complete exports in usable formats. | Transition | Data & Number Portability | Required | 64 |
| 65 | (3.22) Provide complete all-inclusive pricing separated into one-time, recurring, optional, licensing, hardware, professional services, support, warranty, training, carrier, storage, and transition costs. | Pricing | Complete Pricing | Required | 65 |
| 66 | (3.22) Disclose escalation, assumptions, exclusions, future-purchase pricing, discounts, travel, taxes, fees, change-order support, price-hold period, and all potential charges; no hidden charges are permitted. | Pricing | Pricing Terms | Required | 66 |
| 67 | (3.23) Identify and separately price compatible optional products, software, integrations, recording, analytics, AI, professional services, training, support, storage, replacement, and expansion services. | Optional Services | Optional Products & Services | Optional | 67 |
| 68 | (3.24) Submit a complete technical proposal identifying the Solution, architecture, Project Manager, key personnel, implementation and migration approach, schedule, samples, Device Schedule, and Licensing Schedule. | Proposal | Technical Response | Required | 68 |
| 69 | (3.24) Clearly identify all assumptions, exceptions, deviations, alternatives, optional items, and pricing; organize the Proposal as required and ensure all representations and commitments are complete and consistent. | Proposal | Completeness & Exceptions | Required | 69 |
| 70 | (3.25) Provide a detailed milestone and payment schedule covering implementation, migration, training, cutover, stabilization, Deliverables, and Final Acceptance; invoice only after written milestone acceptance. | Project | Milestones & Payment | Required | 70 |
| 71 | (3.26) Accept a five-year base term with implementation during the base term; recurring charges shall begin only after Final Acceptance and no license or service may automatically renew. | Contract | Base Term & Billing | Required | 71 |
| 72 | (3.26) Provide optional-year pricing and continuity without reimplementation; timely request and justify any price adjustment; no adjustment is effective without SRTA approval or retroactively. | Contract | Optional Years | Required | 72 |
| 73 | (3.27) Maintain required availability and service levels, document outages and maintenance, provide performance records and reporting, and disclose all measurement methods, exclusions, and service credits. | Service Levels | Performance Requirements | Required | 73 |
| 74 | (3.27) Correct service failures, provide SRTA-required corrective-action plans, promptly address emergency-communications failures, and acknowledge that service credits are not SRTA's exclusive remedy. | Service Levels | Performance Remedies | Required | 74 |
| 75 | (3.28) Submit all proposed master, cloud, license, support, third-party, and online terms; accept SRTA Contract precedence, no unilateral changes, SRTA data rights, and disclosure of all conflicts. | Contract | Master Services Agreement | Required | 75 |
| 76 | (3.29) Demonstrate enterprise, multi-site, CUCM migration, carrier, Microsoft, platform, support, and technical experience; identify qualified personnel, authorizations, subcontractors, capacity, and similar references. | Qualifications | Experience & Capacity | Required | 76 |
| 77 | (3.30) Maintain all business, professional, technical, manufacturer, and regulatory authorizations; comply with telecommunications, accessibility, prohibited-equipment, and subcontractor requirements. | Compliance | Licensing & Regulatory | Required | 77 |
| 78 | (3.31) Maintain documented change classification, requests, SRTA approvals, scheduling, testing, rollback, emergency procedures, configuration baselines, change history, and current documentation. | Change Management | Configuration Control | Required | 78 |
| 79 | (3.32) Decommission the existing system only with written SRTA authorization and an approved plan after data preservation and acceptance; protect SRTA equipment, numbers, services, and site conditions. | Implementation | Decommissioning | Required | 79 |
| 80 | (3.33) Provide SRTA a centralized administrative portal and independent control of users, devices, licenses, call routing, reporting, roles, authentication, MFA, SSO, and audit logs. | Administration | SRTA Administrative Control | Required | 80 |
| 81 | (3.33) Maintain SRTA administrative access through transition, disclose manufacturer-restricted functions, provide sufficient administrator training, and keep Contractor accounts limited and revocable. | Administration | Administrative Independence | Required | 81 |
| 82 | (3.34) Provide system-wide, SRTA-configurable call recording with designation by user, department, queue, or number; search, playback, export, notices, role-based access, and audit logging. | Recording | Call Recording | Required | 82 |
| 83 | (3.34) Provide SRTA-configurable recording and voicemail retention, deletion, legal-hold information, ownership, export, transition support, security, storage-location disclosure, capacity estimates, and complete storage pricing. | Recording | Retention, Storage & Security | Required | 83 |
| 84 | (3.34) Provide automated voicemail transcription while retaining original audio; disclose delivery methods, accuracy limits, storage and processing locations, third parties, AI use, licensing, and recurring costs. | Voicemail | Transcription & Processing | Required | 84 |
| 85 | (3.6.18) Provide Enhanced 911 capabilities with accurate emergency-calling location information for each applicable SRTA location, user, device, and remote-use scenario. | Recording | Retention, Storage & Security | Required | 85 |
| 86 | (3.19.9) Test emergency calling and validate that correct callback and dispatchable location information is delivered, coordinating test calls with the appropriate public-safety entities. | Voicemail | Transcription & Processing | Required | 86 |
| 87 | (3.12.2) Validate the complete inventory of existing SRTA telephone numbers and preserve all numbers identified by SRTA for continued use. | Carrier Services | Number Inventory & Preservation | Required | 87 |
| 88 | (3.12.3-3.12.4) Prepare and manage number-porting documentation, scheduling, validation, risk identification, issue notification, and corrective action without disrupting service. | Carrier Services | Number Porting | Required | 88 |
| 89 | (3.12.10) Perform number-porting, carrier-migration, and service cutover activities outside SRTA's normal business hours unless SRTA provides prior written approval. | Carrier Services | Cutover Window | Required | 89 |
| 90 | (3.12.13) Do not disconnect any existing telecommunications service without prior written SRTA authorization and confirmation that replacement service is operational. | Carrier Services | Service Disconnects | Required | 90 |
| 91 | (3.6.5) Support multiple SRTA-configurable auto attendants with menus, schedules, holidays, announcements, routing, transfer, directory access, and timeout or invalid-entry treatment. | Telephony | Auto Attendants | Required | 91 |
| 92 | (3.6.6) Support configurable hunt groups with sequential, simultaneous, longest-idle, circular, and other available distribution methods and appropriate overflow treatment. | Telephony | Hunt Groups | Required | 92 |
| 93 | (3.6.7) Support enterprise call queues with configurable greetings, announcements, music or messages on hold, estimated wait treatment, overflow, reporting, and administrative controls. | Telephony | Call Queues | Required | 93 |
| 94 | (3.6.15) Provide enterprise voicemail with individual and shared mailboxes, greetings, message management, notifications, forwarding, administrative control, and applicable retention settings. | Telephony | Voicemail | Required | 94 |
| 95 | (3.6.17) Support required paging systems and analog devices, including fax, elevator, emergency, alarm, and other existing analog services identified during discovery. | Telephony | Paging & Analog Devices | Required | 95 |
| 96 | (3.6.14) Generate and retain Call Detail Records and permit authorized SRTA personnel to search, report, and export available call-origin, destination, route, duration, and disposition information. | Reporting | Call Detail Records | Required | 96 |
| 97 | (3.11.1) Integrate with Microsoft 365, Outlook, and supported calendar functions and disclose all required licensing, dependencies, permissions, and functional limitations. | Integration | Microsoft 365 & Outlook | Required | 97 |
| 98 | (3.11.2-3.11.3) Integrate with Microsoft Entra ID for authentication, Single Sign-On, user provisioning, group-based administration, and directory synchronization. | Integration | Entra ID & Directory | Required | 98 |
| 99 | (3.7.14) Provide Microsoft Teams integration and describe calling, presence, messaging, meeting, directory, client, licensing, configuration, and support capabilities and limitations. | Integration | Microsoft Teams | Required | 99 |
| 100 | (3.7.11.2) Maintain compatibility with SRTA's NICE inContact call-center environment and identify the proposed interface, call-routing method, dependencies, licensing, responsibilities, and limitations. | Integration | NICE inContact | Required | 100 |
| 101 | (3.11.8) Support required call-recording integrations and identify native and third-party interfaces, supported call scenarios, security, licensing, configuration, and ongoing support requirements. | Integration | Call Recording Integration | Required | 101 |
| 102 | (3.13.1-3.13.2) State the committed system availability and provide redundancy for critical components while identifying all single points of failure and scheduled-maintenance exclusions. | Continuity | Availability & Redundancy | Required | 102 |
| 103 | (3.13.3-3.13.6) Provide automatic failover, site survivability, restoration to normal operation, failover notifications, and alternate routing during internet, WAN, or carrier failures. | Continuity | Failover & Survivability | Required | 103 |
| 104 | (3.13.8-3.13.10) Provide documented business-continuity and disaster-recovery procedures, configuration backups, restoration processes, Recovery Time Objective, and Recovery Point Objective. | Continuity | Recovery & Configuration Backup | Required | 104 |
| 105 | (3.14.6) Restrict Contractor remote administrative access to authorized personnel, approved purposes, and secure methods; log such access and allow SRTA to revoke it. | Cybersecurity | Contractor Remote Access | Required | 105 |
| 106 | (3.14.7-3.14.8) Maintain security and administrative logs, provide authorized SRTA access, and generate alerts for applicable suspicious activity, authentication failures, configuration changes, and security events. | Cybersecurity | Security Logging & Monitoring | Required | 106 |
| 107 | (3.14.9-3.14.10) Maintain vulnerability-management and security-patching processes, promptly notify SRTA of material vulnerabilities, and provide remediation guidance and supported security updates. | Cybersecurity | Vulnerability & Patch Management | Required | 107 |
| 108 | (3.14.19-3.14.20) Promptly notify SRTA of security incidents, provide continuing status and impact information, cooperate with response and investigation, and preserve relevant logs and evidence. | Cybersecurity | Security Incident Response | Required | 108 |
| 109 | (3.17.2-3.17.6) Provide 24x7 support for critical outages and comply with the defined Severity 1-4 acknowledgment, response, continuous-work, and communication requirements. | Support | Severity Levels & Response | Required | 109 |
| 110 | (3.17.7-3.17.15) Maintain escalation contacts and incident updates, document resolution, provide root-cause and corrective-action analysis, and timely repair or replace failed hardware. | Support | Escalation, RCA & Hardware | Required | 110 |
| 111 | (3.19.2 and 3.19.14-3.19.17) Obtain SRTA approval of the written Test Plan, maintain a deficiency log, correct and retest deficiencies, and obtain written Final Acceptance. | Testing | Test Plan, Deficiencies & Acceptance | Required | 111 |
| 112 | (3.21.9-3.21.16) Provide the required ninety-day Transition Plan, preserve telephone-number portability, export SRTA data and configurations, maintain administrative access, and coordinate with a successor. | Transition | Contract Transition | Required | 112 |
| 113 | (3.34.3-3.34.4) Provide SRTA-configurable recording and voicemail retention and disclose base and additional storage, capacity assumptions, geographic storage locations, limitations, and all costs. | Recording | Retention & Storage | Required | 113 |
| 114 | (3.34.5-3.34.7 and 3.34.14-3.34.15) Protect recordings with role-based access and audit logging; support notices, authorized deletion, export, transition, and identify legal-hold capabilities. | Recording | Security, Export & Preservation | Required | 114 |
| 115 | (3.34.8-3.34.13) Provide voicemail transcription while retaining original audio and disclose delivery, accuracy limits, retention, storage, processing location, third parties, AI use, licensing, and costs. | Voicemail | Transcription & AI Processing | Required | 115 |
| 116 | 116 | ||||
| 117 | 117 | ||||
| 118 | 118 | ||||
| 119 | 119 | ||||
| 120 | 120 | ||||
| 121 | 121 | ||||
| 122 | 122 | ||||
| 123 | 123 |
| Please do not add more text to the Vendor Notes column that go beyond the available cell space. Excess information will be cut off. |
| Please use only the selection under the Compliance heading to complete the table. |
| Requirement Type | Possible Count | Full | Partial | Not Available |
| Required | 114 | 0 | 0 | 0 |
| Optional | 1 | 0 | 0 | 0 |
| Totals | 0 | 0 | 0 |
| Requirement Type | Full | Partial | Not Available | |
| Required | 0.0% | 0.0% | 0.0% | 0.0% |
| Optional | 0.0% | 0.0% | 0.0% | 0.0% |
| 0.0% |
File details come from the government source that posted it. Updated .