Sheet SYN-01 — Network Operations Manual
Fleet, Integrations & Sites
Vendor integrations through the plugin bridge, the normalized cross-vendor inventory, and the site mapping that anchors everything else.
What this area covers
Everything in Synapse rests on an inventory the team can trust. This area covers how vendor platforms connect through the plugin bridge, how devices from every vendor land on one normalized schema, and how vendor networks get mapped to the physical sites operators actually reason about.
Operational areas in scope
| Area | What operators need from it | Why it matters |
|---|---|---|
| Vendor integrations | Cloud vendor platforms connected through the plugin bridge, with vendors such as Cisco Meraki, Fortinet, and Palo Alto as examples | A multi-vendor estate needs one operating surface, not one console per vendor |
| Sync lifecycle | Scheduled sync on a configurable cadence, plus an on-demand sync with per-step status | Inventory is only useful when the team knows how fresh it is and what failed |
| Normalized fleet | Serial, model, firmware, product type, and brand on one schema regardless of vendor | Cross-vendor questions cannot be answered from vendor-shaped data |
| Staleness | Devices the latest successful sync did not see flagged as stale, never silently deleted | What fell off the map is a finding, not something to hide |
| Sites and labels | Tenant-defined sites with region, country, and arbitrary labels | Policy scope, scoring rollups, and traffic views all resolve through sites |
| Mapping review | A queue where operators confirm which vendor network belongs to which site | Device-to-site truth is confirmed by a person, never guessed silently |
What operators are actually managing
- Connect each vendor account once, with credentials encrypted at rest and never shown again.
- Set a sync cadence that matches how fast the estate changes, and sync on demand when it matters now.
- Review sync runs step by step when an integration reports a partial or failed outcome.
- Work the mapping review queue until every vendor network is confirmed against a real site.
- Watch the stale filter for devices that stopped appearing in syncs.
What this public manual area includes
- Integrations and the plugin bridge, including the schema-driven add wizard.
- The fleet inventory list, its filters, and the lifecycle rollup.
- Sites, labels, and the network mapping review workflow.
What healthy operation looks like
- Every vendor account the team owns is connected and syncing on a known cadence.
- The mapping review queue is empty, so every device resolves to a site.
- Stale devices get investigated, not ignored.
- Nobody opens a vendor console to answer an inventory question.