Documentation
Getting started: week 0 to week 1
What happens between kickoff and the Network Context Report, and what your team prepares.
Prerequisites checklist
| Item | Owner | Needed by |
|---|---|---|
| Deployment model chosen (SaaS today; Customer Cloud or On-Prem by arrangement) and region | Customer architect + REAP | Week 0 |
| Connector cluster VMs provisioned (see sizing) | Customer infrastructure | Day 1 |
| Network requirements approved (see firewall rules) | Customer network / security | Day 1 |
| Read-only device credentials, brokered through PAM where available | Customer network + PAM admin | Day 1 |
| ITSM integration user with the permissions in the ServiceNow or Jira page | ITSM admin | Day 2 |
| One telemetry source connected (native syslog, SNMP or gNMI (opens in a new tab), plus flow records where you configure them; SolarWinds (opens in a new tab) and Zabbix (opens in a new tab) connectors are planned, not available today) | Customer network | Day 3 |
| Runbooks, design documents and naming conventions shared (files or agreed exports; Confluence (opens in a new tab) and SharePoint (opens in a new tab) connectors are planned, not available today) | Customer network | Day 3 |
| SSO application registered (Okta (opens in a new tab) or Microsoft Entra ID (opens in a new tab)) | Identity admin | Day 3 |
| Week-0 data request fulfilled (tickets, configs, topology, runbooks, audit scope) | Champion | Week 0 |
Day-by-day, week 1
| Day | Activity | Output |
|---|---|---|
| 1 | Connector cluster deployed; outbound connectivity verified; credential broker tested | Connectors online in the console |
| 2 | Discovery of the in-scope domain; ITSM connected | Device inventory; first tickets visible |
| 3 | Topology built (L2/L3, paths); configuration history ingestion starts; telemetry flowing | Topology map; configuration baseline |
| 4 | Organizational context ingested (runbooks, designs, conventions); SSO live; roles mapped | Context sources listed with timestamps |
| 5–7 | Validation with the customer architect: device coverage, topology accuracy, integration health | Network Context Report (≥95% discovered · ≥90% topology accuracy · ITSM and telemetry live) |
Who needs access
- Champion / NOC lead: console access, investigation review, runbook approvals.
- Network architect: findings review (week 3), topology validation.
- Security reviewer: security packet, audit export, access review.
- Economic buyer · business review (week 6) only.
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai