Scope matrix
Four workstreams to check for a project in The Valley.
For The Valley, this planning route connects Business computing, Virtualization planning, Support and troubleshooting and meeting-room and av. It is not a fixed package: the final quotation follows the real site, users, existing systems, access constraints, timing and support responsibility.
01Business computing
List user roles, required applications, processor and memory needs, display setup, mobility, docking, warranty expectations, operating-system requirements and lifecycle timing. This keeps device sourcing tied to real workloads and makes it easier to compare current models, approved alternatives and selected pre-owned options where appropriate. Commercial readiness: Confirm quantities, preferred brands or acceptable alternatives, warranty expectation, quotation format and target delivery window before commercial comparison begins.
Review business computing →02Virtualization planning
Document host resources, virtual-machine count, utilization, storage, network design, licensing, backup integration, high availability and growth headroom. A virtualization project should include migration sequence, rollback, monitoring and handover so consolidation improves manageability rather than creating a new unsupported layer. Support readiness: Identify critical services, business hours, escalation contacts, remote-access policy and the systems that require preventive or recurring support after go-live.
Review virtualization →03Support and troubleshooting
Describe the symptoms, affected users or systems, frequency, recent changes, available logs, business impact and what has already been tested. A structured support brief reduces repeated diagnosis and helps determine whether the next action is remote troubleshooting, onsite inspection, configuration change, replacement hardware or a wider redesign. Measurement readiness: Choose a practical post-go-live baseline such as stability, coverage, backup success, utilization, incident volume or user adoption so the result can be verified.
Review technical support →04Meeting-room and AV
Define room purpose, participant count, display size, camera framing, microphone coverage, speakers, conferencing platform, room control, content sharing and support expectations. The design should be based on how meetings are run and who supports the room, not a list of disconnected AV devices. Implementation readiness: Confirm exact site, access rules, change window, dependencies, responsible contacts and acceptance criteria before engineers or equipment are scheduled.
Review meeting room & av →