GCC Build OSv0
/api

Network & Topologyit.network_topology

P1 owner role: ProgrammeLead display order 4

Asset-level counts per location (switches, routers, firewalls, APs), interconnect model, ISPs, SD-WAN posture, OT segmentation. Builds the global topology view.

Questions (17)

id prompt scope category priority artefact
it.network_topology.q01 Per subsidiary: complete site list (HQ, branches, yards, plants, project sites). For each: country, city, headcount, square footage, business criticality. S Sites P0 table
it.network_topology.q02 Per site: count of switches, routers, firewalls, wireless APs, IP phones. Vendor and model where known. S Asset Counts P0 table
it.network_topology.q03 Per site: end-of-life / end-of-support network hardware. Refresh schedule and budget. S Asset Counts P1 table
it.network_topology.q04 Per site: ISP, bandwidth, contract end date, redundancy (dual ILL / 4G/5G failover / none). S Internet / ILL P0 table
it.network_topology.q05 Inter-office connectivity — MPLS / SD-WAN / IPSec VPN / public internet. Vendor and topology diagram if available. S Interconnect P0 table
it.network_topology.q06 Group-level SD-WAN posture — does one exist? If yes, vendor (Cisco/Versa/Fortinet/Cato/Aruba). If no, intent to adopt? G WAN Strategy P0 checklist
it.network_topology.q07 Per site: Wi-Fi vendor (Cisco Meraki / Aruba / Ubiquiti / Mist / other), generation (Wi-Fi 5/6/6E), coverage % of building, guest network model. S Wi-Fi & LAN P1 table
it.network_topology.q08 Voice platform — on-prem PBX (Avaya/Cisco), cloud telephony (Teams Phone / Zoom Phone / Webex), or none. DID counts per site. S Voice P1 table
it.network_topology.q09 For industrial / plant-heavy entities: OT network segmentation status, SCADA/DCS systems, IT-OT boundary controls, Purdue model adherence. S OT / Plant Networks P0 text
it.network_topology.q10 Does a current network topology diagram exist at group level? Last updated when? Discovery/mapping tooling in use (e.g., Lansweeper, Auvik, SolarWinds)? G Topology Visibility P0 file
it.network_topology.q11 How are temporary or project sites typically onboarded from an IT perspective today? Process, lead time, owner, last example. S Field / Project Sites P0 text
it.network_topology.q12 How is connectivity managed at remote or temporary locations — cellular, microwave, VSAT, public Wi-Fi, fibre, leased line? Typical mix. S Field / Project Sites P0 table
it.network_topology.q13 Are there operational challenges related to remote-site support (latency, reliability, response time, OT integration)? Recent examples. S Field / Project Sites P0 text
it.network_topology.q14 How are field devices and endpoints managed today — MDM enrolment, ruggedised hardware standard, BYOD posture, lifecycle? S Field / Project Sites P0 text
it.network_topology.q15 Are remote / project locations included in centralised monitoring or support processes? Coverage % and known blind-spots. S Field / Project Sites P0 text
it.network_topology.q16 Are there bandwidth or connectivity limitations affecting operations? Per-site bandwidth and the apps most affected. S Field / Project Sites P1 text
it.network_topology.q17 How are contractors or temporary users typically granted access — provisioning workflow, MFA, time-bound, deprovisioning trigger? S Field / Project Sites P0 text

Decisions related to this workstream (0)

No decisions in this pack are linked to this workstream.