DAS_RFP_Response_Matrix.xlsx

XLSX spreadsheet 25 KB Posted Oct 26, 2026

Attached to: Strategic Distributed Antenna System Partnership
Solicitation number: RFP-130757
Issued by: Middlesex County, Virginia

About this file

Written by GovTribe AI · Oct 28, 2026

This is a Response Matrix from Virginia Tech documenting the Statement of Needs and RFP requirements for a Distributed Antenna System (DAS) operations and modernization contract. The solicitation encompasses comprehensive management of DAS services including network monitoring, preventative and corrective maintenance, asset lifecycle management, carrier coordination, and RF propagation optimization across the Virginia Tech campus. The contract requires offerors to develop and implement service-level agreements with specified availability standards, performance monitoring protocols, incident management processes, and continuous communication with Virginia Tech. Capital improvements and modernization must address aging equipment replacement, support for current and emerging cellular technologies (5G, 6G, 7G, C-Band, CBRS), spectrum expansion, and capacity enhancements prioritizing Lane Stadium with completion by July 23, 2027, and enhanced fan connectivity operational by Fall 2027. The contract term structure is flexible, with offerors required to propose upgrade timelines for the first year, three years, and five-year periods, along with a minimum 10-year long-term modernization plan.

The financial model requires offerors to propose revenue-sharing arrangements based on DAS revenues including carrier participation agreements, spectrum expansion, infrastructure licensing, and event-related services, with minimum annual revenue guarantees payable to Virginia Tech. Offerors may structure proposals as management partnerships with annual operating fees, long-term concessions with upfront and annual payments, or lease/commercialization models with specified payment schedules. A 20-year financial model must demonstrate total projected value to the University including guaranteed annual payments, revenue-share waterfalls, carrier growth assumptions, capital investment schedules, net present value calculations, and sensitivity analyses. Virginia Tech retains all ownership of DAS infrastructure and ultimate authority over equipment, real estate rights, vendor oversight, system governance, and expansion decisions. The contract mandates equitable, non-discriminatory carrier access; comprehensive performance reporting including monthly operations and revenue reports, quarterly commercial and capital updates, post-event venue reports, and annual strategic reviews; and full support for emergency communications and public safety initiatives.

View the file

Other files

File	Type	Posted
351512703_Attachment C and D Included.pdf	PDF	Oct 26, 2026

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Statement_of_Needs

