Scope matrix
Four workstreams to check for a project in Saadiyat Grove.
For Saadiyat Grove, this planning route connects Network architecture, Surveillance design, AMC coverage 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.
01Network architecture
Document switch capacity, uplinks, internet handoff, VLANs, wireless coverage, critical applications and the devices that must remain reachable during change. A useful network scope separates coverage problems from capacity problems and identifies whether the requirement is a new deployment, expansion, refresh or fault-remediation project. Continuity readiness: Record current backups, rollback options, communication needs and the safest sequence of changes so business-critical services remain protected during implementation.
Review enterprise networking →02Surveillance design
Define camera purpose, field of view, recording duration, storage, monitoring points, network connectivity, power, access permissions and evidence-retention expectations. The design should distinguish operational visibility from security monitoring and state who will review footage, manage user access and maintain the recording platform after handover. Commercial readiness: Confirm quantities, preferred brands or acceptable alternatives, warranty expectation, quotation format and target delivery window before commercial comparison begins.
Review cctv & surveillance →03AMC coverage
List covered systems, sites, business hours, preventive tasks, remote and onsite expectations, exclusions, escalation contacts and parts or vendor dependencies. Maintenance coverage works best when asset ownership and response expectations are explicit, allowing routine checks and incident handling to follow the same documented service model. 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 managed it & amc →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. 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 automation →