Scope matrix
Four workstreams to check for a project in City Walk.
For City Walk, this planning route connects Security controls, Voice and communications, Access and attendance and automation and control. It is not a fixed package: the final quotation follows the real site, users, existing systems, access constraints, timing and support responsibility.
01Security controls
Map internet exposure, user groups, privileged access, endpoints, remote access, firewall policy, logging and the systems that would create the highest business impact if unavailable. The scope should connect preventive controls with monitoring, incident response and ownership instead of buying independent security products without an operating model. Handover readiness: Define the diagrams, configuration records, asset list, warranty documents, test evidence and credential-transfer method required at completion.
Review cybersecurity →02Voice and communications
Record extensions, users, call flows, numbers, trunks, handsets, conferencing needs, remote users, network quality and any contact-centre or recording requirements. Voice systems depend on network, power and support processes, so the scope should include those dependencies as well as the telephony platform itself. Continuity readiness: Record current backups, rollback options, communication needs and the safest sequence of changes so business-critical services remain protected during implementation.
Review voip & communications →03Access and attendance
Identify doors or controlled points, user groups, credentials, attendance reporting, controller topology, network connectivity, power, emergency behavior, integration needs and administrator roles. The scope should explain how users are enrolled, who can change permissions and how access records will be retained and supported. Commercial readiness: Confirm quantities, preferred brands or acceptable alternatives, warranty expectation, quotation format and target delivery window before commercial comparison begins.
Review access control →04Automation and control
Describe the process to automate, users, sensors or endpoints, control interfaces, schedules, integrations, fail-safe behavior and manual override. Automation should make an operating process simpler and more observable; the scope therefore needs both the desired outcome and the technical systems that must exchange data or commands. 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 automation →