Item ID	RFP Section	Subsection	Response Expected	RFP Requirement	Offeror Response	Proposal Reference	Comply / Address?	Notes / Exceptions
VI.A.1	VI. Statement of Needs	A. DAS Operations	Narrative	Manage and oversee the following services: Network monitoring, performance management, preventative maintenance, corrective maintenance, asset lifecycle management, carrier coordination, network optimization, and Radio Frequency (RF) propoagation optimization.
VI.B.1	VI. Statement of Needs	B. Campus Operations	Narrative	Comply with all Virginia Tech requirements concerning construction, scheduling, environmental protection, historic resources, accessibility, traffic control, fire safety, life safety, occupational safety, utility coordination, infection control where applicable, and protection of research and instructional activities.
VI.B.2	VI. Statement of Needs	B. Campus Operations	Narrative	Obtain and maintain all permits, licenses, approvals, inspections, and governmental authorizations required for the work.
VI.B.3	VI. Statement of Needs	B. Campus Operations	Narrative	Protect Virginia Tech property and operations, maintain clean and secure work areas, and promptly repair damage caused by Offeror activities.
VI.C.1	VI. Statement of Needs	C. Service-Level Expectations	SLA attachment and/or narrative	Provide Service Level Agreements, including availability of on-site personnel during events, resolution time during events, and resolution time during non-events.
VI.C.2	VI. Statement of Needs	C. Service-Level Expectations	Narrative	Include services during athletic events, move-in/move-out, commencement, major campus events, emergencies, and other identified high-density periods in capacity planning and operational readiness testing.
VI.C.3	VI. Statement of Needs	C. Service-Level Expectations	SLA attachment and/or narrative	Monitor system performance continuously or at intervals approved by Virginia Tech.
VI.C.4	VI. Statement of Needs	C. Service-Level Expectations	Narrative	Provide dashboards, reports, alarms, and trend data sufficient to identify degradation before it materially impacts users.
VI.C.5	VI. Statement of Needs	C. Service-Level Expectations	Narrative	Provide advance notice and obtain Virginia Tech approval for planned maintenance affecting service, except for emergency maintenance necessary to protect life, safety, security, or system integrity.
VI.C.6	VI. Statement of Needs	C. Service-Level Expectations	Narrative	Minimize outages and coordinate maintenance to avoid critical campus events.
VI.C.7	VI. Statement of Needs	C. Service-Level Expectations	SLA attachment and/or narrative	Maintain a documented incident management process, including severity classifications, escalation contacts, response targets, root-cause analysis, and corrective-action tracking.
VI.C.8	VI. Statement of Needs	C. Service-Level Expectations	Narrative	Maintain regular communication with Virginia Tech and establish a cadence for recurring scheduled meetings to discuss progress and coordinate activity.
VI.D.1	VI. Statement of Needs	D. Commercial Management	Narrative	Market the DAS to cellular carriers.
VI.D.2	VI. Statement of Needs	D. Commercial Management	Narrative	Assist Virginia Tech in negotiating carrier participation agreements.
VI.D.3	VI. Statement of Needs	D. Commercial Management	Narrative	Identify new revenue opportunities for Virginia Tech.
VI.D.4	VI. Statement of Needs	D. Commercial Management	Narrative	Administer carrier contracts on behalf of Virginia Tech, as required and allowable.
VI.D.5	VI. Statement of Needs	D. Commercial Management	Narrative	Manage billing and collections with all carriers in accordance with applicable laws and regulations.
VI.E.1.i	VI. Statement of Needs	E. Revenue Generation	Narrative and Financial Model	Offerors may describe opportunities for revenue generation included in their proposal. The RFP document includes a list of suggested revenue generation opportunities by category for reference.
VI.F.1.i	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Replace or modernize aging DAS components and head-end equipment.
VI.F.1.ii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide upgrades required to support current and upcoming cellular carrier technologies.
VI.F.1.iii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Expand spectrum support across participating carriers.
VI.F.1.iv	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide capacity enhancements for high-density venues and special events, prioritizing Lane Stadium capacity as soon as possible.
VI.F.1.v	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Improve backhaul, transport, and related infrastructure.
VI.F.1.vi	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Upgrade software and monitoring platforms.
VI.F.1.vii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide cybersecurity, network resiliency, and redundancy enhancements.
VI.F.1.viii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide infrastructure standardization recommendations to support long-term efficiency.
VI.F.2.i	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Project plan / schedule	Increase node capacity within Lane Stadium no later than July 23, 2027.
VI.F.2.ii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Project plan / schedule	Increase node capacity and coverage within other athletic facilities, arenas, and major event facilities, including Lane Stadium, Cassell Coliseum, Parking Lots 1-5 surrounding Lane Stadium and Cassell Coliseum, Mosley Practice Field, and the six residential dormitory buildings along Washington Street.
VI.F.2.iii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Extend athletic venue coverage and capacity to the field surface, sufficient for commencement, concerts, and games.
VI.F.2.iv	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Support peak attendance demand during athletic events, concerts, commencement ceremonies, and other large gatherings.
VI.F.2.v	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Project plan / schedule	Improve fan connectivity and mobile engagement experiences no later than the start of the Fall 2027 athletic season.
VI.F.2.vi	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Accommodate increased data consumption and carrier spectrum requirements.
VI.F.2.vii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Support venue technologies including mobile ticketing, digital concessions, and cashless operations.
VI.F.2.viii.1	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide metrics for coverage gaps to measure enhanced capacity.
VI.F.2.viii.2	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide metrics for capacity constraints to measure enhanced capacity.
VI.F.2.viii.3	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide metrics for user experience to measure enhanced capacity.
VI.F.2.viii.4	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide metrics for demographic and density demand to measure enhanced capacity.
VI.F.2.ix	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Exhibit / technical attachment	Provide a cellular coverage heatmap demonstrating improved signal coverage for all outdoor areas of the stadium and improved signal coverage and call quality for all users in the facility.
VI.F.2.x	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Enhance capacity to ensure upload and download speed of up to 25 MBs for all users.
VI.F.3.i	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe 5G Advanced deployment support.
VI.F.3.ii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe future 6G, 7G, and C-Band overlay readiness planning.
VI.F.3.iii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe CBRS and private wireless network integration.
VI.F.3.iv	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe IoT applications.
VI.F.3.v	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe smart campus and smart venue initiatives.
VI.F.3.vi	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe public safety interoperability requirements.
VI.F.3.vii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative / roadmap	Describe emerging technologies not currently deployed.
VI.F.4.i	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Identify current system deficiencies and phased opportunities for improvement.
VI.F.4.ii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Capital improvement and modernization plan	Recommend a timeline of upgrades for the first year, first three years, and first five-year contract term; if a different term structure is recommended, propose two upgrade timelines.
VI.F.4.iii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Capital improvement and modernization plan	Provide long-term modernization plan covering at minimum 10 years of partnership.
VI.F.4.iv	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Capital improvement and modernization plan	State estimated capital investment commitments.
VI.F.4.v	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Capital improvement and modernization plan	Provide proposed funding mechanisms, with a strong preference for continuing carrier-paid infrastructure requirements.
VI.F.4.vi	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Capital improvement and modernization plan	Provide anticipated performance improvements and return-on-investment figures for improvements.
VI.F.4.vii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Describe any additional impacts on revenue generation and carrier participation.
VI.F.5.i	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide technology refresh cycles.
VI.F.5.ii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide equipment replacement standards.
VI.F.5.iii	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide capacity upgrade triggers.
VI.F.5.iv	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide performance thresholds aligned with modernization requirements.
VI.F.5.v	VI. Statement of Needs	F. Capital Improvements and DAS Modernization	Narrative	Provide processes for nimble and low-cost adoption of future wireless technologies.
VI.G.1.i	VI. Statement of Needs	G. Partnership Structure	Acknowledge / describe alignment	Virginia Tech retains ownership of the DAS infrastructure.
VI.G.1.ii	VI. Statement of Needs	G. Partnership Structure	Describe approach	Offeror assumes responsibility for operations, maintenance, modernization, carrier relations, and commercialization activities, subject to final oversight from Virginia Tech.
VI.G.1.iii	VI. Statement of Needs	G. Partnership Structure	Pricing / fee schedule	If applicable, provide annual management or operating fee structure payable to Offeror.
VI.G.1.iv	VI. Statement of Needs	G. Partnership Structure	Financial model	Provide revenue-sharing arrangement based on gross or net DAS revenues, including carrier participation agreements, new carrier onboarding, spectrum expansion initiatives, infrastructure licensing, etc.
VI.G.1.v	VI. Statement of Needs	G. Partnership Structure	Financial model	Provide minimum annual revenue guarantee payable to Virginia Tech.
VI.G.1.vi	VI. Statement of Needs	G. Partnership Structure	Financial model	Provide revenue-sharing percentages based on revenue growth thresholds.
VI.G.1.vii	VI. Statement of Needs	G. Partnership Structure	Financial model	Provide partner-funded capital investment and modernization commitments.
VI.G.1.viii	VI. Statement of Needs	G. Partnership Structure	Financial model	Provide performance incentives tied to carrier growth, revenue growth, and network modernization objectives.
VI.G.2.i	VI. Statement of Needs	G. Partnership Structure	Acknowledge / describe alignment	Virginia Tech retains ownership of the DAS assets.
VI.G.2.ii	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a long-term concession, Virginia Tech grants the Offeror exclusive rights to operate, manage, modernize, and commercialize the DAS infrastructure for a term.
VI.G.2.iii	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide upfront concession payment to Virginia Tech.
VI.G.2.iv	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide fixed annual concession payments across the term.
VI.G.2.v	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide minimum annual guaranteed revenue commitments.
VI.G.2.vi	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide revenue-sharing arrangement above established revenue thresholds.
VI.G.2.vii	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide capital investment commitments over the term of the agreement.
VI.G.2.viii	VI. Statement of Needs	G. Partnership Structure	Plan / schedule	If proposing a long-term concession, provide funding and schedule for technology refreshes and modernization initiatives.
VI.G.2.ix	VI. Statement of Needs	G. Partnership Structure	Financial model	If proposing a long-term concession, provide increasing payment schedules tied to inflation, carrier growth, or revenue performance.
VI.G.3.i	VI. Statement of Needs	G. Partnership Structure	Acknowledge / describe alignment	Virginia Tech retains ownership of the DAS assets.
VI.G.3.ii	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, Virginia Tech grants the right to commercialize the DAS infrastructure, excluding conduit or network pathways, to the Offeror.
VI.G.3.iii	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, Offeror assumes responsibility for operations, maintenance, carrier engagement, and growth initiatives, with oversight from Virginia Tech.
VI.G.3.iv	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, provide annual lease payments payable to Virginia Tech.
VI.G.3.v	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, provide guaranteed minimum annual payments.
VI.G.3.vi	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, provide revenue-sharing arrangement based on gross or net revenues from DAS operations, carrier access agreements, infrastructure licensing, fiber/transport services, colocation, emerging wireless technology, and event-related wireless services.
VI.G.3.vii	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, provide capital investment commitments associated with modernization and expansion.
VI.G.3.viii	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing a lease/commercialization model, provide periodic financial true-up mechanisms to ensure equitable revenue allocation.
VI.G.4.i	VI. Statement of Needs	G. Partnership Structure	Describe only if model proposed	If proposing an alternative partnership structure, clearly describe ownership and governance framework.
VI.G.4.ii	VI. Statement of Needs	G. Partnership Structure	Narrative and Financial Model	If proposing an alternative partnership structure, clearly describe risk and responsibility allocation.
VI.G.4.iii	VI. Statement of Needs	G. Partnership Structure	Narrative and Financial Model	If proposing an alternative partnership structure, clearly describe revenue-generation strategy.
VI.G.4.iv	VI. Statement of Needs	G. Partnership Structure	Narrative and Financial Model	If proposing an alternative partnership structure, clearly describe capital investment commitments.
VI.G.4.v	VI. Statement of Needs	G. Partnership Structure	Narrative and Financial Model	If proposing an alternative partnership structure, clearly describe financial protections for Virginia Tech.
VI.G.4.vi	VI. Statement of Needs	G. Partnership Structure	Narrative and Financial Model	If proposing an alternative partnership structure, clearly describe expected financial and revenue returns over the life of the agreement.
VI.H.1.i	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Provide total projected financial value to the University over the contract term.
VI.H.1.ii	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	If applicable, provide proposed upfront payments.
VI.H.1.iii	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Provide annual guaranteed payments.
VI.H.1.iv	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Provide minimum revenue guarantees.
VI.H.1.v	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Provide revenue-sharing methodology and percentages.
VI.H.1.vi	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Provide capital investment commitments.
VI.H.1.vii	VI. Statement of Needs	H. Financial and Revenue Model	Capital improvement and modernization plan	Provide technology modernization commitments.
VI.H.1.viii	VI. Statement of Needs	H. Financial and Revenue Model	Operating model	Define operating and maintenance responsibilities.
VI.H.1.ix	VI. Statement of Needs	H. Financial and Revenue Model	Narrative and Financial Model	Provide financial reporting and audit provisions.
VI.H.1.x	VI. Statement of Needs	H. Financial and Revenue Model	Financial model assumptions	If applicable, provide assumptions supporting projected financial performance.
VI.H.2.i	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Identify revenue sharing percentage for carrier revenues.
VI.H.2.ii	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Identify revenue sharing percentage for lease revenues.
VI.H.2.iii	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Identify revenue sharing percentage for infrastructure fees.
VI.H.2.iv	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Identify revenue sharing percentage for new commercial services.
VI.H.2.v	VI. Statement of Needs	H. Financial and Revenue Model	Financial model	Identify revenue sharing percentage for event-related services.
VI.H.3.i	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include guaranteed annual payment in the 20-year financial model.
VI.H.3.ii	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include revenue share waterfall in the 20-year financial model.
VI.H.3.iii	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include carrier growth assumptions in the 20-year financial model.
VI.H.3.iv	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include capital growth assumptions in the 20-year financial model.
VI.H.3.v	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include capital investment schedule in the 20-year financial model.
VI.H.3.vi	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include NPV to the University in the 20-year financial model.
VI.H.3.vii	VI. Statement of Needs	H. Financial and Revenue Model	20-year model	Include sensitivity analysis for additional carriers, spectrum additions, and major venue expansions in the 20-year financial model.
VI.I.1.i	VI. Statement of Needs	I. Venue Requirements	Narrative	Address high-density event coverage across athletic venues, with particular attention to Lane Stadium.
VI.I.1.ii	VI. Statement of Needs	I. Venue Requirements	Narrative	Address peak attendance network coverage across athletic venues, with particular attention to Lane Stadium.
VI.I.1.iii	VI. Statement of Needs	I. Venue Requirements	Narrative	Address capacity planning across athletic venues, with particular attention to Lane Stadium.
VI.I.1.iv.1	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the third floor academics level.
VI.I.1.iv.2	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the fourth floor University Club / President’s Suite.
VI.I.1.iv.3	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the fourth and sixth West Indoor Club Spaces.
VI.I.1.iv.4	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the fifth floor press box.
VI.I.1.iv.5	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the seventh floor operations and stadium command level.
VI.I.1.iv.6	VI. Statement of Needs	I. Venue Requirements	Narrative	Address premium seating and suite-level connectivity for the third floor South Endzone Indoor Club Level.
VI.I.1.v	VI. Statement of Needs	I. Venue Requirements	Narrative	Address coverage enhancements across athletic venues.
VI.I.1.vi	VI. Statement of Needs	I. Venue Requirements	Narrative	Address event-day operations across athletic venues.
VI.I.2	VI. Statement of Needs	I. Venue Requirements	Plan / schedule	Submit specific, timebound plans for meaningful connectivity enhancements to Lane Stadium ahead of the Fall 2027 athletics season.
VI.I.3.i	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Cassell Coliseum as another key venue on campus.
VI.I.3.ii	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Miles Hall as another key venue on campus.
VI.I.3.iii	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Ambler Johnston Hall as another key venue on campus.
VI.I.3.iv	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Cochrane Hall as another key venue on campus.
VI.I.3.v	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Harper Hall as another key venue on campus.
VI.I.3.vi	VI. Statement of Needs	I. Venue Requirements	Narrative	Address New Hall West as another key venue on campus.
VI.I.3.vii	VI. Statement of Needs	I. Venue Requirements	Narrative	Address Pritchard Hall as another key venue on campus.
VI.I.3.viii	VI. Statement of Needs	I. Venue Requirements	Optional	Address Burruss Hall as another key venue on campus.
VI.I.3.ix	VI. Statement of Needs	I. Venue Requirements	Optional	Address Holtzman Alumni Center as another key venue on campus.
VI.I.3.x	VI. Statement of Needs	I. Venue Requirements	Optional	Address Center for the Arts as another key venue on campus.
VI.I.4.i	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support mobile ticketing.
VI.I.4.ii	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support mobile concessions.
VI.I.4.iii	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support fan engagement.
VI.I.4.iv	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support sponsorship activations.
VI.I.4.v	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support digital advertising opportunities.
VI.I.4.vi	VI. Statement of Needs	I. Venue Requirements	Narrative	Describe how improved connectivity and infrastructure support sports wagering compliance, if applicable and where permitted.
VI.J.1.i	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for network operations.
VI.J.1.ii	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for maintenance and incidents.
VI.J.1.iii	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for assets and modernization.
VI.J.1.iv	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for carrier relations.
VI.J.1.v	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for revenue and financial performance.
VI.J.1.vi	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for venue connectivity.
VI.J.1.vii	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for technology and resiliency.
VI.J.1.viii	VI. Statement of Needs	J. Key Performance Indicators (KPI)	KPI	Propose KPI targets for strategic value.
VI.J.2	VI. Statement of Needs	J. Key Performance Indicators (KPI)	Narrative	Ensure KPIs are measurable and, where possible, reportable by venue, carrier, technology, event, and timeframe.
VI.J.3	VI. Statement of Needs	J. Key Performance Indicators (KPI)	Acknowledge / describe approach	Acknowledge that repeated or material failure to meet KPIs may result in performance remedies, penalties, and/or breach.
VI.K.1.i	VI. Statement of Needs	K. Performance Management and Reporting	Acknowledge / describe approach	Within 60 days of contract execution, submit a Performance Management Plan identifying KPIs, definitions, calculation methods, data sources, targets, and reporting frequency.
VI.K.1.ii	VI. Statement of Needs	K. Performance Management and Reporting	Acknowledge / describe approach	Within 60 days of contract execution, submit baseline performance and proposed service levels.
VI.K.1.iii	VI. Statement of Needs	K. Performance Management and Reporting	Acknowledge / describe approach	Within 60 days of contract execution, submit responsibilities for data collection, review meetings, and escalation procedures.
VI.K.1.iv	VI. Statement of Needs	K. Performance Management and Reporting	Acknowledge / describe approach	Within 60 days of contract execution, submit processes for identifying risks, addressing missed targets, and updating KPIs as requirements evolve.
VI.K.2.i.1	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide monthly operations reports including network availability and performance by venue and carrier; outages and service degradation; capacity and utilization; incidents and response times; preventive and corrective maintenance; recurring faults; asset condition and lifecycle risks; cybersecurity and resiliency issues; and recommended corrective actions.
VI.K.2.i.2	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide monthly revenue reports including revenue by category; billing, collections, receivables, and disputes; revenue sharing calculations; and results to date compared with minimum commitments, guarantees, and incentives.
VI.K.2.ii.1	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide quarterly commercial and revenue reports summarizing monthly revenue reports, carrier participation and onboarding activity, upcoming agreements and renewals, new revenue opportunities, venue commercialization, and risks impacting carrier growth or financial performance.
VI.K.2.ii.2	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide quarterly capital and modernization reports covering progress against plans, expenditures and forecasts, project schedule/budget/risks, capacity and spectrum upgrades, improvements to head-end/backhaul/transport/monitoring/cybersecurity/resiliency, Lane Stadium and other high-priority venue projects, technology-readiness activities, and updated ROI projections.
VI.K.2.iii.1	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide event and venue reports within 10 business days after major athletic events, concerts, commencement, or other high-density events.
VI.K.2.iii.1.a	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include attendance report in event and venue reports.
VI.K.2.iii.1.b	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include peak demand data in event and venue reports.
VI.K.2.iii.1.c	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include network availability in event and venue reports.
VI.K.2.iii.1.d	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include capacity in event and venue reports.
VI.K.2.iii.1.e	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include utilization in event and venue reports.
VI.K.2.iii.1.f	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include congestion in event and venue reports.
VI.K.2.iii.1.g	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include service in event and venue reports.
VI.K.2.iii.1.h	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include incidents in event and venue reports.
VI.K.2.iii.1.i	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include digital service impacts in event and venue reports.
VI.K.2.iii.1.j	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Include recommended improvements in event and venue reports.
VI.K.2.iii.2	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Ensure all reports are comprehensive and configurable per carrier.
VI.K.2.iii.3	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Ensure event and venue reports address mobile ticketing, mobile concessions, cashless operations, fan engagement, premium areas, and other applicable in-place venue services.
VI.K.2.iii.4	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Deliver an annual strategic report summarizing performance against contractual commitments, financial results and total value delivered, carrier/revenue/utilization/capital trends, modernization and technology-refresh status, updated long-term financial model, and recommended priorities for the following year.
VI.K.2.iii.5	VI. Statement of Needs	K. Performance Management and Reporting	Reporting commitment	Provide the annual strategic report no later than July 15 of every fiscal year.
VI.L.1	VI. Statement of Needs	L. DAS Access	Narrative	Ensure the DAS is available to all major national wireless carriers on commercially reasonable, transparent, and non-discriminatory terms.
VI.L.2	VI. Statement of Needs	L. DAS Access	Narrative	Apply carrier onboarding, pricing, technical requirements, service levels, capacity allocations, upgrade opportunities, and operating requirements consistently, subject only to documented technical differences approved in writing by Virginia Tech.
VI.L.3	VI. Statement of Needs	L. DAS Access	Narrative	Provide Virginia Tech regular reporting to verify equitable carrier participation and system treatment, including carrier participation reports, pricing schedules, capacity allocations, and service records upon request.
VI.M.1.i	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over physical DAS equipment and related infrastructure located on or serving Virginia Tech property.
VI.M.1.ii	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over real estate rights-of-way, easements, licenses, pathways, rooftops, utility spaces, and other access rights.
VI.M.1.iii	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over approval of locations, installation methods, equipment standards, and site access.
VI.M.1.iv	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over vendor and subcontractor oversight.
VI.M.1.v	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over system governance and carrier participation decisions.
VI.M.1.vi	VI. Statement of Needs	M. Relationship with Virginia Tech	Acknowledge / governance	Acknowledge Virginia Tech's ultimate authority over future infrastructure expansion, relocation, replacement, modernization, or decommissioning decisions.
VI.M.2	VI. Statement of Needs	M. Relationship with Virginia Tech	Narrative	Do not restrict or meter Virginia Tech’s direct communications, audits, or oversight regarding carrier relationships and overall system governance.
VI.M.3	VI. Statement of Needs	M. Relationship with Virginia Tech	Narrative	Acknowledge that Offeror receives only limited, non-exclusive, revocable rights expressly granted in the final contract and no transfer of Virginia Tech ownership interests.
VI.M.4	VI. Statement of Needs	M. Relationship with Virginia Tech	Narrative	Do not sell, assign, pledge, encumber, relocate, remove, abandon, or materially modify any DAS asset or university access right without Virginia Tech’s prior written approval.
VI.N.1	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Narrative	Operate the DAS to provide reliable coverage, capacity, resilience, and service continuity throughout the covered locations and venues.
VI.N.2	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Narrative	Use a carrier-agnostic, scalable, interoperable technical architecture capable of supporting current and future wireless technologies, subject to regulatory, engineering, and security requirements.
VI.N.3	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Narrative	Design the DAS to support advanced academic, research, instructional, public-safety, and innovation initiatives while complying with Virginia Tech policies and approved technical standards.
VI.N.4.i	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for radio-frequency design documents and coverage predictions.
VI.N.4.ii	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for capacity models and assumptions.
VI.N.4.iii	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for equipment specifications and bills of materials.
VI.N.4.iv	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for fiber, backhaul, power, grounding, and redundancy designs.
VI.N.4.v	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for integration and interoperability plans.
VI.N.4.vi	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for cybersecurity and access-control architecture.
VI.N.4.vii	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for maintenance, monitoring, and incident-response procedures.
VI.N.4.viii	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Acknowledge / governance	Obtain Virginia Tech written approval for testing, acceptance, and documentation plans.
VI.N.5	VI. Statement of Needs	N. Design, Engineering, and Technical Requirements	Narrative	Do not implement any material design, configuration, software, equipment, or topology change without approvals required in the final contract.
VI.O.1	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Design, operate, and maintain the DAS to fully support emergency communications and public safety.
VI.O.2	VI. Statement of Needs	O. Public Safety and Emergency Communications	Acknowledge / governance	Do not configure or operate the DAS in a manner that prevents any person on Virginia Tech’s campus from dialing emergency services due to their mobile or cellular provider.
VI.O.3	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Support Virginia Tech and local authorities in distributing critical cellular alerts, including severe weather warnings, active shooter warnings, evacuation notices, and other emergency messages.
VI.O.4	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Coordinate emergency testing and incident response with Virginia Tech and, where requested, relevant public safety stakeholders.
VI.O.5	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Notify Virginia Tech immediately of any emergency-impacting incidents.
VI.O.6	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Recognize that campus emergencies may involve multiple public safety agencies whose personnel may use different cellular carriers.
VI.O.7	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Support reliable in-building cellular communications for responding personnel, subject to each agency’s devices, plans, network availability, and lawful operating requirements.
VI.O.8	VI. Statement of Needs	O. Public Safety and Emergency Communications	Narrative	Improve users’ ability on participating national carriers to place emergency calls from supported locations and venues, including hard-to-reach indoor locations.

File details come from the government source that posted it. Updated Oct 28, 2026.